CVE-2026-47350

CVE-2026-47350 is a medium-severity missing authorization vulnerability in typo3/cms-core (composer), affecting versions >= 13.0.0, < 13.4.31. It is fixed in 13.4.31, 14.3.3.

Summary

Problem

Backend users were able to move records to a different page without having edit permissions on the source page.

Credits

TYPO3 CMS thanks Hyunseo Shin for reporting this issue, and TYPO3 security team member Torben Hansen for fixing it.

Resources

Impact

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Affected versions

typo3/cms-core (>= 13.0.0, < 13.4.31) typo3/cms-core (>= 14.0.0, < 14.3.3)

Security releases

typo3/cms-core → 13.4.31 (composer) typo3/cms-core → 14.3.3 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Update to TYPO3 versions 13.4.31 LTS, 14.3.3 LTS that fix the problem described.

Frequently Asked Questions

  1. What is CVE-2026-47350? CVE-2026-47350 is a medium-severity missing authorization vulnerability in typo3/cms-core (composer), affecting versions >= 13.0.0, < 13.4.31. It is fixed in 13.4.31, 14.3.3. The application does not perform an authorization check before performing a sensitive operation.
  2. Which versions of typo3/cms-core are affected by CVE-2026-47350? typo3/cms-core (composer) versions >= 13.0.0, < 13.4.31 is affected.
  3. Is there a fix for CVE-2026-47350? Yes. CVE-2026-47350 is fixed in 13.4.31, 14.3.3. Upgrade to this version or later.
  4. Is CVE-2026-47350 exploitable, and should I be worried? Whether CVE-2026-47350 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2026-47350 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2026-47350?
    • Upgrade typo3/cms-core to 13.4.31 or later
    • Upgrade typo3/cms-core to 14.3.3 or later

Other vulnerabilities in typo3/cms-core

CVE-2026-11607CVE-2026-47349CVE-2026-47347CVE-2026-49741CVE-2026-47350

Stop the waste.
Protect your environment with Kodem.