CVE-2009-2431 json
WordPress 2.7.1 places the username of a post's author in an HTML comment, which allows remote attackers to obtain sensitive information by…
published 2009-07-10 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-2426
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
WordPress 2.7.1 places the username of a post's author in an HTML comment, which allows remote attackers to obtain sensitive information by reading the HTML source.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 2.8.3-1
debian advisories DEBIAN-CVE-2009-2431
- osvdb.org/55716 patch
- vupen.com/english/advisories/2009/1833 advisory
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-2009-2431 updated
wordpress: multiple vulnerabilities
-
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.87% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
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-20 Improper Input Validation
- Technology feeds
References
-
osvdb.org
/55716
vdb-entry, patch
-
vupen.com
/english/advisories/2009/1833
vdb-entry, patch, vendor-advisory
- corelabs.coresecurity.com /index.php?action=view&type=advisory&name=WordPress_Privileges_Unchecked
-
exchange.xforce.ibmcloud.com
/vulnerabilities/51733
vdb-entry
-
securityfocus.com
/archive/1/504795/100/0/threaded
mailing-list
-
securitytracker.com
/id?1022528
vdb-entry
Sources
- CVE List CVE-2009-2431
- NVD CVE-2009-2431
Fencer Vulns 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.