CVE-2005-1688
First published: Fri May 20 2005(Updated: )
Wordpress 1.5 and earlier allows remote attackers to obtain sensitive information via a direct request to files in (1) wp-content/themes/, (2) wp-includes/, or (3) wp-admin/, which reveal the path in an error message.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | <=1.5 |
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-2005-1688?
CVE-2005-1688 is considered to have a medium severity due to the potential for information disclosure.
How do I fix CVE-2005-1688?
Upgrading to WordPress version 1.5.1 or later mitigates the risk associated with CVE-2005-1688.
What type of information can be disclosed by CVE-2005-1688?
CVE-2005-1688 allows for the disclosure of file paths through error messages triggered by direct requests to specific WordPress directories.
Which versions of WordPress are affected by CVE-2005-1688?
CVE-2005-1688 affects all versions of WordPress up to and including 1.5.
What are the impacted directories related to CVE-2005-1688?
The impacted directories for CVE-2005-1688 include wp-content/themes/, wp-includes/, and wp-admin/.
- agent/type
- agent/first-publish-date
- agent/weakness
- agent/author
- agent/softwarecombine
- agent/references
- agent/description
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- collector/nvd-historical
- vendor/wordpress
- canonical/wordpress
- version/wordpress/1.5