CVE-2025-11306
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceReflected cross-site scripting (XSS) vulnerability in qianfox FoxCMS up to version 1.2. The search page at /index.php/Search does not properly sanitize the 'keyword' parameter, allowing injection of malicious HTML/JavaScript that executes in victim browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm FoxCMS installation and versionLocate the FoxCMS installation directory and check for a version file or admin panel that displays the software version. Common locations include a version.php file, README, or the admin dashboard.Affected if The installed version is 1.2 or any version lower than 1.2.
-
Verify search functionality existsAttempt to access the search page at /index.php/Search (or /Search/index) to confirm the search module is enabled and accessible.Affected if The search page loads and accepts a 'keyword' parameter.
-
Check keyword parameter handling in source codeLocate the search controller or model file that handles the 'keyword' parameter. Inspect the code to see if the parameter is directly echoed or displayed without sanitization functions such as htmlspecialchars(), htmlentities(), or equivalent.Affected if The keyword parameter is output directly without sanitization (no htmlspecialchars, htmlentities, or similar function wrapping the output).
-
Test for reflected XSS in keyword parameterSend a crafted request with a test payload in the keyword parameter, such as: /index.php/Search?keyword=<script>alert('XSS')</script> and check if the payload is reflected in the response page without encoding.Affected if The test payload appears literally in the HTML response (the <script> tags are not converted to HTML entities).
You are affected if FoxCMS version 1.2 or lower is installed AND the search page with the 'keyword' parameter is accessible AND the keyword input is reflected without HTML encoding.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement input validation and output encoding for the keyword parameter in the search functionality. Replace any direct echo/display of user input with sanitized output using htmlspecialchars() or equivalent. Consider deploying a WAF rule as an additional layer of defense.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11306 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11306 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data