CVE-2025-8852: WuKongOpenSource WukongCRM · Information Exposure Through Error Message
Affects WuKongOpenSource WukongCRMSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 11 Aug 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WuKongOpenSource WukongCRM | Affected
| Fixed in– |
AI-suggested
Given the absence of an official patch, European organizations should implement the following specific mitigations: 1) Restrict access to the /adminFile/upload endpoint using network-level controls such as IP whitelisting or VPN access to limit exposure to trusted users only. 2) Implement Web Application Firewall (WAF) rules to detect and block anomalous requests targeting the upload endpoint, particularly those that could trigger error messages. 3) Review and harden error handling configurations in WukongCRM to suppress detailed error messages from being returned to clients, ensuring only generic error responses are provided. 4) Conduct thorough logging and monitoring of access to the vulnerable endpoint to detect potential exploitation attempts promptly. 5) Engage with WuKongOpenSource for updates on patches or security advisories and plan for timely application of any forthcoming fixes. 6) Perform security assessments and penetration testing focused on the upload functionality to identify and remediate related weaknesses. These targeted measures go beyond generic advice by focusing on access control, error message management, and proactive detection tailored to this specific vulnerability.
Description
A vulnerability was identified in WuKongOpenSource WukongCRM 11.0. This affects an unknown part of the file /adminFile/upload of the component API Response Handler. The manipulation leads to information exposure through error message. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.