dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-11336

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 security vulnerability has been detected in Four-Faith Water Conservancy Informatization Platform up to 2.2. Affected by this issue is some unknown functionality of the file /stAlarmConfigure/index.do/../../aloneReport/download.do;otherlogout.do. Such manipulation of the argument fileName leads to path traversal. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 the Four-Faith Water Conservancy Informatization Platform (versions up to 2.2) within the file download functionality at /aloneReport/download.do. By manipulating the fileName parameter with directory traversal sequences (e.g., ../../), an attacker can access arbitrary files on the server file system, potentially exposing sensitive configuration files, credentials, or application source code.

MitigationImplement strict input validation on the fileName parameter to restrict access to an allowed directory whitelist, use canonical path resolution to verify the final resolved path lies within the intended base directory, and ensure the web application runs with minimal file system permissions.

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

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
Low
Integrity
None
Availability
None

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

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 Four-Faith Water Conservancy Platform installation
    Examine the web application HTTP responses, check for Four-Faith branding in HTML title/meta tags, or inspect installed web application files for this platform's components
    Affected if The platform is deployed and serves HTTP responses identifying it as the Four-Faith Water Conservancy Informatization Platform
  2. Determine installed version
    Check application version information in deployment files, about pages, or HTTP headers/banners; compare against the affected range (up to 2.2)
    Affected if Installed version is 2.2 or lower
  3. Verify vulnerable endpoint exists
    Send an HTTP request to /aloneReport/download.do and observe if the endpoint responds (even with an error)
    Affected if The endpoint returns any application-generated response, indicating it exists and is reachable
  4. Test for path traversal vulnerability
    Send a request to /aloneReport/download.do with a crafted fileName parameter containing directory traversal sequences (e.g., fileName=../../../../etc/passwd or fileName=../../conf/server.xml); inspect the HTTP response for file contents or path errors
    Affected if The application returns file contents from outside the intended download directory, or reveals resolved file paths in error messages
  5. Review web application file system permissions
    Inspect the user context and file permissions under which the web application server runs; check what directories and files are readable by that process
    Affected if The application runs with permissions that allow reading sensitive system files (e.g., configuration files, credentials, source code)

You are affected if the Four-Faith Water Conservancy Informatization Platform version 2.2 or lower is installed, the /aloneReport/download.do endpoint is accessible, and the fileName parameter allows directory traversal to access files outside the intended directory.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the fileName parameter to restrict access to an allowed directory whitelist, use canonical path resolution to verify the final resolved path lies within the intended base directory, and ensure the web application runs with minimal file system permissions.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11336 — 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-11336 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