CVE-2026-76210Public exploitNetwork attack vector

Authenticated file disclosure via PDF image handling

Published Aug 19, 2026 · Updated Aug 19, 2026

Information disclosure in phpMyFAQ 4.1.6 and earlier allows remote authenticated users to read local files via PDF export. The PDF code passes FAQ answer HTML to TCPDF without cleanUpContent() sanitization, so an attacker-planted img src under content/ is read as a local file and a non-image target raises an uncaught exception whose stack trace echoes file bytes. Planting the payload requires permission to create or edit FAQ content, but once the FAQ is published any user who requests the PDF can trigger the leak; default PHP settings truncate the output, while a larger zend.exception_string_param_max_len can expose complete files such as database.php.

CVSS severity6.5
Medium
EPSS probability0.37%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in phpMyFAQ 4.1.6 and earlier allows remote authenticated users to read local files via PDF export. The PDF code passes FAQ answer HTML to TCPDF without cleanUpContent() sanitization, so an attacker-planted img src under content/ is read as a local file and a non-image target raises an uncaught exception whose stack trace echoes file bytes. Planting the payload requires permission to create or edit FAQ content, but once the FAQ is published any user who requests the PDF can trigger the leak; default PHP settings truncate the output, while a larger zend.exception_string_param_max_len can expose complete files such as database.php.

The record

CVE
CVE-2026-76210
Published
Aug 19, 2026
Updated
Aug 19, 2026
Vendor
Thorsten Rinne
Product
phpMyFAQ
Classifications
CWE-209, CWE-73, T1005
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <4.1.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Thorsten Rinne · phpMyFAQversion=0 <4.1.6

Published CVSS scores

6.5GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-209Generation of Error Message Containing Sensitive Information
CWE-73External Control of File Name or Path
T1005Data from Local System

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo