dbcve.org
TYPO3CMS

CVE-2019-12747

HIGH · 8.8 CVSS v3.1 Published 2019-07-09
Fix available
A fix is available. Upgrade to after 9.5.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
TYPO3 8.x through 8.7.26 and 9.x through 9.5.7 allows Deserialization of Untrusted Data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a PHP deserialization vulnerability in TYPO3 CMS versions 8.x through 8.7.26 and 9.x through 9.5.7. The application deserializes untrusted data (likely via PHP's unsafe unserialize() function), which can allow remote code execution if an attacker can inject malicious serialized PHP objects.

MitigationUpgrade TYPO3 to version 8.7.27 or later for the 8.x branch, or 9.5.8 or later for the 9.x branch. If immediate patching is not possible, review and restrict any user-controlled input that reaches deserialization logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TYPO3CMS
Affected:>= 8.3.0, <= 8.7.26>= 9.0.0, <= 9.5.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed TYPO3 version
    Locate the version file or composer.json in your TYPO3 installation root and read the installed version number
    Affected if The installed version is 8.3.0 through 8.7.26, or 9.0.0 through 9.5.7
  2. Confirm TYPO3 branch
    Check whether your installation is on the 8.x or 9.x branch based on the version number identified
    Affected if The branch is 8.x or 9.x and falls within the affected version ranges
  3. Verify deserialization usage
    Search the codebase for usage of PHP unserialize() function receiving input from request parameters, POST data, or user-controlled sources
    Affected if User-supplied data reaches an unserialize() call without prior validation
  4. Identify exposed entry points
    Review which frontend or backend routes, extensions, or APIs accept serialized data that could be manipulated by an attacker
    Affected if Any publicly accessible endpoint processes untrusted serialized PHP objects

You are affected if your TYPO3 version falls within 8.3.0-8.7.26 or 9.0.0-9.5.7 AND your application deserializes untrusted input from user sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 9.5.7
Interim mitigation

Upgrade TYPO3 to version 8.7.27 or later for the 8.x branch, or 9.5.8 or later for the 9.x branch. If immediate patching is not possible, review and restrict any user-controlled input that reaches deserialization logic.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing12.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12747 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-12747 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data