{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-4916 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-4916 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-4916 is a high-severity vulnerability in glboy OTP Login With Phone Number, OTP Verification, published on 13 Sep 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-4916 and fix it if it is affected.\n\nWhat it is: CVE-2023-4916 is a high-severity vulnerability in glboy OTP Login With Phone Number, OTP Verification, published on 13 Sep 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-4916 in the wild and no public exploit code.\n\nAffected product: glboy OTP Login With Phone Number, OTP Verification. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-4916/ (Markdown: https://insights.sbomify.com/CVE-2023-4916/index.md)","id":"CVE-2023-4916","markdown":"https://insights.sbomify.com/CVE-2023-4916/index.md","name":"CVE-2023-4916","record":{"aliases":["GHSA-qxmq-p4mw-7mw8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can change user passwords via CSRF by tricking administrators into clicking a link, leading to account takeover.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"login_with_phone_number","vendor":"idehweb"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"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 'lwp_update_password_action' function. This makes it possible for unauthenticated attackers to change user password via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Login with phone number \u003c= 1.5.6 - Cross-Site Request Forgery to User Password Change","id":"CVE-2023-4916","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Leyka \u003c= 3.30.7 - Authenticated (Subscriber+) Sensitive Information Exposure","id":"CVE-2023-4917"},"packages":[],"prev":{"headline":"WP User Control \u003c= 1.5.3 - Insecure Password Reset Mechanism","id":"CVE-2023-4915"},"products":["OTP Login With Phone Number, OTP Verification"],"published":"2023-09-13","related":[{"cvss_score":8.8,"headline":"Login with phone number \u003c= 1.7.49 - Authenticated (Subscriber+) Authorization Bypass to Privilege Escalation","id":"CVE-2024-6482","kev_date_added":null,"published":"2024-09-14"},{"cvss_score":8.8,"headline":"SQL injection in Login with Phone Number WordPress Plugin","id":"CVE-2023-23492","kev_date_added":null,"published":"2023-01-20"},{"cvss_score":6.5,"headline":"Login with phone number \u003c 1.3.7 - Unauthenticated remote plugin deletion","id":"CVE-2022-0593","kev_date_added":null,"published":"2022-03-14"},{"cvss_score":5.9,"headline":"WordPress Login with phone number plugin \u003c= 1.7.35 - Admin+ Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-37429","kev_date_added":null,"published":"2024-07-22"},{"cvss_score":4.8,"headline":"Login with phone number \u003c 1.3.8 - Multiple Admin+ Stored XSS","id":"CVE-2022-0598","kev_date_added":null,"published":"2022-08-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["glboy"]},"summary":"Attackers can change user passwords via CSRF by tricking administrators into clicking a link, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2023-4916/"}