LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32383: WordPress Ridhi theme <= 1.1.2 - Broken Access Control vulnerability

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

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32383 is a broken access control issue in the WordPress Ridhi theme through version 1.1.2. A remote attacker may reach functionality that should require authorization, potentially causing limited availability impact. The public record does not show data theft or content modification impact, and no active exploitation is cited.

Executive priority

Treat as a routine but timely WordPress exposure issue. It is remotely reachable and unauthenticated, but currently rated medium with only limited availability impact and no cited active exploitation.

Technical view

The CVE describes CWE-862 Missing Authorization in raratheme Ridhi. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges, no user interaction, unchanged scope, with low availability impact only. Public details do not identify the exact endpoint, patch version, or exploit method.

Likely exposure

Internet-facing WordPress sites using the Ridhi theme version 1.1.2 or earlier are the likely exposure group. Sites not using this theme are not indicated as affected.

Exploitation context

The CVSS vector indicates unauthenticated network exploitation without user interaction. However, the source bundle provides no proof-of-concept, no endpoint details, and no KEV listing or cited active exploitation evidence.

Researcher notes

Public information is sparse. The record names missing authorization in Ridhi through 1.1.2 but does not disclose the vulnerable component, fixed version, or exploitation conditions beyond CVSS. Avoid assuming confidentiality or integrity impact not present in the CVSS vector.

Mitigation direction

  • Inventory WordPress sites for the Ridhi theme and its installed version.
  • If Ridhi is version 1.1.2 or earlier, review vendor and Patchstack guidance.
  • Update the theme if a fixed release is available from trusted sources.
  • If no fix is available, consider disabling or replacing the theme.
  • Prioritize externally reachable WordPress sites for review first.

Validation and detection

  • Check WordPress admin theme details for Ridhi version information.
  • Confirm theme files and metadata match installed production versions.
  • Review vulnerability scanner results against CVE-2026-32383 or Patchstack entry.
  • Verify whether affected sites are publicly reachable.
  • Document any compensating controls or theme removal.
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-32383 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:N/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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-32383Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
rarathemeRidhiridhi, 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.