Slub EventsTYPO3 extension · Slub Dresden
CVE-2019-16700
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 · uneditedThe slub_events (aka SLUB: Event Registration) extension through 3.0.2 for TYPO3 allows uploading of arbitrary files to the webserver. For versions 1.2.2 and below, this results in Remote Code Execution. In versions later than 1.2.2, this can result in Denial of Service, since the web space can be filled up with arbitrary files.
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 slub_events TYPO3 extension through version 3.0.2 contains an arbitrary file upload vulnerability allowing attackers to upload any file type to the webserver. In versions 1.2.2 and below, this enables remote code execution; in later versions it causes denial of service by filling web space.
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
Slub EventsTYPO3 extension
<= 3.0.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify slub_events extension presenceLog into the TYPO3 backend and navigate to the Extension Manager, or use the CLI command 'typo3cms extension:list' to check if slub_events is installed.Affected if The slub_events extension appears in the list of installed extensions.
-
Determine installed extension versionIn the TYPO3 Extension Manager, click on the slub_events extension to view its version details, or use 'typo3cms extension:list --verbose' to confirm the exact version number.Affected if The installed version is 3.0.2 or any version lower than 3.0.2.
-
Confirm extension is activeCheck the Extension Manager status column to verify slub_events is not only installed but also actively loaded and not disabled.Affected if The extension shows as active or enabled in the TYPO3 system.
-
Inspect upload directories for suspicious filesSearch the file system for any recently created or unexpected files, particularly in common upload paths such as uploads/tx_slubevents/ or similar directories under the TYPO3 installation root.Affected if Unexpected or unknown files are present in upload directories, especially executable files (.php, .phtml, .exe) or large numbers of files.
You are affected if the slub_events extension is installed, active, and running version 3.0.2 or lower in your TYPO3 installation.
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 dataImmediately disable or remove the slub_events extension from the TYPO3 installation. If a patched version exists, update to the latest secure release; otherwise, ensure the extension is completely removed and any maliciously uploaded files are identified and removed.
Fix this in Slub Events
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16700 — 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-16700 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