CVE-2011-4898
Reported by mitre · Published January 30, 2012
wp-admin/setup-config.php in the installation component in WordPress 3.3.1 and earlier generates different error messages for requests lacking a dbname parameter depending on whether the MySQL credentials are valid, which makes it easier for remote attackers to conduct brute-force attacks via a series of requests with different uname and pwd parameters. NOTE: the vendor disputes the significance of this issue; also, it is unclear whether providing intentionally vague error messages during installation would be reasonable from a usability perspective
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| wordpress | wordpress | 3.3.1 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
| n/a | n/a | * |
| wordpress | wordpress |
Timeline
- Jan 25, 2012 PoC Published
- Jan 30, 2012 CVE Published
- Feb 4, 2022 EPSS Score (30 in total, the first dated here)
- Apr 11, 2025 CVE Updated
- Apr 5, 2026 Security Advisory
- Oct 29, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2011-4898
vulnetix vdb fixes CVE-2011-4898
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2011-4898/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- 18417 exploitx_refsource_EXPLOIT-DB
- x_refsource_MISC
- 20120124 TWSL2012-002: Multiple Vulnerabilities in WordPress mailing-listx_refsource_BUGTRAQ