Injection Guard <= 1.2.1 - Cross-Site Request Forgery via ig_update
The Injection Guard plugin for WordPress is vulnerable to Cross-Site Request Forgery due to a missing nonce check on the ig_update functions in versions up to, and including, 1.2.1. This makes it possible for unauthenticated attackers to make changes to IP block- and allowlists via a forged request granted they can trick an admin into performing an action such as clicking on a link.
This vulnerability is a medium severity with CVSS 4.3 Cross-Site Request Forgery issue affecting the Plugin Injection Guard. It affects Versions up to 1.2.1 and is fixed in 1.2.2.
Review the full Injection Guard vulnerability cluster
Use the related hub and response guides to connect this vulnerability report with patch validation, scanner checks, and site hardening work.
Open the grouped hub for related CVEs, affected ranges, severity mix, and patch coverage.
Check access, XML-RPC exposure, backup readiness, and monitoring after patching.
Use containment, evidence capture, remediation, and validation steps when exploit risk is high.
the tracked vulnerability is tracked for the Plugin Injection Guard as medium severity with CVSS 4.3. The affected range is Versions up to 1.2.1. Update Injection Guard to 1.2.2 or newer where that version is compatible with the site.
Why this report is useful for search and triage
Search engines and operators need more than a title. This page exposes the identifier, affected range, patch evidence, and source coverage that make the vulnerability actionable.
This report uses the upstream feed identifier because a CVE has not been attached to the record yet.
Affected version data gives operators a concrete comparison point against installed WordPress software.
A fixed version is present, so the page can answer update and remediation intent directly.
External references are available for source validation, advisory review, and incident notes.
How to validate this finding
Use these checks when converting this record into a patch ticket, incident note, or risk acceptance decision.
Inventory the installed Plugin package and compare its version with Versions up to 1.2.1.
Confirm Injection Guard is updated to 1.2.2 or newer.
Review references and CVSS vector details for exploitability, authentication requirements, and exposure path.
After patching, re-run vulnerability monitoring and keep the related plugin or theme hub under review for follow-up CVEs.
| Software Type | Plugin |
|---|---|
| Software Slug |
injection-guard
View on wordpress.org
|
| CVE | No linked CVE entry. |
| Patched Versions |
1.2.2
|
| Affected Versions |
Versions up to 1.2.1
|
Related CVEs for Injection Guard
These internal links group the same WordPress plugin by CVE, issue type, severity, and patch status so operators and search engines can connect the full vulnerability cluster.
Injection Guard <= 1.2.9 - Unauthenticated Stored Cross-Site Scripting via Query Parameter Name
Injection Guard <= 1.2.7 - Reflected Cross-Site Scripting
Injection Guard <= 1.2.1 - Missing Authorization via ig_update
Injection Guard <= 1.2.1 - Missing Authorization to Whitelist Update
Injection Guard <= 1.2.1 - Cross-Site Request Forgery to Whitelist Update
This record contains material that is subject to copyright
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