DrupalCMS
CVE-2014-1475
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 · uneditedThe OpenID module in Drupal 6.x before 6.30 and 7.x before 7.26 allows remote OpenID users to authenticate as other users 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 confidenceThis is an authentication bypass vulnerability in Drupal's OpenID module affecting versions 6.x before 6.30 and 7.x before 7.26. The flaw allows remote attackers to potentially authenticate as other users by exploiting unspecified vectors in the OpenID authentication flow.
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
= 7.0= 7.1= 7.2= 7.10= 7.11= 7.12= 7.13= 7.14= 7.15= 7.16= 7.17= 7.18CVSS 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 OpenID module is enabledLog in to Drupal admin panel and navigate to Modules (admin/modules), or query the database: SELECT name, status FROM system WHERE name = 'openid' AND type = 'module';Affected if The OpenID module status is 1 (enabled)
-
Check installed Drupal core versionCheck the CHANGELOG.txt file in the Drupal root directory for the version number, or query the database: SELECT filename, info FROM system WHERE name = 'system' AND type = 'module'; then parse the version from the info column, or look at the VERSION constant in includes/bootstrap.incAffected if The installed version is 7.x where x is less than 26 (e.g., 7.0 through 7.25), or 6.x where x is less than 30
-
Inspect OpenID user associationsQuery the database table openid_associations or openid_identities if present: SELECT * FROM openid_identities; to see if any users have linked OpenID identitiesAffected if Any rows exist in openid_identities table showing users with linked OpenID providers
-
Review OpenID authentication logsCheck Drupal logs ( watchdog table ) for OpenID-related entries around authentication events: SELECT * FROM watchdog WHERE type = 'openid' ORDER BY timestamp DESC;Affected if Recent OpenID authentication attempts are logged in the system
You are affected if the OpenID module is enabled AND your Drupal core version is 7.x before 7.26 or 6.x before 6.30, and OpenID is actively used for authentication.
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 Drupal core to version 6.30 or 7.26 or later to patch the OpenID module vulnerability. If immediate patching is not possible, disable the OpenID module until the update can be applied.
Fix this in Drupal
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1475 — 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-2014-1475 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