dbcve.org
Toi CategoryApplication · TYPO3

CVE-2012-1072

HIGH · 7.5 CVSS v2.0 Published 2012-02-14
Fix available
A fix is available. Upgrade to after 0.6.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
SQL injection vulnerability in the Category-System (toi_category) extension 0.6.0 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 confidence

SQL injection vulnerability in the toi_category extension for TYPO3 allows remote attackers to execute arbitrary SQL commands through unsanitized input in database queries.

MitigationUpdate the toi_category extension to a version beyond 0.6.0, or disable the extension until a patch is available. If immediate patching is not possible, implement input validation or a WAF rule as a temporary workaround.

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
Toi CategoryApplication
Affected:<= 0.6.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the toi_category extension files
    Check for the presence of the toi_category extension directory in your TYPO3 installation. Typical paths include typo3conf/ext/toi_category or under the main ext/ directory depending on TYPO3 version.
    Affected if The toi_category extension directory exists in your TYPO3 extensions folder
  2. Identify the installed extension version
    Open the ext_emconf.php file within the toi_category extension directory and read the version number defined in the $EM_CONF array.
    Affected if The version number returned is 0.6.0 or lower (any version up to and including 0.6.0)
  3. Verify the extension is loaded and active
    Access the TYPO3 Extension Manager or check the typo3conf/localconf.php (or equivalent configuration file for your TYPO3 version) for the extension key 'toi_category' in the loaded extension list.
    Affected if The extension appears in the list of installed or active extensions and meets the version condition above

You are affected if the toi_category extension is installed and active at version 0.6.0 or lower.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 0.6.0
Interim mitigation

Update the toi_category extension to a version beyond 0.6.0, or disable the extension until a patch is available. If immediate patching is not possible, implement input validation or a WAF rule as a temporary workaround.

Fix this in Toi Category Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-1072 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-1072 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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