CVE-2025-13262
7.3lsfusion · platform
A path traversal vulnerability in the lsfusion platform allows remote attackers to manipulate the sid argument in the UploadFileRequestHandler to access unauthorized files.
Executive summary
The lsfusion platform contains a path traversal vulnerability that permits remote, unauthenticated attackers to access system files, posing a significant risk to data confidentiality.
Vulnerability
This vulnerability is a path traversal flaw (CWE-22) located in the UploadFileRequestHandler function within the platform web-client module. An unauthenticated attacker can exploit this remotely by supplying malicious input to the sid parameter.
Business impact
The ability to perform path traversal allows unauthorized actors to read sensitive configuration files or system data, potentially leading to full system compromise or information disclosure. With a CVSS score of 7.3, this high-severity vulnerability requires immediate attention to prevent unauthorized access to sensitive business information stored on the server.
Remediation
Immediate Action: As no official patch is currently listed, administrators should restrict network access to the affected web-client interface and monitor the platform for any suspicious file access requests.
Proactive Monitoring: Review application access logs for unusual patterns in the sid argument, specifically looking for directory traversal sequences such as double dots or encoded path separators.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block requests containing directory traversal sequences directed at the UploadFileRequestHandler endpoint.
Exploitation status
Public Exploit Available: Yes, a published proof-of-concept exists (referenced in the GitHub issue linked in the vulnerability documentation).
Analyst recommendation
Given the availability of a public proof-of-concept and the ease of remote exploitation, this vulnerability presents a credible risk to the integrity of the lsfusion platform. Organizations should prioritize implementing defensive filtering at the network perimeter and coordinate with the vendor to monitor for official security updates.
Sources
Originally found and disclosed by R1ckyZ (VulDB User), per the CVE Program record.