CVE-20XX-?
agent?

Phpmyfaq CVEs.

Published CVEs affecting Phpmyfaq, ranked by exploit odds.

154 CVEs · updated 2026-11-12 07:09 UTC

Reset all
  1. CVE-2005-3048

    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.

    Disclosure Web app Phpmyfaq

    6.4 MEDIUM 8% exploit odds No fix listed
  2. CVE-2022-3766

    Cross-site Scripting (XSS) - Reflected in GitHub repository thorsten/phpmyfaq prior to 3.1.8.

    XSS Web app Phpmyfaq

    6.1 MEDIUM 8% exploit odds Fix listed
  3. CVE-2014-6047

    phpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to read arbitrary attachments by leveraging incorrect "download an attachment" permission checks.

    Disclosure Web app Phpmyfaq

    5.3 MEDIUM 6% exploit odds Fix listed
  4. CVE-2014-6048

    phpMyFAQ before 2.8.13 allows remote attackers to read arbitrary attachments via a direct request.

    Disclosure Web app Phpmyfaq

    5.3 MEDIUM 6% exploit odds Fix listed
  5. CVE-2022-4407

    Cross-site Scripting (XSS) - Reflected in GitHub repository thorsten/phpmyfaq prior to 3.1.9.

    Phpmyfaq

    6.1 MEDIUM 5% exploit odds Fix listed
  6. CVE-2010-4821

    Cross-site scripting (XSS) vulnerability in phpMyFAQ before 2.6.9 allows remote attackers to inject arbitrary web script or HTML via the PATH_INFO to index.php.

    Phpmyfaq

    4.3 MEDIUM 5% exploit odds Fix listed
  7. CVE-2014-6050

    phpMyFAQ before 2.8.13 allows remote attackers to bypass the CAPTCHA protection mechanism by replaying the request.

    Phpmyfaq

    5.3 MEDIUM 5% exploit odds Fix listed
  8. CVE-2014-6049

    phpMyFAQ before 2.8.13 allows remote authenticated users with admin privileges to bypass authorization via a crafted instance ID parameter.

    Phpmyfaq

    2.7 LOW 3% exploit odds Fix listed
  9. CVE-2005-3049

    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.

    Phpmyfaq

    5.0 MEDIUM 3% exploit odds Fix listed
  10. CVE-2017-15730

    In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.ratings.php.

    Phpmyfaq

    8.8 HIGH 2% exploit odds Fix listed
  11. CVE-2017-14618

    Cross-site scripting (XSS) vulnerability in inc/PMF/Faq.php in phpMyFAQ through 2.9.8 allows remote attackers to inject arbitrary web script or HTML via the Questions field in an "Add New FAQ" action.

    Phpmyfaq

    4.8 MEDIUM 2% exploit odds No fix listed
  12. CVE-2004-2257

    phpMyFAQ 1.4.0 allows remote attackers to access the Image Manager to upload or delete images without authorization via a direct request.

    Phpmyfaq

    5.3 MEDIUM 2% exploit odds Fix listed
  13. CVE-2024-55889

    phpMyFAQ is an open source FAQ web application. Prior to version 3.2.10, a vulnerability exists in the FAQ Record component where a privileged attacker can trigger a file download on a victim's machine upon page visit by embedding it in an <iframe> element without user interaction or explicit consent. Version 3.2.10 fixes the issue.

    XSS Web app Phpmyfaq

    4.9 MEDIUM 2% exploit odds Fix listed
  14. CVE-2017-14619

    Cross-site scripting (XSS) vulnerability in phpMyFAQ through 2.9.8 allows remote attackers to inject arbitrary web script or HTML via the "Title of your FAQ" field in the Configuration Module.

    Phpmyfaq

    6.1 MEDIUM 2% exploit odds Fix listed
  15. CVE-2025-69200

    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.

    Disclosure Web app Phpmyfaq

    7.5 HIGH 2% exploit odds Fix listed
  16. CVE-2014-6045

    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.

    Phpmyfaq

    7.2 HIGH 2% exploit odds Fix listed
  17. CVE-2004-2256

    Directory traversal vulnerability in phpMyFAQ 1.4.0 alpha allows remote attackers to read arbitrary files, and possibly execute local PHP files, via .. sequences in the lang (language) variable.

    Phpmyfaq

    5.0 MEDIUM 2% exploit odds Fix listed
  18. CVE-2004-2255

    Directory traversal vulnerability in phpMyFAQ 1.3.12 allows remote attackers to read arbitrary files, and possibly execute local PHP files, via the action variable, which is used as part of a template filename.

    Phpmyfaq

    6.4 MEDIUM 2% exploit odds Fix listed
  19. CVE-2014-0814

    Cross-site scripting (XSS) vulnerability in phpMyFAQ before 2.8.6 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

    Phpmyfaq

    4.3 MEDIUM 2% exploit odds Fix listed
  20. CVE-2014-6046

    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.

    Phpmyfaq

    8.8 HIGH 2% exploit odds Fix listed
  21. CVE-2017-15727

    In phpMyFAQ before 2.9.9, there is Stored Cross-site Scripting (XSS) via an HTML attachment.

    Phpmyfaq

    5.4 MEDIUM 2% exploit odds Fix listed
  22. CVE-2026-24421

    phpMyFAQ is an open source FAQ web application. Versions 4.0.16 and below have flawed authorization logic which exposes the /api/setup/backup endpoint to any authenticated user despite their permissions. SetupController.php uses userIsAuthenticated() but does not verify that the requester has configuration/admin permissions. Non-admin users can trigger a configuration backup and retrieve its path. The endpoint only checks authentication, not authorization, and returns a link to the generated ZIP. This issue is fixed in version 4.0.17.

    Auth & access Web app Phpmyfaq

    6.5 MEDIUM 2% exploit odds Fix listed
  23. CVE-2023-0789

    Command Injection in GitHub repository thorsten/phpmyfaq prior to 3.1.11.

    Phpmyfaq

    8.1 HIGH 2% exploit odds Fix listed
  24. CVE-2023-1880

    Cross-site Scripting (XSS) - Reflected in GitHub repository thorsten/phpmyfaq prior to 3.1.12.

    Phpmyfaq

    6.1 MEDIUM 2% exploit odds Fix listed
  25. CVE-2022-3754

    Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.8.

    Other Web app Phpmyfaq

    9.8 CRITICAL 2% exploit odds Fix listed
  26. CVE-2006-6913

    Unspecified vulnerability in phpMyFAQ 1.6.7 and earlier allows remote attackers to upload arbitrary PHP scripts via unspecified vectors.

    Phpmyfaq

    7.5 HIGH 1% exploit odds Fix listed
  27. CVE-2005-3734

    Cross-site scripting (XSS) vulnerability in the "add content" page in phpMyFAQ 1.5.3 and earlier allows remote attackers to inject arbitrary web script or HTML via the (1) thema, (2) username, and (3) usermail parameters.

    Phpmyfaq

    4.3 MEDIUM 1% exploit odds Fix listed
  28. CVE-2024-28105

    phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. The category image upload function in phpmyfaq is vulnerable to manipulation of the `Content-type` and `lang` parameters, allowing attackers to upload malicious files with a .php extension, potentially leading to remote code execution (RCE) on the system. This vulnerability is fixed in 3.2.6.

    Phpmyfaq

    7.2 HIGH 1% exploit odds Fix listed
  29. CVE-2010-4558

    phpMyFAQ 2.6.11 and 2.6.12, as distributed between December 4th and December 15th 2010, contains an externally introduced modification (Trojan Horse) in the getTopTen method in inc/Faq.php, which allows remote attackers to execute arbitrary PHP code.

    Phpmyfaq

    7.5 HIGH 1% exploit odds Fix listed
  30. CVE-2018-16651

    The admin backend in phpMyFAQ before 2.9.11 allows CSV injection in reports.

    Phpmyfaq

    7.2 HIGH 1% exploit odds Fix listed
  31. CVE-2005-3050

    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.

    Phpmyfaq

    5.0 MEDIUM 1% exploit odds Fix listed
  32. CVE-2011-3783

    phpMyFAQ 2.6.13 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by lang/language_uk.php and certain other files.

    Phpmyfaq

    5.0 MEDIUM 1% exploit odds No fix listed
  33. CVE-2007-1032

    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."

    Phpmyfaq

    6.8 MEDIUM 1% exploit odds Fix listed
  34. CVE-2022-3608

    Cross-site Scripting (XSS) - Stored in GitHub repository thorsten/phpmyfaq prior to 3.2.0-alpha.

    Phpmyfaq

    8.4 HIGH 1% exploit odds Fix listed
  35. CVE-2009-4780

    Multiple cross-site scripting (XSS) vulnerabilities in index.php in phpMyFAQ before 2.5.5 allow remote attackers to inject arbitrary web script or HTML via (1) the lang parameter in a sitemap action, (2) the search parameter in a search action, (3) the tagging_id parameter in a search action, (4) the highlight parameter in an artikel action, (5) the artlang parameter in an artikel action, (6) the letter parameter in a sitemap action, (7) the lang parameter in a show action, (8) the cat parameter in a show action, (9) the newslang parameter in a news action, (10) the artlang parameter in a send2friend action, (11) the cat parameter in a send2friend action, (12) the id parameter in a send2friend action, (13) the srclang parameter in a translate action, (14) the id parameter in a translate action, (15) the cat parameter in a translate action, (16) the cat parameter in an add action, or (17) the question parameter in an add action. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

    Phpmyfaq

    4.3 MEDIUM 1% exploit odds Fix listed
  36. CVE-2017-15808

    In phpMyFaq before 2.9.9, there is CSRF in admin/ajax.config.php.

    Phpmyfaq

    8.8 HIGH 1% exploit odds Fix listed
  37. CVE-2024-27299

    phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. A SQL injection vulnerability has been discovered in the the "Add News" functionality due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE. The vulnerable field lies in the `authorEmail` field which uses PHP's `FILTER_VALIDATE_EMAIL` filter. This filter is insufficient in protecting against SQL injection attacks and should still be properly escaped. However, in this version of phpMyFAQ (3.2.5), this field is not escaped properly can be used together with other fields to fully exploit the SQL injection vulnerability. This vulnerability is fixed in 3.2.6.

    Phpmyfaq

    8.8 HIGH 1% exploit odds Fix listed
  38. CVE-2005-3046

    SQL injection vulnerability in password.php in PhpMyFaq 1.5.1 allows remote attackers to modify SQL queries and gain administrator privileges via the user field.

    Phpmyfaq

    6.8 MEDIUM 1% exploit odds No fix listed
  39. CVE-2017-15734

    In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.main.php.

    Phpmyfaq

    8.8 HIGH 1% exploit odds Fix listed
  40. CVE-2017-15735

    In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) for modifying a glossary.

    Phpmyfaq

    8.8 HIGH 1% exploit odds Fix listed
  41. CVE-2014-0813

    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.

    Phpmyfaq

    6.8 MEDIUM 1% exploit odds Fix listed
  42. CVE-2023-5863

    Cross-site Scripting (XSS) - Reflected in GitHub repository thorsten/phpmyfaq prior to 3.2.2.

    Phpmyfaq

    6.1 MEDIUM 1% exploit odds Fix listed
  43. CVE-2017-11187

    phpMyFAQ before 2.9.8 does not properly mitigate brute-force attacks that try many passwords in attempted logins quickly.

    Other Web app Phpmyfaq

    9.8 CRITICAL 1% exploit odds Fix listed
  44. CVE-2006-6912

    SQL injection vulnerability in phpMyFAQ 1.6.7 and earlier allows remote attackers to execute arbitrary SQL commands via unspecified vectors, possibly the userfile or filename parameter.

    Phpmyfaq

    7.5 HIGH 1% exploit odds Fix listed
  45. CVE-2005-3047

    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.

    Phpmyfaq

    4.3 MEDIUM 1% exploit odds Fix listed
  46. CVE-2009-4040

    Cross-site scripting (XSS) vulnerability in phpMyFAQ before 2.0.17 and 2.5.x before 2.5.2, when used with Internet Explorer 6 or 7, allows remote attackers to inject arbitrary web script or HTML via unspecified parameters to the search page.

    Phpmyfaq

    4.3 MEDIUM 1% exploit odds Fix listed
  47. CVE-2023-0311

    Improper Authentication in GitHub repository thorsten/phpmyfaq prior to 3.1.10.

    Auth & access Web app Phpmyfaq

    9.8 CRITICAL 1.0% exploit odds Fix listed
  48. CVE-2024-28107

    phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. A SQL injection vulnerability has been discovered in the `insertentry` & `saveentry` when modifying records due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE. This vulnerability is fixed in 3.2.6.

    Phpmyfaq

    8.8 HIGH 1.0% exploit odds Fix listed
  49. CVE-2005-0702

    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.

    Phpmyfaq

    5.0 MEDIUM 1.0% exploit odds Fix listed
  50. CVE-2023-0788

    Code Injection in GitHub repository thorsten/phpmyfaq prior to 3.1.11.

    Phpmyfaq

    8.1 HIGH 0.9% exploit odds Fix listed

All CVEs affecting Phpmyfaq that appear in CVE.org and NVD, sorted by how likely they are to be exploited (EPSS), with fix status and timeline.