CVE-2026-33041: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in WWBN AVideo
CVE-2026-33041 is a medium severity vulnerability in WWBN AVideo versions 25. 0 and below where an unauthenticated endpoint exposes the password hashing algorithm. The endpoint /objects/encryptPass. json. php allows attackers to submit arbitrary passwords and receive their hashed equivalents, revealing the exact hashing method used. This exposure enables attackers who have obtained password hashes from other means (e. g. , SQL injection, backup leaks) to perform rapid offline cracking by comparing hashes against those generated from this endpoint. The hashing algorithm is a weak chain (md5+whirlpool+sha1) without salting by default, further facilitating quick password recovery. The vulnerability does not require authentication or user interaction and affects confidentiality but not integrity or availability.
AI Analysis
Technical Summary
CVE-2026-33041 is a vulnerability in the open-source WWBN AVideo platform, specifically in versions 25.0 and earlier. The issue arises from the endpoint /objects/encryptPass.json.php, which is accessible without authentication and exposes the platform's password hashing algorithm. This endpoint allows any unauthenticated user to submit arbitrary plaintext passwords and receive their hashed outputs as used internally by the application. Because the hashing method is disclosed directly, attackers do not need to reverse-engineer or guess the algorithm. The hashing scheme itself is a weak combination of md5, whirlpool, and sha1 applied sequentially, and crucially, it does not use salting by default, making it vulnerable to precomputed hash attacks. If an attacker has obtained password hashes from the database—via SQL injection, backup file exposure, or other means—they can leverage this endpoint to generate hash equivalents of guessed passwords and compare them directly, dramatically speeding up offline password cracking. This effectively reduces the effort and time required to recover user passwords. The vulnerability impacts confidentiality by exposing sensitive password hashing details and facilitating credential compromise. The flaw does not require any privileges or user interaction, increasing its risk profile. The issue was addressed and fixed in version 26.0 of WWBN AVideo, where presumably the endpoint was removed or access restricted and/or the hashing algorithm improved. No known exploits have been reported in the wild as of the publication date.
Potential Impact
The primary impact of this vulnerability is on the confidentiality of user credentials. Attackers who gain access to password hashes through other vulnerabilities or data leaks can use the exposed hashing algorithm endpoint to perform rapid offline cracking, significantly increasing the likelihood of recovering plaintext passwords. Compromised credentials can lead to unauthorized account access, data breaches, and potential lateral movement within affected organizations. Since WWBN AVideo is a video platform, attackers could gain control over user accounts, potentially leading to unauthorized content access, content manipulation, or privacy violations. The vulnerability does not affect system integrity or availability directly but can facilitate further attacks that do. Organizations relying on affected versions face increased risk of credential compromise, especially if password hashes have been leaked or if other vulnerabilities exist. The ease of exploitation (no authentication or user interaction required) and the widespread use of weak hashing exacerbate the threat. This can undermine user trust and lead to regulatory or compliance issues if user data is exposed.
Mitigation Recommendations
The primary mitigation is to upgrade WWBN AVideo installations to version 26.0 or later, where this vulnerability is fixed. If immediate upgrade is not possible, organizations should restrict access to the /objects/encryptPass.json.php endpoint via network controls or web application firewalls to prevent unauthenticated access. Additionally, consider implementing stronger password hashing algorithms with salting, such as bcrypt, Argon2, or PBKDF2, to replace the weak md5+whirlpool+sha1 chain. Review and secure database backups and other sources of password hashes to prevent leakage. Conduct thorough audits for other vulnerabilities like SQL injection that could expose password hashes. Enforce strong password policies and consider multi-factor authentication to reduce the impact of compromised credentials. Monitor logs for unusual access patterns to the hashing endpoint or other suspicious activities. Finally, educate users about the importance of unique, strong passwords to mitigate risks from offline cracking.
Affected Countries
United States, Germany, France, United Kingdom, Canada, Australia, Netherlands, Japan, South Korea, India
CVE-2026-33041: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in WWBN AVideo
Description
CVE-2026-33041 is a medium severity vulnerability in WWBN AVideo versions 25. 0 and below where an unauthenticated endpoint exposes the password hashing algorithm. The endpoint /objects/encryptPass. json. php allows attackers to submit arbitrary passwords and receive their hashed equivalents, revealing the exact hashing method used. This exposure enables attackers who have obtained password hashes from other means (e. g. , SQL injection, backup leaks) to perform rapid offline cracking by comparing hashes against those generated from this endpoint. The hashing algorithm is a weak chain (md5+whirlpool+sha1) without salting by default, further facilitating quick password recovery. The vulnerability does not require authentication or user interaction and affects confidentiality but not integrity or availability.
AI-Powered Analysis
Technical Analysis
CVE-2026-33041 is a vulnerability in the open-source WWBN AVideo platform, specifically in versions 25.0 and earlier. The issue arises from the endpoint /objects/encryptPass.json.php, which is accessible without authentication and exposes the platform's password hashing algorithm. This endpoint allows any unauthenticated user to submit arbitrary plaintext passwords and receive their hashed outputs as used internally by the application. Because the hashing method is disclosed directly, attackers do not need to reverse-engineer or guess the algorithm. The hashing scheme itself is a weak combination of md5, whirlpool, and sha1 applied sequentially, and crucially, it does not use salting by default, making it vulnerable to precomputed hash attacks. If an attacker has obtained password hashes from the database—via SQL injection, backup file exposure, or other means—they can leverage this endpoint to generate hash equivalents of guessed passwords and compare them directly, dramatically speeding up offline password cracking. This effectively reduces the effort and time required to recover user passwords. The vulnerability impacts confidentiality by exposing sensitive password hashing details and facilitating credential compromise. The flaw does not require any privileges or user interaction, increasing its risk profile. The issue was addressed and fixed in version 26.0 of WWBN AVideo, where presumably the endpoint was removed or access restricted and/or the hashing algorithm improved. No known exploits have been reported in the wild as of the publication date.
Potential Impact
The primary impact of this vulnerability is on the confidentiality of user credentials. Attackers who gain access to password hashes through other vulnerabilities or data leaks can use the exposed hashing algorithm endpoint to perform rapid offline cracking, significantly increasing the likelihood of recovering plaintext passwords. Compromised credentials can lead to unauthorized account access, data breaches, and potential lateral movement within affected organizations. Since WWBN AVideo is a video platform, attackers could gain control over user accounts, potentially leading to unauthorized content access, content manipulation, or privacy violations. The vulnerability does not affect system integrity or availability directly but can facilitate further attacks that do. Organizations relying on affected versions face increased risk of credential compromise, especially if password hashes have been leaked or if other vulnerabilities exist. The ease of exploitation (no authentication or user interaction required) and the widespread use of weak hashing exacerbate the threat. This can undermine user trust and lead to regulatory or compliance issues if user data is exposed.
Mitigation Recommendations
The primary mitigation is to upgrade WWBN AVideo installations to version 26.0 or later, where this vulnerability is fixed. If immediate upgrade is not possible, organizations should restrict access to the /objects/encryptPass.json.php endpoint via network controls or web application firewalls to prevent unauthenticated access. Additionally, consider implementing stronger password hashing algorithms with salting, such as bcrypt, Argon2, or PBKDF2, to replace the weak md5+whirlpool+sha1 chain. Review and secure database backups and other sources of password hashes to prevent leakage. Conduct thorough audits for other vulnerabilities like SQL injection that could expose password hashes. Enforce strong password policies and consider multi-factor authentication to reduce the impact of compromised credentials. Monitor logs for unusual access patterns to the hashing endpoint or other suspicious activities. Finally, educate users about the importance of unique, strong passwords to mitigate risks from offline cracking.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-17T18:10:50.210Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69bce490e32a4fbe5f3388a1
Added to database: 3/20/2026, 6:09:20 AM
Last enriched: 3/20/2026, 6:24:57 AM
Last updated: 3/20/2026, 7:30:28 AM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.