Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.2%top 92%

CVE-2026-48488: CWE-328: Use of Weak Hash in thorsten phpMyFAQ

0
Low
VulnerabilityCVE-2026-48488cvecve-2026-48488cwe-328
Published: 06/08/2026 (06/08/2026, 15:15:12 UTC)
Source: CVE Database V5
Vendor/Project: thorsten
Product: phpMyFAQ

Description

phpMyFAQ versions prior to 4.1.4 use SHA-1, a cryptographically broken hash algorithm, for hashing attachment passwords. SHA-1 has been vulnerable to collision attacks since 2017. This weakness was addressed in version 4.1.4.

CVSS v4.0

Score 2.7low

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
Low
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

GitHub Actionsmore threats →ai
thorsten/phpMyFAQ
pkg:github/thorsten/phpMyFAQ
Affected versions
<4.1.4

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 06/16/2026, 08:38:08 UTC

Technical Analysis

The vulnerability CVE-2026-48488 in phpMyFAQ involves the use of the weak SHA-1 hashing algorithm for attachment passwords in versions before 4.1.4. SHA-1 is considered cryptographically broken due to its susceptibility to collision attacks, which have been publicly demonstrated since 2017. The issue is resolved in phpMyFAQ version 4.1.4, which replaces SHA-1 with a stronger hashing method.

Potential Impact

The use of SHA-1 for hashing attachment passwords weakens the cryptographic protection of these passwords, potentially allowing attackers to exploit collision vulnerabilities to compromise password integrity. However, the CVSS score of 2.7 and the low severity rating indicate that the overall risk is low, and no known exploits are reported in the wild.

Mitigation Recommendations

Upgrade phpMyFAQ to version 4.1.4 or later, where the weak SHA-1 hashing has been replaced with a stronger algorithm. No other mitigation is indicated or required.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-05-21T15:33:08.291Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 6a26e46de29bf47b501e5315

Added to database: 06/08/2026, 15:49:01 UTC

Last enriched: 06/16/2026, 08:38:08 UTC

Last updated: 07/31/2026, 19:22:59 UTC

Views: 86

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses