WordPress plugin · Updated daily · Source: Wordfence Intelligence

Shield Security vulnerabilities: affected versions and fixes

Shield Security has 30,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Shield Security at a glance

  • 12 publicly disclosed vulnerabilities, 4 of them rated High or Critical. The most recent was disclosed on Oct 30, 2026.
  • Ranked #936 by popularity on WordPress.org (30,000+ active installs).
  • The latest version is 22.3.4 (released Oct 27, 2026). The most recent security fix shipped in 22.3.4.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Shield Security version

Enter the Shield Security version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Shield Security”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Shield Security”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (22.3.4). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Shield Security vulnerabilities

  • Shield Security <= 22.3.2 - Unauthenticated Stored Cross-Site Scripting via Request Path (REQUEST_URI) in Traffic Log

    Cross-site scripting (XSS) · CVE-2026-118057

    Affected versions: ≤ 22.3.2

    Fixed in: 22.3.4

    Severity: High 7.2 · Disclosed Oct 30, 2026

  • Shield Security: Blocks Bots, Protects Users, and Prevents Security Breaches <= 21.0.9 - Missing Authorization to Authenticated (Subscriber+) Email MFA Update

    Missing authorization · CVE-2025-14427

    Affected versions: ≤ 21.0.9

    Fixed in: 21.0.10

    Severity: Medium 4.3 · Disclosed Feb 18, 2026

  • Shield Security <= 21.0.8 - Cross-Site Request Forgery to SQL Injection

    SQL injection · CVE-2026-0722

    Affected versions: ≤ 21.0.8

    Fixed in: 21.0.10

    Severity: Medium 6.5 · Disclosed Feb 18, 2026

  • Shield Security <= 21.0.8 - Unauthenticated Reflected Cross-Site Scripting via 'message' Parameter

    Cross-site scripting (XSS) · CVE-2026-0561

    Affected versions: ≤ 21.0.8

    Fixed in: 21.0.10

    Severity: Medium 6.1 · Disclosed Feb 18, 2026

  • Shield Security <= 21.0.9 - Authenticated (Subscriber+) Insecure Direct Object Reference to Disable Google Authenticator

    Missing authorization · CVE-2025-15370

    Affected versions: ≤ 21.0.9

    Fixed in: 21.0.10

    Severity: Medium 4.3 · Disclosed Jan 15, 2026

  • Shield Security – Smart Bot Blocking & Intrusion Prevention Security <= 20.0.5 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-7313

    Affected versions: ≤ 20.0.5

    Fixed in: 20.0.6

    Severity: Medium 6.1 · Disclosed Aug 5, 2024

  • Shield Security – Smart Bot Blocking & Intrusion Prevention Security <= 19.1.13 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2024-4344

    Affected versions: ≤ 19.1.10

    Fixed in: 19.1.11

    Severity: Medium 4.3 · Disclosed Jun 1, 2024

  • Shield Security – Smart Bot Blocking & Intrusion Prevention Security <= 18.5.9 - Unauthenticated Local File Inclusion

    Arbitrary file read or deletion · CVE-2023-6989

    Affected versions: ≤ 18.5.9

    Fixed in: 18.5.10

    Severity: Critical 9.8 · Disclosed Feb 5, 2024

  • Shield Security <= 18.5.7 - Unauthenticated Stored Cross-Site Scripting via getColumnContent_Page

    Cross-site scripting (XSS) · CVE-2024-22163

    Affected versions: ≤ 18.5.7

    Fixed in: 18.5.8

    Severity: High 7.2 · Disclosed Jan 16, 2024

  • Shield Security <= 17.0.17 - Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-0992

    Affected versions: < 17.0.18

    Fixed in: 17.0.18

    Severity: High 7.2 · Disclosed Apr 25, 2023

  • Shield Security <= 17.0.17 - Missing Authorization

    Missing authorization · CVE-2023-0993

    Affected versions: < 17.0.18

    Fixed in: 17.0.18

    Severity: Medium 4.3 · Disclosed Apr 25, 2023

  • Shield Security <= 13.0.5 - Admin+ Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2022-0211

    Affected versions: ≤ 13.0.5

    Fixed in: 13.0.6

    Severity: Medium 5.5 · Disclosed Jan 19, 2022

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 30, 2026.

Most common weaknesses in Shield Security

Cross-site scripting (XSS)

6 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

3 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

SQL injection

1 issue

Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.

Frequently asked questions

Is Shield Security safe to use?

Shield Security is a well-known plugin with 30,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (22.3.4) and turn on automatic updates.

How do I find which version of Shield Security my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesShield Security on WordPress.org