Skip to main content

CVE-2026-107829: Use of Password Hash With Insufficient Computational Effort in banq jivejdon

0
High
VulnerabilityCVE-2026-107829cvecve-2026-107829
Published: 10/08/2026 (10/08/2026, 21:51:33 UTC)
Source: CVE Database V5
Vendor/Project: banq
Product: jivejdon

Description

Jivejdon versions up to 5.0 use unsalted MD5 hashes for password storage, which is cryptographically weak. This allows attackers who gain database access or exploit SQL injection vulnerabilities to efficiently crack user passwords using precomputed tables or GPU-accelerated attacks.

CVSS v4.0

Score 8.2high

Attack Vector
Network
Attack Complexity
High
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Affected software

banq

jivejdon

Affected versions
>=0 <=5.0
GitHub Actionsmore threats →cve
jivejdon
pkg:github/jivejdon
Affected versions
>=0 <=5.0

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: 10/08/2026, 22:18:27 UTC

Technical Analysis

CVE-2026-107829 identifies a vulnerability in banq's Jivejdon product through version 5.0, where account passwords are stored as unsalted MD5 hashes via the ToolsUtil.hash() function in AccountDaoSql. The use of unsalted MD5 is considered weak due to its susceptibility to precomputed hash attacks and GPU-accelerated cracking. An attacker with access to the user table, either through direct database access or SQL injection, can exploit this weakness to recover plaintext passwords.

Potential Impact

Attackers who obtain the user table can efficiently crack stored passwords, potentially leading to unauthorized account access. This compromises user credentials and may facilitate further attacks or data breaches. The vulnerability does not require user interaction and can be exploited remotely if SQL injection is present.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider additional protective measures such as enforcing strong password policies, monitoring for SQL injection vulnerabilities, and restricting database access. Migration to a stronger password hashing algorithm with salting (e.g., bcrypt, Argon2) is recommended once a patch is provided.

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
VulnCheck
Date Reserved
2026-10-08T21:43:58.592Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ac8135e2cdf04f6563b0ce8

Added to database: 10/08/2026, 22:04:14 UTC

Last enriched: 10/08/2026, 22:18:27 UTC

Last updated: 10/08/2026, 22:19:11 UTC

Views: 6

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