LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22430: WordPress Verdure theme <= 1.6 - Insecure Direct Object References (IDOR) vulnerability

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

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22430 affects the WordPress Verdure theme up to version 1.6. It is an authorization bypass/IDOR issue, meaning a logged-in user may be able to access or modify objects they should not control. The published severity is medium, with limited integrity and availability impact and no confidentiality impact in the CVSS vector.

Executive priority

Treat as a medium-priority WordPress exposure. Prioritize sites using Verdure with many user accounts, customer portals, or delegated content editors. There is no provided evidence of active exploitation, but authenticated misuse could affect site content or operations.

Technical view

The issue is classified as CWE-639: Authorization Bypass Through User-Controlled Key. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L, indicating network reachability, low attack complexity, required low privileges, no user interaction, and limited integrity/availability impact. Sources identify Mikado-Themes Verdure theme versions through 1.6 as affected.

Likely exposure

Exposure is limited to WordPress sites using the Mikado-Themes Verdure theme at version 1.6 or earlier. Attackers need some authenticated access according to the CVSS privileges-required value. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Patchstack and CVE describe the flaw type and affected version range, but no exploit details or exploitation-in-the-wild claims are provided here.

Researcher notes

Evidence is limited to the CVE record and Patchstack database entry. The affected range is stated as through 1.6, while the structured affected data includes an unusual version value. No specific patched version, workaround, endpoint, or proof-of-concept details are included in the provided sources.

Mitigation direction

  • Inventory WordPress sites for the Verdure theme and record installed versions.
  • If Verdure is version 1.6 or earlier, check vendor or Patchstack guidance for remediation.
  • Restrict unnecessary WordPress accounts until remediation guidance is confirmed.
  • Review theme-related access controls and user roles for least privilege.

Validation and detection

  • Confirm whether the active or installed theme is Verdure by Mikado-Themes.
  • Verify the installed Verdure version against the affected range through 1.6.
  • Check CVE and Patchstack entries for updated remediation or patch information.
  • Review logs for suspicious authenticated changes to theme-managed objects.
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-22430 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-22430Attack 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-ThemesVerdureverdure, 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.