Radar sectionsDatabase
Check my site
WordPress wordpress core

WordPress Core <= 2.8 — Sensitive Information Disclosure

CVE-2009-2334Published · Updated

Action summary

WordPress: Affected: ≤2.8Update to 2.8.1 or newer

WordPress MU: Affected: ≤2.8Update to 2.8.1 or newer

All remediation steps
Severity
Medium6.1
CVSS
6.1
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:R User interaction
Required
S:C Scope
Changed
C:L Confidentiality
Low
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-200 Information Exposure
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

WordPress wordpress

  1. Affected≤ 2.8
  2. Patched in2.8.1

Update to 2.8.1 or newer.

You are affected if you run ≤ 2.8. Version 2.8.1 and later are not affected by this issue.

WordPress MU wpmu

  1. Affected≤ 2.8
  2. Patched in2.8.1

Update to 2.8.1 or newer.

You are affected if you run ≤ 2.8. Version 2.8.1 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WordPress.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.8.1, or a newer patched version
  2. Update to version 2.8.1, or a newer patched version
  3. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  4. Watch WordPress to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Core Security Technologies.

wp-admin/admin.php in WordPress and WordPress MU before 2.8.1 does not require administrative authentication to access the configuration of a plugin, which allows remote attackers to specify a configuration file in the page parameter to obtain sensitive information or modify this file, as demonstrated by the (1) collapsing-archives/options.txt, (2) akismet/readme.txt, (3) related-ways-to-take-action/options.php, (4) wp-security-scan/securityscan.php, and (5) wp-ids/ids-admin.php files. NOTE: this can be leveraged for cross-site scripting (XSS) and denial of service.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

Same weakness (Information Exposure)

All Information Exposure
Other Information Exposure vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 6.1

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?