TYPO3CMS
CVE-2019-19850
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. Because escaping of user-submitted content is mishandled, the class QueryGenerator is vulnerable to SQL injection. Exploitation requires having the system extension ext:lowlevel installed, and a valid backend user who has administrator privileges.
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 QueryGenerator class in TYPO3 versions 8.x before 8.7.30, 9.x before 9.5.12, and 10.x before 10.2.2 is vulnerable to SQL injection due to improper escaping of user-submitted content. Exploitation requires the lowlevel system extension to be installed and a valid backend user with administrator privileges.
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.0.0, < 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 in the backend under 'Help > About' or in the composer.json file at the web rootAffected if The installed version falls within 8.0.0 to 8.7.29, 9.0.0 to 9.5.11, or 10.0.0 to 10.2.1
-
Verify lowlevel system extension statusIn the TYPO3 backend, navigate to 'Admin Tools > Extensions' and check if the 'lowlevel' extension is loaded. Alternatively, check the typo3/sysext/lowlevel directory exists and is not disabled in the package states configuration.Affected if The lowlevel extension is installed and enabled
-
Confirm administrator backend user existsIn the TYPO3 backend, go to 'Admin Tools > Users' and check for users with administrator privileges, or query the be_users table for rows where admin=1Affected if There is at least one active backend user with administrator privileges
-
Check QueryGenerator accessibilityThe vulnerability resides in the QueryGenerator class (typo3/sysext/lowlevel/Classes/Controller/QueryGeneratorController.php). Verify this file exists and is accessible via the backend module 'Database > Query'Affected if The lowlevel extension is active and the QueryGenerator module is accessible to an administrator user
All conditions must be met: a vulnerable TYPO3 version (8.x before 8.7.30, 9.x before 9.5.12, or 10.x before 10.2.2) with the lowlevel extension installed AND an active administrator backend account.
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 to TYPO3 8.7.30, 9.5.12, or 10.2.2 or later. As a workaround, disable or remove the lowlevel extension if not required, and limit backend administrator access.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19850 — 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-19850 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