CVE-2021-25108

IP2Location Country Blocker <= 2.26.5 - Arbitrary Country Ban via Cross-Site Request Forgery

2022-01-06 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 2.26.6
Affected Version
<= 2.26.5
CVSS
7.1High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2021-25108
View all IP2Location Country Blocker vulnerabilities

At a glance

CVE-2021-25108 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the IP2Location Country Blocker WordPress plugin, affecting versions <= 2.26.5. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high availability impact). Exploitation requires no authentication. The issue is fixed in version 2.26.6; sites on affected versions should update now. Disclosed January 2022, reported by Krzysztof Zając.

Vulnerability Overview

The IP2Location Country Blocker WordPress plugin before 2.26.6 does not have CSRF check in the ip2location_country_blocker_save_rules AJAX action, allowing attackers to make a logged in admin block arbitrary country, or block all of them at once, preventing users from accessing the frontend.

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. A successful exploit has high impact on availability.

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

Reaching this weakness in IP2Location Country Blocker <= 2.26.5 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 IP2Location Country Blocker the fix is 2.26.6: builds <= 2.26.5 are affected, anything from 2.26.6 onward is not.

Remediation

Update to version 2.26.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to IP2Location Country Blocker: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: IP2Location Country Blocker 2.26.6 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