Read the docs

Stored cross-site scripting in Shield Security via request path

Priority LOW 31CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Cross-site scripting
Confidentiality · integrity · availability
Low · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-79.

Summary

Shield Security for WordPress, all versions through 22.3.2, contains a stored cross-site scripting flaw in its traffic log (CWE-79). The REQUEST_URI value is stored without sanitization or escaping, so the hidden path column renders attacker-supplied HTML as live page elements. An unauthenticated remote attacker can inject scripts that run in the browser of any user who opens an affected page.

Written with Claude Haiku 5.5 from the sources below · 2026-11-05

Description from the CNA

The Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'REQUEST_URI' parameter in all versions up to, and including, 22.3.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The hidden 'path' column in ForTraffic.php lacks a client-side render function, so DataTables builds its cell via innerHTML, causing stored HTML in the path value to be parsed into live DOM nodes; a prior partial fix in version 18.5.8 added esc_html() only to the visible 'page' column, leaving the hidden 'path' field unescaped and exploitable through version 22.2.6.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00241 15th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
paultgoodchildShield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanningup to 22.3.2—No fix listedCNA
  • Shield Security – Smart Bot Blocking, Brute-Force Login Protection & File Scanning Vendorpaultgoodchild Affected up to 22.3.2 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Shield Security (Smart Bot Blocking, Brute-Force Login Protection & File Scanning).

Written with Claude Haiku 5.5 from the sources below · 2026-11-05

Timeline

  1. 2026-10-31 Threatist record created from CVE-2026-118057
  2. 2026-10-31 Alias added: GHSA-832v-j8jj-hrq5
  3. 2026-11-01 Priority changed: MEDIUM → LOW
  4. 2026-11-01 CISA SSVC decision points changed

References

  • TI-2026-00509 Shield Security <= 21.0.8 - Cross-Site Request Forgery to SQL Injection CVSS 3.1MEDIUM 6.5
  • TI-2026-00363 Shield Security <= 21.0.8 - Unauthenticated Reflected Cross-Site Scripting via 'message' Parameter CVSS 3.1MEDIUM 6.1
  • TI-2025-14019 Shield Security <= 21.0.9 - Authenticated (Subscriber+) Insecure Direct Object Reference to Disable Google Authenticator CVSS 3.1MEDIUM 4.3
  • TI-2025-13178 Missing authorization in paultgoodchild Shield: Blocks Bots, Protects Users, and Prevents… CVSS 3.1MEDIUM 4.3
  • TI-2024-04046 Shield Security – Smart Bot Blocking & Intrusion Prevention Security <= 19.1.13 - Cross-Site Request Forgery CVSS 3.1MEDIUM 4.3

Sources