fahadmahmood Injection Guard Plugin up to 1.2.9 on WordPress Injection Guard Log Interface ig_settings.php sanitize_ig_data $_SERVER['QUERY_STRING'] cross site scripting

Summaryinfo

A vulnerability was found in fahadmahmood Injection Guard Plugin up to 1.2.9 on WordPress. It has been classified as problematic. Affected by this vulnerability is the function sanitize_ig_data of the file ig_settings.php of the component Injection Guard Log Interface. This manipulation of the argument $_SERVER['QUERY_STRING'] causes cross site scripting. This vulnerability is handled as CVE-2026-3368. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in fahadmahmood Injection Guard Plugin up to 1.2.9 on WordPress. It has been declared as problematic. Affected by this vulnerability is the function sanitize_ig_data of the file ig_settings.php of the component Injection Guard Log Interface. The manipulation of the argument $_SERVER['QUERY_STRING'] with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is:

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.

The weakness was released by Itthidej Aramsri. It is possible to read the advisory at wordfence.com. This vulnerability is known as CVE-2026-3368 since 02/27/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

By approaching the search of inurl:ig_settings.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 1.2.8 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• fahadmahmood

Name

• Injection Guard Plugin

Version

• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.2.4
• 1.2.5
• 1.2.6
• 1.2.7
• 1.2.8
• 1.2.9

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion