CVE-2026-34728: thorsten phpMyFAQ · Path Traversal
Affects thorsten phpMyFAQSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 4.1.1 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.1.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade phpMyFAQ and thorsten/phpMyFAQ to 4.1.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| thorstenphpMyFAQ | Affected
| Fixed in
|
GitHubthorsten/phpMyFAQpkg:github/thorsten/phpMyFAQOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade phpMyFAQ to version 4.1.1 or later, where this vulnerability has been patched. The patch includes proper validation of the file path to prevent directory traversal and adds CSRF token validation to the fileRemove action endpoint. Until upgrading, restrict access to the affected functionality to trusted users only and consider additional protective controls to prevent CSRF attacks. Patch status is confirmed as fixed in version 4.1.1.
Description
A path traversal vulnerability (CWE-22) exists in phpMyFAQ versions prior to 4.1.1 in the MediaBrowserController::index() method. The vulnerability arises because the user-supplied filename parameter is concatenated with the base upload directory path without proper validation, allowing directory traversal sequences like .. / to bypass restrictions. The input sanitization only encodes HTML special characters and does not prevent traversal sequences. Additionally, the endpoint lacks CSRF token validation, making it susceptible to CSRF attacks. This vulnerability has been patched in version 4.1.1.