# CVE-2026-46364: phpMyFAQ - SQL Injection via User-Agent Header in BuiltinCaptcha

> Unauthenticated attackers can extract sensitive database data via SQL injection in the captcha endpoint by crafting malicious User-Agent headers.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-289f-fq7w-6q2w

## What is CVE-2026-46364?

CVE-2026-46364 is a critical SQL injection vulnerability in thorsten phpmyfaq, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

phpMyFAQ before 4.1.2 contains an unauthenticated SQL injection vulnerability in BuiltinCaptcha::garbageCollector() and BuiltinCaptcha::saveCaptcha() methods that interpolate unsanitized User-Agent headers into DELETE and INSERT queries. Unauthenticated attackers can exploit the public GET /api/captcha endpoint by crafting malicious User-Agent headers to perform time-based blind SQL injection, extracting sensitive data including user credentials, admin tokens, and SMTP credentials from the database.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `thorsten/phpmyfaq` | Packagist | All versions | 4.1.2 |
| `thorsten/phpmyfaq` | Packagist | All versions | 4.1.2 |
| `phpmyfaq/phpmyfaq` | Packagist | All versions | 4.1.2 |
| `phpmyfaq/phpmyfaq` | Packagist | All versions | 4.1.2 |

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

Upgrade thorsten/phpmyfaq to 4.1.2 or later.

## Is CVE-2026-46364 being exploited?

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

Public exploit code:

- phpMyFAQ <= 4.1.1 - SQL Injection (nuclei): http/cves/2026/CVE-2026-46364.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46364 is a critical SQL injection vulnerability in thorsten phpmyfaq, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46364 exists.

Affected packages and fixed versions:
- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 4.1.2
- thorsten/phpmyfaq (Packagist): affected all versions; fixed in 4.1.2
- phpmyfaq/phpmyfaq (Packagist): affected all versions; fixed in 4.1.2
- phpmyfaq/phpmyfaq (Packagist): affected all versions; fixed in 4.1.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-46364/ (Markdown: https://insights.sbomify.com/CVE-2026-46364/index.md)
```

## Sources

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

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