Iq Block CountryWordPress extension · Webence
CVE-2022-41155
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 · uneditedBlock BYPASS vulnerability in iQ Block Country plugin <= 1.2.18 on WordPress.
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 confidenceThe iQ Block Country plugin for WordPress versions 1.2.18 and below contains a block bypass vulnerability (CVSS 9.8) that allows attackers to circumvent geographic access restrictions implemented by the plugin, potentially enabling unauthorized access from blocked geographic regions.
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
Iq Block CountryWordPress extension
< 1.2.19CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 iQ Block Country plugin is installedCheck WordPress wp-content/plugins/ directory for the 'iq-block-country' folder, or view installed plugins in WordPress admin under Plugins > Installed PluginsAffected if The iQ Block Country plugin folder exists in the plugins directory
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find the iQ Block Country entry to read the version number, or open wp-content/plugins/iq-block-country/readme.txt and check the 'Stable tag' lineAffected if Version displayed is 1.2.18 or lower (any version below 1.2.19)
-
Confirm geo-blocking is actively configuredNavigate to Settings > iQ Block Country in WordPress admin and verify that country blocking is enabled and at least one country or region is selected for blockingAffected if Country blocking is enabled with one or more countries configured in the blocklist
User is affected if iQ Block Country plugin is installed with version 1.2.18 or below AND geo-blocking is actively configured with countries in the blocklist.
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 · scoped1.2.19
Update the iQ Block Country plugin to a version newer than 1.2.18 to patch the bypass vulnerability.
iQ Block Country version 1.2.19
- Create a full backup of your WordPress site (database and files) before making any changes
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'iQ Block Country' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 1.2.19
- After updating, verify the plugin is running version 1.2.19 under Plugins > Installed Plugins
- Test that the country blocking functionality is working correctly by attempting access from a blocked location
- Clear any caching plugins or server-side caches to ensure the new plugin code is active
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Iq Block Country
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41155 — 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-2022-41155 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