CVE-2009-2851: XSS

Published Feb 20, 2009
·
Updated

Cross-site scripting (XSS) vulnerability in the administrator interface in WordPress before 2.8.2 allows remote attackers to inject arbitrary web script or HTML via a comment author URL.

Other sources

From WordPress blog:

WordPress 2.8.2 fixes an XSS vulnerability. Comment author URLs were not fully sanitized when displayed in the admin. This could be exploited to redirect you away from the admin to another site.

References: ----------- http://wordpress.org/development/2009/07/wordpress-2-8-2/ http://bugs.gentoo.org/showbug.cgi?id=278492

Note: Please be sure to mention CVE identifier in the WordPress's rpm Changelog when scheduling Fedora updates / addressing this flaw.

Red Hat

Affected Software

1 affected component
WordPress<=2.8.1

Event History

Feb 20, 2009
CVE Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionSeverityWeakness
Jul 21, 2009
Data Sourced
via Red Hat·09:07 AM
Affected Software
Aug 18, 2009
CVE Published
via MITRE·08:41 PM
Data Sourced
via MITRE·08:41 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2009-2851?

The severity of CVE-2009-2851 is considered medium due to its potential for cross-site scripting attacks.

2

How do I fix CVE-2009-2851?

To fix CVE-2009-2851, upgrade your WordPress installation to version 2.8.2 or later.

3

What types of attacks can CVE-2009-2851 enable?

CVE-2009-2851 can enable remote attackers to execute arbitrary web scripts or HTML through XSS.

4

Which versions of WordPress are affected by CVE-2009-2851?

CVE-2009-2851 affects all versions of WordPress prior to 2.8.2.

5

Where is the CVE-2009-2851 vulnerability located?

The CVE-2009-2851 vulnerability is located in the administrator interface of WordPress.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203