Quick answers
- Is CVE-2026-57961 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57961 being exploited in the wild.
- How severe is CVE-2026-57961?
- Low severity, with a CVSS score of 3.1, published 10 July 2026.
- Which products and versions are affected?
- phpmyfaq/phpmyfaq (Packagist) ECOSYSTEM:introduced=4.0.0-alpha,fixed=4.1.5; thorsten/phpmyfaq (Packagist) ECOSYSTEM:introduced=4.0.0-alpha,fixed=4.1.5.
- Is there a fix for CVE-2026-57961?
- Yes. phpmyfaq/phpmyfaq (Packagist): upgrade to 4.1.5 or later; thorsten/phpmyfaq (Packagist): upgrade to 4.1.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57961 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-57961?
- Check whether you run phpmyfaq/phpmyfaq (Packagist) or thorsten/phpmyfaq (Packagist) 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.5 or later
composer require phpmyfaq/phpmyfaq:^4.1.5 - thorsten/phpmyfaq (Packagist): upgrade to 4.1.5 or later
composer require thorsten/phpmyfaq:^4.1.5
Technical details
A path traversal vulnerability exists in the `concatenatePaths()` function within `src/phpMyFAQ/Export/Pdf/Wrapper.php`. The application uses `strpos()` to find the substring 'content' in a user-provided path; if the substring is missing, `strpos()` returns false, which is cast to integer 0, causing the application to process the entire attacker-controlled path (e.g., using '../' sequences). This path is subsequently passed to `file_get_contents()` without canonicalization or root-directory validation. An attacker with FAQ editing privileges can exploit this by embedding crafted image tags in FAQ content, potentially leading to local file disclosure during PDF generation. The issue is fixed in version 4.1.5.
Affected products
- phpMyFAQ phpMyFAQ < 4.1.5
Identifiers
- CVE-2026-57961
- GHSA-88g4-74f3-63x9
Timeline
- 2026-06-14: advisory: Vendor advisory published on GitHub
- 2026-07-10: disclosed: NVD publication date