CVE-2026-1675 json
Advanced Country Blocker <= 2.3.1 - Unauthenticated Authorization Bypass via Insecure Default Secret Key
published 2026-02-07 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-5741
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
The Advanced Country Blocker plugin for WordPress is vulnerable to Authorization Bypass in all versions up to, and including, 2.3.1 due to the use of a predictable default value for the secret bypass key created during installation without requiring users to change it. This makes it possible for unauthenticated attackers to bypass the geolocation blocking mechanism by appending the key to any URL on sites where the administrator has not changed the default value.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- brstefanovic Advanced Country Blocker
Classification
- Weakness
-
- CWE-1188 Initialization of a Resource with an Insecure Default
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/30747988-83f9-41f9-9bc5-1f533bc4cb94?source=cve
- plugins.trac.wordpress.org /browser/advanced-country-blocker/tags/2.3.1/advanced-country-blocking.php#L278
- plugins.trac.wordpress.org /browser/advanced-country-blocker/tags/2.3.1/advanced-country-blocking.php#L336
- plugins.trac.wordpress.org /browser/advanced-country-blocker/tags/2.3.1/advanced-country-blocking.php#L420
- plugins.trac.wordpress.org /changeset/3455225/
Sources
- CVE List CVE-2026-1675
- NVD CVE-2026-1675
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.