LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22458: WordPress Wanderland theme <= 1.5 - Broken Access Control vulnerability

Missing Authorization vulnerability in Mikado-Themes Wanderland wanderland allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Wanderland: from n/a through <= 1.5.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22458 is a medium-severity access-control flaw in the WordPress Wanderland theme by Mikado-Themes, affecting versions through 1.5. A logged-in user may be able to perform actions they should not be authorized to perform, causing limited integrity impact. No public source in the bundle reports active exploitation.

Executive priority

Prioritize this for WordPress environments running Wanderland, especially sites with many authenticated users. The expected impact is limited data or content integrity risk, not full system compromise based on available sources. Remediate during normal vulnerability management unless business-critical sites or broad user registration increase exposure.

Technical view

The issue is classified as CWE-862: Missing Authorization. CVSS 3.1 is 4.3 with network attack vector, low complexity, required low privileges, no user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact. Sources identify Wanderland theme versions up to and including 1.5 as affected.

Likely exposure

Exposure is limited to WordPress sites using the Wanderland theme version 1.5 or earlier. Because exploitation requires low privileges, sites allowing user registration, contributors, customers, or other authenticated roles may have higher practical risk.

Exploitation context

The provided sources do not describe exploit details, public proof-of-concept activity, or in-the-wild exploitation. The CVE is not listed as KEV in the supplied data. Treat this as a real authorization weakness, but not as confirmed actively exploited.

Researcher notes

Public details are sparse. The source bundle names broken access control and missing authorization but does not identify the vulnerable endpoint, required role, exploit method, or fixed version. Avoid assuming a patch exists unless vendor or Patchstack guidance confirms it.

Mitigation direction

  • Identify WordPress sites using the Wanderland theme.
  • Check whether the installed Wanderland version is 1.5 or earlier.
  • Review Mikado-Themes and Patchstack guidance for an update or vendor-recommended mitigation.
  • Restrict unnecessary user registration and low-privilege accounts until remediation is confirmed.
  • Back up affected sites before applying theme updates or configuration changes.

Validation and detection

  • Inventory WordPress themes across production, staging, and legacy sites.
  • Confirm the active and installed Wanderland theme versions.
  • Review site user roles for unnecessary low-privilege accounts.
  • Check web application logs for unusual authenticated actions.
  • Document remediation status and any compensating controls.
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-22458 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
4.3 (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: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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-22458Attack 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: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
Mikado-ThemesWanderlandwanderland, 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.