LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1675: Advanced Country Blocker <= 2.3.1 - Unauthenticated Authorization Bypass via Insecure Default Secret Key

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1675 affects the Advanced Country Blocker WordPress plugin through version 2.3.1. Sites that kept the plugin’s default bypass secret may let unauthenticated visitors bypass country-based blocking. This does not grant admin access, but it can defeat a business control used to restrict traffic by geography.

Executive priority

Treat this as a moderate-priority web control bypass. Prioritize sites that depend on country blocking for fraud reduction, compliance segmentation, or abuse prevention. It is less urgent than remote code execution or data theft vulnerabilities, but should be remediated promptly where the plugin enforces business policy.

Technical view

The plugin used a predictable default value for a secret bypass key created during installation and did not require administrators to change it. An unauthenticated attacker who knows that default can access URLs despite the geolocation blocking mechanism. The CVSS 3.1 score is 5.3, with low integrity impact and no confidentiality or availability impact stated.

Likely exposure

WordPress sites using Advanced Country Blocker up to and including 2.3.1 are potentially exposed, especially if administrators did not change the default bypass key after installation. Exposure is limited to bypassing the plugin’s geolocation blocking function, based on the provided sources.

Exploitation context

The issue is network-accessible, low-complexity, and requires no authentication or user interaction. The source bundle does not indicate active exploitation, and the CVE is not listed as KEV. Attackers would need knowledge of the default bypass behavior and a target using the vulnerable configuration.

Researcher notes

Sources identify CWE-1188 and point to plugin code locations and a WordPress changeset. The provided data does not clearly name a fixed version. Validate exposure by configuration review rather than public probing. Avoid assuming broader WordPress compromise; the documented impact is bypass of geolocation blocking.

Mitigation direction

  • Identify WordPress sites running Advanced Country Blocker through version 2.3.1.
  • Change any default bypass secret key to a strong unique value.
  • Check the plugin repository or vendor guidance for an updated fixed release.
  • Do not rely on this plugin alone for high-risk access restrictions.
  • Temporarily disable the bypass feature if business operations allow.

Validation and detection

  • Inventory installed Advanced Country Blocker versions across WordPress environments.
  • Review plugin settings for unchanged default bypass secrets.
  • Confirm geolocation blocking works without using any documented bypass mechanism.
  • Review web logs for suspicious requests targeting bypass behavior.
  • Track Wordfence and WordPress plugin repository updates for fix confirmation.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1188: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1675 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-1675Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
brstefanovicAdvanced Country Blocker0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1188 · source CWE mapping

Initialization of a Resource with an Insecure Default

Initialization of a Resource with an Insecure Default represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.