LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24612: WordPress Orchid Store theme <= 1.5.15 - Broken Access Control vulnerability

Missing Authorization vulnerability in themebeez Orchid Store orchid-store allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Orchid Store: from n/a through <= 1.5.15.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24612 affects the WordPress Orchid Store theme through version 1.5.15. It is a missing authorization issue that can let an unauthenticated attacker perform an unauthorized action. The rated impact is limited to integrity, not confidentiality or availability, but exposed WordPress sites using this theme should be reviewed.

Executive priority

Treat as a moderate-priority WordPress exposure. It is not currently reported as actively exploited in the provided sources, but it requires timely inventory and vendor-guided remediation because unauthenticated attackers may be able to make unauthorized changes.

Technical view

The CVE describes CWE-862 Missing Authorization in themebeez Orchid Store for WordPress, affecting versions up to and including 1.5.15. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites with the Orchid Store theme installed at version 1.5.15 or earlier. The vulnerability is remotely reachable according to the CVSS vector. The source bundle does not identify specific endpoints, actions, or deployment conditions required for exploitation.

Exploitation context

The CVE record indicates unauthenticated network exploitation is possible, but there is no KEV listing and no cited source in the bundle states active exploitation. Public details in the provided sources are limited, so operational risk depends on whether vulnerable theme code is present and reachable on the site.

Researcher notes

The public bundle lacks endpoint-level detail, proof of concept, or confirmed fixed version. Avoid assuming exploitability beyond the CVSS and CWE data. Useful next steps are controlled code review of Orchid Store <=1.5.15 and monitoring the Patchstack entry for expanded advisory content.

Mitigation direction

  • Inventory WordPress sites using the Orchid Store theme.
  • Check whether installed Orchid Store versions are 1.5.15 or earlier.
  • Review Themebeez, WordPress, and Patchstack guidance for a fixed version or workaround.
  • Remove or disable the theme if it is unused.
  • Prioritize internet-facing ecommerce or business-critical WordPress sites.

Validation and detection

  • Confirm the theme name and version from WordPress administration or asset inventory.
  • Check public site inventories for Orchid Store on externally exposed WordPress sites.
  • Review web logs for unusual unauthenticated requests to theme-related functionality.
  • Monitor Patchstack and CVE records for added technical details or remediation updates.
  • Document whether vulnerable versions remain in production.
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-24612 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-24612Attack 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
themebeezOrchid Storeorchid-store, 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.