CVE-2025-1361

IP2Location Country Blocker <= 2.38.8 - Missing Authorization to Unauthenticated Information Exposure via admin_init Function

2025-02-21 19:56
abrahack

Strategic Overview

Status
Patched in 2.38.9
Affected Plugin
IP2Location Country Blocker
Affected Version
<= 2.38.8
CVSS
7.5High
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2025-1361
View all IP2Location Country Blocker vulnerabilities

At a glance

CVE-2025-1361 is a high-severity Improper Authorization vulnerability in the IP2Location Country Blocker WordPress plugin, affecting versions <= 2.38.8. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.38.9; sites on affected versions should update now. Disclosed February 2025, reported by abrahack.

Vulnerability Overview

The IP2Location Country Blocker plugin for WordPress is vulnerable to Regular Information Exposure in all versions up to, and including, 2.38.8 due to missing capability checks on the admin_init() function. This makes it possible for unauthenticated attackers to view the plugin's settings.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-285: Improper Authorization

IP2Location Country Blocker <= 2.38.8 carries this weakness at admin_init(), and reaching it takes no account at all. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For IP2Location Country Blocker the fix is 2.38.9: builds <= 2.38.8 are affected, anything from 2.38.9 onward is not.

Remediation

Update to version 2.38.9, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: IP2Location Country Blocker 2.38.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-1361https://www.wordfence.com/threat-intel/vulnerabilities/id/b63bc2b6-1abc-4cfa-a7e5-3995640f66a7https://nvd.nist.gov/vuln/detail/CVE-2025-1361

Related records

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