Skip to content
Threat Feed

Tag

Phpmyfaq

10 briefs RSS
high advisory

phpMyFAQ Authentication Bypass Vulnerability (CVE-2026-35675)

phpMyFAQ before version 4.1.3 is vulnerable to an authentication bypass in the password reset endpoint, allowing unauthenticated attackers to reset any user account password without token verification or email confirmation, potentially leading to complete account takeover, including administrative access.

phpMyFAQ < 4.1.3 authentication bypass cve-2026-35675 phpMyFAQ
2r 1t 1c
high advisory

phpMyFAQ Authentication Bypass Allows Account Takeover

An authentication bypass vulnerability in phpMyFAQ allows an unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts, by sending a PUT request with a valid username and associated email address to /api/user/password/update, resulting in complete account takeover.

phpmyfaq < 4.1.3 authentication-bypass account-takeover phpmyfaq web-application
2r
high advisory

phpMyFAQ Stored XSS Vulnerability via Malformed URLs (CVE-2026-46367)

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, potentially leading to session hijacking and application takeover.

phpMyFAQ < 4.1.2 stored-xss xss phpmyfaq
2r 1c
medium advisory

phpMyFAQ Unauthenticated Information Disclosure via Solution ID Enumeration

phpMyFAQ before 4.1.2 contains an information disclosure vulnerability in the getIdFromSolutionId() method, allowing unauthenticated attackers to enumerate restricted FAQ entries and read their titles via predictable URL patterns.

phpMyFAQ information-disclosure enumeration
2r 1t 1c
high advisory

phpMyFAQ SQL Injection Vulnerability in CurrentUser::setTokenData (CVE-2026-46359)

phpMyFAQ before version 4.1.2 contains a SQL injection vulnerability in CurrentUser::setTokenData, allowing authenticated attackers with crafted Azure AD accounts to execute arbitrary SQL queries by injecting malicious OAuth token claims.

phpMyFAQ sql-injection vulnerability
2r 1t 1c
medium advisory

phpMyFAQ Unauthenticated TOTP Bypass via Brute-Force (CVE-2026-45010)

phpMyFAQ before 4.1.2 is vulnerable to improper restriction of excessive authentication attempts in the /admin/check endpoint, allowing unauthenticated attackers to brute-force any user's six-digit TOTP code and bypass two-factor authentication, potentially gaining full administrative access (CVE-2026-45010).

phpMyFAQ cve brute-force totp credential-access authentication-bypass
2r 1t 1c
high threat

phpMyFAQ SQL Injection via Unescaped OAuth Token

phpMyFAQ is vulnerable to SQL injection due to the `setTokenData` function failing to sanitize OAuth token fields from Azure AD JWT claims, potentially allowing attackers to execute arbitrary SQL commands via crafted Azure AD display names or custom claims.

phpMyFAQ <= 4.1.1 +1 sql-injection oauth phpmyfaq
2r 1t
medium advisory

phpMyFAQ Unauthenticated FAQ Permission Bypass via Solution ID Enumeration

phpMyFAQ version 4.1.1 and earlier is vulnerable to an unauthenticated FAQ permission bypass, allowing attackers to enumerate solution IDs and discover restricted FAQ titles due to missing permission filters in key functions.

phpmyfaq unauthenticated access information disclosure web server
2r 1t
critical advisory

phpMyFAQ Unauthenticated 2FA Brute-Force Vulnerability

phpMyFAQ is vulnerable to an unauthenticated 2FA brute-force attack via the `/admin/check` endpoint, allowing attackers to bypass two-factor authentication and gain administrative access.

phpMyFAQ 2FA Bypass Brute-Force Authentication
2r 1t 1i
high advisory

phpMyFAQ Stored XSS Vulnerability in Comment Rendering

A stored XSS vulnerability in phpMyFAQ version 4.1.1 allows an authenticated user to inject JavaScript code into comments, leading to session cookie theft and potential admin account takeover when other users view the affected FAQ or News page.

phpMyFAQ 4.1.1 xss phpmyfaq stored-xss
2r 2t 1i