CVE-2008-3747 json
The (1) get_edit_post_link and (2) get_edit_comment_link functions in wp-includes/link-template.php in WordPress before 2.6.1 do not force…
published 2008-08-27 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3733
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
The (1) get_edit_post_link and (2) get_edit_comment_link functions in wp-includes/link-template.php in WordPress before 2.6.1 do not force SSL communication in the intended situations, which might allow remote attackers to gain administrative access by sniffing the network for a cookie.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 2.5.1-6
debian advisories DEBIAN-CVE-2008-3747
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-2008-3747 updated
wordpress: insufficient SSL communication enforcement
-
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.55% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
- Technology feeds
References
-
trac.wordpress.org
/ticket/7359
patch
-
openwall.com
/lists/oss-security/2008/08/20/3
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44569
vdb-entry
-
securityfocus.com
/bid/30750
vdb-entry
-
openwall.com
/lists/oss-security/2008/08/19/1
mailing-list
Sources
- CVE List CVE-2008-3747
- NVD CVE-2008-3747
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.