LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32380: WordPress Numinous theme <= 1.3.0 - Broken Access Control vulnerability

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

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32380 is a broken access control flaw in the WordPress Numinous theme by raratheme, affecting versions through 1.3.0. It may let an unauthenticated network attacker perform an unauthorized action with limited integrity impact. Public sources rate it medium severity. No cited source indicates active exploitation.

Executive priority

Treat this as a moderate-priority WordPress exposure. It is remotely reachable and unauthenticated, but public scoring indicates limited integrity impact and no known active exploitation. Address during near-term website maintenance, faster for high-value or externally exposed WordPress properties.

Technical view

The issue is classified as missing authorization, CWE-862. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact, and no confidentiality or availability impact. The public description does not identify the specific affected function or request path.

Likely exposure

Exposure is most likely on WordPress sites that have the Numinous theme installed at version 1.3.0 or earlier, especially internet-facing sites. The CVSS vector indicates exploitation does not require authentication or user interaction. Public data does not confirm whether the theme must be active.

Exploitation context

The vulnerability could enable unauthorized modification or action because authorization checks are missing or misconfigured. The available sources do not provide technical exploit details, confirmed exploitation, or evidence of inclusion in CISA KEV.

Researcher notes

Public information is sparse. The CVE and Patchstack entry identify missing authorization in Numinous through 1.3.0, but do not provide affected endpoints, patch version, proof of exploitation, or detailed impact. Avoid assuming exploitability beyond the published CVSS vector and description.

Mitigation direction

  • Inventory WordPress sites for the Numinous theme and record installed versions.
  • Prioritize sites running Numinous 1.3.0 or earlier for remediation review.
  • Check raratheme, WordPress theme repository, and Patchstack guidance for a fixed version.
  • Update the theme if a vendor-supported fixed release is available.
  • If no fix is available, consider disabling or replacing the theme.

Validation and detection

  • Confirm whether each WordPress site has Numinous installed or active.
  • Verify the installed Numinous version is above 1.3.0, if a fixed version exists.
  • Review web and application logs for unusual unauthenticated actions.
  • Monitor vendor and Patchstack records for updated remediation details.
  • Document compensating controls if the theme cannot be removed or updated.
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-32380 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-32380Attack 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
rarathemeNuminousnuminous, 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.