Database compromise via unescaped configuration keys
Published Nov 17, 2025 · Updated Nov 17, 2025
SQL injection in phpMyFAQ before 4.0.14 allows remote authenticated users with configuration-edit permission to execute arbitrary SQL. ConfigurationTabController::save accepts form field names as array keys, and Configuration::update concatenates each key into a raw SQL WHERE clause without escaping. Exploitation requires Configuration Edit permission and can read, modify, or delete database data; code execution depends on database configuration.
Summary
What happened
SQL injection in phpMyFAQ before 4.0.14 allows remote authenticated users with configuration-edit permission to execute arbitrary SQL. ConfigurationTabController::save accepts form field names as array keys, and Configuration::update concatenates each key into a raw SQL WHERE clause without escaping. Exploitation requires Configuration Edit permission and can read, modify, or delete database data; code execution depends on database configuration.
The record
- CVE
- CVE-2025-62519
- Published
- Nov 17, 2025
- Updated
- Nov 17, 2025
- Vendor
- Thorsten Rinne
- Product
- phpMyFAQ
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 17, 2025CVE publishedPublication date reported by the CVE source.
- Nov 17, 2025Record 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=< 4.0.14
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- GHSA-fxm2-cmwj-qvx4 authenticated SQL injection 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