WordPress component: A security weakness

WordPress component is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 5.0 CVSS · cve@mitre.org

NVD score 5.0 CVSS 2.0 · nvd@nist.gov

Component: WordPress component
Plugin slug: Not applicable
Affected: See vendor advisory
Safe version: See mitigation notes
Published: Dec 21, 2005
Weakness: NVD-CWE-Other

What to do

Update, patch or deactivate.

Update WordPress component to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

WordPress before 1.5.2 allows remote attackers to obtain sensitive information via a direct request to (1) wp-includes/vars.php, (2) wp-content/plugins/hello.php, (3) wp-admin/upgrade-functions.php, (4) wp-admin/edit-form.php, (5) wp-settings.php, and (6) wp-admin/edit-form-comment.php, which leaks the path in an error message related to undefined functions or failed includes. NOTE: the wp-admin/menu-header.php vector is already covered by CVE-2005-2110. NOTE: the vars.php, edit-form.php, wp-settings.php, and edit-form-comment.php vectors were also reported to affect WordPress 2.0.1.

NVD vector: AV:N/AC:L/Au:N/C:P/I:N/A:N

References

Update, patch or deactivate.

Technical description

Primary and upstream sources