# 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


- **Severity:** Low 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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-j7hf-7jvx-hm98, GHSA-q4mh-222v-3g89

## What is CVE-2026-130368?

CVE-2026-130368 is a low-severity vulnerability in thorsten phpMyFAQ, published on 17 Nov 2026. 

### Official description

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.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-130368?

2 open source packages ship an affected version, including thorsten/phpmyfaq.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `thorsten/phpmyfaq` | Packagist | `pkg:composer/thorsten/phpmyfaq` | From 4.1.9 | 4.1.12 |
| `thorsten/phpmyfaq` | Packagist | `pkg:composer/thorsten/phpmyfaq` | From 4.2.0-alpha | 4.2.0-RC.2 |

## How do I fix CVE-2026-130368?

Upgrade thorsten/phpmyfaq to a fixed version for your release line: 4.1.12 or 4.2.0-RC.2.

## Is CVE-2026-130368 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130368 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130368 and fix it if it is affected.

What it is: CVE-2026-130368 is a low-severity vulnerability in thorsten phpMyFAQ, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130368 exists.

Affected packages and fixed versions:
- thorsten/phpmyfaq (Packagist): affected from 4.1.9; fixed in 4.1.12
- thorsten/phpmyfaq (Packagist): affected from 4.2.0-alpha; fixed in 4.2.0-RC.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130368/ (Markdown: https://insights.sbomify.com/CVE-2026-130368/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130368
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130368
- OSV: https://osv.dev/vulnerability/CVE-2026-130368

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130368/
Summaries are generated and may contain mistakes; the official description above is the record.
