Vulnerability Description
phpMyFAQ before 4.1.7 contains a SQL injection vulnerability in the glossary create and update endpoints caused by truncating an escaped string before embedding it in a SQL literal. Authenticated users with glossary add or edit permissions can craft a payload with a dangling backslash to escape the closing quote and inject arbitrary SQL commands to read sensitive database information.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Phpmyfaq | Phpmyfaq | < 4.1.7 |
Related Weaknesses (CWE)
References
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-79h3-6hxj-g98hExploitVendor Advisory
- https://www.vulncheck.com/advisories/phpmyfaq-before-sql-injection-via-glossaryThird Party Advisory
- https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-79h3-6hxj-g98hExploitVendor Advisory
FAQ
What is CVE-2026-76205?
CVE-2026-76205 is a vulnerability with a CVSS score of 8.1 (HIGH). phpMyFAQ before 4.1.7 contains a SQL injection vulnerability in the glossary create and update endpoints caused by truncating an escaped string before embedding it in a SQL literal. Authenticated user...
How severe is CVE-2026-76205?
CVE-2026-76205 has been rated HIGH with a CVSS base score of 8.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-76205?
Check the references section above for vendor advisories and patch information. Affected products include: Phpmyfaq Phpmyfaq.