CVE-2026-48488: phpMyFAQ has Weak Cryptography - SHA1 for Password Hashing

Published Jun 8, 2026
·
Updated

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:

public function setPassword(string $password): void { $this->passwordHash = passwordhash($password, PASSWORDBCRYPT); }

public function verifyPassword(string $plainPassword): bool { return passwordverify($plainPassword, $this->passwordHash); }

Other sources

phpMyFAQ is an open source FAQ web application. Prior to version 4.1.4, attachment passwords are hashed using SHA-1, a cryptographically broken algorithm. SHA-1 has been vulnerable to collision attacks since 2017 (SHAttered). Version 4.1.4 fixes the issue.

MITRE

Affected Software

3 affected componentsFixes available
PhpMyFaq phpmyfaq<4.1.4
composer/phpmyfaq/phpmyfaq<=4.1.3
4.1.4
composer/thorsten/phpmyfaq<=4.1.3
4.1.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/phpmyfaq/phpmyfaq to a version that resolves this vulnerability.

    Fixed in 4.1.4
  2. Upgrade

    Upgrade composer/thorsten/phpmyfaq to a version that resolves this vulnerability.

    Fixed in 4.1.4
  3. Upgrade

    Upgrade phpMyFAQ to a version that resolves this vulnerability.

    Fixed in 4.1.4

Event History

Jun 8, 2026
CVE Published
via MITRE·03:15 PM
Data Sourced
via MITRE·03:15 PM
DescriptionWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness
Jun 23, 2026
Advisory Published
via GitHub·10:02 PM
Data Sourced
via GitHub·10:02 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-48488?

CVE-2026-48488 has a severity rating of low, with a CVSS score of 4.0.

2

How do I fix CVE-2026-48488?

To fix CVE-2026-48488, upgrade phpMyFAQ to version 4.1.4 or later to ensure secure password hashing.

3

What vulnerability is associated with CVE-2026-48488?

CVE-2026-48488 refers to weak cryptography as it involves using SHA-1 for password hashing, which is considered broken.

4

What are the risks of using SHA-1 as seen in CVE-2026-48488?

Using SHA-1, as noted in CVE-2026-48488, exposes passwords to potential collision attacks, compromising security.

5

Which versions of phpMyFAQ are affected by CVE-2026-48488?

Versions of phpMyFAQ prior to 4.1.4 are affected by CVE-2026-48488 due to the use of SHA-1 for password hashing.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203