LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22400: WordPress Holmes theme <= 1.7 - Insecure Direct Object References (IDOR) vulnerability

Authorization Bypass Through User-Controlled Key vulnerability in Mikado-Themes Holmes holmes allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Holmes: from n/a through <= 1.7.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22400 is a medium-severity access-control flaw in the WordPress Holmes theme. Sites running Holmes version 1.7 or earlier may allow logged-in users to affect objects they should not control. Public sources do not indicate active exploitation or a named vendor patch.

Executive priority

Treat as a routine but time-bound WordPress remediation item. Prioritize internet-facing sites with many contributors, customers, or subscribers. No public source here supports emergency response for active exploitation.

Technical view

The issue is an Insecure Direct Object Reference mapped to CWE-639 in Mikado-Themes Holmes. CVSS 3.1 is 5.4: network reachable, low complexity, privileges required, no user interaction, with low integrity and availability impact and no confidentiality impact.

Likely exposure

Exposure is likely limited to WordPress installations using the Holmes theme through version 1.7, especially where untrusted or low-privileged users can log in. The provided metadata is sparse and has some version-field inconsistency, so asset validation is important.

Exploitation context

Sources describe an authorization bypass through a user-controlled key. Exploitation requires some level of authenticated access. There is no KEV listing and no provided source claims active exploitation.

Researcher notes

The CVE description and Patchstack reference identify Holmes <=1.7 as affected. The bundled affected-version field is inconsistent, listing version “0” while defaulting to unaffected. Do not rely on CPE matching alone; verify theme name and version directly.

Mitigation direction

  • Identify WordPress sites using the Holmes theme.
  • Check whether Holmes is version 1.7 or earlier.
  • Review Mikado-Themes and Patchstack guidance for fixed versions or workarounds.
  • If no supported fix exists, consider disabling or replacing the theme.
  • Restrict or remove unnecessary low-privileged WordPress accounts.

Validation and detection

  • Inventory active and installed WordPress themes across managed sites.
  • Confirm Holmes theme version from administrative or asset records.
  • Review user roles with login access to affected sites.
  • Monitor logs for unusual object modification attempts by low-privileged users.
  • Track CVE and Patchstack entries for updated remediation details.
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 · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22400 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.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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
Mikado-ThemesHolmesholmes, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.