Live › vulnerability › CVE-2026-118057
The Shield Security WordPress plugin stores the request URI from unauthenticated visitors and renders it unescaped in an admin traffic table. An attacker can inject scripts that run in the browser of anyone who views that page, such as an administrator.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-31 08:34 UTC. All times on this page are UTC.
WordPress sites running the Shield Security plugin at version 22.3.2 or earlier are exposed. The flaw is in the admin traffic log, so the risk lands on staff who open that log while logged in. Sites without this plugin are not affected.
No product ranges from the sources yet.
22.3.2 or earlier22.3.2 are affected; the sources do not state a fixed versionEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-118057")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.