CVE-2026-0722

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

2026-02-18 16:19
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 21.0.10
Affected Plugin
Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning
Affected Version
<= 21.0.8
CVSS
6.5Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2026-0722
View all Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning vulnerabilities

At a glance

CVE-2026-0722 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Shield Security WordPress plugin, affecting versions <= 21.0.8. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 21.0.10; sites on affected versions should update now. Disclosed February 2026, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Shield Security plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 21.0.8. This is due to the plugin allowing nonce verification to be bypassed via user-supplied parameter in the 'isNonceVerifyRequired' function. This makes it possible for unauthenticated attackers to execute SQL injection attacks, extracting sensitive information from the database, via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Shield Security <= 21.0.8 carries this weakness at isNonceVerifyRequired, and reaching it takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Shield Security the fix is 21.0.10: builds <= 21.0.8 are affected, anything from 21.0.10 onward is not.

Remediation

Update to version 21.0.10, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Shield Security: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Shield Security 21.0.10 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-0722https://www.wordfence.com/threat-intel/vulnerabilities/id/f53d9579-56e9-41aa-b6b7-2472734ee719https://nvd.nist.gov/vuln/detail/CVE-2026-0722

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C