TYPO3CMS
CVE-2012-1607
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 Command Line Interface (CLI) script in TYPO3 4.4.0 through 4.4.13, 4.5.0 through 4.5.13, 4.6.0 through 4.6.6, 4.7, and 6.0 allows remote attackers to obtain the database name via a direct request.
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 CLI script in versions 4.4.0-4.4.13, 4.5.0-4.5.13, 4.6.0-4.6.6, 4.7, and 6.0 contains an information disclosure vulnerability that allows unauthenticated remote attackers to obtain the database name via direct HTTP request to the script.
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
= 4.4= 4.4.0= 4.4.1= 4.4.2= 4.4.3= 4.4.4= 4.4.5= 4.4.6= 4.4.7= 4.4.8= 4.4.9= 4.4.10CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 checking the version in the TYPO3 admin backend under 'Help > About TYPO3'. Compare the version number against the affected ranges: 4.4.0-4.4.13, 4.5.0-4.5.13, 4.6.0-4.6.6, 4.7, or 6.0.Affected if The installed version falls within any of the affected version ranges.
-
Locate CLI scripts in web rootCheck the web document root for the presence of CLI scripts in paths such as 'typo3/cli_dispatch.phpsh', 'typo3/cli Dispatch.php', or similar 'cli_dispatch' files in the typo3 directory.Affected if CLI scripts exist in the web-accessible directory.
-
Test HTTP access to CLI scriptSend an HTTP GET request directly to the CLI script via a web browser or curl command (e.g., curl http://example.com/typo3/cli_dispatch.phpsh). Observe if the script executes and returns database configuration information instead of blocking the request.Affected if The CLI script is accessible via HTTP and returns any database-related information or executes without authentication.
-
Check web server access restrictionsReview web server configuration files (.htaccess, nginx.conf, Apache config) for rules that block or restrict access to CLI scripts in the typo3 directory. Look for directives like 'deny from all' or rewrite rules blocking 'cli_dispatch' patterns.Affected if No access restrictions are configured for CLI scripts, making them directly accessible over HTTP.
A system is affected if it runs any TYPO3 version between 4.4.0 and 4.4.13 (or other affected branches) and has CLI scripts accessible via direct HTTP requests without web server restrictions.
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 dataRestrict access to CLI scripts via web server configuration (e.g., .htaccess rules or IP allowlisting) or upgrade to a patched TYPO3 version.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1607 — 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-2012-1607 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