Unauthenticated backup and migration via setup API
Published Aug 19, 2026 · Updated Aug 19, 2026
Authentication bypass in phpMyFAQ before 4.1.7 allows remote attackers to call setup backup and database migration endpoints. SetupController makes isSecured() a no-op, so backup() and updateDatabase() rely only on main.maintenanceMode and accept unauthenticated POST requests without CSRF protection. Exploitation is limited to periods when maintenance mode is enabled, but a successful update-database call can switch that mode off and the generated ZIP can expose database credentials if it is read back from disk.
Summary
What happened
Authentication bypass in phpMyFAQ before 4.1.7 allows remote attackers to call setup backup and database migration endpoints. SetupController makes isSecured() a no-op, so backup() and updateDatabase() rely only on main.maintenanceMode and accept unauthenticated POST requests without CSRF protection. Exploitation is limited to periods when maintenance mode is enabled, but a successful update-database call can switch that mode off and the generated ZIP can expose database credentials if it is read back from disk.
The record
- CVE
- CVE-2026-75919
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-862, CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=0 <4.1.7
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Setup API unauthenticated POST proof of conceptproof of concept · demonstrated
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