Skip to main content
Mallory
MediumVulnerability

CVE-2009-2851: XSS in WordPress Admin Interface via Comment Author URL

Published Aug 18, 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.
CVSS4.3Medium · v2
EPSS7.9%95th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Wordpress
IdentifiersCVE-2009-2851CWE-79 · Improper Neutralization of Input…

A cross-site scripting (XSS) vulnerability exists in the administrator interface of WordPress versions prior to 2.8.2. The vulnerability allows remote attackers to inject arbitrary web script or HTML by supplying a crafted comment author URL, which is not properly sanitized before being rendered in the admin interface.

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.

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of the WordPress administrator's browser session. This can lead to session hijacking, privilege escalation, or the execution of administrative actions on behalf of the victim.

Mitigation

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

As a temporary mitigation, restrict access to the WordPress admin interface to trusted IP addresses and ensure that administrators do not click on untrusted comment author URLs. Additionally, consider using web application firewalls (WAFs) to filter malicious input.

Remediation

Patch, then assume compromise.

Upgrade WordPress to version 2.8.2 or later, where the input validation and output encoding for comment author URLs in the admin interface have been corrected to prevent XSS.

Public exploits

Exploits

No validated public exploits yet. Hidden: 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
FAQ

Frequently asked questions

Is CVE-2009-2851 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-2851 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-2851?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2009-2851. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2009-2851?
Upgrade WordPress to version 2.8.2 or later, where the input validation and output encoding for comment author URLs in the admin interface have been corrected to prevent XSS.
What products are affected by CVE-2009-2851?
Wordpress.
How severe is CVE-2009-2851?
CVE-2009-2851 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 7.9% (95th 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.