GHSA-gx8m-f3mp-fg99 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in getformwork/formwork. O3 Security confirms whether GHSA-gx8m-f3mp-fg99 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
formwork Cross-site scripting vulnerability in Markdown fields
Real-World Exposure
getformwork/formworkReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Users with access to the administration panel with page editing permissions could insert <script> 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,<script>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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | getformwork/formwork | all versions | 1.13.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getformwork/formwork. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update getformwork/formwork to 1.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gx8m-f3mp-fg99 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gx8m-f3mp-fg99 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-gx8m-f3mp-fg99. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-gx8m-f3mp-fg99 in your dependencies?
O3 detects GHSA-gx8m-f3mp-fg99 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.