CVE-2026-86187
Received Received - Intake

Weak Password Generation and Insecure Hashing in AVideo

Vulnerability report for CVE-2026-86187, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-05

Last updated on: 2026-09-05

Assigner: VulnCheck

Description

WWBN AVideo generates passwords for external-login accounts using rand() instead of a cryptographic generator, producing only 31-bit integers. Attackers with access to password hashes can recover plaintext passwords in minutes through offline brute-force attacks due to unsalted MD5-based hashing.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-05
Last Modified
2026-09-05
Generated
2026-09-05
AI Q&A
2026-09-05
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wwbn avideo to 29.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-330 The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-86187 affects WWBN AVideo versions up to 29.0 due to weak password generation for external-login accounts. The application uses the insecure rand() function, which produces only 31-bit integers, making passwords predictable. Attackers with access to password hashes can recover plaintext passwords quickly through offline brute-force attacks because passwords are stored using unsalted MD5 hashing.

Detection Guidance

To detect this vulnerability, check if your AVideo instance uses rand() for password generation in external-login flows. Inspect the codebase for rand() calls in login-related files. Look for unsalted MD5/SHA1/Whirlpool password hashes in the database. Verify if accounts created via social logins or plugins have predictable passwords.

Impact Analysis

This vulnerability allows attackers to recover plaintext passwords from exposed hashes in minutes, enabling unauthorized access to accounts created via external logins. If users reuse passwords elsewhere, attackers could gain access to other accounts linked to the same email. The issue is exacerbated by the lack of salt in password hashing, making it easier to crack passwords across all installations.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection standards like GDPR and HIPAA due to inadequate security measures for protecting user credentials. GDPR requires appropriate technical measures to ensure data security, while HIPAA mandates safeguards for protected health information. The use of weak password generation and unsalted hashing undermines these requirements.

Mitigation Strategies

Immediately replace rand() with a cryptographic generator like bin2hex(random_bytes(32)) in all password generation locations. Update the hashing mechanism to use salted hashes with a strong KDF (e.g., Argon2). Rotate all passwords generated via external logins. Monitor for unauthorized access attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-86187. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart