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.

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

Q: 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.

Q: How is CVE-2026-48488 attacked?

It is attacked over the network, in a network appliance.

Q: 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.

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), thorsten/phpmyfaq (Packagist), Thorsten phpMyFAQ. Vendors: Packagist, 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
```
composer require phpmyfaq/phpmyfaq:^4.1.4
```
thorsten/phpmyfaq (Packagist): upgrade to 4.1.4 or later
```
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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.