LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32371: WordPress Elegant Pink theme <= 1.3.3 - Broken Access Control vulnerability

Missing Authorization vulnerability in raratheme Elegant Pink elegant-pink allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Elegant Pink: from n/a through <= 1.3.3.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32371 affects the WordPress Elegant Pink theme through version 1.3.3. The issue is broken access control, meaning the theme may allow actions without proper authorization. The published severity is medium because the known impact is limited to integrity, not data theft or outage. No cited source indicates active exploitation.

Executive priority

Treat as a moderate-priority WordPress exposure. It is remotely reachable and unauthenticated per CVSS, but known impact is limited and no active exploitation is cited. Prioritize validation and remediation where the theme is used on public or high-value sites.

Technical view

The CVE describes CWE-862 Missing Authorization in raratheme Elegant Pink, package name elegant-pink, affecting versions up to 1.3.3. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact only. Public details do not specify the vulnerable endpoint or a confirmed fixed version.

Likely exposure

Exposure is most likely on public WordPress sites using the Elegant Pink theme at version 1.3.3 or earlier. Sites not using this theme are not affected based on the provided sources.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not report active exploitation. The CVSS vector suggests remote unauthenticated access is possible, but public details are insufficient to describe practical attack conditions.

Researcher notes

Public disclosure is sparse. The CVE identifies missing authorization and low integrity impact, but does not provide endpoint, action, proof of concept, or fix details in the supplied bundle. Avoid assuming exploitability beyond the CVSS and advisory text.

Mitigation direction

  • Inventory WordPress sites for the Elegant Pink theme and installed version.
  • If version is 1.3.3 or earlier, check vendor, WordPress, and Patchstack guidance.
  • Upgrade to a vendor-supported fixed version if one is available.
  • If no fix is available, consider replacing or disabling the theme.
  • Prioritize internet-facing and business-critical WordPress sites first.

Validation and detection

  • Confirm whether the Elegant Pink theme is installed on each WordPress site.
  • Record the exact theme version and compare it to 1.3.3.
  • Review vendor or Patchstack advisories for fixed-version information.
  • Check security monitoring for unexpected content or configuration changes.
  • Document remediation status for affected WordPress assets.
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-32371 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-32371Attack 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
rarathemeElegant Pinkelegant-pink, 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.