Skip to content
OpenAdvisories

Package · Packagist

phpmyfaq/phpmyfaq

47 known vulnerabilities.

47 results · Feed

  • High 8.5

    phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion

    phpMyFAQ is an open source FAQ web application. The `StopWords::add()` method inversions prior to 4.1.6 builds a SQL `INSERT` statement using `sprintf()` and inserts the user-supplied stop word value directly into the query string without calling the applicat…

  • High 8.1

    phpMyFAQ's two-factor authentication login bypasses the password factor

    phpMyFAQ is an open source FAQ web application. Versions 3.2.0 through 4.1.5 contain an authentication bypass in its public two-factor authentication verification flow: an unauthenticated attacker can submit an account’s numeric user ID and a valid or brute-f…

  • High 8.2

    phpMyFAQ has Stored XSS in Admin FAQ Editor via HTML Entity Bypass in Frontend FAQ Submission

    phpMyFAQ is an open source FAQ web application. A stored cross-site scripting (XSS) vulnerability in versions prior to 4.2.0-alpha allows any unauthenticated user (or low-privileged registered user) to inject arbitrary JavaScript that executes in an administr…

  • Medium 5.3

    phpMyFAQ - Information Disclosure of Inactive FAQ Content via Public API Endpoints

    phpMyFAQ before 4.1.5 applies inconsistent active=yes and publication-date filtering across its public FAQ API endpoints, allowing unauthenticated attackers to retrieve inactive (draft or review-only) FAQ content. Specifically, GET /api/v3.1/faq/{categoryId}/…

  • Low 2.7

    phpMyFAQ - Authenticated Path Traversal in PDF Export via concatenatePaths Function

    phpMyFAQ before 4.1.5 contains a potential authenticated path traversal vulnerability in the concatenatePaths() function within src/phpMyFAQ/Export/Pdf/Wrapper.php. A user with FAQ editing privileges can store HTML containing crafted image paths that are proc…

  • High 8.8

    phpMyFAQ - Privilege Escalation via Missing Self-Rights Constraint in GroupController::updatePermissions

    phpMyFAQ before 4.1.5 contains a privilege escalation vulnerability in GroupController::updatePermissions that allows GROUP_EDIT administrators to grant arbitrary rights to groups without verifying they hold those rights themselves. A delegated administrator …

  • High 8.8

    phpMyFAQ - Privilege Escalation via Missing Authorization in editUser() and updateUserRights()

    phpMyFAQ before 4.1.4 contains missing authorization vulnerabilities in editUser() and updateUserRights() endpoints that allow authenticated administrators to escalate privileges. Non-SuperAdmin users with edit_user permission can set is_superadmin flag or gr…

  • Medium 6.5

    phpMyFAQ: Missing userHasPermission() in 4 API write endpoints (CVE-2026-24421 Incomplete Fix)

    phpMyFAQ is an open source FAQ web application. Versions prior to 4.1.4 have Missing Authorization in the API CategoryController. CVE-2026-24421 addressed this in the BackupController by adding: $this->userHasPermission(PermissionType::BACKUP). The same fix w…

  • Low 2.7

    phpMyFAQ has Weak Cryptography - SHA1 for Password Hashing

    phpMyFAQ is an open source FAQ web application. Prior to version 4.1.4, attachment passwords are hashed using SHA-1, a cryptographically broken algorithm. SHA-1 has been vulnerable to collision attacks since 2017 (SHAttered). Version 4.1.4 fixes the issue.

  • High 8.2

    phpMyFAQ - Unauthenticated Password Reset via User Password Update Endpoint

    phpMyFAQ before 4.1.3 contains an unauthenticated password reset vulnerability in the user password update API endpoint that allows attackers to change account passwords without token validation. Attackers can enumerate valid username and email pairs and forc…

  • High 8.2

    phpMyFAQ - Authentication Bypass via Missing Password Reset Token in /api/user/password/update

    phpMyFAQ before 4.1.3 contains an authentication bypass vulnerability in the password reset endpoint that allows unauthenticated attackers to reset any user account password without token verification or email confirmation. Attackers can enumerate valid usern…

  • High 7.5

    phpMyFAQ - Authentication Bypass via Empty API Token

    phpMyFAQ before 4.1.3 contains an authentication bypass vulnerability in API v4.0 where the default empty api.apiClientToken allows unauthenticated users to create and modify FAQ entries. Attackers can send an empty x-pmf-token header to bypass token validati…

  • High 8.8

    phpMyFAQ - Insecure Direct Object Reference in User Password API

    phpMyFAQ before 4.1.3 contains an insecure direct object reference vulnerability in the admin API user password endpoint that allows authenticated administrators to change any user's password without authorization verification. An attacker with low-privilege …

  • High 7.6

    phpMyFAQ - Stored XSS via Utils::parseUrl() in Comment Rendering

    phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in Utils::parseUrl() that allows authenticated users to inject JavaScript via malformed URLs in comments. Attackers can craft URLs with unescaped quotes to inject event handlers, steal…

  • High 7.5

    phpMyFAQ - Unauthenticated Information Disclosure via getIdFromSolutionId Permission Bypass

    phpMyFAQ before 4.1.2 contains an information disclosure vulnerability in the getIdFromSolutionId() method that lacks permission filtering, allowing unauthenticated attackers to enumerate restricted FAQ entries and read their titles via the /solution_id_{id}.…

  • Medium 5.4

    phpMyFAQ - Missing Authorization in Tag Deletion Endpoint

    phpMyFAQ before 4.1.2 contains a missing authorization vulnerability in the DELETE /admin/api/content/tags/{tagId} endpoint that allows any authenticated user to delete tags. Any logged-in user, including regular frontend users, can delete arbitrary tags by s…

  • Medium 5.4

    phpMyFAQ - Stored XSS in FAQ Question/Answer via Encode-Decode Bypass

    phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in FAQ creation and update endpoints that bypass sanitization through encode-decode cycles. The vulnerability allows authenticated attackers with FAQ_ADD permission to inject malicious…

  • Critical 9.8

    phpMyFAQ - SQL Injection via User-Agent Header in BuiltinCaptcha

    phpMyFAQ before 4.1.2 contains an unauthenticated SQL injection vulnerability in BuiltinCaptcha::garbageCollector() and BuiltinCaptcha::saveCaptcha() methods that interpolate unsanitized User-Agent headers into DELETE and INSERT queries. Unauthenticated attac…

  • Medium 6.5

    phpMyFAQ - Authorization Bypass in Admin Pages via Non-Terminating Permission Check

    phpMyFAQ before 4.1.2 contains an authorization bypass vulnerability in AbstractAdministrationController::userHasPermission() that fails to terminate execution after sending a forbidden response. Attackers can access all permission-protected admin pages by re…

  • Medium 6.9

    phpMyFAQ - Stored Cross-Site Scripting via raw Filter in search.twig

    phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in search.twig where result.question and result.answerPreview are rendered with the raw filter, disabling autoescape protection. Attackers with FAQ editor privileges can inject HTML-en…

  • Medium 5.4

    phpMyFAQ - Stored XSS via Entity Decoding Depth Limit Bypass in SVG Sanitizer

    phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in SvgSanitizer::decodeAllEntities() that limits recursive entity decoding to 5 iterations, allowing attackers to bypass sanitization. Authenticated users with FAQ_EDIT permission can …

  • High 7.5

    phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token Fields

    phpMyFAQ before 4.1.2 contains a sql injection vulnerability in CurrentUser::setTokenData that allows authenticated attackers to execute arbitrary SQL by injecting malicious OAuth token claims. Attackers with Azure AD accounts containing SQL metacharacters in…

  • Critical 9.1

    phpMyFAQ - Unauthenticated Two-Factor Authentication Brute-Force via /admin/check Endpoint

    phpMyFAQ before 4.1.2 contains an improper restriction of excessive authentication attempts vulnerability in the /admin/check endpoint, which accepts arbitrary user-id parameters without session binding or rate limiting. Unauthenticated attackers can brute-fo…

  • Medium 4.3

    phpMyFAQ - Insufficient Authorization Check in Admin API Endpoints

    phpMyFAQ before 4.1.2 contains an insufficient authorization vulnerability in admin-api routes that allows authenticated ordinary users to access administrative endpoints by only checking login status instead of verifying backend privileges. Attackers with va…

  • Medium 6.5

    phpMyFAQ - Path Traversal in Client::deleteClientFolder via URL Parameter

    phpMyFAQ before 4.1.2 contains a path traversal vulnerability in Client::deleteClientFolder that allows admins with INSTANCE_DELETE permission to delete arbitrary directories. Attackers can submit traversal sequences like https://../../../<path> in the client…

  • Medium 4.3

    phpMyFAQ - Missing Permission Check on 12 Configuration API Endpoints Allows Information Disclosure

    phpMyFAQ before 4.1.2 contains missing permission checks in ConfigurationTabController.php where 12 endpoints use userIsAuthenticated() instead of userHasPermission(CONFIGURATION_EDIT). Any authenticated user can enumerate system configuration metadata includ…

  • Medium 6.1

    phpMyFAQ: Stored XSS via Regex Bypass in Filter::removeAttributes()

    phpMyFAQ is an open source FAQ web application. Prior to version 4.1.1, there is a stored XSS vulnerability via Regex Bypass in Filter::removeAttributes(). This issue has been patched in version 4.1.1.

  • High 8.7

    phpMyFAQ: Path Traversal - Arbitrary File Deletion in MediaBrowserController

    phpMyFAQ is an open source FAQ web application. Prior to version 4.1.1, the MediaBrowserController::index() method handles file deletion for the media browser. When the fileRemove action is triggered, the user-supplied name parameter is concatenated with the …

  • Medium 5.4

    phpMyFAQ: Stored XSS via Unsanitized Email Field in Admin FAQ Editor

    phpMyFAQ is an open source FAQ web application. Prior to version 4.1.1, an unauthenticated attacker can submit a guest FAQ with an email address that is syntactically valid per RFC 5321 (quoted local part) yet contains raw HTML — for example "<script>alert(1)…

  • Medium 5.3

    phpMyFAQ: Public API endpoints expose emails and invisible questions

    phpMyFAQ is an open source FAQ web application. In versions 4.0.16 and below, multiple public API endpoints improperly expose sensitive user information due to insufficient access controls. The OpenQuestionController::list() endpoint calls Question::getAll() …

  • Medium 6.5

    phpMyFAQ: Attachment download allowed without dlattachment right (broken access control)

    phpMyFAQ is an open source FAQ web application. Versions 4.0.16 and below allow an authenticated user without the dlattachment permission to download FAQ attachments due to a incomprehensive permissions check. The presence of a right key is improperly validat…

  • Medium 6.5
    CVE-2026-24421 Public exploit

    phpMyFAQ missing authorization exposes /api/setup/backup to any authenticated user

    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…

  • High 8.8

    phpMyFAQ 3.1.12 CSV Injection via User Profile Export

    phpMyFAQ 3.1.12 contains a CSV injection vulnerability that allows authenticated users to inject malicious formulas into their profile names. Attackers can modify their user profile name with a payload like 'calc|a!z|' to trigger code execution when an admini…

  • High 7.2

    phpMyFAQ has Authenticated SQL Injection in Configuration Update Functionality

    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 arbitrar…

  • Medium 5.2

    phpMyFAQ Vulnerable to Stored HTML Injection at FAQ

    phpMyFAQ is an open source FAQ web application. Starting no later than version 3.2.10 and prior to version 4.0.2, an attacker can inject malicious HTML content into the FAQ editor at `http[:]//localhost/admin/index[.]php?action=editentry`, resulting in a comp…

  • Low 3.8

    phpMyFAQ Path Traversal in Attachments

    phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. There is a Path Traversal vulnerability in Attachments that allows attackers with admin rights to upload malicious files to other locations of the web root.…

  • Medium 4.3

    phpMyFAQ Stored Cross-site Scripting at File Attachments

    phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. An attacker with admin privileges can upload an attachment containing JS code without extension and the application will render it as HTML which allows for …

  • Medium 4.7

    phpMyFAQ Stored HTML Injection at contentLink

    phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Due to insufficient validation on the `contentLink` parameter, it is possible for unauthenticated users to inject HTML code to the page which might affect o…

  • High 8.8

    phpMyFAQ SQL injections at insertentry & saveentry

    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. T…

  • Medium 4.3

    phpMyFAQ Stored XSS at FAQ News Content

    phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. By manipulating the news parameter in a POST request, an attacker can inject malicious JavaScript code. Upon browsing to the compromised news page, the XSS …