How severe is CVE-2025-62519?

CVE-2025-62519 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-62519 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (49th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-62519?

CVE-2025-62519 affects Phpmyfaq. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-62519?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-62519 have an EU (EUVD) identifier?

Yes. CVE-2025-62519 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-197804.

When was CVE-2025-62519 published?

CVE-2025-62519 was published on 2025-11-17 and last updated on 2026-06-17.

CVE-2025-62519

CVE-2025-62519 is a high-severity vulnerability in Phpmyfaq with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-89.

Key facts

Severity: High (CVSS 3.x base score 7.2)
EPSS exploit prediction: 1% (49th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-197804
Weakness: CWE-89
Affected product: Phpmyfaq
Published: 2025-11-17
Last modified: 2026-06-17

Description

phpMyFAQ is an open source FAQ web application. Prior to version 4.0.14, an authenticated SQL injection vulnerability in the main configuration update functionality of phpMyFAQ allows a privileged user with 'Configuration Edit' permissions to execute arbitrary SQL commands. Successful exploitation can lead to a full compromise of the database, including reading, modifying, or deleting all data, as well as potential remote code execution depending on the database configuration. This issue has been patched in version 4.0.14.

Frequently asked questions

What is CVE-2025-62519?: phpMyFAQ is an open source FAQ web application. Prior to version 4.0.14, an authenticated SQL injection vulnerability in the main configuration update functionality of phpMyFAQ allows a privileged user with 'Configuration Edit' permissions to execute arbitrary SQL commands. Successful exploitation can lead to a full compromise of the database, including reading, modifying, or deleting all data, as well as potential remote code execution depending on the database configuration. This issue has been patched in version 4.0.14.
How severe is CVE-2025-62519?: CVE-2025-62519 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-62519 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (49th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-62519?: CVE-2025-62519 affects Phpmyfaq. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-62519?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-62519 have an EU (EUVD) identifier?: Yes. CVE-2025-62519 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-197804.
When was CVE-2025-62519 published?: CVE-2025-62519 was published on 2025-11-17 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*

More vulnerabilities in Phpmyfaq

CVE-2023-5865 — Critical (CVSS 9.8): Insufficient Session Expiration in GitHub repository thorsten/phpmyfaq prior to 3.2.2.
CVE-2023-5227 — Critical (CVSS 9.8): Unrestricted Upload of File with Dangerous Type in GitHub repository thorsten/phpmyfaq prior to 3.1.8.
CVE-2023-4006 — Critical (CVSS 9.8): Improper Neutralization of Formula Elements in a CSV File in GitHub repository thorsten/phpmyfaq prior to 3.1.16.
CVE-2023-2429 — Critical (CVSS 9.8): Improper Access Control in GitHub repository thorsten/phpmyfaq prior to 3.1.13.
CVE-2023-0311 — Critical (CVSS 9.8): Improper Authentication in GitHub repository thorsten/phpmyfaq prior to 3.1.10.
CVE-2023-0307 — Critical (CVSS 9.8): Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.10.

All CVEs affecting Phpmyfaq →

Other CWE-89 (SQL Injection) vulnerabilities

CVE-2026-54350 — Critical (CVSS 10.0): Budibase is an open-source low-code platform. Prior to 3.39.12, an unauthenticated visitor of any published Budibase…
CVE-2026-8054 — Critical (CVSS 10.0): Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in the Publish Audit API endpoints…
CVE-2026-42287 — Critical (CVSS 10.0): Emlog is an open source website building system. Prior to version 2.6.11, direct SQL injection in article creation and…
CVE-2026-3325 — Critical (CVSS 10.0): SQL injection (SQLi) in MegaCMS v12.0.0, specifically in the “id_territorio” parameter of the…
CVE-2025-10878 — Critical (CVSS 10.0): A SQL injection vulnerability exists in the login functionality of Fikir Odalari AdminPando 1.0.1 before 2026-01-26.…
CVE-2025-57792 — Critical (CVSS 10.0): Explorance Blue versions prior to 8.14.9 contain a SQL injection vulnerability caused by insufficient validation of…

Browse all CWE-89 (SQL Injection) vulnerabilities →