LiveActive security incident?Get immediate response
CVE Record

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

Authorization Bypass Through User-Controlled Key vulnerability in Mikado-Themes Innovio innovio allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Innovio: 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-22404 affects the WordPress Innovio theme through version 1.7. It is an insecure direct object reference issue that may let a highly privileged user access or change data they should not. Business urgency is moderate because exploitation requires an already privileged account, but impacted sites should still be reviewed.

Executive priority

Treat as a moderate-priority WordPress exposure. Prioritize sites with many privileged users, weak account governance, or business-sensitive content. No active exploitation is cited, but affected installations should be inventoried and remediated through vendor guidance.

Technical view

The CVE describes CWE-639: authorization bypass through a user-controlled key in Mikado-Themes Innovio. CVSS 3.1 is 5.4 with network access, low complexity, high privileges required, no user interaction, and low confidentiality and integrity impact. Availability impact is not indicated.

Likely exposure

Exposure is limited to WordPress sites using the Mikado-Themes Innovio theme version 1.7 or earlier. The provided data does not identify affected plugins, hosted services, or non-WordPress products.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector indicates an attacker needs high privileges, so risk is most relevant where privileged WordPress accounts are compromised, shared, or poorly controlled.

Researcher notes

Public details are limited. The record identifies an IDOR/access-control weakness but does not describe the vulnerable endpoint, object type, or fixed version. Avoid assuming exploitability beyond the stated CVSS conditions and Patchstack/CVE description.

Mitigation direction

  • Identify WordPress sites using Innovio theme version 1.7 or earlier.
  • Check vendor or Patchstack guidance for a fixed version or official mitigation.
  • Update the theme if a trusted fixed release is available.
  • Remove or disable the theme where it is not required.
  • Review and limit high-privilege WordPress accounts.

Validation and detection

  • Confirm the active and installed WordPress theme name and version.
  • Flag Innovio installations at version 1.7 or earlier.
  • Review privileged account inventory and recent administrative activity.
  • Monitor vendor, 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-22404 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-22404Attack 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-ThemesInnovioinnovio, 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.