CVE-2026-75920Public exploitNetwork attack vectorHinoki check available

Sensitive file disclosure via web-root backup ZIP

Published Aug 19, 2026 · Updated Aug 20, 2026

Information disclosure in phpMyFAQ before 4.1.6 allows attackers to read sensitive files via a web-accessible content backup ZIP. Backup::createContentFolderBackup() writes the archive to PMF_ROOT/content.zip, and BackupController::download removes it only after streaming, leaving a race window and a leftover-file exposure if deletion fails. Creating the archive requires an authenticated principal with BACKUP permission, but fetching content.zip does not; admin-context XSS can also trigger the backup and expose database credentials and other content data to unauthenticated retrieval.

CVSS severity5.3
Medium
EPSS probability0.33%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
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 before 4.1.6 allows attackers to read sensitive files via a web-accessible content backup ZIP. Backup::createContentFolderBackup() writes the archive to PMF_ROOT/content.zip, and BackupController::download removes it only after streaming, leaving a race window and a leftover-file exposure if deletion fails. Creating the archive requires an authenticated principal with BACKUP permission, but fetching content.zip does not; admin-context XSS can also trigger the backup and expose database credentials and other content data to unauthenticated retrieval.

The record

CVE
CVE-2026-75920
Published
Aug 19, 2026
Updated
Aug 20, 2026
Vendor
Thorsten Rinne
Product
phpMyFAQ
Classifications
CWE-377
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 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 privilegesunauthenticated

What is affected?

Thorsten Rinne · phpMyFAQversion=0 <4.1.6

Published CVSS scores

6.0VulnCheckCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
5.3VulnCheckCVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-377Insecure Temporary File

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