Security readout for executives and security teams
Plain-English summary
Affected WordPress sites may let an unauthenticated attacker sign in as another user, including an administrator, because the plugin accepts Google identity tokens intended for a different application. This could expose site data and enable unauthorized administrative changes without victim interaction.
Executive priority
Treat this as an immediate remediation priority for internet-accessible WordPress sites using the affected Google sign-in configuration. Administrator takeover could permit data theft and site modification. Rapidly identify exposed sites, update or disable the feature, and investigate suspicious access.
Technical view
Simple JWT Login before 3.6.8 fails to validate the audience claim in accepted Google id_token values. When Google sign-in is enabled, a token carrying a site user's email may be accepted despite targeting another application, causing authentication bypass and account takeover. The issue is classified as CWE-287 with CVSS 3.1 score 9.1.
Likely exposure
Exposure requires the Simple JWT Login WordPress plugin earlier than 3.6.8 with Google sign-in enabled. Sites without that configuration are not identified as affected. The bundle's structured affected-version field is inconsistent with its narrative, so confirm scope against vendor guidance.
Exploitation context
The flaw is remotely reachable, requires no authentication or user interaction, and may compromise administrator accounts. The source bundle links a WPScan entry tagged as exploit-related, but CVE-2026-19714 is not listed as KEV and the supplied evidence does not establish active exploitation.
Researcher notes
The trust failure concerns token audience validation, not Google token signature validation according to the supplied description. Testing should verify rejection of validly issued Google tokens whose audience does not match the site's configured client. The bundle provides no confirmed exploitation telemetry, affected CPEs, or detailed vendor advisory.
Mitigation direction
- Update Simple JWT Login to version 3.6.8 or later.
- Disable Google sign-in until the plugin can be updated.
- Review vendor guidance for additional remediation or configuration requirements.
- Investigate unauthorized administrative changes and invalidate suspicious sessions.
Validation and detection
- Inventory WordPress sites using Simple JWT Login.
- Confirm the installed plugin version on every identified site.
- Determine whether Google sign-in is enabled on each site.
- Review authentication and administrator activity for unexpected Google-based access.
- Confirm the updated installation reports version 3.6.8 or later.
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-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-19714 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
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
SSVC decision data
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:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/dc6e54eb-d856-484b-88c1-b3e04a37669d/CVE reference, WPScan · exploit, vdb-entry
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.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.