1985 matches found
CVE-2026-75919 phpMyFAQ before 4.1.7 Authentication Bypass via Setup API
phpMyFAQ before 4.1.7 contains an authentication bypass vulnerability in SetupController that allows unauthenticated attackers to run database migrations and create configuration backups when maintenance mode is enabled. Attackers can call POST /api/setup/update-database and POST /api/setup/backu...
EUVD-2026-62444
phpMyFAQ before 4.1.7 contains an authentication bypass vulnerability in SetupController that allows unauthenticated attackers to run database migrations and create configuration backups when maintenance mode is enabled. Attackers can call POST /api/setup/update-database and POST /api/setup/backu...
CVE-2026-75919
phpMyFAQ before 4.1.7 has an authentication bypass in SetupController. Unauthenticated attackers can call POST /api/setup/update-database and POST /api/setup/backup while maintenance mode is enabled to run database migrations, disable maintenance mode, and extract database credentials from genera...
CVE-2026-75918 phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File
phpMyFAQ before 4.1.7 stores password reset tokens in a publicly accessible tracking file when user tracking is enabled. Unauthenticated attackers can read the tracking file at content/core/data/trackingDDMMYYYY to extract reset tokens and replay them against the password reset API to take over...
EUVD-2026-62443
phpMyFAQ before 4.1.7 stores password reset tokens in a publicly accessible tracking file when user tracking is enabled. Unauthenticated attackers can read the tracking file at content/core/data/trackingDDMMYYYY to extract reset tokens and replay them against the password reset API to take over...
CVE-2026-75918
phpMyFAQ versions before 4.1.7 write password-reset tokens to the world-readable file content/core/data/trackingDDMMYYYY when user tracking is enabled; unauthenticated attackers read it and replay tokens against the reset API for account takeover. CVSS 3.1 scores 8.8 HIGH. Remediation: upgrade to...
CVE-2026-75918 phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File
phpMyFAQ before 4.1.7 stores password reset tokens in a publicly accessible tracking file when user tracking is enabled. Unauthenticated attackers can read the tracking file at content/core/data/trackingDDMMYYYY to extract reset tokens and replay them against the password reset API to take over...
PT-2026-78387
Name of the Vulnerable Software and Affected Versions phpMyFAQ versions prior to 4.1.7 Description An issue exists in the glossary create and update endpoints where an escaped string is truncated before being embedded in a SQL literal. Authenticated users with permissions to add or edit the...
PT-2026-78393
Name of the Vulnerable Software and Affected Versions phpMyFAQ versions prior to 4.1.7 Description Insufficient enforcement of the CONFIGURATION EDIT permission on administrative API read endpoints allows any authenticated user to access sensitive administrative data. By utilizing a valid session...
PT-2026-78391
Name of the Vulnerable Software and Affected Versions phpMyFAQ versions prior to 4.1.6 Description Failure to validate the security.enableRegistration setting in API endpoints allows the creation of user accounts even when registration is disabled. This bypasses the restriction enforced on the HT...
PT-2026-78392
Name of the Vulnerable Software and Affected Versions phpMyFAQ versions prior to 4.1.7 Description Insufficient sanitization of HTML in FAQ answers occurs before generating PDFs via TCPDF. An attacker with permissions to create or edit FAQ content can embed an tag with a src attribute referencing...
PT-2026-78396
Name of the Vulnerable Software and Affected Versions phpMyFAQ versions prior to 4.1.7 Description The software fails to persist the WebAuthn login challenge generated by the prepareForLogin function because the WebAuthn controller does not save the mutated key objects back to the database. Durin...
PT-2026-78386
Name of the Vulnerable Software and Affected Versions phpMyFAQ versions prior to 4.1.6 Description The software writes content backup ZIP archives to the web-accessible document root at the endpoint 'content.zip', which exposes sensitive files such as database credentials. Unauthenticated attacke...
PT-2026-78397
Name of the Vulnerable Software and Affected Versions phpMyFAQ versions prior to 4.1.7 Description An issue exists where the software fails to apply visibility checks for parent FAQ records before returning associated child resources. Unauthenticated attackers can retrieve restricted comment text...
CVE-2026-47132
creationtimestamp| type| source ---|---|--- 2026-08-12 16:35:05+00:00| published-proof-of-concept| https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6pvm-2vjj-rx4w...
SQL Injection
Overview thorsten/phpmyfaq is a FAQ system for PHP and MySQL, PostgreSQL and other databases Affected versions of this package are vulnerable to SQL Injection via the searchUsers process. An attacker can retrieve sensitive user information, such as user IDs and display names, by submitting...
SQL Injection
Overview phpmyfaq/phpmyfaq is a FAQ system for PHP and MySQL, PostgreSQL and other databases Affected versions of this package are vulnerable to SQL Injection via the searchUsers process. An attacker can retrieve sensitive user information, such as user IDs and display names, by submitting...
phpMyFAQ: SQL LIKE Wildcard Injection in Chat User Search Allows Authenticated User Enumeration
Summary An authenticated SQL LIKE wildcard injection vulnerability in phpMyFAQ’s chat user search allows any logged-in user to bypass the intended display-name search filter and enumerate active users. The endpoint escapes SQL string syntax but does not escape % and , which remain active LIKE...
phpmyfaq -- multiple vulnerabilities
phpMyFAQ team reports: The WebAuthn login flow never persists the challenge it issues, so the replay guard never runs. An attacker who captures a valid assertion can replay it to authenticate as the victim. The brute-force throttle protecting the administration two-factor prompt is scoped to the...
CVE-2026-66397
phpMyFAQ before 4.1.6 fails to validate path traversal sequences in the existingimage field during category updates, allowing authenticated attackers to delete arbitrary files by exploiting insufficient sanitization in Image::delete. Attackers can delete the database.php configuration file to...