# CVE-2026-76210: phpMyFAQ before v4.1.6 Local File Disclosure via PDF Export

> An attacker with FAQ editing permissions can trigger PDF export to disclose local file contents, including database credentials, via error message leakage.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-c63q-xx7x-j8w2, GHSA-m98p-5698-x2wc

## What is CVE-2026-76210?

CVE-2026-76210 is a high-severity vulnerability in Phpmyfaq Phpmyfaq, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

phpMyFAQ before 4.1.6 does not adequately sanitize HTML in FAQ answers before generating PDFs via TCPDF. An attacker with permission to create or edit FAQ content can embed an <img> tag whose src references a local file under the web root's content/ directory (e.g., content/core/config/database.php). When the PDF is generated, phpMyFAQ attempts to read the referenced file; because it is not a valid image the resulting error is converted into an uncaught exception whose stack trace discloses part of the file's contents to any user who triggers the PDF export. By default the disclosed portion is truncated (zend.exception_string_param_max_len), but a larger configured value can result in disclosure of entire files, including database credentials.

Weakness: CWE-73 (External Control of File Name or Path)

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

It affects 1 product.


Products: Phpmyfaq Phpmyfaq.

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

No fix has been published for CVE-2026-76210 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76210 being exploited?

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

## Other vulnerabilities in Phpmyfaq Phpmyfaq

- [CVE-2023-0310](https://insights.sbomify.com/CVE-2023-0310/): Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq (critical 9.8)
- [CVE-2022-4407](https://insights.sbomify.com/CVE-2022-4407/): Cross-site Scripting (XSS) - Reflected in thorsten/phpmyfaq (critical 9.8)
- [CVE-2017-11187](https://insights.sbomify.com/CVE-2017-11187/): Security feature bypass in n/a (critical 9.8)
- [CVE-2026-76213](https://insights.sbomify.com/CVE-2026-76213/): phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle (critical 9.1)
- [CVE-2026-76214](https://insights.sbomify.com/CVE-2026-76214/): phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76210 is a high-severity vulnerability in Phpmyfaq Phpmyfaq, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76210 exists.

Affected product: Phpmyfaq Phpmyfaq. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-76210/ (Markdown: https://insights.sbomify.com/CVE-2026-76210/index.md)
```

## Sources

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

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