How severe is GHSA-vf6x-59hh-332f?

GHSA-vf6x-59hh-332f has a CVSS score of 4.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vf6x-59hh-332f?

GHSA-vf6x-59hh-332f affects the following packages: getformwork/formwork (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-vf6x-59hh-332f?

Update getformwork/formwork to 2.0.0-beta.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vf6x-59hh-332f is resolved across your whole dependency graph.

How do I detect GHSA-vf6x-59hh-332f in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getformwork/formwork, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vf6x-59hh-332f if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-vf6x-59hh-332f?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vf6x-59hh-332f can be triaged on real exposure rather than presence alone.

Is GHSA-vf6x-59hh-332f actively exploited in the wild?

No public exploit code has been indexed for GHSA-vf6x-59hh-332f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-vf6x-59hh-332f published, and has it been updated?

GHSA-vf6x-59hh-332f was published on March 1, 2025 and was last updated on February 18, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

GHSA-vf6x-59hh-332f — getformwork/formwork

MEDIUMFix: getformwork/formwork@aa3e9c6

GHSA-vf6x-59hh-332f is a medium-severity (CVSS 4.7) vulnerability in getformwork/formwork. A fix is available for getformwork/formwork — see the affected versions and patch details below.

Formwork has a cross-site scripting (XSS) vulnerability in Site title

Published

Mar 1, 2025

Updated

Feb 18, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 18, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘getformwork/formwork

Real-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

Summary

The site title field at /panel/options/site/allows embedding JS tags, which can be used to attack all members of the system. This is a widespread attack and can cause significant damage if there is a considerable number of users.

Impact

The attack is widespread, leveraging what XSS can do. This will undoubtedly impact system availability.

Patches

Formwork 2.x (aa3e9c6) escapes site title from panel header navigation.

Details

By embedding "<!--", the source code can be rendered non-functional, significantly impacting system availability. However, the attacker would need admin privileges, making the attack more difficult to execute.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`getformwork/formwork`	≥ 2.0.0-beta.3&&< 2.0.0-beta.4	2.0.0-beta.4`composer require getformwork/formwork:^2.0.0-beta.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getformwork/formwork, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update getformwork/formwork to 2.0.0-beta.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vf6x-59hh-332f 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vf6x-59hh-332f can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vf6x-59hh-332f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The site title field at /panel/options/site/allows embedding JS tags, which can be used to attack all members of the system. This is a widespread attack and can cause significant damage if there is a considerable number of users. ### Impact The attack is widespread, leveraging what XSS can do. This will undoubtedly impact system availability. ### Patches - [**Formwork 2.x** (aa3e9c6)](https://github.com/getformwork/formwork/commit/aa3e9c684035d9e8495169fde7c57d97faa3f9a2) escapes site title from panel header navigation. ### Details By embedding "<!--", the source code can be

O3 Security · Impact-Aware SCA

Is GHSA-vf6x-59hh-332f in your dependencies?

O3 Security finds GHSA-vf6x-59hh-332f across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works