{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3655 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3655 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3655 is a critical authentication bypass vulnerability in glboy OTP Login With Phone Number, OTP Verification, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3655 and fix it if it is affected.\n\nWhat it is: CVE-2026-3655 is a critical authentication bypass vulnerability in glboy OTP Login With Phone Number, OTP Verification, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-3655 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-2026-3655/ (Markdown: https://insights.sbomify.com/CVE-2026-3655/index.md)","id":"CVE-2026-3655","markdown":"https://insights.sbomify.com/CVE-2026-3655/index.md","name":"CVE-2026-3655","record":{"aliases":["GHSA-8p28-978j-q34v"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass authentication and log in as any user, including administrators, by exploiting a flaw in the Firebase OTP verification flow.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The OTP Login With Phone Number, OTP Verification plugin for WordPress is vulnerable to authentication bypass in versions 1.8.50 through 1.8.60. This is due to the Firebase verification flow in the `lwp_ajax_register` AJAX handler not binding the Firebase session to the phone number supplied in the request. The `idehweb_lwp_activate_through_firebase()` function validates that a Firebase OTP session is legitimate, but the `phoneNumber` returned by Firebase is never compared against the victim's stored phone number. This makes it possible for unauthenticated attackers to authenticate as any user who has a phone number stored in user meta, including administrators, by verifying their own Firebase session and supplying the victim's phone number in the same request.","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":"Auth bypass in OTP Login With Phone Number, OTP Verification","id":"CVE-2026-3655","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"My Sticky Bar \u003c= 2.8.6 - Unauthenticated SQL Injection via 'stickymenu_contact_lead_form' Action","id":"CVE-2026-3657"},"packages":[],"prev":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2026-3653"},"products":["OTP Login With Phone Number, OTP Verification"],"published":"2026-05-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-29","vendors":["glboy"]},"summary":"Unauthenticated attackers can bypass authentication and log in as any user, including administrators, by exploiting a flaw in the Firebase OTP verification flow.","url":"https://insights.sbomify.com/CVE-2026-3655/"}