LiveActive security incident?Get immediate response
CVE Record

CVE-2023-39998: WordPress BeTheme theme <= 27.1.1 - Author+ Broken Access Control vulnerability

Missing Authorization vulnerability in Muffingroup Betheme.This issue affects Betheme: from n/a through 27.1.1.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-39998 is a high-severity access-control flaw in the WordPress Betheme theme through version 27.1.1. A user with Author-level privileges or higher may access functionality or data they should not. The main business risk is unauthorized exposure of sensitive information on affected WordPress sites.

Executive priority

Treat this as a near-term remediation item for any public WordPress site using Betheme. It is not reported as actively exploited in the supplied sources, but the confidentiality impact is high and Author-level accounts are often harder to govern than administrator accounts.

Technical view

The CVE describes a missing authorization issue, CWE-862, in Muffingroup Betheme through 27.1.1. The CVSS 3.1 score is 8.2 with network attack vector, low complexity, high privileges required, no user interaction, changed scope, high confidentiality impact, and low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress installations using Betheme through 27.1.1 where an attacker already has Author-level or higher authenticated access. Sites with multiple authors, guest contributors, weak account controls, or compromised WordPress users face greater practical risk.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The vulnerability is still important because authenticated Author-level access is common on content-heavy WordPress sites, and broken authorization can turn a low-trust contributor account into a broader data exposure path.

Researcher notes

Evidence is sparse in the supplied bundle. The CVE and Patchstack reference identify missing authorization in Betheme through 27.1.1, but no affected endpoint, fixed version, proof of exploitation, or detailed mitigation is included. Avoid assumptions beyond authenticated Author+ exposure and vendor-guidance remediation.

Mitigation direction

  • Inventory WordPress sites using the Betheme theme.
  • Identify any installations running Betheme 27.1.1 or earlier.
  • Check Muffingroup and Patchstack guidance for a patched release or mitigation.
  • Restrict Author-level access to trusted users only.
  • Review and remove dormant or unnecessary WordPress accounts.
  • Monitor affected sites for unexpected author account activity.

Validation and detection

  • Confirm the installed Betheme version from WordPress administration or asset inventory.
  • Review WordPress user roles and identify Author-level or higher accounts.
  • Check whether all contributor accounts are still required and individually owned.
  • Verify vendor or Patchstack guidance before declaring remediation complete.
  • Look for unusual content-management activity by Author-level accounts.
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 · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
cve · low confidence lookup

CVE-2023-39998 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
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

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

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
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:L2.35.3Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2023-39998Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
MuffingroupBethemen/aunaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.