CVE-2026-35676High· 8.2▾ MidnightPoC availablephpMyFAQ before 4.1.3 contains an unauthenticated password reset vulnerability in the user password update API endpoint that allows attackers to change account passwords without token validation. Attackers can enumerate valid username an…
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 45.1 · likelihood 0.1 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.3%
phpMyFAQ before 4.1.3 contains an unauthenticated password reset vulnerability in the user password update API endpoint that allows attackers to change account passwords without token validation. Attackers can enumerate valid username and email pairs and force immediate password changes by sending PUT requests to the /api/index.php/user/password/update endpoint, causing account disruption and invalidating legitimate user credentials.
phpMyFAQ < 4.1.3Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-35671High· 8.8phpMyFAQ - Insecure Direct Object Reference in User Password API
CVE-2026-35672High· 7.5phpMyFAQ - Authentication Bypass via Empty API Token
CVE-2026-35675High· 8.2phpMyFAQ - Authentication Bypass via Missing Password Reset Token in /api/user/password/update
CVE-2026-45007Medium· 4.3phpMyFAQ - Missing Permission Check on 12 Configuration API Endpoints Allows Information Disclosure
CVE-2026-45009Medium· 4.3phpMyFAQ - Insufficient Authorization Check in Admin API Endpoints
CVE-2026-45008Medium· 6.5phpMyFAQ - Path Traversal in Client::deleteClientFolder via URL Parameter