# CVE-2026-34728: phpMyFAQ: Path Traversal - Arbitrary File Deletion in MediaBrowserController

Source: https://junglewise.ai/threats/cve-2026-34728-phpmyfaq-path-traversal-arbitrary-file-deletion-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-02  
License: CC BY 4.0 with a link back

CVE-2026-34728 · Severity: high · CVSS 8.7 · Published 2026-04-02

phpMyFAQ is an open source FAQ web application. Prior to version 4.1.1, the MediaBrowserController::index() method handles file deletion for the media browser. When the fileRemove action is triggered, the user-supplied name parameter is concatenated with the base upload directory path without any path traversal validation. The FILTER_SANITIZE_SPECIAL_CHARS filter only encodes HTML special characters (&, ', ", <, >) and characters with ASCII value < 32, and does not prevent directory traversal sequences like ../. Additionally, the endpoint does not validate CSRF tokens, making it exploitable via CSRF attacks. This issue has been patched in version 4.1.1.

Technologies: [phpmyfaq/phpmyfaq (Packagist)](https://junglewise.ai/threats/technologies/phpmyfaq-phpmyfaq), [Phpmyfaq](https://junglewise.ai/threats/technologies/phpmyfaq-phpmyfaq-1). Vendors: [Packagist](https://junglewise.ai/threats/vendors/packagist), [Phpmyfaq](https://junglewise.ai/threats/vendors/phpmyfaq).

## Quick answers

**Is CVE-2026-34728 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-34728 being exploited in the wild.

**How severe is CVE-2026-34728?** High severity, with a CVSS score of 8.7, published 2 April 2026.

**Which products and versions are affected?** phpmyfaq/phpmyfaq (Packagist) ECOSYSTEM:introduced=0,fixed=4.1.1.

**Is there a fix for CVE-2026-34728?** Yes. phpmyfaq/phpmyfaq (Packagist): upgrade to 4.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-34728?** Check whether you run phpmyfaq/phpmyfaq (Packagist) or Phpmyfaq at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- phpmyfaq/phpmyfaq (Packagist): upgrade to 4.1.1 or later

  ```sh
  composer require phpmyfaq/phpmyfaq:^4.1.1
  ```


## Affected products

- phpmyfaq/phpmyfaq (Packagist) ECOSYSTEM:introduced=0,fixed=4.1.1
- Phpmyfaq

## Identifiers

- CVE-2026-34728
- GHSA-38m8-xrfj-v38x

## Related threats

- [phpMyFAQ insecure direct object reference in admin user API](https://junglewise.ai/threats/cve-2026-111905-phpmyfaq-3-2-0-before-4-1-9-and-4-2-0-alpha-before-4-2-0-beta)
- [phpMyFAQ uncontrolled resource consumption in API pagination](https://junglewise.ai/threats/cve-2026-111901-phpmyfaq-4-2-0-alpha-before-4-2-0-beta-contains-an-uncontrolled)
- [phpMyFAQ improper authorization in attachment.php](https://junglewise.ai/threats/cve-2026-111900-phpmyfaq-before-4-1-9-and-4-2-0-alpha-before-4-2-0-beta-contains)
- [phpMyFAQ authentication bypass in Microsoft Entra ID login](https://junglewise.ai/threats/cve-2026-111895-phpmyfaq-3-2-0-before-4-0-0-and-4-0-2-before-4-2-0-beta-contains)
- [phpMyFAQ SQL injection in StopWords::add()](https://junglewise.ai/threats/cve-2026-56738-phpmyfaq-sql-injection-in-stopwords-add)