Skip to main content
Security libraryReviewed

WordPress plugin vulnerabilities, plugin by plugin: what each guide records and the update guidance it gives

A register of the 80 WordPress plugin guides in this library.

Each row gives the plugin's category, how many vulnerability records the source data lists for it, and the update guidance its guide gives, read from the same data the guide uses. Use it to check the plugins on your own site against their guides. It ranks no plugin and passes no verdict on any.

Pages in this section

80 pages

WordPress plugin register: records and update guidance by plugin

Find each plugin you run in the first column, then read across to its category and to what its guide shows: the number of records the source lists for it and the guide's update guidance, in the guide's own words. The third column's heading gives the date the source was retrieved.

How to use it

Rows run by category and then in the library's order. Plugins share a category where their guides are joined by related-guide links, each reachable from every other in the group, and the rest sit under Other plugins. Each name, count and guidance line comes from the same data and code as the plugin's guide, which lists the records behind the count and the checks to run on a live site. All the guides are linked under Pages in this section, and the source and its licence are at the foot of the page.

80 rows

PluginCategoryRecords and update guidance, source retrieved on 21 Nov 2026
ElementorPage builders62 records. Update to at least version 4.3.6.
Essential Addons for ElementorPage builders76 records. Update to at least version 6.8.8.
Ultimate Addons for ElementorPage builders14 records. Update to at least version 2.9.6.
SiteOrigin Page BuilderPage builders12 records. Update to at least version 2.38.0.
Beaver BuilderPage builders38 records. Update to at least version 2.11.0.6.
Kadence BlocksPage builders44 records. Update to at least version 3.9.1.1.
SpectraPage builders37 records. Update to at least version 2.20.6.
Contact Form 7Forms11 records. Update to at least version 6.2.5.
WPFormsForms28 records. Update to at least version 2.0.3.1.
Ninja FormsForms95 records. Update to at least version 3.15.6.
ForminatorForms84 records. Update to at least version 1.58.5.
Formidable FormsForms29 records. Update to at least version 7.0.
Fluent FormsForms47 records. Update to at least version 6.2.17.
WooCommerceEcommerce and payments48 records. Update to at least version 11.3.0.
WooCommerce PayPal PaymentsEcommerce and payments3 records. Update to at least version 4.0.2.
WooCommerce Stripe Payment GatewayEcommerce and payments6 records. Update to at least version 11.1.0.
WooPaymentsEcommerce and payments7 records. Update to at least version 10.6.0.
Easy Digital DownloadsEcommerce and payments51 records. Update to at least version 3.7.3.
SureCartEcommerce and payments22 records. Update to at least version 4.13.0.
CartFlowsEcommerce and payments11 records. Update to at least version 3.3.1.
Yoast SEOSEO20 records. Update to at least version 28.1.
All in One SEOSEO34 records. Update to at least version 5.0.5.1.
Rank MathSEO36 records. Update to at least version 1.0.280.
SEOPressSEO20 records. Update to at least version 10.4.
RedirectionSEO5 records. Update to at least version 3.6.4.
XML Sitemap GeneratorSEO3 records. Update to at least version 4.1.23.
LiteSpeed CachePerformance and images30 records. Update to at least version 7.9.2.
WP Super CachePerformance and images12 records. Update to at least version 1.9.
W3 Total CachePerformance and images41 records. Update to at least version 2.11.0.
WP Fastest CachePerformance and images40 records. Update to at least version 1.5.5.
WP-OptimizePerformance and images5 records. Update to at least version 4.5.3.
AutoptimizePerformance and images15 records. Update to at least version 3.1.16.
SmushPerformance and images11 records. Update to at least version 4.3.6.
NextGEN GalleryPerformance and images58 records. Update to at least version 4.6.0.
EWWW Image OptimizerPerformance and images15 records. Update to at least version 8.9.2.
UpdraftPlusBackup and migration20 records. Check the patched version for your edition.
All-in-One WP MigrationBackup and migration18 records. Update to at least version 7.111.
DuplicatorBackup and migration20 records. Update to at least version 5.1.0.
Backup MigrationBackup and migration20 records. Update to at least version 2.1.8.
BackWPupBackup and migration16 records. Update to at least version 5.7.7.
WPvividBackup and migration38 records. Update to at least version 0.9.138.
WordfenceSecurity and login12 records. Update to at least version 7.6.1.
Really Simple SecuritySecurity and login13 records. Update to at least version 9.8.3.
AkismetSecurity and login2 records. Update to at least version 3.1.5.
JetpackSecurity and login33 records. Update to at least version 16.3.
All-in-One SecuritySecurity and login29 records. Update to at least version 5.5.0.
Sucuri SecuritySecurity and login1 record. Update to at least version 1.8.34.
Kadence SecuritySecurity and login19 records. Update to at least version 9.3.2.
Limit Login Attempts ReloadedSecurity and login6 records. Update to at least version 3.4.2.
LoginizerSecurity and login8 records. Update to at least version 1.9.3.
WPS Hide LoginSecurity and login10 records. Update to at least version 1.9.16.4.
Ultimate MemberMembership87 records. Update to at least version 2.14.2.
MembersMembership2 records. Update to at least version 3.2.23.
Paid Member SubscriptionsMembership37 records. Update to at least version 3.1.5.
Simple MembershipMembership39 records. Update to at least version 4.8.5.
LifterLMSOnline courses21 records. Update to at least version 11.0.0.
LearnPressOnline courses111 records. No single update clears every record.
Tutor LMSOnline courses104 records. No single update clears every record.
Sensei LMSOnline courses10 records. Update to at least version 4.26.4.
Site Kit by GoogleAnalytics3 records. Update to at least version 1.187.0.
MonsterInsightsAnalytics12 records. Update to at least version 11.1.0.
ExactMetricsAnalytics7 records. Update to at least version 9.1.3.
WP StatisticsAnalytics44 records. Update to at least version 14.16.15.
Advanced Custom FieldsCustom fields and code27 records. Check the patched version for your edition.
Custom Post Type UICustom fields and code4 records. Update to at least version 1.18.2.
WPCodeCustom fields and code5 records. Update to at least version 2.4.0.
Code SnippetsCustom fields and code10 records. Update to at least version 4.1.0.
WP Mail SMTPEmail sending2 records. Update to at least version 4.1.0.
Post SMTPEmail sending28 records. Update to at least version 4.0.2.
FluentSMTPEmail sending6 records. Update to at least version 2.3.0.
CookieYesCookie consent2 records. Update to at least version 3.5.8.
ComplianzCookie consent25 records. Update to at least version 7.5.6.
PolylangMultilingual8 records. Update to at least version 3.9.1.
TranslatePressMultilingual20 records. Update to at least version 3.4.
LatePointOther plugins60 records. No single update clears every record.
WP Go MapsOther plugins31 records. Update to at least version 10.2.00.
The Events CalendarOther plugins47 records. Update to at least version 6.18.3.1.
WP File ManagerOther plugins16 records. Update to at least version 8.0.5.
Yoast Duplicate PostOther plugins5 records. Update to at least version 4.6.
AI EngineOther plugins47 records. Update to at least version 3.9.4.

About this library

How to read a row of the register

Each row is one plugin guide in this library.

The first column gives the plugin's name as its guide gives it, and the second its category. The third gives the two things a guide shows at the top of its vulnerability history: how many records the source data lists for the plugin, and the guide's update guidance.

That column's heading carries the date the source was retrieved, and the data source and licence note at the foot of the page names the source.

The register and the guides read the same data through the same code, so a row and its guide show the same count and the same guidance. The count covers the records the source holds under the plugin's slug, the last part of its guide's address, across every version those records name.

It counts published records, not problems on any site. The guidance takes one of five forms, worded as the guides word them:

  • Update to at least version: every affected range the source lists for the plugin ends before that version. When the copy of the source has not been refreshed within its window, this form reads Version X or later, as listed on the date the copy was retrieved.
  • No single update clears every record: at least one record lists no patched version. Read those records and the source's remediation note on the guide before relying on an update.
  • Check the patched version for your edition: some records list more than one edition of the plugin, each with its own version line, so use the patched version shown for the edition you run.
  • Check the patched version in each record: the versions listed do not give one version that clears every affected range.
  • No records in this source: the source lists none for the plugin, which is not evidence the plugin is free of vulnerabilities.

Checking the plugins on your own site

Start from the Plugins screen in your WordPress dashboard.

WordPress's documentation describes it as a table of your plugins in alphabetical order, with the version number in each plugin's Description column, and an Update Available link that lists the plugins with an upgrade available at the WordPress Plugin Directory.

Find each installed plugin in the register and read its guidance. Where the guidance names a version, compare yours with it. Where it asks you to check each record or your edition, or your version sits below the one named, open the plugin's guide and compare your version with the affected range in each record. Every guide also carries a checklist of what to look at on a live site.

Two cases need more than the register. A plugin installed from a ZIP file or another outside source shows an update notice only if its author built an updater into it, and WordPress's documentation says to check with the plugin's author or developer for the latest version when no notice appears.

And a vendor can publish a security release before the source records it, so read the plugin's own changelog as well as its guide.

Since WordPress 5.5 an administrator can opt in to automatic updates plugin by plugin, from the Automatic update column on the same screen. WordPress's guidance is to make sure the site can be rolled back to a previous version before turning them on.

What a count and a guidance line cannot tell you

A larger count is not a worse plugin, and the register ranks nothing.

It sorts by category and then by the library's own order. A count says how many records the source has published for a plugin across every version those records name, old and current, and nothing in a row says whether a plugin suits your site.

A row knows nothing about your installation. It cannot see which version you run, which features you have switched on, which roles can reach them, or whether anyone has tried a flaw on your site. Nor does it cover a premium edition that installs as a separate plugin with its own slug, custom plugins written for your site, or themes.

The register does not show whether WordPress.org has closed a plugin or flagged it as untested either. WordPress.org's plugin handbook says a plugin that has not been tested with the latest three major releases of WordPress shows a warning that it may no longer be maintained, and that a closed plugin shows a notice that it is no longer available for download. Check each free plugin's own page on WordPress.org as well.

The counts are only as current as the copy of the source this site holds. When that copy has not been refreshed within its window, a notice at the foot of this page says so, and records published since then are not counted.

Where a WordPress security audit takes over

The WordPress security audit described in the WordPress guide covers the same ground and goes further.

It takes each plugin and theme version from the Plugins and Themes screens, keeps a dated export or screenshot, and notes where the version visible from outside the site says something different. Each version is compared with public vulnerability advisories, including this register, and every match is recorded with the advisory identifier and the version that fixed it.

A version match is not where the audit ends: the report keeps findings proved with evidence apart from version matches that still need confirming on the live site. The audit signs in as each role your site hands out, with test accounts, and tries the actions that role should be refused.

Custom plugins written for your site have no public advisories, so it reads how they register their routes. You receive a written report with the evidence for each finding and a fix for each one, plus an update-priority list.

If Clever Ops built or hosts your WordPress site, the work is run as a security review rather than an independent audit, and the report names who built the site and who runs its hosting. An audit is the wrong first step for a site that is compromised now: contact your host and a specialist in incident response and cleanup first. The hacked website guide covers what to do.

Frequently asked questions

Not in itself. It is an index to the plugin guides in this library, built from a copy of a published vulnerability feed. Each row gives totals from that copy: the number of records for the plugin and the update guidance its guide works out from them. The records themselves, with their affected and patched versions, are on each plugin's guide, and the source is named at the foot of this page.

On its guide. Each record in a guide's history lists its affected ranges and patched versions as the source gives them, and a range can start partway through a plugin's version history, so compare your installed version with every range rather than only the newest record. The guidance line in the register sums up those ranges; it does not replace them.

The register does not say, and a count cannot. A count reflects how many records the source has published for the plugin across every version they name, and where the update guidance names a version, every listed range ends before it. Whether to keep a plugin depends on the version you run, whether it is still maintained and what it does on your site.

Because at least one of the plugin's records lists no patched version, so no update can be shown to clear it. The plugin's guide shows which records those are, with the source's remediation note for each. Read them before relying on an update, and check the plugin's own changelog, since a vendor can publish a security release before the source records it.

As current as the copy of the source this site holds. The date in the heading of the register's third column is when that copy was retrieved. When the copy has not been refreshed within its window, a notice at the foot of this page and on each plugin guide says so, and records published since then are not counted.

Yes. The audit records every installed plugin and theme, active or not, with evidence of its version, and compares each version with public vulnerability advisories, including this register. It also signs in as each role your site hands out and tests what each one can reach, which a version list cannot show.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The record counts and update guidance in the register on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . They are worked out from records that contain material subject to copyright. Each copyright notice and its licence are reproduced once below. The register shows no record itself: each plugin's guide lists the records it counts, and its own data source and licence section links every one of them.

Copyright 2012-2026 Defiant Inc.

Applies to every record counted in the register.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to 1932 of the 2155 records counted in the register.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.