2 lines
3.9 KiB
JSON
2 lines
3.9 KiB
JSON
{"affected":[{"affectedData":[{"defaultStatus":"unaffected","product":"OTP Login With Phone Number, OTP Verification","vendor":"glboy","versions":[{"lessThanOrEqual":"1.8.60","status":"affected","version":"1.8.50","versionType":"semver"}]}],"source":"security@wordfence.com"}],"cveTags":[],"descriptions":[{"lang":"en","value":"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."},{"lang":"es","value":"El plugin OTP Login With Phone Number, OTP Verification para WordPress es vulnerable a omisión de autenticación en las versiones 1.8.50 a 1.8.60. Esto se debe a que el flujo de verificación de Firebase en el gestor AJAX 'lwp_ajax_register' no vincula la sesión de Firebase al número de teléfono proporcionado en la solicitud. La función 'idehweb_lwp_activate_through_firebase()' valida que una sesión OTP de Firebase es legítima, pero el 'phoneNumber' devuelto por Firebase nunca se compara con el número de teléfono almacenado de la víctima. Esto hace posible que atacantes no autenticados se autentiquen como cualquier usuario que tenga un número de teléfono almacenado en los metadatos del usuario, incluidos los administradores, al verificar su propia sesión de Firebase y proporcionar el número de teléfono de la víctima en la misma solicitud."}],"id":"CVE-2026-3655","lastModified":"2026-07-21T12:10:00.090","metrics":{"cvssMetricV31":[{"cvssData":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":9.8,"baseSeverity":"CRITICAL","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"exploitabilityScore":3.9,"impactScore":5.9,"source":"security@wordfence.com","type":"Secondary"}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"id":"CVE-2026-3655","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"role":"CISA Coordinator","timestamp":"2026-05-29T10:01:30.010604Z","version":"2.0.3"}}]},"published":"2026-05-29T08:16:18.920","references":[{"source":"security@wordfence.com","url":"https://plugins.trac.wordpress.org/browser/login-with-phone-number/tags/1.8.60/inc/ajax-handlers.php#L1167"},{"source":"security@wordfence.com","url":"https://plugins.trac.wordpress.org/browser/login-with-phone-number/tags/1.8.60/inc/ajax-handlers.php#L649"},{"source":"security@wordfence.com","url":"https://plugins.trac.wordpress.org/browser/login-with-phone-number/tags/1.8.60/inc/ajax-handlers.php#L659"},{"source":"security@wordfence.com","url":"https://plugins.trac.wordpress.org/browser/login-with-phone-number/trunk/inc/ajax-handlers.php#L649"},{"source":"security@wordfence.com","url":"https://plugins.trac.wordpress.org/changeset/3479314/login-with-phone-number/trunk/inc/ajax-handlers.php?old=3455810&old_path=login-with-phone-number%2Ftrunk%2Finc%2Fajax-handlers.php"},{"source":"security@wordfence.com","url":"https://www.wordfence.com/threat-intel/vulnerabilities/id/7fc410f2-5f2b-4eea-a0fb-fe58f988f95f?source=cve"}],"sourceIdentifier":"security@wordfence.com","vulnStatus":"Deferred","weaknesses":[{"description":[{"lang":"en","value":"CWE-287"}],"source":"security@wordfence.com","type":"Secondary"}]}
|