Hamid Alinia Login With Phone Number Plugin up to 1.8.77 on WordPress privileges management

Summaryinfo

A vulnerability has been found in Hamid Alinia Login With Phone Number Plugin up to 1.8.77 and classified as critical. Affected by this issue is some unknown functionality. The manipulation leads to privileges management. This vulnerability is uniquely identified as CVE-2026-110373. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Hamid Alinia Login With Phone Number Plugin up to 1.8.77. This issue affects an unknown part. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Incorrect Privilege Assignment vulnerability in Hamid Alinia Login with phone number login-with-phone-number allows Privilege Escalation.This issue affects Login with phone number: from n/a through 1.8.77.

The advisory is shared at patchstack.com. The identification of this vulnerability is CVE-2026-110373 since 10/14/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/18/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• Hamid Alinia

Name

• Login With Phone Number Plugin

Version

• 1.8.0
• 1.8.1
• 1.8.2
• 1.8.3
• 1.8.4
• 1.8.5
• 1.8.6
• 1.8.7
• 1.8.8
• 1.8.9
• 1.8.10
• 1.8.11
• 1.8.12
• 1.8.13
• 1.8.14
• 1.8.15
• 1.8.16
• 1.8.17
• 1.8.18
• 1.8.19
• 1.8.20
• 1.8.21
• 1.8.22
• 1.8.23
• 1.8.24
• 1.8.25
• 1.8.26
• 1.8.27
• 1.8.28
• 1.8.29
• 1.8.30
• 1.8.31
• 1.8.32
• 1.8.33
• 1.8.34
• 1.8.35
• 1.8.36
• 1.8.37
• 1.8.38
• 1.8.39
• 1.8.40
• 1.8.41
• 1.8.42
• 1.8.43
• 1.8.44
• 1.8.45
• 1.8.46
• 1.8.47
• 1.8.48
• 1.8.49
• 1.8.50
• 1.8.51
• 1.8.52
• 1.8.53
• 1.8.54
• 1.8.55
• 1.8.56
• 1.8.57
• 1.8.58
• 1.8.59
• 1.8.60
• 1.8.61
• 1.8.62
• 1.8.63
• 1.8.64
• 1.8.65
• 1.8.66
• 1.8.67
• 1.8.68
• 1.8.69
• 1.8.70
• 1.8.71
• 1.8.72
• 1.8.73
• 1.8.74
• 1.8.75
• 1.8.76
• 1.8.77

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion