<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: login with phone number</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-6482: The Login with phone number plugin for WordPress is vulnerable to privilege escalation in all versions up to, </title><link>https://patchthecve.com/cve/CVE-2024-6482.html</link><guid>https://patchthecve.com/cve/CVE-2024-6482.html</guid><pubDate>Wed, 17 Jun 2026 08:18:06 +0000</pubDate><description>HIGH 8.8: The Login with phone number plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.7.49. This is due to a lack of validation and missing capability check on user-supplied data in the &#x27;lwp_update_password_action&#x27; function. This makes it possible for authent</description></item><item><title>CVE-2024-37429: Improper Neutralization of Input During Web Page Generation (&#x27;Cross-site Scripting&#x27;) vulnerability in Hamid Al</title><link>https://patchthecve.com/cve/CVE-2024-37429.html</link><guid>https://patchthecve.com/cve/CVE-2024-37429.html</guid><pubDate>Wed, 17 Jun 2026 07:38:21 +0000</pubDate><description>MEDIUM 5.9: Improper Neutralization of Input During Web Page Generation (&#x27;Cross-site Scripting&#x27;) vulnerability in Hamid Alinia Login with phone number login-with-phone-number.This issue affects Login with phone number: from n/a through &lt;= 1.7.35.</description></item><item><title>CVE-2023-4916: The Login with phone number plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to</title><link>https://patchthecve.com/cve/CVE-2023-4916.html</link><guid>https://patchthecve.com/cve/CVE-2023-4916.html</guid><pubDate>Wed, 17 Jun 2026 06:38:53 +0000</pubDate><description>HIGH 8.8: The Login with phone number plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.6. This is due to missing nonce validation on the &#x27;lwp_update_password_action&#x27; function. This makes it possible for unauthenticated attackers to change user password via</description></item></channel></rss>