p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in phpmyfaq/phpmyfaq · Seite 3

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für phpmyfaq/phpmyfaq: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 47

  1. CVE-2024-28105

    Hoch · CVSS 7.2EPSS 1,48%Korrektur verfügbar

    phpMyFAQ's File Upload Bypass at Category Image Leads to RCE

    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.

    • Auf 3.2.6 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2024-27300

    Mittel · CVSS 5.5EPSS 0,69%Korrektur verfügbar

    phpMyFAQ Stored XSS at user email

    phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. The `email` field in phpMyFAQ's user control panel page is vulnerable to stored XSS attacks due to the inadequacy of PHP's `FILTER_VALIDATE_EMAIL` function, which only validates the email format, not its content. This vulnerability enables an attacker to execute arbitrary client-side JavaScript within the context of another user's phpMyFAQ session. This vulnerability is fixed in 3.2.6.

    • Auf 3.2.6 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2024-27299

    Hoch · CVSS 8.8EPSS 1,15%Korrektur verfügbar

    phpMyFAQ SQL Injection at "Save News"

    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 versio

    • Auf 3.2.6 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2024-24574

    Mittel · CVSS 6.5EPSS 0,88%Korrektur verfügbar

    phpMyFAQ vulnerable to stored XSS on attachments filename

    phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Unsafe echo of filename in phpMyFAQ\phpmyfaq\admin\attachments.php leads to allowed execution of JavaScript code in client side (XSS). This vulnerability has been patched in version 3.2.5.

    • Auf 3.2.5 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2024-22208

    Mittel · CVSS 6.5EPSS 0,74%Korrektur verfügbar

    phpMyFAQ sharing FAQ functionality can easily be abused for phishing purposes

    phpMyFAQ is an Open Source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. The 'sharing FAQ' functionality allows any unauthenticated actor to misuse the phpMyFAQ application to send arbitrary emails to a large range of targets. The phpMyFAQ application has a functionality where anyone can share a FAQ item to others. The front-end of this functionality allows any phpMyFAQ articles to be shared with 5 email addresses. Any unauthenticated actor can perform this action. There is a CAPTCHA in place, however the amount of people you email with a single request is not limited to 5 by the backend. An attacker can thus sol

    • Auf 3.2.5 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2024-22202

    Mittel · CVSS 5.7EPSS 0,59%Korrektur verfügbar

    User Removal Page Allows Spoofing Of User Details

    phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. phpMyFAQ's user removal page allows an attacker to spoof another user's detail, and in turn make a compelling phishing case for removing another user's account. The front-end of this page doesn't allow changing the form details, an attacker can utilize a proxy to intercept this request and submit other data. Upon submitting this form, an email is sent to the administrator informing them that this user wants to delete their account. An administrator has no way of telling the difference between the actual user wishing to delete their account o

    • Auf 3.2.5 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →