Skip to main content
CVE-2025-65956VulnerabilityPublished

CVE-2025-65956: getformwork formwork · Cross-site Scripting

Affects getformwork formworkSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.2.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Nov 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 2026-10-25.

What to do

Upgrade getformwork/formwork to 2.2.0.

Affected software

ProductAffectedFixed in
GitHubgetformwork/formworkpkg:github/getformwork/formworkOther threatsAffected
  • <2.2.0
Fixed in
  • 2.2.0

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 upgrade Formwork CMS to version 2.2.0 or later, where the vulnerability is patched. Until the upgrade can be performed, administrators should restrict access to the CMS to trusted users only and enforce strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise. Regularly audit user accounts and permissions to ensure that only necessary personnel have administrative privileges. Implement Content Security Policy (CSP) headers to limit the impact of potential XSS attacks by restricting the execution of unauthorized scripts. Monitor CMS logs and web traffic for unusual activity indicative of exploitation attempts. Educate CMS users about the risks of XSS and the importance of cautious interaction with content, especially when editing or reviewing blog posts. Consider deploying web application firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting the blog tag field. Finally, conduct periodic security assessments of the CMS environment to identify and remediate any residual or related vulnerabilities.

Description

Formwork is a flat file-based Content Management System (CMS). Prior to version 2.2.0, inserting unsanitized data into the blog tag field results in stored cross‑site scripting (XSS). Any user with credentials to the Formwork CMS who accesses or edits an affected blog post will have attacker‑controlled script executed in their browser. The issue is persistent and impacts privileged administrative workflows. This issue has been patched in version 2.2.0.

References

Community reviews

Loading reviews…