CVE-2025-65868: eyoucms · n/a
Affects eyoucmsSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Dec 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 |
|---|---|---|
GitHubweng-xianhu/eyoucmspkg:github/weng-xianhu/eyoucmsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately disable XML external entity processing in the XML parsers used by eyoucms, if configurable, to prevent XXE injection. 2. Implement strict input validation and sanitization on all XML inputs, especially POST request bodies. 3. Employ web application firewalls (WAFs) with rules to detect and block malicious XML payloads indicative of XXE attacks. 4. Monitor network traffic for unusual POST requests containing XML data and anomalous spikes in resource usage that may indicate DoS attempts. 5. Isolate and limit the privileges of the eyoucms application to restrict access to sensitive files and network resources. 6. Regularly audit and update all third-party libraries and dependencies related to XML parsing. 7. Engage with the eyoucms vendor or community to obtain patches or updates as soon as they become available. 8. Prepare incident response plans specifically addressing XXE and DoS scenarios to reduce downtime. 9. Consider deploying rate limiting on POST requests to reduce the risk of automated exploitation. 10. Conduct penetration testing and vulnerability scanning focused on XML processing to identify residual risks.
Description
XML external entity (XXE) injection in eyoucms v1.7.1 allows remote attackers to cause a denial of service via crafted body of a POST request.