Authenticated SQL injection via escape-then-truncate
Published Aug 19, 2026 · Updated Aug 19, 2026
SQL injection in phpMyFAQ before 4.1.7 allows remote authenticated users to read database content via glossary endpoints. GlossaryRepository::create and GlossaryRepository::update escape the item field, truncate the escaped result to 254 characters, and then interpolate it into a quoted SQL string, so a 253-character value ending in a single quote leaves a dangling backslash that consumes the next quote and turns the definition field into attacker-controlled SQL. Reachability requires a valid account with addglossary or editglossary permission, and the published proof of concept demonstrates direct disclosure of user, configuration, and password-hash data rather than a service interrupt.
Summary
What happened
SQL injection in phpMyFAQ before 4.1.7 allows remote authenticated users to read database content via glossary endpoints. GlossaryRepository::create and GlossaryRepository::update escape the item field, truncate the escaped result to 254 characters, and then interpolate it into a quoted SQL string, so a 253-character value ending in a single quote leaves a dangling backslash that consumes the next quote and turns the definition field into attacker-controlled SQL. Reachability requires a valid account with addglossary or editglossary permission, and the published proof of concept demonstrates direct disclosure of user, configuration, and password-hash data rather than a service interrupt.
The record
- CVE
- CVE-2026-76205
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
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
- GHSA-79h3-6hxj-g98h 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