CVE-2026-47348

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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: cna:typo3, epss
5.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.1Exploit: NoneExposed: 0

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

Editors with access to create or modify page content were able to include HTML markup in page titles that were stored in the search index without sanitization. When displayed in frontend search results via the Indexed Search plugin, these titles were rendered without proper output encoding, resulting in a Cross-Site Scripting vulnerability. This issue affects TYPO3 CMS versions 13.0.0-13.4.30 and 14.0.0-14.3.2.

CVSS v3
5.1
EG Score
5.1(medium)
EPSS
18.5%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 11, 2026

Advisory Details (3)

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

commit 8004b91a5951 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit 8004b91a5951 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/8004b91a5951cfe01dda8554f77d0daa82d6b899
github_commit

commit 2e96dd0e9fab (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit 2e96dd0e9fab — awaiting tagged release

https://github.com/TYPO3/typo3/commit/2e96dd0e9fab7ad877b741fb9f6fc645b4270a3e
generic

TYPO3-CORE-SA-2026-010: Cross-Site Scripting in Indexed Search - TYPO3 News

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

Vendor Advisories for CVE-2026-47348(1)

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

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFixed inDependents
typo3/cms-corev14.0.0 ... v14.3.2 (9 versions)14.3.3—
typo3/cms-indexed-searchv14.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 / 66× 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-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 15:47 UTCEG score recompute
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 15:35 UTCEG score recompute
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-03 15:59 UTCEG score recompute
  8. 2026-07-02 14:49 UTCEG score recompute
  9. 2026-07-01 15:12 UTCEG score recompute
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 15:38 UTCEG score recompute
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 12:00 UTCEG score recompute
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 12:25 UTCEG score recompute
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 12:48 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 13:13 UTCEG score recompute
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 13:39 UTCEG score recompute
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 41 more
  1. 2026-06-24 14:04 UTCEG score recompute
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-23 21:33 UTCEPSS rescore
  4. 2026-06-23 13:12 UTCEG score recompute
  5. 2026-06-22 14:25 UTCEPSS rescore
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-22 13:26 UTCEG score recompute
  8. 2026-06-21 14:56 UTCEPSS rescore
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-21 10:43 UTCEG score recompute
  11. 2026-06-21 01:59 UTCEPSS rescore
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-20 09:34 UTCEG score recompute
  14. 2026-06-19 19:26 UTCEPSS rescore
  15. 2026-06-19 19:26 UTCEPSS rescore
  16. 2026-06-19 09:46 UTCEG score recompute
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-18 07:43 UTCEG score recompute
  20. 2026-06-17 17:53 UTCEPSS rescore
  21. 2026-06-17 08:07 UTCEG score recompute
  22. 2026-06-16 17:53 UTCEPSS rescore
  23. 2026-06-16 08:33 UTCEG score recompute
  24. 2026-06-15 17:49 UTCEPSS rescore
  25. 2026-06-15 17:49 UTCEPSS rescore
  26. 2026-06-15 08:50 UTCEG score recompute
  27. 2026-06-14 23:18 UTCEPSS rescore
  28. 2026-06-14 09:12 UTCEG score recompute
  29. 2026-06-13 23:00 UTCEPSS rescore
  30. 2026-06-13 09:38 UTCEG score recompute
  31. 2026-06-12 23:12 UTCEPSS rescore
  32. 2026-06-12 23:12 UTCEPSS rescore
  33. 2026-06-12 10:02 UTCEG score recompute
  34. 2026-06-11 14:00 UTCEPSS rescore
  35. 2026-06-11 10:28 UTCEG score recompute
  36. 2026-06-10 22:18 UTCEPSS rescore
  37. 2026-06-10 13:22 UTCEPSS rescore
  38. 2026-06-10 13:22 UTCEPSS rescore
  39. 2026-06-10 10:54 UTCEG score recompute
  40. 2026-06-09 11:20 UTCEG score recompute
  41. 2026-06-09 11:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47348?
CVE-2026-47348 is a medium vulnerability published on June 9, 2026. Editors with access to create or modify page content were able to include HTML markup in page titles that were stored in the search index without sanitization. When displayed in frontend search results via the Indexed Search plugin, these titles were rendered without proper output encoding,…
When was CVE-2026-47348 disclosed?
CVE-2026-47348 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on June 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47348 actively exploited?
CVE-2026-47348 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47348?
CVE-2026-47348 has a CVSS v4.0 base score of 5.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-47348?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47348, 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-47348

Explore →

Is Your Infrastructure Affected by CVE-2026-47348?

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

Start Free Scan →Browse All CVEs