phpMyFAQ versions before 4.1.12 and between 4.2.0-alpha and before 4.2.0-RC.2 have an information disclosure vulnerability. Authenticated low-privilege users can exploit this flaw via the bookmark_action parameter to read unpublished FAQ titles, including draft and pending submission questions. This occurs by requesting FAQ detail pages with bookmark_action=add across sequential IDs and then viewing the /user/bookmarks page. The issue is fixed in versions 4.1.12 and 4.2.0-RC.2.
phpMyFAQ versions before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contain a stored cross-site scripting (XSS) vulnerability. Registered users can inject javascript: links via FAQ comments. A flaw in the comment editor's URL parsing causes https:// to be stripped from sanitized hrefs, enabling execution of injected scripts when clicked on the shared admin origin. This vulnerability has a medium severity score of 5.1 CVSS v4.0. Fixed versions are 4.1.12 and 4.2.0-RC.2.
phpMyFAQ versions before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have an authorization bypass vulnerability in multisite deployments. This flaw allows editors to delete attachment files belonging to other instances due to improper reference counting. The issue arises because linkedRecords() only counts local attachments, so deleting a shared attachment by its md5 hash causes File::delete() to remove the shared file, affecting other instances.
phpMyFAQ versions 3.2.5 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contain an authorization bypass vulnerability in the user/request-removal API endpoint. Authenticated users can submit account removal requests on behalf of other users by exploiting improper ownership checks. This can cause administrators to receive spoofed removal requests, potentially leading to unintended deletion of victim accounts and their data.
phpMyFAQ versions from 4.2.0-alpha up to but not including 4.2.0-RC.2 have an information disclosure vulnerability. Authenticated frontend users can receive restricted FAQ titles by subscribing to Web Push notifications. This occurs because the WebPushService::sendToAll() function sends restricted FAQ data to all subscribers, bypassing access controls.
phpMyFAQ versions before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have a vulnerability in the password recovery mechanism that allows authentication bypass. Attackers with access to the mailbox of external-identity accounts (such as OIDC, Keycloak, Entra ID, LDAP, SSO, or WebAuthn) can request password reset tokens and log in locally without going through identity provider multi-factor authentication or deprovisioning controls. This issue has been fixed in versions 4.1.12 and 4.2.0-RC.2.
phpMyFAQ versions 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have a missing authorization vulnerability. This flaw allows unauthenticated users to access metadata of restricted and inactive categories, including names, descriptions, images, and FAQ counts. Attackers can enumerate category IDs via specific URL patterns or API queries.
phpMyFAQ versions from 4.2.0-alpha.2 up to but not including 4.2.0-RC.2 contain an authorization vulnerability. This flaw allows editors restricted by category or language to bypass their scoped rights using public REST write endpoints if they have the shared API token. Exploitation enables rewriting published FAQs and creating root categories outside their authorized scope. The issue is fixed in version 4.2.0-RC.2.
phpMyFAQ versions before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contain an authorization vulnerability. This flaw allows delegated group or user administrators to remove rights they do not possess by submitting empty rights lists. Specifically, attackers can send empty rightIds or userRights arrays to certain endpoints to wipe all rights of more privileged groups or administrators. The vulnerability has a medium severity score of 5.1 and was fixed in versions 4.1.12 and 4.2.0-RC.2.
phpMyFAQ versions from 4.2.0-alpha up to but not including 4.2.0-RC.2 contain an authorization bypass vulnerability in the multisite Redis configuration store. This flaw allows tenant administrators to read and overwrite the master instance's configuration, including sensitive settings such as SMTP configuration, API tokens, and authentication parameters. The vulnerability arises because the Redis configuration store is not properly scoped per tenant, enabling unauthorized access to the master configuration.
phpMyFAQ versions before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 have an information disclosure vulnerability. Unauthenticated attackers can access editor-only Private Notes by querying the public FAQ list API endpoints. This allows retrieval of internal remarks and ticket details from FAQs that are otherwise anonymously readable.
phpMyFAQ versions before 4.1.12 and 4.2.0-alpha prior to 4.2.0-RC.2 have an information disclosure vulnerability in the public FAQ REST API. This flaw allows unauthenticated attackers to access author names and email addresses via the faq and paginated faqs endpoints. The vulnerability can be exploited to bulk-harvest emails and de-anonymize users who opted out of GDPR author visibility.
phpMyFAQ versions 4.1.0 up to but not including 4.1.12, and 4.2.0-alpha up to but not including 4.2.0-RC.2, contain an authentication bypass vulnerability in the POST /api/webauthn/prepare endpoint. This flaw allows anonymous attackers to create accounts that are automatically active, bypassing manual activation and domain whitelisting. Attackers can obtain a CSRF token without authentication and register accounts with unverified emails, gaining access to content and functions restricted to registered users.
phpMyFAQ versions from 4.2.0-alpha.2 up to but not including 4.2.0-RC.2 contain an authorization vulnerability in the admin API endpoint for importing FAQs. Authenticated users with FAQ_ADD rights can bypass the FAQ_PUBLISH permission, allowing them to publish unreviewed FAQs, including potentially malicious content such as phishing entries. This issue is fixed in version 4.2.0-RC.2.
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 category- or language-restricted editors to modify visibility ACLs and tags of any FAQ by sending crafted update requests with specific faqId and untranslated language parameters. The vulnerability enables exposure of restricted FAQs, removal of tags, or overwriting of orphaned FAQs. The issue was fixed in version 4.2.0-RC.2.
phpMyFAQ versions from 4.2.0-alpha.2 up to but not including 4.2.0-RC.2 have an improper authorization vulnerability in the updateUserRights function. This flaw allows USER_EDIT administrators to escalate privileges by removing category restrictions on group rights, effectively converting restricted rights into global direct rights. Exploiting this, attackers can edit, publish, or delete FAQs in categories that should be withheld from them. The vulnerability is fixed in version 4.2.0-RC.2.
phpMyFAQ versions 4.1.9 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contain an account enumeration vulnerability. This flaw allows unauthenticated attackers to identify valid usernames by observing differences in responses from the /api/webauthn/prepare endpoint. Attackers can reuse a single CSRF token without rate limiting to submit large username lists, facilitating discovery of administrator accounts for further attacks such as password spraying and phishing.
phpMyFAQ versions from 4.2.0-alpha.2 up to but not including 4.2.0-RC.2 contain an authorization vulnerability. This flaw allows authenticated editors with scoped editing rights to view draft FAQs outside their assigned categories or languages. The issue arises because the dashboard and admin search functions do not enforce category or language restrictions properly, enabling leakage of unpublished FAQ titles, IDs, and content snippets. The vulnerability is fixed in version 4.2.0-RC.2.
phpMyFAQ versions from 4.2.0-alpha up to but not including 4.2.0-RC.2 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows users with FAQ_EDIT privileges to bypass the SvgSanitizer by using namespace-prefixed SVG elements such as <x:script>. Malicious SVG files can be uploaded via the admin image upload feature, enabling script execution within the site origin on IIS servers. This can lead to session hijacking of privileged users like super-admins. The vulnerability is fixed in version 4.2.0-RC.2.
phpMyFAQ versions through 4.1.12 and from 4.2.0-alpha up to but not including 4.2.0-RC.2 have an authorization bypass vulnerability in the admin FAQ copy and translate pages. This flaw allows authenticated users with add-only or category-scoped editor rights to access restricted FAQ content, including drafts, ACL-restricted records, private notes, and author email addresses. The issue is fixed starting from version 4.2.0-RC.2.