dbcve.org
Country BlockerWordPress extension · Ip2location

CVE-2024-22294

HIGH · 7.5 CVSS v3.1 Published 2024-01-24
Fix available
A fix is available. Upgrade to 2.33.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in IP2Location IP2Location Country Blocker.This issue affects IP2Location Country Blocker: from n/a through 2.33.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An information disclosure vulnerability in the IP2Location Country Blocker WordPress plugin allows unauthenticated actors to access sensitive data. The vulnerability affects versions up to 2.33.3 and rates 7.5 on the CVSS scale, indicating significant risk of exposing potentially location-based visitor data or blocking rules.

MitigationUpdate IP2Location Country Blocker to the latest version if available, or review plugin configuration and access logs for signs of unauthorized data access. If no update exists, consider disabling the plugin until a patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Country BlockerWordPress extension
Affected:< 2.33.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > IP2Location Country Blocker and view the version number. Alternatively, inspect the plugin main file header in wp-content/plugins/ip2location-country-blocker/ip2location-country-blocker.php
    Affected if The installed version is 2.33.3 or lower (any version below 2.33.4)
  2. Confirm plugin is active
    Verify the IP2Location Country Blocker plugin is currently activated in the WordPress site. Check via Plugins > Installed Plugins status
    Affected if The plugin is active and the version is below 2.33.4
  3. Review access logs for suspicious patterns
    Examine web server access logs (Apache error_log, Nginx access.log, or WordPress debug logs) for unusual requests to IP2Location Country Blocker endpoints, particularly any direct access attempts to plugin files from unauthenticated sources
    Affected if Unusual or high volume of requests to plugin endpoints from unauthenticated IP addresses observed

If the IP2Location Country Blocker plugin is installed at version 2.33.3 or below and is active, the environment is affected by this information disclosure vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.33.4 or later
Fixed in 2.33.4
Interim mitigation

Update IP2Location Country Blocker to the latest version if available, or review plugin configuration and access logs for signs of unauthorized data access. If no update exists, consider disabling the plugin until a patch is released.

Recommended fix High confidence

Version 2.33.4 or later of IP2Location Country Blocker plugin

  1. 1. Backup your WordPress site and database before performing any updates
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find IP2Location Country Blocker in the plugin list
  5. 5. If an update is available, click 'Update Now' to update to version 2.33.4 or higher
  6. 6. Alternatively, you can update manually by downloading the latest version from the WordPress plugin repository
  7. 7. After updating, verify the plugin is running version 2.33.4 or higher in the Plugins section
  8. 8. Test that the Country Blocker functionality works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Country Blocker Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22294 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22294 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data