Another Backend LoginApplication · TYPO3
CVE-2008-5087
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 TYPO3 Another Backend Login (wrg_anotherbelogin) extension before 0.0.4 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 · high confidenceSQL injection vulnerability in the TYPO3 'wrg_anotherbelogin' (Another Backend Login) extension versions prior to 0.0.4 allows remote attackers to execute arbitrary SQL commands via unspecified vectors. The vulnerability stems from improper input sanitization in the extension's backend login functionality, enabling attackers to manipulate SQL 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
Another Backend LoginApplication
<= 0.0.3= 0.0.1= 0.0.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
- 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 wrg_anotherbelogin extension is installedCheck the TYPO3 Extension Manager or inspect the directory typo3conf/ext/wrg_anotherbelogin for the presence of extension filesAffected if The extension directory exists and contains extension files
-
Determine the installed version of wrg_anotherbeloginOpen the ext_emconf.php file in the extension directory and read the version number from the $EM_CONF arrayAffected if The version is 0.0.3, 0.0.2, 0.0.1, or any version <= 0.0.3
-
Confirm the extension is enabledCheck the TYPO3 backend under Admin Tools > Extension Manager or inspect the ext_tables.sql and localconf.php/LocalConfiguration.php for active extension statusAffected if The extension is loaded and active in the TYPO3 installation
-
Inspect backend login-related files for vulnerable code patternsSearch the extension directory for files handling login functionality (such as pi1/class.tx_wrganotherbelogin_pi1.php or similar) and inspect for unsanitized database query constructionAffected if Login handling code contains SQL queries built without proper input sanitization using parameters like $this->db->sql_escape() or prepared statements
-
Review access logs for SQL injection attemptsExamine web server access logs and TYPO3 logs for unusual SQL syntax or quote characters in login-related request parametersAffected if Logs contain SQL injection payloads targeting the backend login functionality
You are affected if the wrg_anotherbelogin extension is installed, enabled, and running version 0.0.3 or lower in a TYPO3 environment.
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 wrg_anotherbelogin extension to version 0.0.4 or later which contains the security patch. If upgrading is not feasible, disable or remove the extension until a patch can be applied. Review extension usage logs for signs of exploitation.
Fix this in Another Backend Login
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-5087 — 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-5087 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