CVE-2012-5651 json
Drupal 6.x before 6.27 and 7.x before 7.18 displays information for blocked users, which might allow remote attackers to obtain sensitive i…
published 2013-01-03 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5535
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Drupal 6.x before 6.27 and 7.x before 7.18 displays information for blocked users, which might allow remote attackers to obtain sensitive information by reading the search results.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-5651 updated cvss 5.1
drupal: multiple flaws fixed in 6.27/7.18 (SA-CORE-2012-004)
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.75% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
drupalcode.org
/project/drupal.git/commitdiff/da8023a
patch
-
drupal.org
/SA-CORE-2012-004
patch, vendor-advisory
-
drupalcode.org
/project/drupal.git/commitdiff/b47f95d
patch
-
mandriva.com
/security/advisories?name=MDVSA-2013:074
vendor-advisory
-
debian.org
/security/2013/dsa-2776
vendor-advisory
-
securityfocus.com
/bid/56993
vdb-entry
-
osvdb.org
/88528
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/80792
vdb-entry
-
openwall.com
/lists/oss-security/2012/12/20/1
mailing-list
Sources
- CVE List CVE-2012-5651
- NVD CVE-2012-5651
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.