LiveActive security incident?Get immediate response
CVE Record

CVE-2023-41134: WordPress Antispam Bee plugin <= 2.11.3 - Country IP Restriction Bypass vulnerability

Authentication Bypass by Spoofing vulnerability in pluginkollektiv Antispam Bee allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Antispam Bee: from n/a through 2.11.3.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects the WordPress Antispam Bee plugin through version 2.11.3. An attacker may bypass country/IP restriction logic by spoofing identity-related information, reducing the reliability of controls meant to restrict unwanted activity. The published impact is limited to integrity, not data theft or service outage.

Executive priority

Treat as a moderate WordPress plugin risk. Prioritize sites where Antispam Bee restrictions influence public-facing spam controls or access decisions, but do not escalate as actively exploited based on the provided evidence.

Technical view

CVE-2023-41134 is a CWE-290 authentication bypass by spoofing in pluginkollektiv Antispam Bee through 2.11.3. The CVSS 3.1 score is 5.3: network exploitable, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact only.

Likely exposure

Exposure is likely limited to WordPress sites running Antispam Bee version 2.11.3 or earlier, especially where country/IP restriction behavior is relied on for spam or access control decisions.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Public data supports a remotely reachable, low-complexity bypass, but not exploit maturity, weaponization, or observed attacks.

Researcher notes

Evidence is concise: affected versions are through 2.11.3, weakness is spoofing-based authentication bypass, and impact is low integrity only. The provided sources do not identify a fixed version, proof of exploitation, or detailed vulnerable code path.

Mitigation direction

  • Inventory WordPress sites for Antispam Bee through version 2.11.3.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed version or workaround.
  • Update the plugin if a vendor-supported fixed release is available.
  • Do not rely solely on country/IP restriction for security-sensitive decisions.
  • Review moderation and access logs for suspicious restriction bypass patterns.

Validation and detection

  • Confirm whether Antispam Bee is installed and record the exact version.
  • Verify whether country/IP restriction functionality is enabled or security-relevant.
  • Compare plugin findings against the CVE and Patchstack advisory scope.
  • Review logs for activity that conflicts with configured country/IP restrictions.
  • Document compensating controls if no vendor fix is confirmed.
Prepared
Confidence
medium
Sources
3

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-290: 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
cve · low confidence lookup

CVE-2023-41134 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
2Source 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-2023-41134Attack 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
pluginkollektivAntispam Beeantispam-bee, n/aunaffected
Weakness

CWE details

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

CWE-290 · source CWE mapping

Authentication Bypass by Spoofing

Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.