Advisory record · GHSA-w9xh-5f39-vq89

phpMyFAQ: Missing Password Reset Token Allows Account Takeover via Username/Email Enumeration

CVSS 8.8 HighEPSS 0.0042 · 36th percentile

Published by the GitHub Advisory Database at 20 May 2026, 15:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
thorsten/phpmyfaqPackagist<4.1.34.1.3
phpmyfaq/phpmyfaqPackagist<4.1.34.1.3
Identifiers
GHSA-w9xh-5f39-vq89 · CVE-2026-35675 · PKSA-527c-n963-c1j5 · PKSA-x1b3-f9q9-1brm
Weakness (CWE)
CWE-307 · CWE-359 · CWE-640
Published
20 May 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The phpMyFAQ packages thorsten/phpmyfaq and phpmyfaq/phpmyfaq, versions before 4.1.3, have a flaw in the password reset API endpoint /api/user/password/update, which the source says accepts a request with only a username and email address and issues a new plaintext password by email without a token, rate limiting, or confirmation. An unauthenticated network attacker who knows or guesses a valid username and matching email address could reset any account, including SuperAdmin accounts, and then log in as that user. The fix is to upgrade to version 4.1.3.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0042, the 36th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:01 UTC First seen by agentprime
  2. 31 Oct 2026, 14:01 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.