CVE-2025-11306VulnerabilityPublished 5 Oct 2025Updated 24 Feb 2026

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

Affects qianfox FoxCMSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% 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 5 Oct 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.

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
qianfox FoxCMS	Affected =1.0 =1.1 =1.2	Fixed in–

AI-suggested

Given the lack of an official patch, organizations should implement immediate mitigations to reduce risk. First, apply strict input validation and output encoding on the 'keyword' parameter in the Search Page to neutralize malicious scripts. Web application firewalls (WAFs) can be configured to detect and block typical XSS payloads targeting this parameter. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. Educate users to avoid clicking on suspicious links, especially those containing search parameters. If possible, temporarily disable or restrict the search functionality until a vendor patch is released. Monitor web logs for unusual query patterns or attempts to exploit the vulnerability. Regularly check for vendor updates or community patches. For long-term mitigation, consider migrating to a more actively maintained CMS or contributing to FoxCMS security improvements. Additionally, implement multi-factor authentication and session management best practices to limit the impact of session hijacking.

Description

A vulnerability was found in qianfox FoxCMS up to 1.2. This affects an unknown part of the file /index.php/Search of the component Search Page. The manipulation of the argument keyword results in cross site scripting. The attack can be executed remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of this XSS vulnerability is on the confidentiality and integrity of user data and sessions. Attackers can execute arbitrary scripts in the context of the victim's browser, potentially stealing session cookies, redirecting users to malicious websites, or defacing web content. This can lead to account compromise, phishing attacks, and erosion of user trust. Since the vulnerability is remotely exploitable without authentication, any user visiting a compromised or maliciously crafted search URL is at risk. Organizations running FoxCMS-powered websites may face reputational damage, data breaches, and regulatory compliance issues if user data is exposed. The absence of an official patch and vendor response increases the window of exposure. Although availability impact is minimal, the overall risk to web application security posture is significant, especially for sites with high user interaction or sensitive data. Attackers could also use this vulnerability as a foothold for further attacks within the network if users with elevated privileges are targeted.

Summary

CVE-2025-11306 identifies a cross-site scripting vulnerability in qianfox FoxCMS, specifically in versions 1.0 through 1.2. The vulnerability resides in the Search Page component, located at /index.php/Search, where the 'keyword' parameter is improperly sanitized. This allows an attacker to inject arbitrary JavaScript code that executes in the context of the victim's browser when they visit a crafted URL or interact with the vulnerable search functionality. The vulnerability is remotely exploitable without requiring authentication, but user interaction is necessary to trigger the malicious script. The CVSS 4.0 base score is 5.3 (medium severity), reflecting the network attack vector, low complexity, no privileges required, but requiring user interaction and causing limited integrity impact. The vendor was notified early but has not issued any patches or advisories, and no official remediation is currently available. While no known exploits are actively used in the wild, a public proof-of-concept exploit has been released, increasing the risk of exploitation. This vulnerability can be leveraged for session hijacking, phishing, or delivering malware by manipulating the victim's browser environment. The lack of vendor response and patch availability increases the urgency for organizations to implement mitigations. FoxCMS is a content management system used by various organizations, and the presence of this vulnerability in a core search feature makes it a notable risk for web applications relying on this platform.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 21:50 UTC

Technical details

References

Community reviews

Related threats