Skip to main content
VulnerabilityPublished

CVE-2025-55420: FoxCMS · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

AI-suggested

  1. Immediate mitigation should include implementing input validation and output encoding on the /index.php endpoint to sanitize all user-supplied data, especially GET parameters, to prevent script injection.
  2. If a patch is not yet available from FoxCMS, organizations should consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block reflected XSS attack patterns targeting the vulnerable endpoint.
  3. Educate users about the risks of clicking on suspicious links, especially those received via email or untrusted sources, to reduce the likelihood of successful social engineering.
  4. Review and restrict user privileges within FoxCMS to limit the impact of compromised accounts.
  5. Monitor web server logs and application logs for unusual requests or error patterns that may indicate attempted exploitation.
  6. Plan and test an upgrade path to a patched version of FoxCMS once available, or consider migrating to alternative CMS platforms with active security support.
  7. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing the CMS.

Description

A Reflected Cross Site Scripting (XSS) vulnerability was found in /index.php in FoxCMS v1.2.6. When a crafted script is sent via a GET request, it is reflected unsanitized into the HTML response. This permits execution of arbitrary JavaScript code when a logged-in user submits the malicious input.

References

Community reviews

Loading reviews…