dbcve.org
Lsfusion PlatformApplication · Lsfusion

CVE-2025-13262

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-17
Fix available
A fix is available. Upgrade to after 6.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in lsfusion platform up to 6.1. Affected by this vulnerability is the function UploadFileRequestHandler of the file platform/web-client/src/main/java/lsfusion/http/controller/file/UploadFileRequestHandler.java. Executing manipulation of the argument sid can lead to path traversal. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability exists in lsfusion platform's UploadFileRequestHandler component. The 'sid' parameter in the file upload function is not properly validated, allowing attackers to manipulate the parameter to access files outside the intended directory through directory traversal sequences (e.g., ../../../). This remote vulnerability in the web client component affects all versions up to 6.1.

MitigationImplement strict input validation on the 'sid' parameter to reject path traversal characters and sanitize all file paths to ensure they resolve within the intended upload directory. Consider using canonical path resolution and implementing an allowlist of permitted characters/patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Lsfusion PlatformApplication
Affected:<= 6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Lsfusion Platform is running
    Locate running Java processes or services associated with Lsfusion, check for web application servers (Tomcat, Jetty) hosting Lsfusion applications, or review network listeners on common web ports (8080, 8443).
    Affected if Lsfusion Platform is actively running as a web application
  2. Determine the installed Lsfusion version
    Check the Lsfusion installation directory for version manifests, README files, or admin interface 'About' section. Common paths include the root installation folder or WEB-INF/lib directory of the deployed application.
    Affected if The installed version is Lsfusion Platform at version 6.1 or lower
  3. Verify UploadFileRequestHandler is exposed
    Identify the web endpoint path for file upload functionality. The handler typically responds to requests under the application's upload or file API paths. Check application routing configuration or web.xml for UploadFileRequestHandler mappings.
    Affected if UploadFileRequestHandler is accessible via HTTP/HTTPS endpoints
  4. Test sid parameter for path traversal vulnerability
    Send a crafted HTTP request to the UploadFileRequestHandler endpoint with a sid parameter containing directory traversal sequences (e.g., sid=../../../../etc/passwd or sid=../../../config.xml) and observe if the response returns file contents or reveals file paths.
    Affected if The sid parameter accepts and processes path traversal sequences, allowing arbitrary file access

A user is affected if Lsfusion Platform version 6.1 or lower is running with the UploadFileRequestHandler exposed and the sid parameter accepts path traversal sequences.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 6.1
Interim mitigation

Implement strict input validation on the 'sid' parameter to reject path traversal characters and sanitize all file paths to ensure they resolve within the intended upload directory. Consider using canonical path resolution and implementing an allowlist of permitted characters/patterns.

Fix this in Lsfusion Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13262 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data