phpMyFAQ 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an improper restriction of excessive
Source GCVE Database
Not known to be exploited · CVSS 2.3 Low : upgrade to 4.2.0-RC.2 or 4.1.12 when convenient.
Data as of 17 Nov 2026, 04:50 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 2.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.2 |
- Patch
- Available – fixed in 4.2.0-RC.2, 4.1.12
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade phpMyFAQ to 4.2.0-RC.2 or 4.1.12.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| thorstenphpMyFAQ | Affected
| Fixed in
|
| thorstenphpMyFAQ | Affected
| Fixed in
|
PackagistphpMyFAQpkg:composer/phpMyFAQOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict access to admin sessions and monitor for suspicious activity involving password changes. Avoid reuse of CSRF tokens and consider additional manual throttling or rate limiting on password change attempts.
Description
phpMyFAQ versions 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have a vulnerability in the PasswordChangeController::update() function. This flaw allows attackers with a hijacked admin session to bypass throttling on authentication attempts and repeatedly guess the old password using a reusable CSRF token, potentially leading to account takeover.
References
- github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j7hf-7jvx-hm98 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-130368 (opens in a new tab)
- github.com/thorsten/phpMyFAQ/commit/eff1b6411dd94b3a7d4cbb4b4e3c9ef13d2398b1 (opens in a new tab)
- github.com/thorsten/phpMyFAQ/releases/tag/4.1.12 (opens in a new tab)
- github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2 (opens in a new tab)
- vulncheck.com/advisories/phpmyfaq-4.1.9-before-4.1.12-and-4.2.0-alpha-before-4.2.0-rc.2-brute-force-via-admin-password-update (opens in a new tab)