CVE-2025-12920VulnerabilityPublished 9 Nov 2025Updated 24 Feb 2026

CVE-2025-12920: qianfox FoxCMS · Cross Site Scripting

Affects qianfox FoxCMSSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

4.8Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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: High
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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 Nov 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 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 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
GitHubqianfox/FoxCMS`pkg:github/qianfox/FoxCMS`Other threats	Affected =1.2.0 =1.2.1 =1.2.2 =1.2.3 =1.2.4 =1.2.5 =1.2.6 =1.2.7 =1.2.8 =1.2.9 =1.2.10 =1.2.11 =1.2.12 =1.2.13 =1.2.14 =1.2.15 =1.2.16	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 from the vendor, organizations should implement immediate mitigations to reduce risk. These include: 1) Applying strict input validation on the Title parameter to reject or sanitize suspicious characters such as script tags or event handlers before processing; 2) Implementing robust output encoding (e.g., HTML entity encoding) on all user-supplied input before rendering it in the browser to prevent script execution; 3) Employing Content Security Policy (CSP) headers to restrict the execution of inline scripts and reduce the impact of XSS; 4) Monitoring web server and application logs for unusual input patterns or error messages indicative of attempted exploitation; 5) Restricting access to the add/edit product functionality to trusted administrators and enforcing multi-factor authentication to reduce the risk of unauthorized changes; 6) Considering temporary disabling or restricting the vulnerable functionality if feasible until a vendor patch is released; 7) Educating users and administrators about the risks of XSS and encouraging vigilance for suspicious activity. Organizations should also track vendor communications for updates and apply official patches promptly once available.

Description

A flaw has been found in qianfox FoxCMS up to 1.2.16. Affected by this vulnerability is the function add/edit of the file app/admin/controller/Product.php. This manipulation of the argument Title causes cross site scripting. It is possible to initiate the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2025-12920 is the potential compromise of user sessions and the execution of arbitrary scripts within the browsers of users visiting affected FoxCMS websites. This can lead to theft of sensitive information such as authentication tokens, unauthorized actions performed on behalf of users, defacement of websites, or redirection to malicious sites. For organizations, this undermines the integrity and trustworthiness of their web presence, potentially damaging reputation and leading to regulatory or compliance issues if user data is compromised. Although the vulnerability does not directly affect server availability or confidentiality of backend data, the indirect consequences of successful exploitation can be severe, including loss of customer trust and potential financial losses. The ease of remote exploitation without authentication increases the risk, especially since a public exploit exists. Organizations relying on FoxCMS for e-commerce, customer portals, or public-facing content are particularly vulnerable to targeted attacks or opportunistic exploitation by attackers scanning for vulnerable instances.

Summary

CVE-2025-12920 is a cross-site scripting vulnerability identified in the qianfox FoxCMS content management system, affecting all versions up to 1.2.16. The vulnerability resides in the add/edit functionality of the Product.php controller file, where the Title parameter is improperly sanitized. This improper input validation allows an attacker to inject malicious JavaScript code remotely. The attack vector is network-based and does not require prior authentication, although user interaction is necessary to trigger the malicious script once injected. The vulnerability can be exploited by submitting crafted input to the Title field, which is then reflected without proper encoding in the web application’s response, enabling execution of arbitrary scripts in the context of the victim’s browser. The vendor was notified early but has not provided a patch or response, and a public exploit is available, increasing the risk of exploitation. The CVSS 4.0 base score is 4.8, reflecting medium severity, with factors including no required privileges but requiring user interaction and limited impact on confidentiality and integrity. This vulnerability can be leveraged for session hijacking, phishing, or delivering malware to users interacting with the affected FoxCMS sites. The lack of vendor remediation and public exploit availability make this a notable risk for organizations using FoxCMS.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:18 UTC

Technical details

References

Community reviews

Related threats