Security readout for executives and security teams
Plain-English summary
CVE-2026-22391 affects the WordPress Cocco theme through version 1.5.1. It is an IDOR-style authorization weakness where a logged-in user may influence an object key and bypass intended access controls. Reported impact is limited integrity and availability impact, with no confidentiality impact in the CVSS record.
Executive priority
Treat this as a medium-priority WordPress exposure. It is not reported as actively exploited, but it affects access control and may let logged-in users make unauthorized changes or disrupt functionality. Prioritize externally reachable sites with many contributors, customers, or subscribers.
Technical view
The CVE describes CWE-639 Authorization Bypass Through User-Controlled Key in Mikado-Themes Cocco. CVSS 3.1 is 5.4: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, no confidentiality impact, low integrity and availability impact. Public sources do not provide endpoint details or a named fixed version.
Likely exposure
Exposure is most likely on WordPress sites running the Mikado-Themes Cocco theme at version 1.5.1 or earlier, especially where untrusted or lower-privileged users can authenticate. The source bundle does not identify affected endpoints or whether inactive installed copies are exploitable.
Exploitation context
The vulnerability requires authenticated low-privileged access according to CVSS. It is not listed as CISA KEV in the provided data, and no cited source states active exploitation. Public details are sparse, so assess as a real but bounded WordPress theme authorization risk.
Researcher notes
The provided record lacks endpoint, parameter, proof-of-concept, patch, and fixed-version details. Avoid assuming exploitability beyond the CVSS and CVE description. Key research tasks are confirming installed versions, correlating Patchstack/vendor advisories, and determining whether privilege boundaries are meaningful on each site.
Mitigation direction
- Inventory WordPress sites for the Cocco theme and record installed versions.
- Prioritize sites allowing public registration or many low-privileged users.
- Check Mikado-Themes, Patchstack, or marketplace guidance for an update or workaround.
- Apply any vendor-provided fixed version when available.
- Restrict unnecessary user accounts and review low-privileged access until remediated.
Validation and detection
- Confirm whether Cocco is installed and active on each WordPress site.
- Verify the theme version is greater than 1.5.1, if a fixed version exists.
- Review access logs for unusual authenticated actions affecting theme-managed objects.
- Check vulnerability scanners or Patchstack data for detection coverage.
- Document compensating controls if no vendor fix is available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupPrivilege 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 lookupCVE-2026-22391 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.