Branchenbuch ExtensionPlugin / extension · TYPO3
CVE-2008-3054
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 Branchenbuch (aka Yellow Pages o (mh_branchenbuch) extension 0.8.1 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 Branchenbuch (mh_branchenbuch) TYPO3 extension versions 0.8.1 and earlier allows remote attackers to execute arbitrary SQL commands through unsanitized user input in 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
Branchenbuch ExtensionPlugin / extension
<= 0.8.1CVSS 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.
-
Verify if mh_branchenbuch extension is installedAccess TYPO3 extension manager or check typo3conf/ext/ for mh_branchenbuch directoryAffected if The mh_branchenbuch directory exists in the extensions folder
-
Check installed version of mh_branchenbuchOpen extension configuration or ext_emconf.php file within the mh_branchenbuch extension directory and locate the version numberAffected if The reported version is 0.8.1 or lower
-
Determine if extension database queries handle user inputReview extension PHP files for database query implementations, specifically look for user-supplied parameters being passed directly to SQL queries without sanitizationAffected if User input parameters are used in SQL queries without prepared statements or input escaping
-
Inspect database for signs of compromiseReview database logs or table records for unexpected entries, unknown admin accounts, or suspicious queries that may indicate exploitationAffected if Unexpected database changes, unknown user accounts, or suspicious query patterns are found
You are affected if the mh_branchenbuch extension is installed and its version is 0.8.1 or earlier, with unescaped user input reaching 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 mh_branchenbuch extension to a patched version if available; otherwise uninstall the extension immediately. Review and sanitize database queries, implement parameterized queries, and audit the application for any signs of compromise.
Fix this in Branchenbuch Extension
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-3054 — 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-2008-3054 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