Security readout for executives and security teams
Plain-English summary
CVE-2026-22393 affects the WordPress Curly theme from Mikado-Themes through version 3.3. It is an authorization bypass/IDOR issue, meaning a logged-in user may be able to access or change objects they should not control. Public sources rate it medium severity, with limited integrity and availability impact and no confidentiality impact in the CVSS data.
Executive priority
Treat this as a medium-priority WordPress exposure. It is not reported as actively exploited in the provided sources, but it can affect business-facing sites using an older Curly theme. Prioritize inventory and vendor guidance checks, especially on sites with customer, subscriber, or staff logins.
Technical view
The issue is CWE-639: authorization bypass through a 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, and no user interaction. The provided sources do not identify a fixed version, exploitation details, or compensating controls.
Likely exposure
Exposure is likely limited to WordPress sites using the Curly theme version 3.3 or earlier, especially where untrusted or low-privileged users can authenticate. Sites not using this theme are not indicated as affected by the provided sources.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and the cited sources do not state active exploitation. The required privilege level lowers the risk compared with unauthenticated flaws, but public-facing WordPress sites with many user accounts should prioritize review.
Researcher notes
The public record is sparse. It identifies the product, affected range through 3.3, CWE-639, and CVSS 5.4, but does not provide endpoint details, proof of concept, fixed version, or exploit telemetry. Avoid assuming exploitability beyond the stated authenticated IDOR/access-control weakness.
Mitigation direction
- Identify WordPress sites using the Mikado-Themes Curly theme.
- Check whether the installed Curly version is 3.3 or earlier.
- Check vendor or Patchstack guidance for a fixed version or official remediation.
- Limit or remove unnecessary low-privileged WordPress user accounts.
- Monitor WordPress logs for unexpected authenticated actions involving theme-managed objects.
Validation and detection
- Inventory installed WordPress themes across production and staging sites.
- Confirm the Curly theme version from WordPress administration or asset inventory.
- Verify whether public registration or broad contributor access is enabled.
- Review vendor, CVE, and Patchstack pages for updated remediation details.
- Document affected sites and track remediation status to closure.
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-22393 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.