WordPress vulnerabilities in 2026: what 59,713 records tell us

·

This is the first of a series of posts where we open up the WPVulnerability database and look at what it says about WordPress security. WPVulnerability is a free and open API (no API key needed) that collects vulnerability information for WordPress core, plugins and themes from several public sources. Every number below comes from a snapshot of the database taken on 21 November 2026.

The short version: more vulnerabilities are being published than ever, nine out of ten of them are in plugins, and the type of bug being reported is changing in a way that matters to everyone who runs a WordPress site.

Vulnerability records in the database
59,713
WordPress core, plugins and themes, all years
Published in 2026 so far
12,120
Already 5.5% more than all of 2025
October 2026
1,908
Busiest month since February 2022
Core vulnerabilities in 2026
84
More than 2023, 2024 and 2025 combined (57)

Where the vulnerabilities live

The database holds 59,713 vulnerability records. 54,367 of them, 91%, are in plugins. Themes account for 4,427 (7.4%) and WordPress core for 919 (1.5%).

Nine out of ten vulnerabilities are in plugins

All 59,713 records by component type, all years

Plugins 54,367Themes 4,427Core 919
91%
7.4%

Source: WPVulnerability database, snapshot of 21 November 2026.

This is the most useful fact in this post. WordPress core is built by a large team with a dedicated security process. The plugin and theme ecosystem is tens of thousands of products, maintained by everyone from large companies to a single developer in their spare time. The attack surface of a typical WordPress site is not really WordPress; it is everything installed on top of it.

Twenty years, one direction

Until 2020, the ecosystem typically saw anywhere from a few hundred to about 1,700 published vulnerabilities a year. Then the curve took off: 2,360 in 2021, 5,585 in 2022, 8,839 in 2024 and 11,485 in 2025. 2026 has already passed that with 12,120 records and six weeks still to go. At the current pace it will end the year at around 13,500.

Vulnerabilities published per year

By component type, 2003 to 2026 (2026 up to 21 November)

PluginsThemesCore
Vulnerabilities per year by type, 2003 to 202603K6K9K12K2003: 2 (plugins 0, themes 0, core 2)2004: 2 (plugins 0, themes 0, core 2)20042005: 25 (plugins 1, themes 0, core 24)2006: 34 (plugins 3, themes 1, core 30)20062007: 115 (plugins 22, themes 14, core 79)2008: 76 (plugins 40, themes 0, core 36)20082009: 66 (plugins 31, themes 1, core 34)2010: 47 (plugins 30, themes 1, core 16)20102011: 280 (plugins 227, themes 23, core 30)2012: 473 (plugins 370, themes 55, core 48)20122013: 541 (plugins 382, themes 124, core 35)2014: 1,198 (plugins 856, themes 296, core 46)20142015: 1,692 (plugins 1,512, themes 150, core 30)1,6922016: 889 (plugins 822, themes 27, core 40)20162017: 791 (plugins 677, themes 13, core 101)2018: 493 (plugins 433, themes 14, core 46)20182019: 1,029 (plugins 909, themes 70, core 50)2020: 1,022 (plugins 812, themes 157, core 53)1,02220202021: 2,360 (plugins 2,172, themes 164, core 24)2022: 5,585 (plugins 5,193, themes 343, core 49)5,58520222023: 7,207 (plugins 6,968, themes 214, core 25)2024: 8,839 (plugins 8,485, themes 340, core 14)20242025: 11,485 (plugins 10,519, themes 948, core 18)2026: 12,120 (plugins 10,925, themes 1,111, core 84)12,1202026

3,342 records (5.6%) have no published date in any of their sources and are not shown. Hover a column for its breakdown.

Show the data
YearPluginsThemesCoreTotal
202610,9251,1118412,120
202510,5199481811,485
20248,485340148,839
20236,968214257,207
20225,193343495,585
20212,172164242,360
2020812157531,022
201990970501,029
20184331446493
201767713101791
20168222740889
20151,512150301,692
2014856296461,198
201338212435541
20123705548473
20112272330280
20103011647
20093113466
20084003676
2007221479115
2006313034
2005102425
20040022
20030022
Undated2,97836133,342

More vulnerabilities does not necessarily mean worse code. Much of this growth reflects more people looking: WordPress-focused security companies running bug bounty programmes, more independent researchers, and more organisations issuing CVE identifiers for plugin and theme bugs. What it does mean is more advisories to act on. In 2026 that has been an average of around 37 new vulnerabilities a day.

2026, month by month

Monthly figures are lumpy. Vulnerabilities are often published in batches, when a research team releases the results of a large audit or a source publishes a backlog, so single months can spike well above the trend. The four busiest months on record are February 2022 (2,001), October 2026 (1,908), January 2025 (1,703), July 2023 (1,653).

Vulnerabilities published per month

All component types, 2015 to 2026. Darker means more; months with 1,500 or more are labelled

under 100100–249250–499500–749750–9991,000–1,4991,500+
Vulnerabilities published per month, 2015 to 2026JanFebMarAprMayJunJulAugSepOctNovDecTotal2026Jan 2026: 1,036Feb 2026: 1,013Mar 2026: 913Apr 2026: 751May 2026: 755Jun 2026: 1,045Jul 2026: 1,198Aug 2026: 1,388Sep 2026: 1,139Oct 2026: 1,9081,908Nov 2026: 974Dec 2026: not yet–12,120*2025Jan 2025: 1,7031,703Feb 2025: 897Mar 2025: 1,056Apr 2025: 1,390May 2025: 717Jun 2025: 868Jul 2025: 661Aug 2025: 729Sep 2025: 1,047Oct 2025: 739Nov 2025: 621Dec 2025: 1,05711,4852024Jan 2024: 447Feb 2024: 438Mar 2024: 837Apr 2024: 1,136May 2024: 659Jun 2024: 772Jul 2024: 663Aug 2024: 635Sep 2024: 501Oct 2024: 831Nov 2024: 940Dec 2024: 9808,8392023Jan 2023: 539Feb 2023: 465Mar 2023: 512Apr 2023: 445May 2023: 598Jun 2023: 460Jul 2023: 1,6531,653Aug 2023: 390Sep 2023: 393Oct 2023: 529Nov 2023: 737Dec 2023: 4867,2072022Jan 2022: 380Feb 2022: 2,0012,001Mar 2022: 803Apr 2022: 275May 2022: 293Jun 2022: 250Jul 2022: 177Aug 2022: 259Sep 2022: 192Oct 2022: 245Nov 2022: 359Dec 2022: 3515,5852021Jan 2021: 89Feb 2021: 108Mar 2021: 163Apr 2021: 219May 2021: 167Jun 2021: 208Jul 2021: 189Aug 2021: 326Sep 2021: 237Oct 2021: 354Nov 2021: 154Dec 2021: 1462,3602020Jan 2020: 119Feb 2020: 77Mar 2020: 70Apr 2020: 84May 2020: 58Jun 2020: 74Jul 2020: 99Aug 2020: 94Sep 2020: 121Oct 2020: 104Nov 2020: 64Dec 2020: 581,0222019Jan 2019: 32Feb 2019: 178Mar 2019: 59Apr 2019: 50May 2019: 82Jun 2019: 107Jul 2019: 135Aug 2019: 71Sep 2019: 82Oct 2019: 135Nov 2019: 39Dec 2019: 591,0292018Jan 2018: 98Feb 2018: 32Mar 2018: 28Apr 2018: 39May 2018: 39Jun 2018: 41Jul 2018: 15Aug 2018: 27Sep 2018: 41Oct 2018: 38Nov 2018: 36Dec 2018: 594932017Jan 2017: 49Feb 2017: 35Mar 2017: 71Apr 2017: 119May 2017: 117Jun 2017: 46Jul 2017: 55Aug 2017: 52Sep 2017: 75Oct 2017: 54Nov 2017: 67Dec 2017: 517912016Jan 2016: 42Feb 2016: 102Mar 2016: 61Apr 2016: 91May 2016: 61Jun 2016: 74Jul 2016: 165Aug 2016: 85Sep 2016: 49Oct 2016: 40Nov 2016: 60Dec 2016: 598892015Jan 2015: 59Feb 2015: 82Mar 2015: 101Apr 2015: 220May 2015: 514Jun 2015: 108Jul 2015: 160Aug 2015: 214Sep 2015: 68Oct 2015: 57Nov 2015: 70Dec 2015: 391,692

* 2026 runs to 21 November; December 2026 has not happened yet. Hover a cell for its exact value.

Show the data
YearJanFebMarAprMayJunJulAugSepOctNovDecTotal
20261,0361,0139137517551,0451,1981,3881,1391,908974–12,120
20251,7038971,0561,3907178686617291,0477396211,05711,485
20244474388371,1366597726636355018319409808,839
20235394655124455984601,6533903935297374867,207
20223802,0018032752932501772591922453593515,585
2021891081632191672081893262373541541462,360
20201197770845874999412110464581,022
201932178595082107135718213539591,029
2018983228393941152741383659493
201749357111911746555275546751791
201642102619161741658549406059889
20155982101220514108160214685770391,692

What stands out about 2026 is its consistency more than any single spike. Every month from January to October saw at least 751 new vulnerabilities, and the second half of the year has been heavier than the first. October, with 1,908, was the busiest month in more than four and a half years.

Plugins: still where the risk is

Plugins account for 10,925 of this year’s vulnerabilities. That is a new annual record, already 4% more than the whole of 2025, with November still in progress. October alone added 1,762 plugin vulnerabilities.

For site owners the arithmetic is simple. Every plugin you install is a dependency with its own release cycle, its own maintainers and its own vulnerability history. A site with 30 plugins doesn’t have one security posture. It has 31.

Themes: a record year, front-loaded

Themes reached 1,111 vulnerabilities in 2026, the highest annual figure so far (the previous record was 948, in 2025) and more than three times the 340 of 2024. The year was unusually front-loaded: 636 of them, 57%, were published between January and March.

Themes are often thought of as “just the design”, but many modern themes ship settings panels, demo importers, page-builder integrations and their own AJAX endpoints. That is code, and it gets the same kinds of bugs as plugins.

WordPress core: small numbers, unusual year

Core has 919 unique vulnerabilities in the database across its whole history, deduplicated across sources and affected versions. Most years see a few dozen at most. 2026 is different: 84 so far, more than 2023, 2024 and 2025 combined (57) and the highest annual figure since 2017 (101). Most arrived late in the year: 74 between August and November.

WordPress core vulnerabilities per year

Unique vulnerabilities, deduplicated across sources and affected versions, 2003 to 2026

WordPress core vulnerabilities per year, 2003 to 202603060901202003: 22004: 220042005: 242006: 3020062007: 79792008: 3620082009: 342010: 1620102011: 302012: 4820122013: 352014: 4620142015: 302016: 4020162017: 1011012018: 4620182019: 502020: 5320202021: 242022: 4920222023: 252024: 1420242025: 182026: 84842026

2026 runs to 21 November. Hover a column for its value.

Show the data
YearCore vulnerabilities
202684
202518
202414
202325
202249
202124
202053
201950
201846
2017101
201640
201530
201446
201335
201248
201130
201016
200934
200836
200779
200630
200524
20042
20032

Core is still the best-defended part of the stack. Minor releases, which carry the security fixes, install automatically by default, so most sites get those patches without anyone lifting a finger. It is worth checking that nothing on your site has quietly switched that off: a hosting panel setting, a constant in wp-config.php or a management tool.

What kinds of vulnerabilities?

When a vulnerability has a CVE, its CWE classification tells us what kind of weakness it is. Across all years, four families account for 76% of all classifications:

  • Cross-site scripting (XSS), 41.4%: an attacker gets their own JavaScript to run in someone else’s browser, often an administrator’s.
  • Authorization and access control, 16.4%: code does something without checking that the user is allowed to do it.
  • Cross-site request forgery (CSRF), 11.3%: a logged-in user is tricked into sending a request they didn’t intend, usually by visiting a malicious page.
  • SQL injection, 6.4%: user input ends up inside a database query.
Attack typeClassificationsShare
Cross-site scripting (XSS)18,14541.4%
Authorization / access control7,19816.4%
CSRF4,94211.3%
SQL injection2,8256.4%
PHP file inclusion (LFI/RFI)1,2442.8%
Path traversal1,1112.5%
Arbitrary file upload1,0892.5%
Deserialization (object injection)1,0172.3%
Sensitive information exposure9722.2%
IDOR (user-controlled key)8381.9%
Top 10 attack types, all years. Shares are of 43,817 CWE classifications; a vulnerability with two CWEs counts twice.

The mix, however, is changing.

XSS and CSRF are shrinking; authorization flaws are growing

Share of all CWE classifications per year, 2014 to 2026

XSSAuthorizationCSRF
Share of CWE tags by attack type, 2014 to 20260%20%40%60%2014201620182020202220242026XSS, 2014: 54.0%XSS, 2015: 44.0%XSS, 2016: 54.6%XSS, 2017: 50.9%XSS, 2018: 53.1%XSS, 2019: 43.0%XSS, 2020: 34.7%XSS, 2021: 40.5%XSS, 2022: 31.9%XSS, 2023: 52.1%XSS, 2024: 48.1%XSS, 2025: 40.2%XSS, 2026: 29.3%29.3% XSSAuthorization, 2014: 0.3%Authorization, 2015: 2.3%Authorization, 2016: 1.3%Authorization, 2017: 2.1%Authorization, 2018: 1.3%Authorization, 2019: 3.7%Authorization, 2020: 11.2%Authorization, 2021: 17.7%Authorization, 2022: 28.8%Authorization, 2023: 13.0%Authorization, 2024: 15.4%Authorization, 2025: 16.8%Authorization, 2026: 20.3%20.3% AuthorizationCSRF, 2014: 16.4%CSRF, 2015: 12.5%CSRF, 2016: 11.5%CSRF, 2017: 5.2%CSRF, 2018: 8.7%CSRF, 2019: 14.0%CSRF, 2020: 16.2%CSRF, 2021: 12.3%CSRF, 2022: 16.6%CSRF, 2023: 17.3%CSRF, 2024: 11.0%CSRF, 2025: 12.9%CSRF, 2026: 3.4%3.4% CSRF

2026 is provisional: so far 76.1% of this year’s CVE-linked vulnerabilities have a CWE assigned, against 96.5% for 2025.

Show the data
YearXSSAuthorizationCSRF
202629.3%20.3%3.4%
202540.2%16.8%12.9%
202448.1%15.4%11.0%
202352.1%13.0%17.3%
202231.9%28.8%16.6%
202140.5%17.7%12.3%
202034.7%11.2%16.2%
201943.0%3.7%14.0%
201853.1%1.3%8.7%
201750.9%2.1%5.2%
201654.6%1.3%11.5%
201544.0%2.3%12.5%
201454.0%0.3%16.4%

Cross-site scripting has dominated WordPress vulnerability reports for more than a decade, and it still made up more than half of all classifications as recently as 2023. Its share has fallen for three years in a row, to 29.3% in 2026. CSRF has dropped even faster, from 12.9% in 2025 to 3.4%. Meanwhile, authorization and access-control bugs have climbed to 20.3%, their highest share since 2022.

2026: fewer noisy bugs, more dangerous ones

Comparing 2026 with 2025 makes the shift clearer. Together, XSS and CSRF went from 53.1% of all classifications to 32.7%. Most of the categories that grew are server-side flaws with serious consequences:

How the mix of attack types changed in a year

Share of all CWE classifications, 2025 compared with 2026. Top 12 types in 2026

20252026
Share of CWE tags, 2025 compared with 20260%10%20%30%40%2025 → 2026Cross-site scripting (XSS): 40.2% in 2025, 29.3% in 2026Cross-site scripting (XSS)40.2% → 29.3%Authorization / access control: 16.8% in 2025, 20.3% in 2026Authorization / access control16.8% → 20.3%SQL injection: 5.9% in 2025, 7.6% in 2026SQL injection5.9% → 7.6%PHP file inclusion (LFI/RFI): 5.8% in 2025, 5.5% in 2026PHP file inclusion (LFI/RFI)5.8% → 5.5%IDOR (user-controlled key): 1.2% in 2025, 4.7% in 2026IDOR (user-controlled key)1.2% → 4.7%Deserialization (object injection): 2.6% in 2025, 4.5% in 2026Deserialization (object injection)2.6% → 4.5%Sensitive information exposure: 1.1% in 2025, 3.8% in 2026Sensitive information exposure1.1% → 3.8%CSRF: 12.9% in 2025, 3.4% in 2026CSRF12.9% → 3.4%Path traversal: 2.5% in 2025, 3.0% in 2026Path traversal2.5% → 3.0%Improper privilege management: 0.5% in 2025, 2.6% in 2026Improper privilege management0.5% → 2.6%Arbitrary file upload: 2.3% in 2025, 2.4% in 2026Arbitrary file upload2.3% → 2.4%Improper authentication: 0.2% in 2025, 2.0% in 2026Improper authentication0.2% → 2.0%

2026 is provisional (76.1% CWE coverage so far). Hover a row for exact values.

Show the data
Attack type20252026
Cross-site scripting (XSS)40.2%29.3%
Authorization / access control16.8%20.3%
SQL injection5.9%7.6%
PHP file inclusion (LFI/RFI)5.8%5.5%
IDOR (user-controlled key)1.2%4.7%
Deserialization (object injection)2.6%4.5%
Sensitive information exposure1.1%3.8%
CSRF12.9%3.4%
Path traversal2.5%3.0%
Improper privilege management0.5%2.6%
Arbitrary file upload2.3%2.4%
Improper authentication0.2%2.0%
  • IDOR (authorization bypass through a user-controlled key): 1.2% to 4.7%. Change an ID in a request and get, or change, someone else’s data.
  • Deserialization of untrusted data (PHP object injection): 2.6% to 4.5%.
  • Sensitive information exposure: 1.1% to 3.8%.
  • Improper privilege management: 0.5% to 2.6%. Typically privilege escalation, such as a subscriber account becoming an administrator.
  • Improper authentication: 0.2% to 2.0%, from 19 classifications to 188.
  • SQL injection: 5.9% to 7.6%.

Why is this happening? Part of the answer is probably that the easy bugs are being caught earlier: automated scanners and code review tools are good at finding missing escaping and missing nonces before a release ships. The other part is incentives. Researchers, and attackers, are spending their time on bugs that pay off. A stored XSS that needs an administrator to visit a page is worth far less than an unauthenticated privilege escalation.

One caution: 2026 figures will move. So far 76.1% of this year’s CVE-linked vulnerabilities have a CWE assigned, against 96.5% for 2025, because classification of recent CVEs is still catching up. The direction, though, matches a trend that has been building for several years.

A small number worth watching: malicious code

25 vulnerabilities in 2026 are classified as embedded malicious code (CWE-506): plugins or themes that shipped with a backdoor or other deliberately malicious code, rather than an accidental bug. That is up from 1 in 2025 and 11 in 2024.

The numbers are small, but this is a different kind of threat. No amount of careful configuration protects a site from code that was written to attack it. Common routes include a compromised developer account and an abandoned plugin changing hands. It is one more reason to know exactly what is installed on your sites, and who maintains it.

What this means for you

If you run WordPress sites

  • Know what you run. Keep an inventory of every plugin and theme on every site, including inactive ones: an inactive plugin’s files are still on the server.
  • Remove what you don’t use. Fewer components means fewer advisories to track and less code an attacker can reach.
  • Turn on auto-updates for plugins and themes you trust, and keep core’s automatic minor updates enabled.
  • Watch for abandoned software. A plugin that has been closed in the directory, or not updated in years, will not get a fix when its next vulnerability is found.
  • Get alerts. The free WPVulnerability plugin checks core, plugins and themes (plus server software such as PHP, the web server and the database) against the database and can email you when something needs attention.

If you host or manage many sites

  • Monitor the whole fleet. The WPVulnerability API is free, needs no API key and returns JSON, so it is easy to wire into your own tooling (documentation).
  • Don’t rely on the firewall alone. WAF rules are good at spotting injection payloads. They are much worse at spotting a request that is perfectly well-formed but should not have been allowed. As the mix moves towards authorization and access-control flaws, how fast you update matters more than what you filter.
  • Measure time to patch. At around 37 new vulnerabilities a day, the useful question is not whether your sites are affected but how long they stay affected.

If you build plugins or themes

  • Check capabilities on every action, with current_user_can(), including AJAX handlers and admin-post actions. REST routes need a real permission_callback; use __return_true only for endpoints that are public by design.
  • Check the object, not just the role. Knowing that a user is logged in, or is an editor, is not enough. Check that they may act on that object, for example current_user_can( 'edit_post', $post_id ). This is what prevents IDOR.
  • Prepare every query with $wpdb->prepare().
  • Never call unserialize() on data a user can influence. Use JSON instead.
  • Never build include or require paths from request data. If a file must be chosen dynamically, choose it from a fixed allowlist.
  • Keep doing the basics: escape output late and verify nonces. XSS and CSRF are shrinking as a share, but they are still the largest categories in absolute numbers.
  • Publish a way to report security issues, so researchers can reach you before they publish.

How we count

  • Plugins and themes are counted per product. The same CVE affecting two different plugins is two records, one for each product, because each needs its own fix and its own update. These totals match the public API.
  • WordPress core is counted per vulnerability. Advisories are deduplicated through their CVE cross-references, so a vulnerability reported by several sources, or affecting many core versions, counts once.
  • Dates are the earliest published date found across all the advisories linked to each vulnerability.
  • 3,342 records (5.6%) have no published date in any of their sources. They are included in the totals but left out of the per-year and per-month charts.
  • Attack types come from CWE classifications and cover CVE-linked vulnerabilities only. A vulnerability with two CWEs counts once for each, so shares are shares of classifications, not of vulnerabilities. Near-duplicate CWEs are grouped into families (for example, all XSS variants under XSS).
  • The current year is provisional. CWE classification of recent CVEs takes time, so 2026 attack-type shares will shift as coverage catches up.

Get the data

Everything in this post comes from the WPVulnerability database. The API is open to everyone with no key required, and its documentation covers every endpoint. Live figures are on the statistics page. To get alerts on your own site, install the WPVulnerability plugin. The project is open source on GitHub.

If there is a cut of the data you would like to see in a future post, let us know.