Skip to main content
VulnerabilityPublished

CVE-2026-65570: Login with phone number (WordPress plugin) · Authentication Bypass by Spoofing

Affects Login with phone number (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Hamid AliniaLogin with phone numberAffected
  • ≥ n/a, < 1.8.71
Fixed in–

AI-suggested

Until an official fix is released, users should monitor vendor communications for updates and consider implementing additional access controls or compensating controls to mitigate risk.

Description

CVE-2026-65570 is an authentication bypass vulnerability affecting the 'Login with phone number' product by Hamid Alinia in versions up to and including 1.8.70. This vulnerability allows unauthenticated attackers to bypass authentication mechanisms by spoofing, potentially leading to full compromise of confidentiality, integrity, and availability. The vulnerability is classified under CWE-290 (Authentication Bypass by Spoofing) and has a high severity with a CVSS score of 8.1. No official patch or remediation guidance has been provided yet.

References

Community reviews

Loading reviews…