Menu

Star on GitHub · 3.2k

CVE-2010-0682

4.0 · MEDIUM

WordPress 2.9 before 2.9.2 allows remote authenticated users to read trash posts from other authors via a direct request with a modified p parameter.

Published Feb 23, 2010wordpressCWE-264EPSS 10.04%

Overview

CVE-2010-0682 is a medium-severity vulnerability affecting wordpress wordpress. It was published on February 23, 2010 and has a CVSS 2.0 base score of 4.0 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 4.0, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

WordPress 2.9 before 2.9.2 allows remote authenticated users to read trash posts from other authors via a direct request with a modified p parameter.

Remediation

Check the references section for vendor advisories and patches from wordpress. Update wordpress to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2010-0682?

CVE-2010-0682 is a medium-severity vulnerability affecting wordpress wordpress. It was published on February 23, 2010 and has a CVSS 2.0 base score of 4.0 (MEDIUM).

How severe is CVE-2010-0682?

This vulnerability has a CVSS 2.0 base score of 4.0, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2010-0682?

Check the references section for vendor advisories and patches from wordpress. Update wordpress to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2010-0682?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2010-0682 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2010

View all