Injection Guard <= 1.2.1 - Cross-Site Request Forgery via ig_update

2023-05-11 00:00
Anonymous

Strategic Overview

Status
Patched in 1.2.2
Affected Plugin
Injection Guard
Affected Version
<= 1.2.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Injection Guard vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Injection Guard WordPress plugin, affecting versions <= 1.2.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.2; sites on affected versions should update now. Disclosed May 2023.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Injection Guard <= 1.2.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Injection Guard the fix is 1.2.2: builds <= 1.2.1 are affected, anything from 1.2.2 onward is not.

Remediation

Update to version 1.2.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Injection Guard: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Injection Guard 1.2.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C