Security readout for executives and security teams
Plain-English summary
A flaw in the WordPress plugin’s phone-based login can let an unauthenticated attacker repeatedly guess short one-time codes. Successful guessing could take over any targeted account, including an administrator, exposing site content and administrative control.
Executive priority
Treat as an immediate remediation priority because compromise could grant full WordPress administrator control without prior access. Prioritize public sites and administrator accounts using phone OTP login, while investigating authentication logs for possible abuse.
Technical view
Versions before 1.8.71 lack OTP attempt limits and do not invalidate a code after an incorrect guess. Because anyone can request a login code for an account and repeatedly submit guesses, the authentication mechanism is vulnerable to brute force. CVSS 3.1 scores it 9.1 under CWE-287.
Likely exposure
Internet-accessible WordPress sites running this plugin before 1.8.71 are the likely exposure. Risk is greatest where phone-number OTP login is enabled and administrator accounts are reachable through it. The sources do not quantify affected installations or identify configuration exceptions.
Exploitation context
The weakness is remotely reachable without authentication, privileges, or user interaction. However, it is not listed as a CISA KEV in the supplied bundle, and the cited material does not establish active exploitation in the wild.
Researcher notes
The structured affected entry is internally unclear, listing version “0” and default status “unaffected,” while the narrative explicitly identifies versions before 1.8.71. No CPEs are supplied. Validate product identity and installed versions directly; do not infer broader WordPress or OTP-product exposure.
Mitigation direction
- Identify installations and determine whether the plugin version is earlier than 1.8.71.
- Check current plugin or vendor guidance and update to a confirmed non-vulnerable release.
- Disable the affected OTP login feature until remediation if immediate updating is not possible.
- Review administrator accounts and recent authentication activity for unexplained access or changes.
- Reset affected credentials and sessions if account compromise is suspected.
Validation and detection
- Confirm the installed plugin version through trusted WordPress inventory or administrative records.
- Verify that production instances no longer run a version earlier than 1.8.71.
- Confirm the affected OTP endpoint is disabled wherever remediation remains pending.
- Review logs for excessive OTP requests, repeated verification failures, and unexpected successful logins.
- Check administrator accounts, sessions, and configuration changes for unauthorized activity.
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 lookupCVE-2026-15210 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/96101127-8b13-4770-9204-f540fb044040/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.