LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22407: WordPress Roam theme <= 2.1.1 - Insecure Direct Object References (IDOR) vulnerability

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

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22407 affects the Mikado-Themes Roam WordPress theme through version 2.1.1. It is an IDOR issue: an authorized user may access or modify data they should not by controlling an object reference. The published severity is medium, and the CVSS vector indicates high privileges are required.

Executive priority

Treat as a moderate-priority WordPress exposure. It is not currently sourced as actively exploited and requires high privileges, but affected public sites should still be inventoried and remediated because privileged account compromise could lead to unauthorized data access or changes.

Technical view

The vulnerability is classified as CWE-639, Authorization Bypass Through User-Controlled Key. CVSS 3.1 is 5.4: network exploitable, low complexity, high privileges required, no user interaction, with low confidentiality and integrity impact and no availability impact. Public details do not describe specific endpoints, parameters, or a fixed version.

Likely exposure

Exposure is limited to WordPress sites using the Roam theme at version 2.1.1 or earlier. The CVSS vector suggests exploitation requires a highly privileged authenticated account, reducing broad internet-wide risk but increasing concern for compromised admin/editor workflows or insider misuse.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public information is limited to the CVE record and Patchstack entry. Do not assume exploitation in the wild without additional vendor or threat-intelligence confirmation.

Researcher notes

The public record lacks endpoint-level detail, proof-of-concept information, and explicit remediation version. Assessment should focus on confirming affected theme deployment, tracking vendor guidance, and reviewing authorization boundaries. Avoid assuming impact beyond low confidentiality and integrity effects reflected in CVSS.

Mitigation direction

  • Identify WordPress sites using the Roam theme and record installed versions.
  • If Roam is version 2.1.1 or earlier, check vendor and Patchstack guidance for updates.
  • Limit and review high-privilege WordPress accounts until remediation is confirmed.
  • Back up affected sites before theme updates or configuration changes.
  • Monitor administrative activity for unusual access to theme-related objects or content.

Validation and detection

  • Confirm whether the Roam theme is installed and active on each WordPress site.
  • Compare installed Roam versions against the affected range: through 2.1.1.
  • Review vendor, CVE, and Patchstack pages for a fixed version or workaround.
  • Audit privileged account activity for unexpected object access or content changes.
  • Validate authorization behavior in staging after any vendor-provided update.
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-22407 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:H/UI:N/S:U/C:L/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.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N1.22.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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-ThemesRoamroam, 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.