Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-3368

HIGH · 7.2 CVSS v3.1 Published 2026-03-21

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

81/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · high confidence

The Injection Guard WordPress plugin (versions up to 1.2.9) has a stored XSS vulnerability where the sanitize_ig_data() function only sanitizes array values but not array keys. The plugin captures the query string, applies esc_url_raw() (which preserves URL-encoded characters), then parse_str() URL-decodes it. Malicious HTML/JavaScript in array keys gets stored via update_option() and later rendered without escaping in the admin log page, executing when administrators view the log.

MitigationUpdate to version 1.3.0 or later which adds sanitization for array keys and output escaping in the template. Until then, disable the plugin or restrict admin access to prevent log viewing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Injection Guard plugin is installed

Navigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Injection Guard', or inspect the plugin directory at /wp-content/plugins/ for a folder named 'injection-guard' or similar

Affected if The plugin is present in the WordPress installation
Determine installed plugin version

In WordPress admin, click on the plugin from the plugin list to view its details, or read the main plugin file header (usually injection-guard.php) for the 'Version' comment

Affected if The version number is 1.2.9 or lower (versions up to and including 1.2.9 are affected)
Confirm plugin is active

Check the 'Status' column in WordPress Plugins admin page; the plugin must be active for the vulnerability to be exploitable

Affected if The plugin status shows as 'Active'
Identify admin log page access

Attempt to access the plugin's log viewing page in the WordPress admin (typically under Tools or a dedicated Injection Guard admin menu), or examine plugin code for update_option calls storing query string data

Affected if An administrator account can access the log page where unsanitized array keys would be rendered

A user is affected if the Injection Guard plugin is installed with version 1.2.9 or lower and an administrator can access the plugin's log page where stored XSS would execute.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update to version 1.3.0 or later which adds sanitization for array keys and output escaping in the template. Until then, disable the plugin or restrict admin access to prevent log viewing.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,240

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-3368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3368 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-3368?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 7.2 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 7 hrs · Moderate

Typical engagement from $1,240

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-3368 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References