# CVE-2026-48488: phpMyFAQ weak cryptographic hash for attachment passwords

Source: https://junglewise.ai/threats/cve-2026-48488-phpmyfaq-weak-cryptographic-hash-for-attachment-passwords  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-08. Updated: 2026-06-23  
License: CC BY 4.0 with a link back

CVE-2026-48488 · Severity: medium · CVSS 4 · Published 2026-06-08

phpMyFAQ, an open-source FAQ software, uses an outdated and insecure method (SHA-1) to protect passwords for file attachments. This could allow an attacker to bypass password protection on sensitive documents or quickly crack passwords if they gain access to the system's database. Organizations using this software should update to ensure their shared files remain confidential.

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

## Quick answers

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

**How severe is CVE-2026-48488?** Medium severity, with a CVSS score of 4, published 8 June 2026.

**Which products and versions are affected?** phpmyfaq/phpmyfaq (Packagist) <= 4.1.3, ECOSYSTEM:introduced=0,fixed=4.1.4; thorsten/phpmyfaq (Packagist) <= 4.1.3, ECOSYSTEM:introduced=0,fixed=4.1.4; Thorsten phpMyFAQ <= 4.1.3.

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

**How is CVE-2026-48488 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-48488?** Check whether you run phpmyfaq/phpmyfaq (Packagist), thorsten/phpmyfaq (Packagist) or Thorsten 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.4 or later

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

- thorsten/phpmyfaq (Packagist): upgrade to 4.1.4 or later

  ```sh
  composer require thorsten/phpmyfaq:^4.1.4
  ```


## Technical details

phpMyFAQ versions up to and including 4.1.3 utilize SHA-1 for hashing attachment passwords in `src/phpMyFAQ/Attachment/AbstractAttachment.php`. SHA-1 is vulnerable to collision attacks and lacks the computational cost required to resist modern brute-force or rainbow table attacks. An attacker with network access could potentially bypass attachment protections via hash collisions or perform offline cracking in under a minute if the database is compromised. The vulnerability is addressed in version 4.1.4 by migrating to the bcrypt (PASSWORD_BCRYPT) hashing algorithm.

## Affected products

- thorsten phpMyFAQ <= 4.1.3

## Identifiers

- CVE-2026-48488
- GHSA-58fg-62fg-3fcj

## Timeline

- 2026-05-25: disclosed
- 2026-06-08: advisory: NVD publication date
- 2026-06-23: patched: GitHub Advisory reviewed and updated

## References

- [https://api.github.com/users/N0tFix3d](https://api.github.com/users/N0tFix3d)
- [https://github.com/N0tFix3d](https://github.com/N0tFix3d)
- [https://api.github.com/users/N0tFix3d/gists%7B/gist_id%7D](https://api.github.com/users/N0tFix3d/gists%7B/gist_id%7D)
- [https://api.github.com/users/N0tFix3d/repos](https://api.github.com/users/N0tFix3d/repos)
- [https://avatars.githubusercontent.com/u/36280029?v=4](https://avatars.githubusercontent.com/u/36280029?v=4)
- [https://api.github.com/users/N0tFix3d/events%7B/privacy%7D](https://api.github.com/users/N0tFix3d/events%7B/privacy%7D)

## Related threats

- [phpMyFAQ insufficient authorization in group deletion](https://junglewise.ai/threats/cve-2026-124433-phpmyfaq-before-4-1-11-contains-an-insufficient-authorization)
- [phpMyFAQ WebAuthn account enumeration in prepare-login](https://junglewise.ai/threats/cve-2026-124432-phpmyfaq-4-1-9-before-4-1-11-and-4-2-0-pre-releases-before-4-2-0)
- [phpMyFAQ authorization bypass in attachment downloads](https://junglewise.ai/threats/cve-2026-111910-phpmyfaq-before-4-1-9-and-4-2-0-alpha-before-4-2-0-beta-contains)
- [phpMyFAQ missing authorization in deleteUser API](https://junglewise.ai/threats/cve-2026-111909-phpmyfaq-before-4-1-9-contains-a-missing-authorization)
- [phpMyFAQ broken object-level authorization in FAQ update API](https://junglewise.ai/threats/cve-2026-111908-phpmyfaq-4-0-0-before-4-1-9-and-4-2-0-alpha-before-4-2-0-beta)
