CVE-2019-16699
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 sr_freecap (aka freeCap CAPTCHA) extension 2.4.5 and below and 2.5.2 and below for TYPO3 fails to sanitize user input, which allows execution of arbitrary Extbase actions, resulting in Remote Code Execution.
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 sr_freecap (freeCap CAPTCHA) extension for TYPO3 versions 2.4.5 and below and 2.5.2 and below fails to properly sanitize user input, allowing attackers to invoke arbitrary Extbase actions. This vulnerability can be exploited to achieve remote code execution on the affected TYPO3 instance.
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>= 2.4.0, <= 2.4.5>= 2.5.0, <= 2.5.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.
-
Identify if sr_freecap extension is installedCheck the TYPO3 Extension Manager list of installed extensions, or inspect the directory typo3conf/ext/ for a folder named sr_freecapAffected if The sr_freecap folder exists in typo3conf/ext/ or the extension appears in the installed extensions list
-
Determine installed sr_freecap versionOpen the file ext_emconf.php or composer.json within the sr_freecap extension directory and read the 'version' fieldAffected if The reported version falls within 2.4.0 to 2.4.5 inclusive, or 2.5.0 to 2.5.2 inclusive
-
Verify if the extension is actively enabledIn the TYPO3 Extension Manager, confirm the extension status shows as 'Loaded' or 'Active'. Alternatively, check the ext_localconf.php file is being loaded by TYPO3Affected if The extension is loaded and processing requests, not merely installed but disabled
-
Confirm Extbase framework is in useCheck if any TYPO3 extensions using the Extbase framework are installed (typically in typo3conf/ext/ or typo3/sysext/extbase), or inspect the TYPO3 bootstrap configurationAffected if Extbase is available on the system, which is required for the arbitrary action invocation vulnerability to be exploitable
Your environment is affected if the sr_freecap extension is installed with a version between 2.4.0-2.4.5 or 2.5.0-2.5.2 and the extension is currently enabled on a TYPO3 instance with Extbase available.
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 update the sr_freecap extension to a version newer than 2.4.5 and 2.5.2. If no patched version is available, disable or uninstall the extension until a fix is released.
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16699 — 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-16699 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