CVE-2026-47343

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0 through 11.5.50, 12.0.0 through 12.4.45, 13.0.0 through 13.4.30, and 14.0.0 through 14.3.2.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity72% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jun 11, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

TYPO3-CORE-SA-2026-007: Broken Access Control in File Abstraction Layer - TYPO3 Project

https://typo3.org/security/advisory/typo3-core-sa-2026-007
github_commit

commit ac4125aef8b9 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit ac4125aef8b9 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/ac4125aef8b9b94528a7f74db2444db57b05a87b
github_commit

commit 504e72470ff7 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit 504e72470ff7 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/504e72470ff72aaf5d2256878bf473747f389798

Vendor Advisories for CVE-2026-47343(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
typo3/cms-corev14.0.0 ... v14.3.2 (9 versions)14.3.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-03 10:36 UTCEPSS rescore
  2. 2026-08-02 09:17 UTCEG score recompute
  3. 2026-08-02 02:27 UTCEPSS rescore
  4. 2026-08-01 10:26 UTCEG score recompute
  5. 2026-08-01 04:16 UTCEPSS rescore
  6. 2026-07-31 01:23 UTCEG score recompute
  7. 2026-07-30 16:28 UTCEPSS rescore
  8. 2026-07-30 11:14 UTCEG score recompute
  9. 2026-07-30 01:30 UTCEPSS rescore
  10. 2026-07-29 05:28 UTCEG score recompute
  11. 2026-07-28 15:37 UTCEPSS rescore
  12. 2026-07-28 02:47 UTCEG score recompute
  13. 2026-07-26 21:27 UTCEG score recompute
  14. 2026-07-26 14:54 UTCEPSS rescore
  15. 2026-07-26 06:55 UTCEG score recompute
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-23 14:18 UTCEPSS rescore
  18. 2026-07-23 03:17 UTCEG score recompute
  19. 2026-07-22 14:08 UTCEPSS rescore
  20. 2026-07-21 15:24 UTCEPSS rescore
  21. 2026-07-20 17:08 UTCEPSS rescore
  22. 2026-07-19 14:31 UTCEPSS rescore
  23. 2026-07-19 02:29 UTCEPSS rescore
  24. 2026-07-18 10:04 UTCEPSS rescore
  25. 2026-07-16 17:03 UTCEPSS rescore
Show 49 more
  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-24 14:05 UTCEPSS rescore
  24. 2026-06-23 21:33 UTCEPSS rescore
  25. 2026-06-23 21:33 UTCEPSS rescore
  26. 2026-06-22 14:25 UTCEPSS rescore
  27. 2026-06-22 14:25 UTCEPSS rescore
  28. 2026-06-21 14:56 UTCEPSS rescore
  29. 2026-06-21 14:56 UTCEPSS rescore
  30. 2026-06-21 01:59 UTCEPSS rescore
  31. 2026-06-21 01:59 UTCEPSS rescore
  32. 2026-06-19 19:26 UTCEPSS rescore
  33. 2026-06-19 19:26 UTCEPSS rescore
  34. 2026-06-18 17:52 UTCEPSS rescore
  35. 2026-06-18 17:52 UTCEPSS rescore
  36. 2026-06-17 17:53 UTCEPSS rescore
  37. 2026-06-16 17:53 UTCEPSS rescore
  38. 2026-06-15 17:49 UTCEPSS rescore
  39. 2026-06-15 17:49 UTCEPSS rescore
  40. 2026-06-14 23:18 UTCEPSS rescore
  41. 2026-06-13 23:00 UTCEPSS rescore
  42. 2026-06-12 23:12 UTCEPSS rescore
  43. 2026-06-12 23:12 UTCEPSS rescore
  44. 2026-06-11 14:00 UTCEPSS rescore
  45. 2026-06-10 22:18 UTCEPSS rescore
  46. 2026-06-10 13:22 UTCEPSS rescore
  47. 2026-06-10 13:22 UTCEPSS rescore
  48. 2026-06-09 11:20 UTCEG score recompute
  49. 2026-06-09 11:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47343?
CVE-2026-47343 is a high vulnerability published on June 9, 2026. 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. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0 through 11.5.50, 12.0.0…
When was CVE-2026-47343 disclosed?
CVE-2026-47343 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47343 actively exploited?
CVE-2026-47343 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.0% of all scored CVEs.
What is the CVSS score of CVE-2026-47343?
CVE-2026-47343 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-47343?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47343, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47343

Explore →

Is Your Infrastructure Affected by CVE-2026-47343?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs