Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2009-2335: Username Enumeration in WordPress <2.8.1

Published Jul 10, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.0Medium · v2
EPSS85.0%100th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Wordpress
IdentifiersCVE-2009-2335CWE-203

WordPress and WordPress MU versions prior to 2.8.1 allow remote attackers to enumerate valid usernames by observing the application's response to failed login attempts. The application exhibits different behavior depending on whether the username exists, thus leaking information about valid accounts.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Attackers can enumerate valid usernames, which can be leveraged in subsequent attacks such as brute-force password guessing, targeted phishing, or social engineering. This increases the attack surface by making it easier to identify valid accounts.

Mitigation

If you can’t patch tonight, do this now.

As an interim measure, implement custom error messages that do not reveal whether a username exists. Employ rate limiting and account lockout mechanisms to reduce the risk of automated enumeration and brute-force attacks.

Remediation

Patch, then assume compromise.

Upgrade to WordPress or WordPress MU version 2.8.1 or later, where this behavior is addressed. Ensure that login failure responses are uniform regardless of whether the username exists.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
WordpressWordpressapplication
WordpressWordpress Muapplication
FAQ

Frequently asked questions

Is CVE-2009-2335 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-2335 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-2335?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2009-2335.
Is there a patch for CVE-2009-2335?
Upgrade to WordPress or WordPress MU version 2.8.1 or later, where this behavior is addressed. Ensure that login failure responses are uniform regardless of whether the username exists.
What products are affected by CVE-2009-2335?
Wordpress and Wordpress Mu.
How severe is CVE-2009-2335?
CVE-2009-2335 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 85.0% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.