phpMyFAQ has Weak Cryptography - SHA1 for Password Hashing

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U · score source

EPSS

• CVE-2026-48488: 0.18% estimated exploitation activity in the next 30 days; percentile 7.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Attachment passwords are hashed using SHA-1, a cryptographically broken algorithm. SHA-1 has been vulnerable to collision attacks since 2017 (SHAttered). Details Affected File : phpmyfaq/src/phpMyFAQ/Attachment/AbstractAttachment.php <img width="810" height="427" alt="image" src="https://github.com/user-attachments/assets/6499a008-3ece-4291-8296-f1d3303ba35c" / Impact - An attacker can generate SHA-1 collisions to bypass attachment protection - Risk of password cracking if database is compromised - Estimated cracking time: < 1 minute for standard attachment Solution Use bcrypt:

Published by the source

23 Jun 2026, 22:02 UTC

Last modified by the source

23 Jun 2026, 22:02 UTC

Source last checked

26 Oct 2026, 14:49 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-58fg-62fg-3fcj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-48488

Advisory: phpMyFAQ has Weak Cryptography - SHA1 for Password Hashing
IDs: CVE-2026-48488, GHSA-58fg-62fg-3fcj
Record: https://patchnext.com/advisories/cve-2026-48488 (revision 1, source checked 26 Oct 2026, 14:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: phpmyfaq/phpmyfaq 4.1.4; thorsten/phpmyfaq 4.1.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist phpmyfaq/phpmyfaq: affected <= 4.1.3; fixed in 4.1.4
- Packagist thorsten/phpmyfaq: affected <= 4.1.3; fixed in 4.1.4

## Suggested inspection (read-only)
- Packagist phpmyfaq/phpmyfaq: check the installed version with your package manager.
- Packagist thorsten/phpmyfaq: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on phpmyfaq/phpmyfaq, thorsten/phpmyfaq.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-58fg-62fg-3fcj (GitHub-reviewed advisory GHSA-58fg-62fg-3fcj lists affected ranges: Packagist thorsten/phpmyfaq >=0 =0 <=4.1.3)

Commands are suggestions: review each one before running it.