CVE-2026-14262
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Simple JWT Login – Allows you to use JWT on REST endpoints. plugin for WordPress is vulnerable to Authentication Bypass to Privilege Escalation in all versions up to, and including, 3.6.6 via the `payload` parameter. The vulnerability exists because `AuthenticateService::generatePayload()` only overwrites JWT payload keys whose names appear in the admin-configured `jwt_payload` list — leaving any attacker-supplied identity claims such as `email`, `id`, or `username` intact and signed into the JWT with the site's HS256 secret. This makes it possible for authenticated attackers, with subscriber-level access and above, to escalate their privileges to that of an Administrator by injecting a target administrator's email address into the `payload` parameter at the `/wp-json/simple-jwt-login/v1/auth` endpoint, then redeeming the resulting JWT at the `/autologin` endpoint to obtain a fully authenticated session as that administrator.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Simple JWT Login plugin fails to sanitize attacker-supplied identity claims in JWT payloads. Because generatePayload() only overwrites keys present in the admin-configured jwt_payload list, attackers with subscriber-level access can inject admin email/id/username into the payload parameter at the /wp-json/simple-jwt-login/v1/auth endpoint. The resulting JWT is signed with the site's HS256 secret, allowing the attacker to redeem it at /autologin and obtain a full Administrator session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Simple JWT Login plugin is installedCheck the WordPress plugins directory or wp-admin plugins list for 'Simple JWT Login'Affected if The plugin is installed and active
-
Determine the installed plugin versionInspect the plugin main file (simple-jwt-login.php) or view in WordPress admin under Plugins > Installed PluginsAffected if Version is lower than 3.6.7 (or unable to confirm version)
-
Verify the REST API endpoint is accessibleSend a GET request to /wp-json/simple-jwt-login/v1/auth and confirm it returns a responseAffected if The endpoint is publicly accessible without authentication restrictions
-
Check if subscriber-level users existReview WordPress user roles at Users > All Users, looking for subscribers or low-privilege accountsAffected if Subscriber or low-privilege user accounts exist on the site
-
Confirm JWT autologin endpoint is activeAccess /autologin or check plugin settings for autologin functionality enabledAffected if The autologin feature is enabled and accessible
If Simple JWT Login plugin versions before 3.6.7 are installed with the REST API and autologin endpoints accessible, and low-privilege users exist, the environment is vulnerable to privilege escalation via JWT payload injection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the Simple JWT Login plugin to version 3.6.7 or later, which patches the payload sanitization vulnerability.
Simple JWT Login version 3.6.7 or latest version
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Find the 'Simple JWT Login' plugin
- Check the current version - if it is 3.6.6 or earlier, an update is needed
- Update the plugin to the latest available version (3.6.7 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14262 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data