LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22426: WordPress Sweet Jane theme <= 1.2 - Insecure Direct Object References (IDOR) vulnerability

Authorization Bypass Through User-Controlled Key vulnerability in Elated-Themes Sweet Jane sweetjane allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sweet Jane: from n/a through <= 1.2.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22426 affects the WordPress Sweet Jane theme through version 1.2. It is an authorization bypass/IDOR issue where a logged-in user may be able to act on objects they should not access. The reported impact is limited integrity and availability, with no confidentiality impact listed.

Executive priority

Treat as a medium-priority WordPress exposure. Prioritize sites with many contributors, customer portals, or untrusted accounts. There is no provided evidence of active exploitation, but affected public sites should be inventoried and tracked for vendor remediation.

Technical view

The CVE describes CWE-639: authorization bypass through a user-controlled key in Elated-Themes Sweet Jane. CVSS 3.1 is 5.4: network-accessible, low complexity, low privileges required, no user interaction, unchanged scope, with low integrity and availability impact.

Likely exposure

Exposure is most likely on WordPress sites running the Sweet Jane theme version 1.2 or earlier. The source bundle does not identify affected endpoints, roles, or a fixed version.

Exploitation context

The CVSS vector indicates exploitation requires an authenticated, low-privileged user and no victim interaction. CISA KEV is false in the provided data, and the cited sources do not state active exploitation.

Researcher notes

Evidence is limited to the CVE record and Patchstack reference. The vulnerability class is IDOR/authorization bypass, but the bundle does not provide affected parameters, routes, proof of concept, or patch details. Avoid assuming confidentiality impact because the CVSS vector lists C:N.

Mitigation direction

  • Inventory WordPress sites for the Sweet Jane theme and installed version.
  • If Sweet Jane is unused, disable or remove it.
  • Check Elated-Themes, Patchstack, and WordPress administration channels for a fixed release or vendor guidance.
  • Restrict untrusted low-privileged accounts until remediation is confirmed.
  • Back up the site before making theme changes.

Validation and detection

  • Confirm whether Sweet Jane is installed and active on each WordPress site.
  • Record the installed theme version and compare it with affected versions through 1.2.
  • Review user roles and accounts with access to the affected site.
  • Check vendor or Patchstack advisories for remediation status.
  • Monitor logs for unusual authenticated changes or availability-impacting actions.
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-22426 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:L/UI:N/S:U/C:N/I:L/A:L

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:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-22426Attack 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:L

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
Elated-ThemesSweet Janesweetjane, 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.