PatchSiren cyber security CVE debrief
CVE-2026-76210 thorsten CVE debrief
CVE-2026-76210 is a vulnerability in phpMyFAQ before version 4.1.6 that allows for local file disclosure via PDF export. 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. 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. Organizations using phpMyFAQ, especially those with sensitive data stored in the content/ directory, should prioritize patching to prevent potential local file disclosure via PDF export. The CVE record was published on 2026-08-19T14:17:46.510Z and has not been modified since then.
- Vendor
- thorsten
- Product
- phpMyFAQ
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-19
- Original CVE updated
- 2026-09-01
- Advisory published
- 2026-08-19
- Advisory updated
- 2026-09-01
Who should care
Organizations using phpMyFAQ, especially those with sensitive data stored in the content/ directory, should prioritize patching to prevent potential local file disclosure via PDF export.
Technical summary
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. 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.
Defensive priority
Organizations using phpMyFAQ should prioritize patching to prevent potential local file disclosure via PDF export.
Recommended defensive actions
- Patch phpMyFAQ to version 4.1.6 or later
- Restrict access to FAQ content creation and editing
- Monitor for suspicious PDF export activity
- Implement additional security measures to protect against local file disclosure
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE description indicates that phpMyFAQ before 4.1.6 does not adequately sanitize HTML in FAQ answers before generating PDFs via TCPDF, potentially leading to local file disclosure. 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. 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.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-76210 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-76210
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-76210 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-76210
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-c63q-xx7x-j8w2
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/phpmyfaq-before-local-file-disclosure-via-pdf-export
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.