Country BlockerWordPress extension · Ip2location
CVE-2023-37865
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 · uneditedAuthentication Bypass by Spoofing vulnerability in IP2Location Download IP2Location Country Blocker allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Download IP2Location Country Blocker: from n/a through 2.29.1.
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 confidenceAuthentication bypass vulnerability in IP2Location Country Blocker allows unauthorized access to restricted functionality through spoofing, enabling attackers to bypass ACL constraints and potentially execute administrative actions they should not have access to.
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
< 2.29.2CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify IP2Location Country Blocker is installedCheck your WordPress plugins directory or admin panel for the IP2Location Country Blocker plugin presenceAffected if The plugin is found in the WordPress installation
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > IP2Location Country Blocker and note the version number displayedAffected if Version shown is below 2.29.2 (e.g., 2.29.1, 2.28.0, etc.)
-
Check plugin file version constantIf admin access is unavailable, inspect the main plugin file (e.g., ip2location-country-blocker.php) for the version defined in the plugin header commentAffected if The Version field in the plugin header is less than 2.29.2
-
Verify ACL bypass is exploitableConfirm the Country Blocker access control settings are configured with restricted rules (e.g., specific countries blocked, whitelist mode enabled, or role-based restrictions applied)Affected if ACL rules are active and the plugin version is below 2.29.2
You are affected if the IP2Location Country Blocker plugin is installed with a version number lower than 2.29.2 and has access control rules configured.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.29.2
Update the IP2Location Country Blocker plugin to version 2.29.2 or later. Review user role permissions and access controls after patching.
2.29.2
- Backup your WordPress site and database before making any changes
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Find the 'Country Blocker' plugin by IP2Location
- Click 'Update now' if an update is available, or manually upload version 2.29.2
- Verify the plugin version shows 2.29.2 or later after updating
- Test that the Country Blocker functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Country Blocker
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37865 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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