Quick answers
- Is CVE-2026-107829 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107829 being exploited in the wild.
- How severe is CVE-2026-107829?
- Medium severity, with a CVSS score of 5.9, published 8 October 2026.
- Which products and versions are affected?
- Jivejdon through 5.0.
- Is there a fix for CVE-2026-107829?
- No fixed version is recorded yet. Restrict database access controls to prevent unauthorized SQL injection or direct database exposure. Migrate to a version using cryptographically strong password hashing functions such as bcrypt or PBKDF2 with a salt.</anigation> </invoke> If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-107829 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-107829?
- Check whether you run Jivejdon 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
Restrict database access controls to prevent unauthorized SQL injection or direct database exposure. Migrate to a version using cryptographically strong password hashing functions such as bcrypt or PBKDF2 with a salt.</anigation> </invoke>
Technical details
Jivejdon stores passwords as unsalted MD5 digests via the ToolsUtil.hash() or DigestUtil.hash() method in the AccountDaoSql component. The vulnerability requires database access (via SQL injection or direct DB compromise) to retrieve password hashes, but once obtained, unsalted MD5 hashes are trivial to crack with modern hardware. A fix involving stronger hashing algorithms (bcrypt, scrypt, or PBKDF2 with salt) should replace the legacy DigestUtil implementation.
Affected products
- Jivejdon Jivejdon through 5.0
Timeline
- 2026-10-08: disclosed