Cross-Site Scripting (XSS) in getformwork/formwork (CVE-2024-35621)
Summary
Cross-site scripting in getformwork/formwork (CVE-2024-35621). Risk of unauthorized operations or information disclosure. Exploitable via content.safe_mode. Mitigation: upgrade to 1.13.0 or later.
Original description
The description as published by the source.
Impact
Users with access to the administration panel with page editing permissions could insert `` tags in markdown fields, which are exposed on the publicly accessible site pages, leading to potential XSS injections.
Patches
- Formwork 1.13.0 has been released with a patch that solves this vulnerability. Now the system config option
content.safe_mode(enabled by default) controls whether HTML tags and potentially dangerous links are escaped. This is configurable as in some cases more flexibility should be given. Panel users should be only a controlled group of editors, which cannot enable the option by themselves, and not a generic group. This mitigates the chance of introducing vulnerabilities. - Formwork 2.x (6adc302) adds a similar
content.safeModesystem option. Like Formwork 1.13.0, by default HTML tags and dangerous link are escaped. Even if enabled by an administrator, however, `` and other dangerous tags are still converted to text, but secure tags are allowed.
References
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-35621
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-35621 has been found in getformwork/formwork.
Attackers can target a specific entry point like content.safe_mode over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade getformwork/formwork to 1.13.0 or later.
If unsure, ask your IT team or search "getformwork/formwork CVE-2024-35621" on the vendor's site.
CVE-2024-35621 (getformwork/formwork) — CWE-79
Attack vector: remote (network-reachable)
Attack surface: content.safe_mode / content.safeMode
Patched: 1.13.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in getformwork/formwork. Attackers reach the vulnerable code path via content.safe_mode.
Check the vendor advisory for the affected versions of getformwork/formwork. Attack surface: content.safe_mode / content.safeMode.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.13.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'getformwork/formwork' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'getformwork/formwork' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
getformwork/formworkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade getformwork/formwork to 1.13.0ステージング環境で 1.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com