How severe is GHSA-wf98-vxv9-jqfv?

No CVSS score has been assigned to GHSA-wf98-vxv9-jqfv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wf98-vxv9-jqfv?

GHSA-wf98-vxv9-jqfv affects the following packages: craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-wf98-vxv9-jqfv?

Update craftcms/cms to 3.7.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wf98-vxv9-jqfv is resolved across your whole dependency graph.

How do I detect GHSA-wf98-vxv9-jqfv in my Packagist dependencies?

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

How do I mitigate GHSA-wf98-vxv9-jqfv 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-wf98-vxv9-jqfv?

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

Is GHSA-wf98-vxv9-jqfv actively exploited in the wild?

No public exploit code has been indexed for GHSA-wf98-vxv9-jqfv 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-wf98-vxv9-jqfv published, and has it been updated?

GHSA-wf98-vxv9-jqfv was published on April 5, 2022 and was last updated on December 5, 2024. 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

GHSA-wf98-vxv9-jqfv — craftcms/cms

GHSA-wf98-vxv9-jqfv is a security vulnerability in craftcms/cms. A fix is available for craftcms/cms — see the affected versions and patch details below.

XSS Injection Vulnerability

Published

Apr 5, 2022

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 5, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘craftcms/cms

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

Impact

Under some circumstances, the Feeds widget on the dashboard could have an XSS vulnerability if a malformed feed was supplied.

Patches

This has been patched in Craft 3.7.29.

References

https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#3729---2022-01-18

For more information

If you have any questions or comments about this advisory, email us at [email protected]

Credits: https://github.com/noobpk

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	all versions	3.7.29`composer require craftcms/cms:^3.7.29`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update craftcms/cms to 3.7.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wf98-vxv9-jqfv 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-wf98-vxv9-jqfv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-wf98-vxv9-jqfv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Under some circumstances, the Feeds widget on the dashboard could have an XSS vulnerability if a malformed feed was supplied. ### Patches This has been patched in Craft 3.7.29. ### References * https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#3729---2022-01-18 ### For more information If you have any questions or comments about this advisory, email us at [[email protected]](mailto:[email protected]) ---------- Credits: https://github.com/noobpk

O3 Security · Impact-Aware SCA

Is GHSA-wf98-vxv9-jqfv in your dependencies?

O3 Security finds GHSA-wf98-vxv9-jqfv 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