WordPress Vulnerability Database

Search All Vulnerabilities

Tip: You can search by CVE ID, software name or slug, or the researcher name. Expand to read about more advanced search options.

If you want to perform more advanced lookups, you can use keywords to further refine your search.

For example, woocommerce researcher:"chloe chamberland" would search for any vulnerabilities discovered by Chloe Chamberland in software that has WooCommerce in the title.

Keywords are added in keyword:value format. If the value contains spaces, you must enclose it in quotation marks.

You can use the following keywords to add criteria to your search:

title
Searches through the title of each vulnerability for matches.
date
Returns vulnerabilities by publication date. Use YYYY-MM-DD, YYYY-MM or YYYY format.
cvss-rating
Use low, medium, high or critical to limit the search to vulnerabilities with the specified rating.
researcher
Returns vulnerabilities credited to researchers containing the given text.
software
Returns vulnerabilities discovered in software containing the given text.
software-slug
Returns vulnerabilities discovered in software exactly matching the given slug.
software-type
Use plugin, theme or core to limit the search to the specified type of software.
By selecting “Search” you acknowledge that you have read and agree to the Wordfence Intelligence Terms and Conditions.

All Vulnerabilities

5.3
CVE ID Unknown
Dec 15, 2010
Researcher: TheLightCosine
Title CVE ID CVSS Researchers Date
WordPress Core <= 3.0.3 - Cross-Site Scripting CVE-2010-4536 6.4 Mauro Gentile, Jon Cave December 29, 2010
Embedded Video <= 4.1 - Cross-Site Scripting CVE-2010-4277 7.1 Wagner Elias December 17, 2010
CformsII <= 14.10.1 - CAPTCHA Bypass 5.3 TheLightCosine December 15, 2010
WP Safe Search <= 0.7 - Cross-Site Scripting CVE-2010-4518 6.1 John Leitch December 8, 2010
WordPress Processing Embed <= 0.5.1 - Cross-Site Scripting CVE-2010-4747 6.1 John Leitch December 8, 2010
WordPress Core < 3.0.3 - Access Control Bypass CVE-2010-5106 6.3 December 8, 2010
Peadig's Twitter Feed: Embedded Timeline WordPress Plugin <= 2.2 - Reflected Cross-Site Scripting CVE-2010-4825 7.1 John Leitch December 7, 2010
WPtouch < 1.9.20 - Cross-Site Scripting CVE-2010-4779 6.1 High-Tech Bridge Security Research Lab December 1, 2010
WordPress Core < 3.0.2 - Spam Protection Bypass CVE-2010-5293 5.3 November 30, 2010
WordPress Core < 3.0.2 - Cross-Site Scripting CVE-2010-5295 6.4 November 30, 2010
WordPress Core <= 3.0.1 - SQL Injection CVE-2010-4257 8.8 Vladimir Kolesnikov November 30, 2010
WordPress Core < 3.0.2 - Cross-Site Scripting CVE-2010-5294 6.4 November 30, 2010
Register Plus <= 3.5.11 - Stored Cross-Site Scripting CVE-2010-4402 7.2 November 24, 2010
Register Plus <= 3.5.11 - Sensitive Information Disclosure CVE-2010-4403 5.3 Eugene Dokukin November 24, 2010
Event Registration < 6.00.03 - SQL Injection CVE-2010-4839 9.8 k3m4n9i November 15, 2010
WP Survey And Quiz Tool < 1.3 - Cross-Site Scripting CVE-2010-4630 6.1 John Leitch November 8, 2010
FeedList <= 2.61.03 - Reflected Cross-Site Scripting CVE-2010-4637 6.1 John Leitch November 5, 2010
Vodpod Video Gallery <= 3.1.7 - Reflected Cross-Site Scripting CVE-2010-4875 6.1 John Leitch November 5, 2010
CformsII <=11.5 - Cross-Site Scripting CVE-2010-3977 6.1 November 2, 2010
WordPress Core < 3.0.1 - Missing Authorization CVE-2010-5297 4.7 July 29, 2010

Researcher Hall of Fame (Past 30 days)

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation