LiveActive security incident?Get immediate response
CVE Record

CVE-2022-45353: WordPress Betheme theme <= 26.6.1 is vulnerable to Broken Access Control

Broken Access Control in Betheme theme <= 26.6.1 on WordPress.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-45353 affects WordPress sites using the Betheme theme version 26.6.1 or earlier. It is a broken access control issue, meaning a logged-in low-privileged user may access information they should not. The published CVSS score is 4.3, so urgency is moderate, not emergency-level.

Executive priority

Treat this as a moderate-risk web exposure issue. It is most relevant for public WordPress sites that allow user logins. Remediation should be scheduled promptly through normal patch management, with higher priority for customer-facing or high-trust sites.

Technical view

The issue is classified as CWE-863 in Muffingroup Betheme <= 26.6.1. CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N indicates remote reachability, low attack complexity, required low privileges, no user interaction, and limited confidentiality impact only.

Likely exposure

Exposure is likely limited to WordPress sites running Betheme 26.6.1 or earlier, especially where untrusted or semi-trusted users can log in. The source bundle does not identify a specific vulnerable endpoint or configuration dependency.

Exploitation context

The source bundle does not provide evidence of active exploitation, and the CVE is not listed as KEV. Successful abuse requires a low-privileged authenticated user and is described as limited to confidentiality impact, with no integrity or availability impact in the CVSS vector.

Researcher notes

Evidence is sparse in the provided bundle. The CVSS vector supports authenticated, low-complexity access with limited confidentiality impact. No exploit details, vulnerable endpoint, fixed version, or vendor mitigation text are included, so validation should stay inventory-focused unless vendor guidance provides more detail.

Mitigation direction

  • Inventory WordPress sites using the Betheme theme.
  • Check current Betheme versions against 26.6.1 or earlier.
  • Review Muffingroup or Patchstack guidance for fixed versions or mitigations.
  • Restrict unnecessary low-privileged WordPress accounts until remediated.
  • Prioritize update testing on externally reachable WordPress sites.

Validation and detection

  • Confirm whether Betheme is installed and active on each WordPress site.
  • Record the installed Betheme version from trusted administrative inventory.
  • Review user roles for unnecessary subscriber, contributor, or customer access.
  • Check access logs for unusual authenticated access patterns.
  • Track vendor advisory updates for fixed-version confirmation.
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-863: 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-2022-45353 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2022-45353Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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
MuffingroupBethemen/aunaffected
Weakness

CWE details

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

CWE-863 · source CWE mapping

Incorrect Authorization

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