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

Published Aug 19, 2026
·
Updated

phpMyFAQ before 4.1.7 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.exceptionstringparammaxlen), but a larger configured value can result in disclosure of entire files, including database credentials.

Affected Software

1 affected component
PhpMyFaq phpmyfaq<4.1.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade phpMyFAQ to a version that resolves this vulnerability.

    Fixed in 4.1.7
  2. Upgrade

    Upgrade phpMyFAQ to a version that resolves this vulnerability.

    Fixed in 4.1.6
  3. Compensating control

    Restrict the ability to create or edit FAQ content to trusted/admin users only, since the vulnerability requires permission to create or edit FAQ content in order to embed an <img> tag pointing to a local file under the web root (e.g., content/core/config/database.php).

Event History

Aug 19, 2026
CVE Published
via MITRE·02:01 PM
Data Sourced
via MITRE·02:01 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue, and who can view the disclosed data?

An attacker needs permission to create or edit FAQ content so they can place a crafted image reference in an answer. Any user who triggers PDF export can receive the uncaught exception and its stack trace containing the disclosed file content.

2

What configuration conditions affect the amount of data exposed?

The referenced local file must be under the web root's content/ directory. By default, disclosed content is truncated by zend.exception_string_param_max_len; increasing that setting can expose entire files, including database credentials.

3

How can I determine whether an instance may already be affected?

Review FAQ answers created or edited by users with content permissions for img tags whose src points to local files in the content/ directory. Also review PDF export errors and exception output for stack traces that include file contents.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203