VulnerabilityPublished 9 Jun 2025

CVE-2025-5879: WuKongOpenSource WukongCRM · Cross-site Scripting

Affects WuKongOpenSource WukongCRMSource CVE Database V5

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% 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:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubwukongopensource/WukongCRM`pkg:github/wukongopensource/WukongCRM`Other threats	Affected =9.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of an official patch, European organizations should implement several specific mitigations: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the file upload parameter in WukongCRM. 2) Conduct thorough input validation and output encoding on the server side where possible, or implement reverse proxies that sanitize inputs to the vulnerable endpoint. 3) Restrict access to the AdminSysConfigController interface to trusted IP ranges or VPN-only access to reduce exposure. 4) Educate users about the risks of interacting with untrusted links or content within the CRM interface to reduce the likelihood of successful user interaction exploitation. 5) Monitor logs for unusual activity related to file uploads or script injections. 6) Plan for an upgrade or migration to a patched or alternative CRM solution once available, as the vendor has not responded to the vulnerability disclosure. 7) Implement Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers accessing the CRM.

Description

A vulnerability, which was classified as problematic, was found in WuKongOpenSource WukongCRM 9.0. This affects an unknown part of the file AdminSysConfigController.java of the component File Upload. The manipulation of the argument File leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using WukongCRM 9.0, this vulnerability poses a moderate risk. Successful exploitation could lead to the compromise of user sessions, enabling attackers to impersonate legitimate users and access sensitive customer data or internal CRM functionalities. This could result in data breaches, loss of customer trust, and regulatory non-compliance, especially under GDPR requirements. The XSS vulnerability could also be leveraged to deliver further malware or phishing payloads within the corporate network. Since the vulnerability requires user interaction, the risk is somewhat mitigated by user awareness, but the public availability of exploit code increases the likelihood of targeted attacks. Organizations relying on WukongCRM for customer data management or sales operations may face operational disruptions and reputational damage if exploited.

Summary

CVE-2025-5879 is a cross-site scripting (XSS) vulnerability identified in WuKongOpenSource's WukongCRM version 9.0. The vulnerability resides in the AdminSysConfigController.java file, specifically within the file upload component. The flaw arises from improper sanitization or validation of the 'File' argument, allowing an attacker to inject malicious scripts. This vulnerability can be exploited remotely without requiring authentication, although it does require some user interaction (UI:P). The CVSS 4.0 vector indicates that the attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:L), and user interaction needed. The impact on confidentiality is none, but there is a low impact on integrity and no impact on availability. The vulnerability has been publicly disclosed, and although no known exploits are currently reported in the wild, the exploit code is available, increasing the risk of exploitation. The vendor has not responded to the disclosure, and no patches or mitigations have been provided yet. This XSS vulnerability could allow attackers to execute arbitrary JavaScript in the context of the victim's browser, potentially leading to session hijacking, defacement, or redirection to malicious sites. Given that WukongCRM is a customer relationship management system, exploitation could compromise sensitive customer data or internal business processes if combined with social engineering or phishing attacks targeting users of the CRM interface.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2025, 14:12 UTC

Technical details

References

Community reviews

Related threats