Phpmyfaq vulnerabilities

159 vulnerabilities

Known vulnerabilities in Phpmyfaq products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 1 product.

Products

1
9CVE-2018-16651phpmyfaqphpmyfaq
EPSS score
1.37%
The admin backend in phpMyFAQ before 2.9.11 allows CSV injection in reports.
8.8CVE-2018-16650phpmyfaqphpmyfaq
EPSS score
0.50%
phpMyFAQ before 2.9.11 allows CSRF.
6.8CVE-2007-1032phpmyfaqphpmyfaq
EPSS score
1.23%
Unspecified vulnerability in phpMyFAQ 1.6.9 and earlier, when register_globals is enabled, allows remote attackers to "gain the privilege for uploading files on the server."
9.8CVE-2025-59943phpmyfaqphpmyfaq+1
EPSS score
0.42%
phpMyFAQ is an open source FAQ web application. Versions 4.0-nightly-2025-10-03 and below do not enforce uniqueness of email addresses during user registration. This allows multiple distinct accounts to be created with the same email. Because email is often used as an identifier for password resets, notifications, and administrative actions, this flaw can cause account ambiguity and, in certain configurations, may lead to privilege escalation or account takeover. This issue is fixed in version 4.0.13.
7.2CVE-2025-62519phpmyfaqphpmyfaq+1
EPSS score
0.80%
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.
6.1CVE-2025-68951phpmyfaqphpmyfaq+1
EPSS score
0.28%
phpMyFAQ is an open source FAQ web application. Versions 4.0.14 and 4.0.15 have a stored cross-site scripting (XSS) vulnerability that allows an attacker to execute arbitrary JavaScript in an administrator’s browser by registering a user whose display name contains HTML entities. When an administrator views the admin user list, the payload is decoded server-side and rendered without escaping, resulting in script execution in the admin context. Version 4.0.16 contains a patch for the issue.
7.5CVE-2025-69200phpmyfaqphpmyfaq+1
EPSS score
2.14%
phpMyFAQ is an open source FAQ web application. In versions prior to 4.0.16, an unauthenticated remote attacker can trigger generation of a configuration backup ZIP via `POST /api/setup/backup` and then download the generated ZIP from a web-accessible location. The ZIP contains sensitive configuration files (e.g., `database.php` with database credentials), leading to high-impact information disclosure and potential follow-on compromise. Version 4.0.16 fixes the issue.
6.8CVE-2014-0813phpmyfaqphpmyfaq
EPSS score
1.07%
Cross-site request forgery (CSRF) vulnerability in phpMyFAQ before 2.8.6 allows remote attackers to hijack the authentication of arbitrary users for requests that modify settings.
4.3CVE-2014-0814phpmyfaqphpmyfaq
EPSS score
1.95%
Cross-site scripting (XSS) vulnerability in phpMyFAQ before 2.8.6 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
7.2CVE-2014-6045phpmyfaqphpmyfaq
EPSS score
2.09%
SQL injection vulnerability in phpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to execute arbitrary SQL commands via vectors involving the restore function.
5.3CVE-2014-6047phpmyfaqphpmyfaq
EPSS score
5.68%
phpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to read arbitrary attachments by leveraging incorrect "download an attachment" permission checks.
8.8CVE-2014-6046phpmyfaqphpmyfaq
EPSS score
1.93%
Multiple cross-site request forgery (CSRF) vulnerabilities in phpMyFAQ before 2.8.13 allow remote attackers to hijack the authentication of unspecified users for requests that (1) delete active users by leveraging improper validation of CSRF tokens or that (2) delete open questions, (3) activate users, (4) publish FAQs, (5) add or delete Glossary, (6) add or delete FAQ news, or (7) add or delete comments or add votes by leveraging lack of a CSRF token.
5.3CVE-2014-6048phpmyfaqphpmyfaq
EPSS score
5.68%
phpMyFAQ before 2.8.13 allows remote attackers to read arbitrary attachments via a direct request.
5.3CVE-2014-6050phpmyfaqphpmyfaq
EPSS score
4.55%
phpMyFAQ before 2.8.13 allows remote attackers to bypass the CAPTCHA protection mechanism by replaying the request.
5.5CVE-2014-6049phpmyfaqphpmyfaq
EPSS score
3.19%
phpMyFAQ before 2.8.13 allows remote authenticated users with admin privileges to bypass authorization via a crafted instance ID parameter.
5CVE-2005-0702phpmyfaqphpmyfaq
EPSS score
0.96%
SQL injection vulnerability in phpMyFAQ 1.4 and 1.5 allows remote attackers to add FAQ records to the database via the username field in forum messages.
5CVE-2005-3049phpmyfaqphpmyfaq
EPSS score
2.62%
PhpMyFaq 1.5.1 stores data files under the web document root with insufficient access control and predictable filenames, which allows remote attackers to obtain sensitive information via a direct request to the data/tracking[DATE] file.
4.3CVE-2005-3047phpmyfaqphpmyfaq
EPSS score
1.04%
Multiple cross-site scripting (XSS) vulnerabilities in PhpMyFaq 1.5.1 allow remote attackers to inject arbitrary web script or HTML via the (1) PMF_CONF[version] parameter to footer.php or (2) PMF_LANG[metaLanguage] to header.php.
6.4CVE-2005-3048phpmyfaqphpmyfaq
EPSS score
8.31%
Directory traversal vulnerability in index.php in PhpMyFaq 1.5.1 allows remote attackers to read arbitrary files or include arbitrary PHP files via a .. (dot dot) in the LANGCODE parameter, which also allows direct code injection via the User Agent field in a request packet, which can be activated by using LANGCODE to reference the user tracking data file.
5CVE-2005-3050phpmyfaqphpmyfaq
EPSS score
1.36%
PhpMyFaq 1.5.1 allows remote attackers to obtain sensitive information via a LANGCODE parameter that does not exist, which reveals the path in an error message.