phpmyfaq/phpmyfaq
Composer (PHP) package
Overview
Package versions
| Versions | Range | Direct vulnerabilities |
|---|---|---|
| 4.2.0-alpha | and later versions | 0C0H0M0L |
| 4.1.6 | up to 4.2.0-alpha | 0C1H0M0L |
| 4.1.5 | up to 4.1.6 | 0C3H0M0L |
| 4.1.4 | up to 4.1.5 | 0C4H2M0L |
| 4.1.3 | up to 4.1.4 | 0C5H3M1L |
| 4.1.2 | up to 4.1.3 | 0C9H3M1L |
| 4.1.1 | up to 4.1.2 | 2C15H8M1L |
| 4.1.0 | up to 4.1.1 | 2C15H9M1L |
| 4.0.17 | up to 4.1.0 | 2C15H8M1L |
| 4.0.14 | up to 4.0.17 | 2C16H10M1L |
| after 4.0.1 | up to 4.0.14 | 2C17H10M1L |
| 4.0.0-alpha | up to 4.0.1 (included) | 2C18H10M1L |
| 3.2.10 | up to 4.0.0-alpha | 2C18H9M1L |
| 3.2.6 | up to 3.2.10 | 2C17H9M1L |
| 3.2.5 | up to 3.2.6 | 2C20H13M2L |
| 3.2.0 | up to 3.2.5 | 2C17H12M1L |
| 3.2.0-alpha | up to 3.2.0 | 2C16H12M1L |
| after 3.1.12 | up to 3.2.0-alpha | 2C17H12M1L |
| 3.1.12 | and all earlier versions | 2C17H13M1L |
No known vulnerabilities in 4.2.0-alpha and later versions
Nothing in our data affects this version.
19 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.
Vulnerabilities · 47
| CVE | Severity | Published | Vulnerable | Fixed in |
|---|---|---|---|---|
| CVE-2026-56738phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion | HIGH | 24 Sep 2026 | <4.1.6 | 4.1.6 |
| CVE-2026-56737phpMyFAQ's two-factor authentication login bypasses the password factor | HIGH | 24 Sep 2026 | >=3.2.0, <4.1.6 | 4.1.6 |
| CVE-2026-56736phpMyFAQ has Stored XSS in Admin FAQ Editor via HTML Entity Bypass in Frontend FAQ Submission | HIGH | 24 Sep 2026 | <4.2.0-alpha | 4.2.0-alpha |
| GHSA-PG62-F8G4-4WQHphpMyFAQ privilege escalation: GroupController::updatePermissions lets a GROUP_EDIT admin grant rights they do not hold | HIGH | 25 Aug 2026 | <4.1.5 | 4.1.5 |
| GHSA-MF8R-WM2W-F8C5phpMyFAQ public FAQ APIs expose inactive FAQ content | MEDIUM | 25 Aug 2026 | >=4.1.0, <4.1.5 | 4.1.5 |
| GHSA-88G4-74F3-63X9phpMyFAQ has Potential Authenticated Path Traversal in PDF Export | MEDIUM | 25 Aug 2026 | >=4.0.0-alpha, <4.1.5 | 4.1.5 |
| GHSA-985R-Q3QP-299HphpMyFAQ has an incomplete fix for GHSA-xvp4-phqj-cjr3 — editUser() and updateUserRights() lack authorization guards | HIGH | 26 Jun 2026 | <4.1.4 | 4.1.4 |
| CVE-2026-49205phpMyFAQ: Missing userHasPermission() in 4 API write endpoints (CVE-2026-24421 Incomplete Fix) | MEDIUM | 18 Jun 2026 | <4.1.4 | 4.1.4 |
| CVE-2026-48488phpMyFAQ has Weak Cryptography - SHA1 for Password Hashing | LOW | 8 Jun 2026 | <4.1.4 | 4.1.4 |
| CVE-2026-35676phpMyFAQ: Unauthenticated Password Reset Endpoint Allows User Enumeration and Forced Password Change Without Token Validation | HIGH | 28 May 2026 | <4.1.3 | 4.1.3 |
| CVE-2026-35675phpMyFAQ: Missing Password Reset Token Allows Account Takeover via Username/Email Enumeration | HIGH | 28 May 2026 | <4.1.3 | 4.1.3 |
| CVE-2026-35672phpMyFAQ: Default Empty API Token Authentication Bypass | HIGH | 28 May 2026 | <4.1.3 | 4.1.3 |
| CVE-2026-35671phpMyFAQ: IDOR Account Takeover | HIGH | 28 May 2026 | <4.1.3 | 4.1.3 |
| CVE-2026-46367phpMyFAQ has stored XSS via Utils::parseUrl() in comment rendering | HIGH | 15 May 2026 | >=4.1.1, <4.1.2 | 4.1.2 |
| CVE-2026-46366phpMyFAQ has unauthenticated FAQ permission bypass via getFaqBySolutionId fallback query | HIGH | 15 May 2026 | <4.1.2 | 4.1.2 |
| CVE-2026-46364phpMyFAQ has unauthenticated SQL injection via User-Agent header in BuiltinCaptcha | CRITICAL | 15 May 2026 | <4.1.2 | 4.1.2 |
| CVE-2026-46363phpMyFAQ has Stored XSS in FAQ Question/Answer via Encode-Decode Bypass of removeAttributes() Sanitization | MEDIUM | 15 May 2026 | <4.1.2 | 4.1.2 |
| CVE-2026-46362phpMyFAQ has an Authorization Bypass in All Admin Pages Due to Non-Terminating Permission Check | HIGH | 15 May 2026 | <4.1.2 | 4.1.2 |
| CVE-2026-46361phpMyFAQ has stored XSS via | raw Filter in search.twig — html_entity_decode(strip_tags()) Bypass in Search Result Rendering | HIGH | 15 May 2026 | <4.1.2 | 4.1.2 |
| CVE-2026-46360phpMyFAQ has a SVG Sanitizer Entity Decoding Depth Limit Bypass Leading to Stored XSS | MEDIUM | 15 May 2026 | <4.1.2 | 4.1.2 |
| CVE-2026-46359phpMyFAQ has SQL Injection in CurrentUser::setTokenData through unescaped OAuth token fields | HIGH | 15 May 2026 | <4.1.2 | 4.1.2 |
| CVE-2026-45010phpMyFAQ enables unauthenticated 2FA brute-force attack via /admin/check acceptance of arbitrary user-id | CRITICAL | 15 May 2026 | <4.1.2 | 4.1.2 |
| CVE-2026-45009phpMyFAQ: Ordinary Authenticated User Can Access Admin-Only API Endpoints Due to Insufficient Authorization Check in phpMyFAQ | MEDIUM | 15 May 2026 | >=4.1.1, <4.1.2 | 4.1.2 |
| CVE-2026-45008phpMyFAQ: Path Traversal in Client::deleteClientFolder enables arbitrary directory deletion by non-super-admin admins | HIGH | 15 May 2026 | <4.1.2 | 4.1.2 |
| CVE-2026-45007phpMyFAQ's Missing CONFIGURATION_EDIT Permission Check on 12 Admin API Configuration Tab Endpoints Allows Information Disclosure by Any Authenticated User | MEDIUM | 15 May 2026 | <4.1.2 | 4.1.2 |
| GHSA-7CX3-2QX2-3G6WphpMyFAQ's Missing Authorization on Tag Deletion Allows Any Authenticated User to Delete Tags | MEDIUM | 6 May 2026 | <4.1.2 | 4.1.2 |
| CVE-2026-34729phpMyFAQ: Stored XSS via Regex Bypass in Filter::removeAttributes() | MEDIUM | 2 Apr 2026 | <4.1.1 | 4.1.1 |
| CVE-2026-34728phpMyFAQ: Path Traversal - Arbitrary File Deletion in MediaBrowserController | HIGH | 2 Apr 2026 | <4.1.1 | 4.1.1 |
| CVE-2026-32629phpMyFAQ is Vulnerable to Stored XSS via Unsanitized Email Field in Admin FAQ Editor | MEDIUM | 2 Apr 2026 | <4.1.1 | 4.1.1 |
| CVE-2026-24422phpMyFAQ: Public API endpoints expose emails and invisible questions | HIGH | 24 Jan 2026 | <4.0.17 | 4.0.17 |
| CVE-2026-24420phpMyFAQ: Attachment download allowed without dlattachment right (broken access control) | MEDIUM | 24 Jan 2026 | <4.0.17 | 4.0.17 |
| CVE-2026-24421phpMyFAQ: /api/setup/backup accessible to any authenticated user (authz missing) | MEDIUM | 24 Jan 2026 | <4.0.17 | 4.0.17 |
| CVE-2023-53929phpMyFAQ contains a CSV injection vulnerability | MEDIUM | 17 Dec 2025 | <=3.1.12 | No fix yet |
| CVE-2025-62519phpMyFAQ has Authenticated SQL Injection in Configuration Update Functionality | HIGH | 17 Nov 2025 | <4.0.14 | 4.0.14 |
| CVE-2024-56199phpMyFAQ Vulnerable to Stored HTML Injection at FAQ | HIGH | 2 Jan 2025 | >=3.2.10, <=4.0.1 | No fix yet |
| CVE-2024-29196phpMyFAQ Path Traversal in Attachments | LOW | 26 Mar 2024 | >=3.2.5, <3.2.6 | 3.2.6 |
| CVE-2024-29179phpMyFAQ Stored Cross-site Scripting at File Attachments | MEDIUM | 25 Mar 2024 | >=3.2.5, <3.2.6 | 3.2.6 |
| CVE-2024-28108phpMyFAQ Stored HTML Injection at contentLink | MEDIUM | 25 Mar 2024 | >=3.2.5, <3.2.6 | 3.2.6 |
| CVE-2024-28107phpMyFAQ SQL injections at insertentry & saveentry | HIGH | 25 Mar 2024 | >=3.2.5, <3.2.6 | 3.2.6 |
| CVE-2024-28106phpMyFAQ Stored Cross-site Scripting at FAQ News Content | MEDIUM | 25 Mar 2024 | >=3.2.5, <3.2.6 | 3.2.6 |
| CVE-2024-28105phpMyFAQ's File Upload Bypass at Category Image Leads to RCE | HIGH | 25 Mar 2024 | >=3.2.5, <3.2.6 | 3.2.6 |
| CVE-2024-27300phpMyFAQ stored Cross-site Scripting at user email | MEDIUM | 25 Mar 2024 | >=3.2.5, <3.2.6 | 3.2.6 |
| CVE-2024-27299phpMyFAQ SQL Injection at "Save News" | HIGH | 25 Mar 2024 | >=3.2.5, <3.2.6 | 3.2.6 |
| CVE-2024-24574phpMyFAQ vulnerable to stored XSS on attachments filename | MEDIUM | 5 Feb 2024 | <3.2.5 | 3.2.5 |
| CVE-2024-22208phpMyFAQ sharing FAQ functionality can easily be abused for phishing purposes | MEDIUM | 5 Feb 2024 | <3.2.5 | 3.2.5 |
| CVE-2024-22202phpMyFAQ User Removal Page Allows Spoofing Of User Details | MEDIUM | 5 Feb 2024 | <3.2.5 | 3.2.5 |
| CVE-2022-3608phpMyFAQ vulnerable to Cross-site Scripting | HIGH | 19 Oct 2022 | <3.2.0-alpha | 3.2.0-alpha |
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.