2348 matches found
CVE-2017-15731: Cross-Site Request Forgery (CSRF)
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery CSRF in admin/stat.adminlog.php...
CVE-2017-15727: Improper Neutralization of Input During Web Page Generation
In phpMyFAQ before 2.9.9, there is Stored Cross-site Scripting XSS via an HTML attachment...
CVE-2017-15732: Cross-Site Request Forgery (CSRF)
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery CSRF in admin/news.php...
CVE-2017-15733
The CVE-2017-15733 entry concerns phpMyFAQ prior to version 2.9.9, where CSRF protections are missing for admin/ajax.attachment.php and admin/att.main.php. Several connected sources (NVD/NVD-derived records, Red Hat advisory RH:CVE-2017-15733, CNVD, OSV, and Veracode) corroborate that an attacker...
CVE-2017-15730
CVE-2017-15730 affects phpMyFAQ before 2.9.9. The vulnerability is a Cross-Site Request Forgery (CSRF) in the admin/stat.ratings.php handler that allows an attacker to cause unauthorized actions (modifying information) without user consent. Public references in the provided documents include CVE ...
CVE-2017-15734
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery CSRF in admin/stat.main.php...
CVE-2017-15727
In phpMyFAQ before 2.9.9, there is Stored Cross-site Scripting XSS via an HTML attachment...
CVE-2017-15732
In phpMyFAQ (versions before 2.9.9), there is a Cross-Site Request Forgery (CSRF) vulnerability in admin/news.php due to missing CSRF protection. This affects the news-management functionality and can allow an attacker to perform unauthorized operations (e.g., actions on news entries) without use...
CVE-2017-15735
CVE-2017-15735 affects phpMyFAQ prior to 2.9.9, with a CSRF vulnerability that allows modification of glossary items. Multiple connected sources document CSRF for glossary updates (including PoC showing a form POST to admin/index.php?action=updateglossary while authenticated). The root cause desc...
CVE-2017-15733
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery CSRF in admin/ajax.attachment.php and admin/att.main.php...
CVE-2017-15729
CVE-2017-15729 affects phpMyFAQ versions earlier than 2.9.9. The issue is a Cross-Site Request Forgery (CSRF) vulnerability that allows an attacker to add a glossary without proper protection. Public documentation from multiple sources describes that, in vulnerable installations, a malicious acto...
CVE-2017-15728
CVE-2017-15728 affects phpMyFAQ prior to 2.9.9, exposing a Stored Cross-site Scripting (XSS) vulnerability through metaDescription or metaKeywords fields. Public sources (NVD entry and Red Hat advisory) describe the flaw as an XSS issue in phpMyFAQ versions before 2.9.9. The OpenVAS entry and CNV...
CVE-2017-15727
The CVE-2017-15727 entry concerns phpMyFAQ prior to 2.9.9, with a Stored Cross-site Scripting (XSS) vulnerability via an HTML attachment. Multiple connected sources (NVD/NVD-derived, CNVD, OSV, CVE lists, and OpenVAS notes) consistently describe that an attacker can inject arbitrary script by upl...
CVE-2017-15734
Summary: CVE-2017-15734 affects phpMyFAQ prior to 2.9.9 and is a CSRF in admin/stat.main.php. The vulnerability arises due to missing CSRF token validation in the affected action (e.g., clear-visits) within stat.main.php, allowing unauthorized state-changing requests when a user is authenticated....
CVE-2017-15735
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery CSRF for modifying a glossary...
CVE-2017-15728
In phpMyFAQ before 2.9.9, there is Stored Cross-site Scripting XSS via metaDescription or metaKeywords...
CVE-2017-15732
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery CSRF in admin/news.php...
CVE-2017-15731
In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery CSRF in admin/stat.adminlog.php...