Unrestricted File Upload in Sangfor Operation and Maintenance Management System common.jsp
CVE-2025-15503 is an unrestricted file upload vulnerability affecting Sangfor Operation and Maintenance Management System through version 3.0.8. The issue is reported in an unknown function within /fort/trust/version/common/common.jsp, where manipulation of the File argument allows an attacker to upload arbitrary files without adequate validation or restriction. The vulnerability is remotely exploitable. Public reporting indicates that exploit details are available, increasing the likelihood of opportunistic exploitation. Because the vulnerable component appears to be a server-side JSP endpoint, successful upload of attacker-controlled content may enable follow-on compromise depending on how uploaded files are stored and handled by the application server.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
The primary impact is arbitrary file upload to the target system. If uploaded files can be placed in a web-accessible or executable location, an attacker may be able to deploy a webshell and achieve remote code execution on the underlying server. Secondary impacts can include unauthorized modification of application content, persistence, access to sensitive data, lateral movement from the compromised host, and potentially full system takeover depending on the privileges of the application and server configuration.
If you can’t patch tonight, do this now.
Restrict access to /fort/trust/version/common/common.jsp using network controls such as VPN-only exposure, IP allowlisting, reverse-proxy ACLs, or segmentation. Require strong authentication and authorization in front of the endpoint if operationally possible. Deploy WAF or reverse-proxy rules to inspect and block suspicious multipart/form-data requests and abuse of the File parameter. Disable script execution in upload directories, ensure uploaded files are stored outside web-accessible paths, and monitor for newly created or modified files in application directories. Because public exploit information exists, defenders should also review logs for prior access to the vulnerable endpoint and scan for webshell indicators.
Patch, then assume compromise.
Upgrade Sangfor Operation and Maintenance Management System to a vendor-fixed version if one becomes available. If no official patch is available, the vulnerable upload handling in /fort/trust/version/common/common.jsp should be corrected to enforce strict server-side validation of file type, extension, MIME type, content, filename, and destination path; reject dangerous file types; normalize and constrain paths; and store uploaded content outside the web root with non-executable permissions. Review and remove any ability for user-controlled input in the File parameter to influence unsafe upload behavior. Conduct a compromise assessment for unexpected uploaded files, especially JSP or other executable content, and remove any malicious artifacts.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.