VulnerabilityPublished 26 Jun 2025

CVE-2025-6700: Xuxueli xxl-sso · Cross-site Scripting

Affects Xuxueli xxl-ssoSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% 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: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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 26 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
Mavencom.xuxueli/xxl-sso`pkg:maven/com.xuxueli/xxl-sso`Other threats	Affected =1.1.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 the following specific mitigations: 1) Employ web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the 'errorMsg' parameter in the /xxl-sso-server/login endpoint. 2) Conduct input validation and output encoding on the server side if possible by applying temporary code-level fixes or wrappers to sanitize the 'errorMsg' parameter before rendering. 3) Educate users about phishing risks and encourage cautious behavior regarding unsolicited links, especially those pointing to authentication portals. 4) Monitor web server logs and application telemetry for unusual or suspicious requests containing script tags or encoded payloads in the 'errorMsg' parameter. 5) Isolate the xxl-sso service behind VPN or restrict access to trusted networks to reduce exposure. 6) Consider deploying Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. 7) Plan for an upgrade or migration to a patched or alternative SSO solution once available. 8) Regularly review and update incident response plans to quickly address potential exploitation attempts.

Description

A vulnerability classified as problematic was found in Xuxueli xxl-sso 1.1.0. This vulnerability affects unknown code of the file /xxl-sso-server/login. The manipulation of the argument errorMsg leads to cross site scripting. The attack can be initiated 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 xxl-sso 1.1.0, this vulnerability poses a moderate risk. Exploitation could lead to unauthorized access to user sessions, enabling attackers to impersonate legitimate users or steal sensitive information. This is particularly concerning for organizations relying on xxl-sso for centralized authentication across multiple internal or cloud services, as a successful attack could cascade into broader access compromises. The impact is amplified in sectors handling sensitive personal data, such as finance, healthcare, and government, due to potential GDPR implications and reputational damage. Additionally, the lack of vendor response and absence of patches increases exposure time. Attackers could leverage this vulnerability in targeted phishing campaigns to trick users into clicking malicious links, leading to session hijacking or credential theft. While the vulnerability does not directly affect system availability, the resulting breaches could disrupt business operations and lead to costly incident response and remediation efforts.

Summary

CVE-2025-6700 is a cross-site scripting (XSS) vulnerability identified in version 1.1.0 of the Xuxueli xxl-sso product, specifically within the /xxl-sso-server/login endpoint. The vulnerability arises from improper handling and sanitization of the 'errorMsg' parameter, which can be manipulated by an attacker to inject malicious scripts. This flaw allows an attacker to craft a specially crafted URL or request that, when processed by the vulnerable login page, executes arbitrary JavaScript in the context of the victim's browser session. The vulnerability is remotely exploitable without requiring authentication, and user interaction is necessary to trigger the malicious script execution (e.g., by clicking a malicious link). The CVSS v4.0 base score is 5.3, indicating a medium severity level. Although no known exploits are currently observed in the wild, the public disclosure of the vulnerability increases the risk of exploitation by attackers. Xxl-sso is a single sign-on solution, and compromise of its login interface could lead to session hijacking, credential theft, or further attacks targeting authenticated sessions. The vulnerability affects confidentiality and integrity primarily through potential theft of session tokens or user credentials, and availability impact is minimal. The attack vector is network-based with low attack complexity and no privileges required, but user interaction is necessary to trigger the exploit. Given the nature of XSS, the risk is heightened in environments where users have elevated privileges or where sensitive data is accessible post-login.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Jun 2025, 16:04 UTC

Technical details

References

Community reviews

Related threats