CVE-2009-1030 json
Cross-site scripting (XSS) vulnerability in the choose_primary_blog function in wp-includes/wpmu-functions.php in WordPress MU (WPMU) befor…
published 2009-03-20 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1031
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.7%
- EPSS 4.7% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site scripting (XSS) vulnerability in the choose_primary_blog function in wp-includes/wpmu-functions.php in WordPress MU (WPMU) before 2.7 allows remote attackers to inject arbitrary web script or HTML via the HTTP Host header.
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-1030 updated
wordpress-mu: XSS vulnerability in helper function for WPMU
-
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
Timeline
- First public exploit (EDB-8196)
- Published
Exploit prediction
4.66% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-8196 WordPress MU < 2.7 - 'HOST' HTTP Header Cross-Site Scripting webapps, 2009-03-10
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
exploit-db.com
/exploits/8196
exploit
-
marc.info
/?l=bugtraq&m=126996727024732&w=2
vendor-advisory
-
securityfocus.com
/bid/34075
vdb-entry
-
securitytracker.com
/id?1021838
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/49184
vdb-entry
-
securityfocus.com
/archive/1/501667/100/0/threaded
mailing-list
Sources
- CVE List CVE-2009-1030
- NVD CVE-2009-1030
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.