CVE-2025-7567: ShopXO · Cross-site Scripting
Affects ShopXOSource CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 11:07 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% 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:PExploitation evidence
Disclosed: evidence found.
CVE published 14 Jul 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubgongfuxiang/shopxopkg:github/gongfuxiang/shopxoOther 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
European organizations should immediately audit their ShopXO installations to identify affected versions (6.0 through 6.5.0). Until an official patch is released, implement the following mitigations: 1) Apply strict input validation and output encoding on the 'lang/system_type' parameter at the web application firewall (WAF) or reverse proxy level to block or sanitize malicious payloads. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers, mitigating the impact of XSS. 3) Monitor web server logs for suspicious requests targeting the vulnerable parameter and implement rate limiting to reduce attack surface. 4) Educate administrators and users about the risk of phishing or social engineering stemming from XSS attacks. 5) Plan for rapid deployment of official patches once available and test updates in a staging environment before production rollout. 6) Consider temporary disabling or restricting access to features that utilize the vulnerable parameter if feasible. These targeted actions go beyond generic advice by focusing on the specific vulnerable vector and leveraging layered defenses.
Description
A vulnerability was found in ShopXO up to 6.5.0 and classified as problematic. This issue affects some unknown processing of the file header.html. The manipulation of the argument lang/system_type leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.