CVE-2025-59014

CVE-2025-59014 is a low-severity vulnerability in Typo3 with a CVSS 3.x base score of 2.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-248.

Key facts

Description

An uncaught exception in the Bookmark Toolbar of TYPO3 CMS versions 11.0.0–11.5.47, 12.0.0–12.4.36, and 13.0.0–13.4.17 lets administrator‑level backend users trigger a denial‑of‑service condition in the backend user interface by saving manipulated data in the bookmark toolbar.

Frequently asked questions

What is CVE-2025-59014?
An uncaught exception in the Bookmark Toolbar of TYPO3 CMS versions 11.0.0–11.5.47, 12.0.0–12.4.36, and 13.0.0–13.4.17 lets administrator‑level backend users trigger a denial‑of‑service condition in the backend user interface by saving manipulated data in the bookmark toolbar.
How severe is CVE-2025-59014?
CVE-2025-59014 has a CVSS 3.x base score of 2.7, rated low severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.
Is CVE-2025-59014 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-59014?
CVE-2025-59014 affects Typo3. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-59014?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-59014 have an EU (EUVD) identifier?
Yes. CVE-2025-59014 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-27231.
When was CVE-2025-59014 published?
CVE-2025-59014 was published on 2025-09-09 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Typo3

All CVEs affecting Typo3 →

Other CWE-248 vulnerabilities

Browse all CWE-248 vulnerabilities →