CVE-2011-4899 json
wp-admin/setup-config.php in the installation component in WordPress 3.3.1 and earlier does not ensure that the specified MySQL database se…
published 2012-01-30 14 y ago modified 2026-11-03 6 d ago also EUVD-2011-4816
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.0%
- EPSS 9.0% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
wp-admin/setup-config.php in the installation component in WordPress 3.3.1 and earlier does not ensure that the specified MySQL database service is appropriate, which allows remote attackers to configure an arbitrary database via the dbhost and dbname parameters, and subsequently conduct static code injection and cross-site scripting (XSS) attacks via (1) an HTTP request or (2) a MySQL query. NOTE: the vendor disputes the significance of this issue; however, remote code execution makes the issue important in many realistic environments
Timeline
- First public exploit (EDB-18417)
- Published
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
9.02% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-18417 WordPress Core 3.3.1 - Multiple Vulnerabilities webapps, 2012-01-25
- trustwave.com https://www.trustwave.com/spiderlabs/advisories/TWSL2012-002.txt referenced PoC, tagged "exploit" by a source, unverified
- archives.neohapsis.com http://archives.neohapsis.com/archives/bugtraq/2012-01/0150.html referenced PoC, tagged "exploit" by a source, unverified
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
- Technology feeds
References
-
exploit-db.com
/exploits/18417
exploit
-
trustwave.com
/spiderlabs/advisories/TWSL2012-002.txt
exploit
-
archives.neohapsis.com
/archives/bugtraq/2012-01/0150.html
mailing-list, exploit
Sources
- CVE List CVE-2011-4899
- NVD CVE-2011-4899
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.