LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32341: WordPress Benevolent theme <= 1.3.9 - Broken Access Control vulnerability

Missing Authorization vulnerability in raratheme Benevolent benevolent allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Benevolent: from n/a through <= 1.3.9.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32341 affects the WordPress Benevolent theme through version 1.3.9. It is a missing authorization issue, meaning an action may be accessible without the intended permission checks. The published impact is limited to low integrity impact, not data theft or service outage. Treat it as a medium-priority WordPress theme exposure.

Executive priority

Prioritize identification and remediation on public WordPress sites using Benevolent. The issue is not currently evidenced as exploited, but it is remotely reachable and unauthenticated per CVSS. Address during normal vulnerability remediation cycles, faster for high-traffic or business-critical sites.

Technical view

The CVE describes CWE-862 Missing Authorization in raratheme Benevolent. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact. Public sources do not identify the specific vulnerable function, endpoint, fixed version, or workaround.

Likely exposure

Exposure is likely limited to WordPress sites using the Benevolent theme at version 1.3.9 or earlier. Sites not using this theme are not affected based on the provided sources.

Exploitation context

The CVSS vector indicates possible unauthenticated remote interaction with low complexity. The source bundle does not report public exploitation, exploit code, or CISA KEV listing. Do not assume active exploitation without additional evidence.

Researcher notes

Available public details are limited. The CVE and Patchstack reference identify the class and affected range, but not the vulnerable code path or fixed version. Validation should focus on asset/version confirmation and monitoring rather than attempting exploitation.

Mitigation direction

  • Inventory WordPress sites for the Benevolent theme and version.
  • Check vendor, WordPress theme, and Patchstack guidance for a fixed release.
  • Update the theme if a fixed version is available.
  • If no fix is available, consider disabling or replacing the theme.
  • Restrict administrative access and monitor WordPress change activity.

Validation and detection

  • Confirm whether the Benevolent theme is installed or active.
  • Record the installed theme version on each WordPress site.
  • Compare findings against the affected range: through 1.3.9.
  • Review vendor or Patchstack advisories for remediation status.
  • Check logs for unexpected unauthenticated changes or theme-related requests.
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-2026-32341 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-2026-32341Attack 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
rarathemeBenevolentbenevolent, 0unaffected
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.