| CVE | CVE-2026-3368 |
|---|---|
| CVSS | 7.2 (High) |
| Publicly Published | March 20, 2026 |
| Last Updated | March 20, 2026 |
| Researcher |
Itthidej Aramsri (Boeing777)
|
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 sanitize_ig_data() function which only sanitizes array values but not array keys, combined with missing output escaping in the ig_settings.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['QUERY_STRING'], applies esc_url_raw() (which preserves URL-encoded special characters like %22, %3E, %3C), then passes it to parse_str() which URL-decodes the string, resulting in decoded HTML/JavaScript in the array keys. These keys are stored via update_option('ig_requests_log') and later rendered without esc_html() or esc_attr() 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.
Learn more about Cross-Site Scripting vulnerabilities and how to prevent them.
| Software Type | Plugin |
|---|---|
| Software Slug | injection-guard (view on wordpress.org) |
| Patched? | Yes |
| Remediation | Update to version 1.3.0, or a newer patched version |
| Affected Version |
|
| Patched Version |
|
| # | Title | CVE ID | CVSS | Researchers | Date |
|---|---|---|---|---|---|
| 1 | Injection Guard <= 1.2.7 - Reflected Cross-Site Scripting | CVE-2025-8046 | Bob Matyas | July 24, 2025 | |
| 2 | Injection Guard <= 1.2.1 - Missing Authorization via ig_update | CVE-2023-32574 | Abdi Pranata | May 11, 2023 | |
| 3 | Injection Guard <= 1.2.1 - Cross-Site Request Forgery via ig_update | May 11, 2023 | |||
| 4 | Injection Guard <= 1.2.1 - Missing Authorization to Whitelist Update | Darius Sveikauskas | May 10, 2023 | ||
| 5 | Injection Guard <= 1.2.1 - Cross-Site Request Forgery to Whitelist Update | Darius Sveikauskas | May 10, 2023 |
This record contains material that is subject to copyright.
Copyright 2012-2026 Defiant Inc.
License: Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy. Read more.
Copyright 1999-2026 The MITRE Corporation
License: CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy. Read more.
Have information to add, or spot any errors? Contact us at wfi-support@wordfence.com so we can make any appropriate adjustments.
Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!
Learn moreWant to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.
The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.
Documentation