phpMyFAQ versions 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have a vulnerability in the PasswordChangeController::update() function that improperly restricts excessive authentication attempts. This flaw allows an attacker with a hijacked admin session and a reusable CSRF token to repeatedly guess the old password (faqpassword_old), bypassing throttling controls and potentially taking over the account.
phpMyFAQ versions 4.1.9 through before 4.1.12 and 4.2.0-alpha through before 4.2.0-RC.2 contain an authorization bypass vulnerability in multisite deployments. This flaw allows attackers to overwrite passkeys of accounts on other tenants by exploiting a shared PHP session store. By initiating a WebAuthn prepare() login on one tenant and replaying the session on another tenant or the master site, attackers can replace user passkeys and gain administrative access.
phpMyFAQ versions 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have a missing authentication vulnerability. Attackers with a hijacked session can enroll new passkeys via the webauthn API endpoints, enabling persistent passwordless login that bypasses password changes and resets.
phpMyFAQ versions before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have an authentication bypass vulnerability in the web installer. This flaw allows unauthenticated attackers to reinstall the application using a database they control, enabling them to create an administrator account and take over the application.
phpMyFAQ versions from 4.2.0-alpha.2 up to but not including 4.2.0-RC.2 contain an authorization vulnerability in the DELETE /admin/api/faq/delete endpoint. This flaw allows FAQ_DELETE administrators scoped to a specific language to bypass their language restrictions. Attackers can delete shared ACLs, tags, votes, comments, and attachments of FAQ entries in other language translations by submitting a faqId with an in-scope faqLanguage that lacks a translation.
phpMyFAQ versions from 4.2.0-alpha.2 up to but not including 4.2.0-RC.2 contain an authorization bypass vulnerability. This flaw allows language-scoped editors to access translations beyond their authorized scope by exploiting a mismatch between the checked FAQ_EDIT permission and the UI language parameter. Attackers can read sensitive information such as drafts, private notes, author emails, and revision data by manipulating request parameters. The issue is fixed in version 4.2.0-RC.2.
phpMyFAQ versions before 4.1.12 and between 4.2.0-alpha.2 and before 4.2.0-RC.2 contain an authorization bypass vulnerability. Authenticated editors can manipulate search index documents by supplying arbitrary solutionId values to the /admin/api/faq/update endpoint. This allows category-restricted editors on Elasticsearch or OpenSearch deployments to remove published FAQs from search results, overwrite other FAQs' search documents, or create entries that remain searchable after unpublishing.
phpMyFAQ version 4.2.0-alpha contains an authenticated SQL LIKE wildcard injection vulnerability in its chat user search API. This flaw allows any logged-in user to inject SQL LIKE wildcards (%) and (_) into search queries, bypassing intended display-name filtering and enabling enumeration of active user IDs and display names. The vulnerability is due to improper escaping of SQL LIKE metacharacters. A patch is available to address this issue. The vulnerability has a medium severity with a CVSS score of 5.4.
phpMyFAQ versions prior to 4.1.2 contain an authorization bypass vulnerability in the TagController delete endpoint. The DELETE /admin/api/content/tags/{tagId} endpoint only verifies that the user is authenticated but does not check for the required FAQ_EDIT permission. This allows any authenticated user, including non-admin frontend users, to delete any tag by ID. The vulnerability leads to permanent deletion of tags and their associations, disrupting FAQ organization and navigation. A patch is available in version 4.1.2 that adds proper permission and CSRF token checks.
phpMyFAQ versions 4.0.13 and earlier contain an authenticated SQL injection vulnerability in the configuration update functionality. A privileged user with 'Configuration Edit' permissions can exploit this flaw by crafting malicious form parameter names, which are used unsafely in SQL queries. This allows arbitrary SQL command execution, potentially leading to full database compromise and possibly remote code execution depending on the database setup. The vulnerability is fixed in version 4.0.14.