HomeWordPress vulnerabilitiesInjection Guard
Injection Guard vulnerabilities
Injection Guard has 2 known vulnerabilities in this database. The most recent published record is dated 21 Mar 2026.
- Known vulnerabilities
- 2
- Active installs
- 1,000+
- Latest version
- 1.3.1
- Last updated
- 2 Jul 2026
- Most recent
- 21 Mar 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-3368 | High 7.2 | Up to 1.2.9 | Fixed in a later version (latest 1.3.1) | 21 Mar 2026 |
| Cross-site scripting (XSS) CVE-2025-8046 | Medium 6.1 | Before 1.2.8 | Fixed in 1.2.8 | 14 Aug 2025 |
Read the published descriptions
- CVE-2026-3368, 21 Mar 2026
- 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. CVE record
- CVE-2025-8046, 14 Aug 2025
- The Injection Guard WordPress plugin before 1.2.8 does not escape the $_SERVER['REQUEST_URI'] parameter before outputting it back in an attribute, which could lead to Reflected Cross-Site Scripting in old web browsers CVE record
What to do if you run Injection Guard
If you run Injection Guard, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Injection Guard vulnerabilities
Free. We email you when a new vulnerability is published for Injection Guard, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.