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

Title CVE ID CVSS Researchers Date
WordPress Core < 2.0.2 - Sensitive Information Disclosure CVE-2006-0986 7.5 March 10, 2006
WordPress Core < 2.0.1 - Cross-Site Scripting CVE-2006-1796 6.1 January 31, 2006
WordPress Core <= 1.5.2 - SQL Injection CVE-2006-1012 7.2 December 31, 2005
secure-files <= 1.1 - Directory Traversal CVE-2005-10002 5.3 October 3, 2005
WordPress Core < 1.5.2 - Remote Code Execution CVE-2005-2612 8.8 August 9, 2005
WordPress Core < 1.5.1.3 - Arbitrary Email Content Change CVE-2005-2109 5.3 James Bercegay June 29, 2005
WordPress Core < 1.5.1.3 - SQL Injection CVE-2005-2108 8.8 James Bercegay June 29, 2005
WordPress Core <= 1.5.1.2 - Cross-Site Scripting CVE-2005-2107 7.2 June 29, 2005
WordPress Core < 1.5.1.3 - Sensitive Information Disclosure CVE-2005-2110 7.3 James Bercegay June 29, 2005
WordPress Core <= 1.5 - Stored Cross-Site Scripting CVE-2005-1102 6.4 Nicolas Montoza June 27, 2005
WordPress Core < 1.5.1.2 - SQL Injection CVE-2005-1810 8.8 Alberto Trivero May 27, 2005
WordPress Core < 1.5.1 - SQL Injection CVE-2005-1687 8.8 Thomas Waldegger May 9, 2005
WordPress Core < 1.5.1 - Full Path Disclosure CVE-2005-1688 5.3 Thomas Waldegger May 9, 2005
WordPress Core < 1.2.1 - Cross-Site Scripting CVE-2004-1559 6.1 Thomas Waldegger October 6, 2004
WordPress Core <= 1.2 - HTTP Response Splitting CVE-2004-1584 5.3 Chaotic Evil October 6, 2004
WordPress Core < 0.72 - SQL Injection CVE-2003-1598 8.8 October 11, 2003
WordPress Core <= 0.70 - Remote File Inclusion CVE-2003-1599 9.8 June 9, 2003

Researcher Hall of Fame (Past 30 days)

Rank Name
Vulnerabilities since Nov 21, 2024
Vulns
1 SOPROBRO 139
2 vgo0 68
3 Peter Thaleikis 66
4 Francesco Carlucci 39
5 Mika 37
6 João Pedro Soares de Alcântara 37
7 stealthcopter 23
8 theviper17y 19
9 zaim 19
10 Gab 16
11 thiennv 16
12 zakaria 15
13 ardias 15
14 Arkadiusz Hydzik 15
15 Colin Xu 13
16 mikemyers 12
17 Tieu Pham Trong Nhan 12
18 zer0gh0st 11
19 LVT-tholv2k 11
20 yudha 11

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