WordPress Vulnerability Database

Wordfence Intelligence   >   Vulnerability Database
WordPress Core
WordPress Plugins
WordPress Themes

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

Submit Vulnerability
Myflash < 1.11 - Remote File Inclusion
9.8
CVE-2007-2485
May 1, 2007
Researcher: Crackers_Child
The Hacker's Diet <= 0.9.6b - SQL Injection
9.8
CVE-2007-10003
Apr 30, 2007
Researchers:
MySliderGallery <= 1.2.1 - Remote File Inclusion
9.8
CVE-2007-2426
Apr 29, 2007
Researcher: GolD_M
WordPress Core < 2.1.3 - Authorization Bypass
4.3
CVE-2007-1893
Apr 3, 2007
Researchers:
WordPress Core < 2.1.3 - SQL Injection
8.8
CVE-2007-1897
Apr 3, 2007
Researchers:
WordPress Core < 2.0.10 - Open Redirect
6.1
CVE-2007-1599
Apr 3, 2007
Researchers:
WordPress Core <= 2.1.2 - Cross-Site Scripting
6.1
CVE-2007-1622
Apr 3, 2007
Researchers:
WordPress Core <= 2.1.2 - Cross-Site Scripting
6.4
CVE-2007-1894
Apr 3, 2007
Researchers:
WordPress Core <= 2.0.9 - Cross-Site Scripting
7.2
CVE-2008-0192
Apr 3, 2007
Researchers:
WordPress Core 2.2.1 - Backdoor
9.8
CVE-2007-1277
Mar 3, 2007
Researcher: Ivan Fratric
WordPress Core <= 2.1.1 - Cross-Site Scripting
6.4
CVE-2007-1230
Mar 2, 2007
Researchers:
WordPress Core 2.1.1 - Supply Chain Compromise
9.8
CVE ID Unknown
Mar 2, 2007
Researchers:
WordPress Core <= 2.1.1 - Cross-Site Scripting
6.4
CVE-2007-1244
Mar 2, 2007
Researchers:
WordPress Core < 2.09 - Cross-Site Scripting
7.2
CVE-2007-1049
Feb 21, 2007
Researchers:
WordPress Core <= 3.0.4 - Cross-Site Scripting
6.4
CVE-2011-0700
Feb 11, 2007
Researchers: Nils Jueneman, Saddy
WordPress Core < 2.1 - Directory Traversal
6.5
CVE-2007-0541
Jan 24, 2007
Researcher: Blake Matheny
WordPress Core < 2.1 - Full Path Disclosure
5.3
CVE-2008-0195
Jan 22, 2007
Researchers:
WordPress Core < 2.1 - Denial of Service
4.3
CVE-2007-0539
Jan 22, 2007
Researcher: Blake Matheny
WordPress Core < 2.0.7 - Full Path Disclosure
5.3
CVE-2007-0262
Jan 15, 2007
Researchers:
WordPress Core < 2.0.7 - SQL Injection
8.8
CVE-2007-0233
Jan 15, 2007
Researchers:
Title CVE ID CVSS Researchers Date
Myflash < 1.11 - Remote File Inclusion CVE-2007-2485 9.8 Crackers_Child May 1, 2007
The Hacker's Diet <= 0.9.6b - SQL Injection CVE-2007-10003 9.8 April 30, 2007
MySliderGallery <= 1.2.1 - Remote File Inclusion CVE-2007-2426 9.8 GolD_M April 29, 2007
WordPress Core < 2.1.3 - Authorization Bypass CVE-2007-1893 4.3 April 3, 2007
WordPress Core < 2.1.3 - SQL Injection CVE-2007-1897 8.8 April 3, 2007
WordPress Core < 2.0.10 - Open Redirect CVE-2007-1599 6.1 April 3, 2007
WordPress Core <= 2.1.2 - Cross-Site Scripting CVE-2007-1622 6.1 April 3, 2007
WordPress Core <= 2.1.2 - Cross-Site Scripting CVE-2007-1894 6.4 April 3, 2007
WordPress Core <= 2.0.9 - Cross-Site Scripting CVE-2008-0192 7.2 April 3, 2007
WordPress Core 2.2.1 - Backdoor CVE-2007-1277 9.8 Ivan Fratric March 3, 2007
WordPress Core <= 2.1.1 - Cross-Site Scripting CVE-2007-1230 6.4 March 2, 2007
WordPress Core 2.1.1 - Supply Chain Compromise 9.8 March 2, 2007
WordPress Core <= 2.1.1 - Cross-Site Scripting CVE-2007-1244 6.4 March 2, 2007
WordPress Core < 2.09 - Cross-Site Scripting CVE-2007-1049 7.2 February 21, 2007
WordPress Core <= 3.0.4 - Cross-Site Scripting CVE-2011-0700 6.4 Nils Jueneman, Saddy February 11, 2007
WordPress Core < 2.1 - Directory Traversal CVE-2007-0541 6.5 Blake Matheny January 24, 2007
WordPress Core < 2.1 - Full Path Disclosure CVE-2008-0195 5.3 January 22, 2007
WordPress Core < 2.1 - Denial of Service CVE-2007-0539 4.3 Blake Matheny January 22, 2007
WordPress Core < 2.0.7 - Full Path Disclosure CVE-2007-0262 5.3 January 15, 2007
WordPress Core < 2.0.7 - SQL Injection CVE-2007-0233 8.8 January 15, 2007
Submit Vulnerability

Researcher Hall of Fame (Past 30 days)

View All
Rank Name
Vulnerabilities since Nov 22, 2024
Vulns
1 SOPROBRO 119
2 vgo0 62
3 Peter Thaleikis 57
4 João Pedro Soares de Alcântara 37
5 Mika 36
6 Francesco Carlucci 36
7 stealthcopter 22
8 theviper17y 19
9 zaim 19
10 thiennv 15
11 ardias 15
12 Gab 15
13 Arkadiusz Hydzik 14
14 zakaria 14
15 Colin Xu 13
16 Tieu Pham Trong Nhan 11
17 Trương Hữu Phúc (truonghuuphuc) 11
18 zer0gh0st 11
19 mikemyers 11
20 LVT-tholv2k 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