How severe is GHSA-3v8v-4wg6-r7qh?

No CVSS score has been assigned to GHSA-3v8v-4wg6-r7qh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3v8v-4wg6-r7qh?

GHSA-3v8v-4wg6-r7qh affects the following packages: typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-3v8v-4wg6-r7qh?

Update typo3/cms-core to 10.4.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3v8v-4wg6-r7qh is resolved across your whole dependency graph.

How do I detect GHSA-3v8v-4wg6-r7qh in my Packagist dependencies?

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

How do I mitigate GHSA-3v8v-4wg6-r7qh if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

How does O3 Security protect against GHSA-3v8v-4wg6-r7qh?

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

Is GHSA-3v8v-4wg6-r7qh actively exploited in the wild?

No public exploit code has been indexed for GHSA-3v8v-4wg6-r7qh 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-3v8v-4wg6-r7qh?

GHSA-3v8v-4wg6-r7qh has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th 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-3v8v-4wg6-r7qh?

GHSA-3v8v-4wg6-r7qh is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3v8v-4wg6-r7qh published, and has it been updated?

GHSA-3v8v-4wg6-r7qh was published on June 12, 2026 and was last updated on September 10, 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

GHSA-3v8v-4wg6-r7qh — typo3/cms-core

Fix: TYPO3/typo3@504e724

GHSA-3v8v-4wg6-r7qh is a CWE-862 vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.

TYPO3 CMS: Destructive Actions on File Mount Folders

Also known asCVE-2026-47343

Published

Jun 12, 2026

Updated

Sep 10, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3v8v-4wg6-r7qh.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

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.

Real-World Exposure

5 pkgs affected

🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core

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

Non-privileged backend users with file mount access were able to perform write operations (move, delete, rename) on folders representing the root of an active file mount due to missing authorization restrictions.

Solution

Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.

Credits

TYPO3 CMS thanks Arne Uplegger for reporting this issue, and TYPO3 security team member Elias Häußler for fixing it.

Resources

TYPO3-CORE-SA-2026-007

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	all versions	10.4.57`composer require typo3/cms-core:^10.4.57`
🐘Packagist	`typo3/cms-core`	≥ 11.0.0&&< 11.5.51	11.5.51`composer require typo3/cms-core:^11.5.51`
🐘Packagist	`typo3/cms-core`	≥ 12.0.0&&< 12.4.46	12.4.46`composer require typo3/cms-core:^12.4.46`
🐘Packagist	`typo3/cms-core`	≥ 13.0.0&&< 13.4.31	13.4.31`composer require typo3/cms-core:^13.4.31`
🐘Packagist	`typo3/cms-core`	≥ 14.0.0&&< 14.3.3	14.3.3`composer require typo3/cms-core:^14.3.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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 10.4.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3v8v-4wg6-r7qh is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3v8v-4wg6-r7qh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3v8v-4wg6-r7qh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Problem Non-privileged backend users with file mount access were able to perform write operations (move, delete, rename) on folders representing the root of an active file mount due to missing authorization restrictions. ### Solution Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described. ### Credits TYPO3 CMS thanks Arne Uplegger for reporting this issue, and TYPO3 security team member Elias Häußler for fixing it. ### Resources * [TYPO3-CORE-SA-2026-007](https://typo3.org/security/advisory/typo3-core-sa-2026-007)

O3 Security · Impact-Aware SCA

Is GHSA-3v8v-4wg6-r7qh in your dependencies?

O3 Security finds GHSA-3v8v-4wg6-r7qh 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