VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2025-15370Published · Updated

Action summary

Affected: ≤21.0.9Update to 21.0.10 or newer

All remediation steps
Watch plugin
Severity
Medium4.3
CVSS
4.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning wp-simple-firewall

  1. Affected≤ 21.0.9
  2. Patched in21.0.10

Update to 21.0.10 or newer.

You are affected if you run ≤ 21.0.9. Version 21.0.10 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 21.0.10, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Dmitrii Ignatyev.

The Shield: Blocks Bots, Protects Users, and Prevents Security Breaches plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 21.0.9 via the MfaGoogleAuthToggle class due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to disable Google Authenticator for any user.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning

All 12
More vulnerabilities in Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Request Path (REQUEST_URI) in Traffic Log
≤22.3.2Update to 22.3.4
CVE-2026-118057
Medium6.5Cross-Site Request Forgery to SQL Injection
≤21.0.8Update to 21.0.10
CVE-2026-0722
Medium6.1Unauthenticated Reflected Cross-Site Scripting via 'message' Parameter
≤21.0.8Update to 21.0.10
CVE-2026-0561
Medium4.3Missing Authorization to Authenticated (Subscriber+) Email MFA Update
≤21.0.9Update to 21.0.10
CVE-2025-14427
Medium6.1Reflected Cross-Site Scripting
≤20.0.5Update to 20.0.6
CVE-2024-7313

Timeline

  1. CVE published

    Severity medium, CVSS 4.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?