How severe is GHSA-ww7h-g2qf-7xv6?

GHSA-ww7h-g2qf-7xv6 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-ww7h-g2qf-7xv6?

GHSA-ww7h-g2qf-7xv6 affects the following packages: typo3/cms-form (Packagist), typo3/cms-form (Packagist), typo3/cms-form (Packagist), typo3/cms-form (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-ww7h-g2qf-7xv6?

Update typo3/cms-form to 10.4.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ww7h-g2qf-7xv6 is resolved across your whole dependency graph.

How do I detect GHSA-ww7h-g2qf-7xv6 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-form. 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.

How do I mitigate GHSA-ww7h-g2qf-7xv6 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-ww7h-g2qf-7xv6?

O3 pinpoints whether GHSA-ww7h-g2qf-7xv6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-ww7h-g2qf-7xv6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-ww7h-g2qf-7xv6 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.

What is the EPSS score for GHSA-ww7h-g2qf-7xv6?

GHSA-ww7h-g2qf-7xv6 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-ww7h-g2qf-7xv6?

GHSA-ww7h-g2qf-7xv6 is classified as Cross-Site Request Forgery (CSRF) (CWE-352), CWE-749 (CWE-749). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-ww7h-g2qf-7xv6 published, and has it been updated?

GHSA-ww7h-g2qf-7xv6 was published on January 14, 2025 and was last updated on May 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-ww7h-g2qf-7xv6

MEDIUM

TYPO3 Form Framework Module vulnerable to Cross-Site Request Forgery

Also known asCVE-2024-55922

Published

Jan 14, 2025

Updated

May 21, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk8th percentile-0.01%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

🐘typo3/cms-form🐘typo3/cms-form🐘typo3/cms-form🐘typo3/cms-form

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

Problem

A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method.

Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions:

the user opens a malicious link, such as one sent via email.
the user visits a compromised or manipulated website while the following settings are misconfigured:
- security.backend.enforceReferrer feature is disabled,
- BE/cookieSameSite configuration is set to lax or none

The vulnerability in the affected downstream component “Form Framework Module” allows attackers to manipulate or delete persisted form definitions.

Solution

Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS that fix the problem described.

Credits

Thanks to TYPO3 core and security members Benjamin Franzke, Oliver Hader, Andreas Kienast, Torben Hansen, Elias Häußler who fixed the issue.

References

TYPO3-CORE-SA-2025-007

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-form`	≥ 10.0.0&&< 10.4.48	10.4.48
🐘Packagist	`typo3/cms-form`	≥ 11.0.0&&< 11.5.42	11.5.42
🐘Packagist	`typo3/cms-form`	≥ 12.0.0&&< 12.4.25	12.4.25
🐘Packagist	`typo3/cms-form`	≥ 13.0.0&&< 13.4.3	13.4.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-form. 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 typo3/cms-form to 10.4.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ww7h-g2qf-7xv6 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-ww7h-g2qf-7xv6 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-ww7h-g2qf-7xv6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Problem A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method. Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following cond

O3 Security · Impact-Aware SCA

Is GHSA-ww7h-g2qf-7xv6 in your dependencies?

O3 detects GHSA-ww7h-g2qf-7xv6 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works