LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51542: WordPress Branda plugin <= 3.4.14 - IP Restriction Bypass vulnerability

Authentication Bypass by Spoofing vulnerability in WPMU DEV Branda allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Branda: from n/a through 3.4.14.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-51542 affects the WordPress Branda plugin through version 3.4.14. A remote unauthenticated attacker may bypass IP restriction logic by spoofing, potentially reaching functionality that should be access-controlled. The cited impact is limited integrity impact, not data disclosure or service outage.

Executive priority

Treat this as a moderate-priority WordPress plugin exposure. It does not show evidence of active exploitation in the supplied sources, but it affects unauthenticated remote access-control behavior and should be remediated during normal vulnerability management cycles.

Technical view

This is a CWE-290 authentication bypass by spoofing in WPMU DEV Branda. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges or user interaction required, unchanged scope, no confidentiality or availability impact, and low integrity impact.

Likely exposure

Exposure is most likely on WordPress sites running Branda, package branda-white-labeling, at version 3.4.14 or earlier, especially where Branda IP restrictions are treated as a security boundary for protected functionality.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not listed as KEV. The CVSS vector indicates unauthenticated remote reachability, but the provided sources do not include exploit availability, exploitation volume, or detailed attack procedure.

Researcher notes

The provided evidence is limited to the CVE metadata and Patchstack listing. Sources identify the affected product and version range, CWE-290, and CVSS vector, but do not provide patch version, exploit status, indicators of compromise, or detailed technical root cause.

Mitigation direction

  • Inventory WordPress sites using WPMU DEV Branda.
  • Identify any Branda installations at version 3.4.14 or earlier.
  • Check WPMU DEV and Patchstack guidance for fixed versions or compensating controls.
  • Upgrade affected Branda installations when a vendor-supported fixed version is available.
  • Avoid relying solely on Branda IP restrictions for sensitive access control.

Validation and detection

  • Confirm installed Branda version on each WordPress site.
  • Review whether Branda IP restriction features are enabled.
  • Check access logs for unexpected requests to restricted functionality.
  • Verify vendor advisory status before closing remediation tickets.
  • Retest access-control behavior after updating or changing configuration.
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-51542 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-51542Attack 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
WPMU DEVBrandabranda-white-labeling, 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.