dbcve.org
TYPO3CMS

CVE-2019-11832

HIGH · 7.5 CVSS v3.0 Published 2019-05-09
Fix available
A fix is available. Upgrade to 8.7.25 / 9.5.6 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 before 8.7.25 and 9.x before 9.5.6 allows remote code execution because it does not properly configure the applications used for image processing, as demonstrated by ImageMagick or GraphicsMagick.

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 · moderate confidence

TYPO3 versions 8.x before 8.7.25 and 9.x before 9.5.6 improperly configure ImageMagick and GraphicsMagick image processing libraries, allowing remote code execution through maliciously crafted image files that trigger vulnerable delegate handlers in these libraries.

MitigationUpgrade TYPO3 to version 8.7.25 or 9.5.6 or later. Additionally, review and secure ImageMagick/GraphicsMagick policy configurations by disabling dangerous delegate handlers (such as MSL, PLT, EPUB, etc.) in /etc/ImageMagick/policy.xml.

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.0.0, < 8.7.25>= 9.0.0, < 9.5.6

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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. Identify installed TYPO3 version
    Check the version.php file in the TYPO3 root directory, typically at typo3/sysext/core/Classes/Information/Version.php or inspect the TYPO3 version via the admin backend under 'Help > About TYPO3'. Compare the version number to the affected ranges: 8.0.0 through 8.7.24, or 9.0.0 through 9.5.5.
    Affected if The installed version falls within 8.0.0 to 8.7.24 or 9.0.0 to 9.5.5.
  2. Confirm ImageMagick or GraphicsMagick is enabled
    In the TYPO3 Install Tool, navigate to 'All Configuration' and search for 'im' settings (GFX/im) or check the LocalConfiguration.php file for $GLOBALS['TYPO3_CONF_VARS']['GFX']['im']. Also run 'which convert' or 'which gm' on the server command line.
    Affected if ImageMagick (im) or GraphicsMagick (im_gm) is enabled in TYPO3 configuration.
  3. Locate ImageMagick policy configuration
    Check for the presence of /etc/ImageMagick/policy.xml or /etc/ImageMagick-6/policy.xml. Also inspect any custom policy file paths defined in TYPO3 installation or server configuration.
    Affected if A policy.xml file exists and is readable for inspection.
  4. Inspect dangerous delegate handlers in policy
    Read the ImageMagick policy.xml file and look for entries containing delegate handlers such as MSL (label name="MSL"), PLT, EPUB, or other script-based handlers. Check if these are set to something other than 'disabled' or 'none'.
    Affected if Dangerous delegate handlers like MSL, PLT, or EPUB are not explicitly disabled in the policy configuration.
  5. Check GraphicsMagick configuration if used
    If GraphicsMagick is configured, search for any security policy files in /etc/GraphicsMagick or check the Imagick extension settings in PHP. GraphicsMagick typically uses delegates.xml or similar configuration.
    Affected if GraphicsMagick is in use and has similar vulnerable delegate configurations that are not restricted.

You are affected if TYPO3 version is 8.0.0-8.7.24 or 9.0.0-9.5.5 AND ImageMagick/GraphicsMagick is enabled with dangerous delegate handlers (MSL, PLT, EPUB, etc.) not disabled in the policy configuration.

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 8.7.25 / 9.5.6 or later
Fixed in 8.7.259.5.6
Interim mitigation

Upgrade TYPO3 to version 8.7.25 or 9.5.6 or later. Additionally, review and secure ImageMagick/GraphicsMagick policy configurations by disabling dangerous delegate handlers (such as MSL, PLT, EPUB, etc.) in /etc/ImageMagick/policy.xml.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11832 — 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-11832 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