CVE-2025-62519
BaseFortify
Publication date: 2025-11-17
Last updated on: 2026-01-05
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpmyfaq | phpmyfaq | to 4.0.14 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an authenticated SQL injection in phpMyFAQ versions prior to 4.0.14. It occurs in the main configuration update functionality and allows a privileged user with 'Configuration Edit' permissions to execute arbitrary SQL commands on the database. This means the attacker can manipulate the database by reading, modifying, or deleting data, and potentially execute remote code depending on the database setup.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to a full compromise of the database, including unauthorized reading, modification, or deletion of all data stored in phpMyFAQ. Additionally, depending on the database configuration, it may allow remote code execution, which could lead to further system compromise beyond the database.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively impact compliance with standards like GDPR and HIPAA because it allows unauthorized access and modification of sensitive data stored in the database. Such a compromise could lead to data breaches, violating data protection and privacy requirements mandated by these regulations.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade phpMyFAQ to version 4.0.14 or later, where the SQL injection vulnerability has been patched. Additionally, restrict 'Configuration Edit' permissions to only trusted users to minimize risk until the upgrade is applied.