CVE-2026-3368: Injection Guard <= 1.2.9 - Unauthenticated Stored Cross-Site Scripting via Query Parameter Name
The Injection Guard plugin for WordPress is vulnerable to Stored Cross-Site Scripting via malicious query parameter names in all versions up to and including 1.2.9. This is due to insufficient input sanitization in the sanitizeigdata() function which only sanitizes array values but not array keys, combined with missing output escaping in the igsettings.php template where stored parameter keys are echoed directly into HTML. When a request is made to the site, the plugin captures the query string via $SERVER['QUERYSTRING'], applies escurlraw() (which preserves URL-encoded special characters like %22, %3E, %3C), then passes it to parsestr() which URL-decodes the string, resulting in decoded HTML/JavaScript in the array keys. These keys are stored via updateoption('igrequestslog') and later rendered without eschtml() or escattr() on the admin log page. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in the admin log page that execute whenever an administrator views the Injection Guard log interface.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-3368?
CVE-2026-3368 has been classified as a high severity vulnerability due to its potential for unauthenticated stored cross-site scripting.
How do I fix CVE-2026-3368?
To remediate CVE-2026-3368, update the Injection Guard plugin to version 1.3.0 or later.
What versions are affected by CVE-2026-3368?
CVE-2026-3368 affects all versions of the Injection Guard plugin up to and including version 1.2.9.
What type of vulnerability is CVE-2026-3368?
CVE-2026-3368 is a stored cross-site scripting vulnerability that allows attackers to inject malicious scripts via query parameter names.
Who is impacted by CVE-2026-3368?
Anyone using the Injection Guard plugin for WordPress versions up to 1.2.9 is at risk from CVE-2026-3368.