DrupalCMS
CVE-2012-2306
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 Addressbook module for Drupal 6.x-4.2 and earlier 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 Drupal Addressbook module allows remote attackers to execute arbitrary SQL commands through unspecified vectors. The vulnerability affects versions 6.x-4.2 and earlier of the module. Successful exploitation could allow attackers to read, modify, or delete database contents including user credentials and sensitive data.
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
DrupalCMS
all versionsCVSS 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 Addressbook module presenceCheck the Drupal modules directory for the addressbook folder. On typical installations, this is in sites/all/modules/ or sites/all/modules/contrib/. Also check the system table in the Drupal database for the addressbook module record.Affected if The Addressbook module directory exists in the modules folder or a record exists in the Drupal system table for the addressbook module.
-
Determine installed Addressbook versionIf the module is present, locate the addressbook.info or addressbook.module file and read the version string from the header. Alternatively, query the system table: SELECT schema_version FROM system WHERE name = 'addressbook'; Compare this version against 6.x-4.2 and earlier.Affected if The installed version is 6.x-4.2 or any version earlier than 6.x-4.2.
-
Confirm if module is enabledQuery the system table: SELECT status FROM system WHERE name = 'addressbook'; A status value of 1 indicates the module is enabled. Alternatively, check in Drupal admin UI at Administer > Modules.Affected if The module status is set to enabled (status = 1).
-
Inspect for SQL injection indicatorsReview database query logs, Apache logs, or Drupal watchdog logs for unusual SQL syntax, UNION SELECT statements, OR 1=1 patterns, or unexpected queries targeting the addressbook table. Check for any unauthorized changes to user credentials or addressbook data.Affected if Log analysis reveals SQL injection patterns in requests or unexpected database activity related to the addressbook module.
You are affected if the Addressbook module is installed, enabled, and running version 6.x-4.2 or earlier.
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 Addressbook module to a patched version. If immediate updating is not feasible, disable the Addressbook module until a fix can be applied. Review Drupal's SQL injection prevention best practices for future hardening.
Fix this in Drupal
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2306 — 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-2306 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