Skip to main content

Simple JWT Login CVE-2026-39793

| EUVDEUVD-2026-93037 HIGH
Authentication Bypass Using an Alternate Path or Channel (CWE-288)
2026-10-06 Patchstack GHSA-c2jh-6qgg-g87w
8.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain subscriber-level WordPress account
  2. Delivery
    Send crafted JWT auth request to plugin endpoint
  3. Exploit
    Bypass authentication via alternate path (CWE-288)
  4. Execution
    Assume higher-privileged user identity
  5. Impact
    Read/modify site data and settings

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Alternate path authentication
Exploitation Conditions

Exploitation requires a low-privileged authenticated account on the target WordPress site - consistent with PR:L - typically a subscriber-level account, which is often self-registerable when open user registration is enabled, lowering the practical barrier. The condition is the specific presence of Simple JWT Login version 4.0.0 with its JWT authentication feature in use. Limiting factors: an attacker must first hold a subscriber (or equivalent low-privilege) account, so sites that disable open registration or restrict account creation raise the bar; no special user interaction is required (UI:N) and the vector is remote over the network (AV:N).

Impact

The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) indicates a network-exploitable, low-complexity flaw that requires only low-level authenticated access (PR:L) and no user interaction, yielding high confidentiality, integrity, and availability impact. The CWE-288 (Authentication Bypass Using an Alternate Path) classification aligns with the 'Subscriber Broken Authentication' description: a low-privileged subscriber-level account can abuse the plugin's JWT authentication flow to authenticate or act as a higher-privileged user. No EPSS score, CISA KEV listing, POC reference, or SSVC decision data was provided in the input, so exploitation probability and automatability cannot be quantified from this data. Exploitation status is therefore 'no public exploit identified at time of analysis.' One tension to flag explicitly: the input Tags label this 'Information Disclosure,' but the CVSS vector shows C:H/I:H/A:H and CWE-288 describes authentication bypass - the impact is broader than disclosure alone, so the tag understates severity. Net: this is a genuine high-severity priority for sites running the affected plugin because exploitation needs only a low-privileged (commonly self-registerable subscriber) account, but the absence of KEV/EPSS/POC signals means there is no current evidence of active or widespread exploitation.

Exploit ScenarioDerived

An attacker registers or obtains a subscriber-level account on a WordPress site running Simple JWT Login 4.0.0, then abuses the plugin's broken JWT authentication logic to obtain a token or session representing a higher-privileged user. No public exploit code is identified at time of analysis, and the low attack complexity (AC:L) plus no required user interaction (UI:N) make the flaw straightforward to trigger once subscriber access is held.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

Broken authentication in the Simple JWT Login WordPress plugin 4.0.0 allows a remote authenticated attacker with subscriber-level privileges to bypass intended JWT authentication controls, resulting in high confidentiality, integrity, and availability impact (CVSS 8.8, CWE-288). The vulnerability is network-exploitable, requires low complexity, and needs no user interaction, but an attacker must first obtain a low-privileged account-often self-registerable when open registration is enabled. No public exploit code or confirmed active exploitation has been identified at time of analysis.

RemediationAI

No vendor-released patch has been identified at time of analysis; check the Patchstack advisory for updates. As a primary mitigation, disable the Simple JWT Login plugin if JWT authentication is not essential-this removes the vulnerable code but eliminates the JWT login functionality. If the plugin is required, restrict access to its JWT endpoints using web server ACLs or a Web Application Firewall (WAF) to allow only trusted IPs, with the trade-off that legitimate API clients from other networks will be blocked. Disable open user registration in WordPress to prevent attackers from obtaining the subscriber-level account required for exploitation; this may impact legitimate user onboarding. Additionally, enforce least privilege for subscriber accounts and monitor logs for anomalous JWT authentication attempts. Since no fixed version is available, these compensating controls should be applied until an official patch is released.

Affected VersionsENISA

Simple JWT Login 4.0.0

Affected Packages

euvd simple_jwt_login no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Simple JWT Login is a WordPress plugin that enables JWT-based authentication for WordPress REST API and login flows. The flaw is classified as CWE-288: Authentication Bypass Using an Alternate Path or Channel, meaning the plugin likely fails to properly validate JWT tokens or allows an authenticated user to reach privileged functionality through a path that bypasses intended authorization checks. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates remote exploitation with low complexity, requiring low privileges, no user interaction, and resulting in high impact across confidentiality, integrity, and availability. The CPE string cpe:2.3:a:nicu_micle:simple_jwt_login:*:*:*:*:*:*:*:* identifies the plugin, though the Patchstack advisory specifically targets version 4.0.0. The underlying JWT mechanism should enforce signature verification and claim validation; a broken authentication issue here could allow token forgery, privilege escalation, or unauthorized access to protected endpoints.

Know when Simple Jwt Login gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Remote network vector, low complexity, and only a subscriber account needed give AV:N/AC:L/PR:L/UI:N; authentication bypass to a privileged identity yields C:H/I:H/A:H.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Subscriber Broken Authentication in Simple JWT Login 4.0.0 versions.

Executive ViewAI

Why It Matters

A broken authentication flaw in the Simple JWT Login WordPress plugin version 4.0.0 allows someone holding a low-privileged subscriber account to bypass the plugin's JWT authentication controls, gaining high-impact access to confidentiality, integrity, and availability of the affected site. Because open self-registration on many WordPress sites makes obtaining such an account trivial, this represents a meaningful risk to any organization running the plugin, including potential site takeover, data exposure, or defacement. No vendor patch is currently available, so leadership should treat this as an exposure requiring immediate mitigation decisions and ownership.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable or remove the Simple JWT Login plugin where feasible; disable open user registration and restrict creation of subscriber accounts; limit access to the plugin's authentication endpoints by IP allowlist or network segmentation; rotate JWT secrets and signing keys; audit and remove unnecessary low-privileged accounts; deploy WAF rules targeting the plugin's authentication routes; and monitor for authentication bypass or privilege escalation activity.

Threat Intelligence Overview

EPSS Score
0.4%
Top 66% exploitable
Prevalence
Medium
common WordPress plugin, moderate but not universal install base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy