CVE-2026-76210phpMyFAQ before v4.1.6 Local File Disclosure via PDF Export
Updated under an hour ago ()
Does this affect you?
It affects thorsten phpMyFAQ and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 6.5 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Weakness (CWE)
- CWE-73
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- VulnCheck
- NVD analysis
- Analyzed
- Record last updated
- Aug 21, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
thorsten phpMyFAQ thorsten:phpmyfaq (from the name) | before 4.1.6; 4.1.6 not affected | CNA record |
phpmyfaq phpmyfaq phpmyfaq:phpmyfaq | before 4.1.6 | NVD |
References
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-c63q-xx7x-j8w2vendor-advisory, exploit, mitigation
- https://www.vulncheck.com/advisories/phpmyfaq-before-local-file-disclosure-via-pdf-exportthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.