TYPO3CMS
CVE-2019-19848
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 · uneditedAn issue was discovered in TYPO3 before 8.7.30, 9.x before 9.5.12, and 10.x before 10.2.2. It has been discovered that the extraction of manually uploaded ZIP archives in Extension Manager is vulnerable to directory traversal. Admin privileges are required in order to exploit this vulnerability. (In v9 LTS and later, System Maintainer privileges are also required.)
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 confidenceThe TYPO3 Extension Manager's ZIP archive extraction feature does not properly sanitize file paths during extraction, allowing an authenticated administrator or system maintainer to craft malicious ZIP files containing path traversal sequences (e.g., ../../../) that write files to arbitrary locations on the server filesystem.
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
< 8.7.30>= 9.0.0, < 9.5.12>= 10.0.0, < 10.2.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed TYPO3 versionCheck the TYPO3 version by viewing the file typo3/sysext/core/Classes/Information/Typo3Version.php or by accessing the TYPO3 admin backend under 'Admin Tools > About'. Alternatively, check composer.json if using Composer-based installation.Affected if The installed version falls into any of these ranges: < 8.7.30, >= 9.0.0 and < 9.5.12, or >= 10.0.0 and < 10.2.2.
-
Confirm administrator or System Maintainer accessLog into the TYPO3 backend and navigate to 'Admin Tools > Users' to list all backend users. Check their role assignments to identify accounts with Administrator or System Maintainer privileges.Affected if Any user account with Administrator or System Maintainer role exists in the TYPO3 installation, as these roles are required to access the Extension Manager.
-
Verify Extension Manager is accessibleNavigate to the TYPO3 backend and confirm access to the Extension Manager module (usually under 'Admin Tools > Extensions' or 'Extensions > Extension Manager' depending on version).Affected if The Extension Manager module is accessible to any Administrator or System Maintainer user account.
-
Review recent extension installationsCheck the typo3temp/var/log/ directory for any Extension Manager related log files, or review the sys_log database table for recent records involving extension installation or import actions.Affected if Any ZIP-based extension installation or import was performed recently, as this is the attack vector for path traversal.
You are affected if your TYPO3 version is below 8.7.30, between 9.0.0-9.5.11, or between 10.0.0-10.2.1 AND you have administrator or System Maintainer accounts that can access the Extension Manager.
Generated from the published advisory. Verify against your own configuration.
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 data8.7.309.5.1210.2.2
Upgrade TYPO3 to version 8.7.30, 9.5.12, or 10.2.2 or later. Additionally, restrict admin and System Maintainer privileges to only trusted users since these roles are required for exploitation.
Fix this in TYPO3
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19848 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-19848 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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