Mm WhtpprApplication · TYPO3
CVE-2012-1074
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 · uneditedSQL injection vulnerability in the White Papers (mm_whtppr) extension 0.0.4 and earlier for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
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 · moderate confidenceSQL injection vulnerability in the White Papers (mm_whtppr) TYPO3 extension versions 0.0.4 and earlier allows remote attackers to execute arbitrary SQL commands through unspecified vectors in the extension's database queries.
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
Mm WhtpprApplication
<= 0.0.4CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Check if the mm_whtppr extension is installedAccess the TYPO3 Extension Manager in the backend and look for 'mm_whtppr' or 'White Papers' in the list of installed extensions, or query the typo3 extension database table for this extensionAffected if The extension appears in the list of installed extensions
-
Verify the installed version of mm_whtpprIn the TYPO3 Extension Manager, view the details of the mm_whtppr extension to see its version number, or check the ext_emconf.php file in the extension directoryAffected if The version is 0.0.4 or any version lower than 0.0.4
-
Confirm the extension is active and loadedCheck the TYPO3 system extension list or the 'ext' column in the 'tt_content' or related tables if the extension adds content elements, or verify the extension is not disabled in the Extension ManagerAffected if The extension is loaded and enabled in the TYPO3 instance
-
Check if the extension database tables existQuery the TYPO3 database for tables that may have been created by the mm_whtppr extension, such as those prefixed with 'tx_mmwhtppr' or similar naming patternsAffected if The extension's database tables exist in the TYPO3 database
You are affected if the mm_whtppr extension is installed, enabled, and running at version 0.0.4 or earlier, as this version contains the SQL injection vulnerability in its database queries.
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 dataUpdate the mm_whtppr extension to a patched version if available; otherwise remove the extension from the TYPO3 installation. Alternatively, disable the extension until a fix is released and review the extension's database query code for proper parameterized queries.
Fix this in Mm Whtppr
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1074 — 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-1074 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