CVE-2011-3818: Infoleak
First published: Sat Sep 24 2011(Updated: )
WordPress 2.9.2 and 3.0.4 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by wp-admin/includes/user.php and certain other files.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | =3.0.4 | |
| WordPress | =2.9.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2011-3818?
CVE-2011-3818 is classified as a moderate severity vulnerability that allows unauthorized access to sensitive information.
How do I fix CVE-2011-3818?
To fix CVE-2011-3818, upgrade your WordPress installation to a version later than 3.0.4 or 2.9.2.
Which versions of WordPress are affected by CVE-2011-3818?
CVE-2011-3818 affects WordPress versions 2.9.2 and 3.0.4.
What type of information can be exposed due to CVE-2011-3818?
CVE-2011-3818 can expose the installation path of the WordPress application in error messages.
Can CVE-2011-3818 be exploited remotely?
Yes, CVE-2011-3818 can be exploited remotely through direct requests to certain .php files.
- agent/type
- agent/softwarecombine
- agent/references
- agent/weakness
- agent/author
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/wordpress
- canonical/wordpress
- version/wordpress/3.0.4
- version/wordpress/2.9.2