Skip to main content
Menu
CVEs

CVE

thorsten/phpmyfaq account takeover via brute force in password change

CVE-2026-130368EUVD-2026-126779GHSA-Q4MH-222V-3G89

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

2.3LowCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 4.1.12, 4.2.0-RC.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.1.12, 4.2.0-RC.2.

Published
Last modified
Reference
Last checked
0.22% · 12th percentile
30/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: partial

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.

cve.now Index

30Pcve.now Index 30 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Affects Packagist packages
  • Severity2.3/10CVSS 2.3
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 49 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.1.12, 4.2.0-RC.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130368 (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), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130368 (entry last updated 2026-11-17):
Affected:
- Packagist package thorsten/phpmyfaq: from 4.1.9, fixed in 4.1.12; from 4.2.0-alpha, fixed in 4.2.0-RC.2
Fixed versions: 4.1.12, 4.2.0-RC.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130368 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130368 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-j7hf-7jvx-hm98
- https://github.com/thorsten/phpMyFAQ/commit/eff1b6411dd94b3a7d4cbb4b4e3c9ef13d2398b1
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.1.12
- https://github.com/thorsten/phpMyFAQ/releases/tag/4.2.0-RC.2
- https://www.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
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130368
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130368"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • From 4.1.9 · fixed in 4.1.12; From 4.2.0-alpha · fixed in 4.2.0-RC.2

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Patch
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130368

Is CVE-2026-130368 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-130368?

thorsten/phpmyfaq (Packagist): from 4.1.9 before 4.1.12; from 4.2.0-alpha before 4.2.0-RC.2.Source: cve.now feed data

How do I fix CVE-2026-130368?

Upgrade to a fixed version: 4.1.12, 4.2.0-RC.2.Source: cve.now feed data

More CVEs