CVE-2025-11336: Four-Faith Water Conservancy Informatization Platform · Path Traversal
Affects Four-Faith Water Conservancy Informatization PlatformSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Four-Faith Water Conservancy Informatization Platform | Affected
| Fixed in– |
AI-suggested
1. Immediately restrict external access to the affected endpoints (/stAlarmConfigure/index.do, /aloneReport/download.do, otherlogout.do) via network controls such as firewalls or web application firewalls (WAFs). 2. Implement strict input validation and sanitization on the 'fileName' parameter to prevent directory traversal characters (e.g., '../'). 3. Employ least privilege principles on the file system to limit the files accessible by the application process, ensuring sensitive files are not readable by the web server. 4. Monitor server logs and network traffic for unusual access patterns or attempts to exploit path traversal. 5. If possible, isolate the affected platform in a segmented network zone to reduce exposure. 6. Engage with Four-Faith or third-party security experts to develop or apply patches or workarounds. 7. Conduct regular security assessments and penetration tests focusing on web application vulnerabilities. 8. Prepare incident response plans specific to water infrastructure to quickly address potential breaches. 9. Educate operational staff about the risks and signs of exploitation attempts. 10. Consider deploying runtime application self-protection (RASP) tools to detect and block exploitation attempts in real time.
Description
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.