CVE-2026-130368 json
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
published yesterday modified 13h ago also EUVD-2026-126779 , GHSA-j7hf-7jvx-hm98
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository thorsten/phpMyFAQ. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 4.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
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 authentication attempts vulnerability in PasswordChangeController::update() that bypasses the step-up throttle. Attackers holding a hijacked admin-area session can repeatedly guess faqpassword_old with a reusable CSRF token to learn the original password and take over the account.
Patch / fix
- thorsten phpMyFAQ 4.1.12, 4.2.0-RC.2
Is CVE-2026-130368 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 14h ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-17).
Exploits and checks
- github.com https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j7hf-7jvx-hm98 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N |
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- thorsten phpMyFAQ
Classification
- Weakness
-
- CWE-307 Improper Restriction of Excessive Authentication Attempts
References
-
github.com
/thorsten/phpMyFAQ/commit/eff1b6411dd94b3a7d4cbb4b4e3c9ef13d2398b1
patch
-
github.com
/thorsten/phpMyFAQ/security/advisories/GHSA-j7hf-7jvx-hm98
vendor-advisory, exploit, advisory
-
github.com
/thorsten/phpMyFAQ/releases/tag/4.1.12
release-notes
-
github.com
/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2
release-notes
-
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-upda
third-party-advisory
Sources
- CVE List CVE-2026-130368
- NVD CVE-2026-130368
- Maintainer advisory GHSA-j7hf-7jvx-hm98
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of thorsten/phpMyFAQ published their own advisory on GitHub. Reviewed sources take precedence over it.