Monthly
Weak password hashing in JuggleIM im-server and its imserver-console through 1.8.16 stores admin-console credentials as unsalted SHA-1 digests in the accounts table, allowing an attacker who first obtains the database or its backups to crack those passwords offline with precomputed rainbow tables or GPU brute force. The issue is conditional rather than directly network-reachable, because it requires prior read access to the database or backup files, and no public exploit identified at time of analysis. The independent assessment rates it a moderate, conditional risk with high attack complexity and confidentiality-only impact.
Unsalted MD5 password storage in Xxyopen novel through 3.5.0 allows offline recovery of user plaintext passwords from the user_info.password column, because UserServiceImpl.register() calls DigestUtils.md5DigestAsHex without any per-user salt or key stretching. The flaw is a confidentiality amplifier rather than a directly reachable bug: an attacker must first obtain the password column via a database leak, SQL injection, exposed backup, or insider access, after which precomputed rainbow tables and GPU brute force make short or common passwords recoverable in seconds to hours, enabling credential reuse against the application and elsewhere. No public exploit code was identified at time of analysis and there is no evidence of confirmed active exploitation (CISA KEV), though the root cause and the upstream BCrypt fix are both publicly documented; instances migrated to the patched code, and accounts that have re-logged-in to trigger the BCrypt upgrade, are no longer affected.
Jivejdon through 5.0 stores account passwords as unsalted MD5 digests - computed by ToolsUtil.hash() and persisted through AccountDaoSql - so an attacker who obtains the user table can recover plaintext credentials offline with precomputed tables or GPU-accelerated cracking. The flaw is not self-contained: it requires a prior database compromise or a separate SQL injection to reach the credential table, which is why the assessed vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N (vendor CVSS 4.0 rates it 8.2 with AC:H/AT:P), making this an impact amplifier rather than an initial-access vector. No public exploit code and no confirmed active exploitation of this password-storage weakness were identified at time of analysis, although the advisory carries an associated SQLi tag.
CareCam CM2507 IP cameras running firmware v251211.1507 store the root account password as a fixed, legacy hash that offers insufficient resistance to offline cracking, so anyone who obtains the firmware image or the on-device password database can potentially recover the root credential. The exposure is not a single-step remote compromise: the independent assessment rates it CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, because an attacker must first acquire the hash artifact (vendor firmware download, physical/debug filesystem access, or a chained bug) and then crack it offline, and the recovered credential is only useful if it remains valid and is genuinely shared across the firmware line - the advisory says cross-device reuse 'may' occur rather than confirming it. No public exploit code and no confirmed active exploitation have been identified at time of analysis, and the vendor's CVSS 4.0 score of 9.3 overstates real-world risk relative to the assessed vector.
Weak key derivation in openssl_encrypt before 1.4.9 exposes all files encrypted via the D-Bus CryptoService.EncryptFile handler to accelerated offline password guessing attacks that shatter the tool's documented confidentiality guarantees. The handler uses a single-pass SHA-256 hash for key derivation instead of a memory-hard algorithm such as Argon2id, enabling any attacker who obtains an encrypted file to crack the password six to seven orders of magnitude faster than the product implies. No public exploit code or active exploitation has been identified at time of analysis, though the weakness is structurally trivial to exploit with commodity GPU cracking tooling.
Weak pepper wrap key derivation in openssl_encrypt (versions before 1.4.9) allows fleet-wide offline password recovery against all users from a single precomputed dictionary table. The library derives its remote-pepper wrap key using unsalted HKDF-SHA256 or bare SHA-256 of the password, producing identical wrap keys across every user and every file - eliminating the per-user randomness that salting is designed to provide. Any attacker who obtains wrapped pepper blobs can precompute one lookup table and attack the entire user population at GPU-limited speed. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Unsalted MD5 password hashing in FrontAccounting through 2.4.20 renders every stored credential recoverable in minutes if the database is compromised. All authentication-related code paths - user creation, password updates, self-service password change, forgotten-password reset, and login verification - use raw md5() with no per-user salt, so identical passwords produce identical digests and the entire user table can be cracked en masse with rainbow tables or GPU-accelerated tools. No active exploitation (CISA KEV) has been identified, but the CVSS 4.0 score of 8.2 with VC:H reflects that a single database breach translates directly to full plaintext credential exposure across all accounts.
Credential disclosure in TP-Link Deco M5 v1 mesh routers stems from a weak (computationally cheap) password-hashing scheme used to store local user credentials, letting an attacker who has already obtained the stored hash recover the plaintext password via offline brute-force or dictionary attacks. Affected devices are the Deco M5 v1 hardware revision, and successful cracking yields access to device management functions scoped to the recovered account's privileges. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; the CVSS 4.0 vector (AV:L/AC:H/PR:H) reflects that it is a post-compromise credential-recovery weakness rather than a remote entry point.
Offline administrator password recovery in Kestra OSS (versions prior to 1.3.24) stems from its BasicAuth component storing the admin credential as a fast SHA-512 hash. An attacker who already holds read access to the backing PostgreSQL database can extract that hash and crack it offline at high speed, then log in as administrator; in Kubernetes deployments this further exposes the cluster ServiceAccount token and all K8s Secrets, enabling vertical privilege escalation. No public exploit identified at time of analysis and not on CISA KEV; EPSS data was not provided.
Weak password hashing in QloApps through 1.7.0 enables credential compromise because Tools::encrypt() in classes/Tools.php hashes passwords with unsalted MD5 concatenated with a static cookie key, allowing offline brute-force recovery of customer and employee credentials. The risk is amplified by an 8-character auto-generated password used during guest-to-customer conversion in classes/Customer.php, making cracked hashes practically trivial. No public exploit identified at time of analysis, but the upstream fix in commit 64e9722 replaces MD5 with the PasswordHashing class for credential storage.
Weak password hashing in JuggleIM im-server and its imserver-console through 1.8.16 stores admin-console credentials as unsalted SHA-1 digests in the accounts table, allowing an attacker who first obtains the database or its backups to crack those passwords offline with precomputed rainbow tables or GPU brute force. The issue is conditional rather than directly network-reachable, because it requires prior read access to the database or backup files, and no public exploit identified at time of analysis. The independent assessment rates it a moderate, conditional risk with high attack complexity and confidentiality-only impact.
Unsalted MD5 password storage in Xxyopen novel through 3.5.0 allows offline recovery of user plaintext passwords from the user_info.password column, because UserServiceImpl.register() calls DigestUtils.md5DigestAsHex without any per-user salt or key stretching. The flaw is a confidentiality amplifier rather than a directly reachable bug: an attacker must first obtain the password column via a database leak, SQL injection, exposed backup, or insider access, after which precomputed rainbow tables and GPU brute force make short or common passwords recoverable in seconds to hours, enabling credential reuse against the application and elsewhere. No public exploit code was identified at time of analysis and there is no evidence of confirmed active exploitation (CISA KEV), though the root cause and the upstream BCrypt fix are both publicly documented; instances migrated to the patched code, and accounts that have re-logged-in to trigger the BCrypt upgrade, are no longer affected.
Jivejdon through 5.0 stores account passwords as unsalted MD5 digests - computed by ToolsUtil.hash() and persisted through AccountDaoSql - so an attacker who obtains the user table can recover plaintext credentials offline with precomputed tables or GPU-accelerated cracking. The flaw is not self-contained: it requires a prior database compromise or a separate SQL injection to reach the credential table, which is why the assessed vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N (vendor CVSS 4.0 rates it 8.2 with AC:H/AT:P), making this an impact amplifier rather than an initial-access vector. No public exploit code and no confirmed active exploitation of this password-storage weakness were identified at time of analysis, although the advisory carries an associated SQLi tag.
CareCam CM2507 IP cameras running firmware v251211.1507 store the root account password as a fixed, legacy hash that offers insufficient resistance to offline cracking, so anyone who obtains the firmware image or the on-device password database can potentially recover the root credential. The exposure is not a single-step remote compromise: the independent assessment rates it CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, because an attacker must first acquire the hash artifact (vendor firmware download, physical/debug filesystem access, or a chained bug) and then crack it offline, and the recovered credential is only useful if it remains valid and is genuinely shared across the firmware line - the advisory says cross-device reuse 'may' occur rather than confirming it. No public exploit code and no confirmed active exploitation have been identified at time of analysis, and the vendor's CVSS 4.0 score of 9.3 overstates real-world risk relative to the assessed vector.
Weak key derivation in openssl_encrypt before 1.4.9 exposes all files encrypted via the D-Bus CryptoService.EncryptFile handler to accelerated offline password guessing attacks that shatter the tool's documented confidentiality guarantees. The handler uses a single-pass SHA-256 hash for key derivation instead of a memory-hard algorithm such as Argon2id, enabling any attacker who obtains an encrypted file to crack the password six to seven orders of magnitude faster than the product implies. No public exploit code or active exploitation has been identified at time of analysis, though the weakness is structurally trivial to exploit with commodity GPU cracking tooling.
Weak pepper wrap key derivation in openssl_encrypt (versions before 1.4.9) allows fleet-wide offline password recovery against all users from a single precomputed dictionary table. The library derives its remote-pepper wrap key using unsalted HKDF-SHA256 or bare SHA-256 of the password, producing identical wrap keys across every user and every file - eliminating the per-user randomness that salting is designed to provide. Any attacker who obtains wrapped pepper blobs can precompute one lookup table and attack the entire user population at GPU-limited speed. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Unsalted MD5 password hashing in FrontAccounting through 2.4.20 renders every stored credential recoverable in minutes if the database is compromised. All authentication-related code paths - user creation, password updates, self-service password change, forgotten-password reset, and login verification - use raw md5() with no per-user salt, so identical passwords produce identical digests and the entire user table can be cracked en masse with rainbow tables or GPU-accelerated tools. No active exploitation (CISA KEV) has been identified, but the CVSS 4.0 score of 8.2 with VC:H reflects that a single database breach translates directly to full plaintext credential exposure across all accounts.
Credential disclosure in TP-Link Deco M5 v1 mesh routers stems from a weak (computationally cheap) password-hashing scheme used to store local user credentials, letting an attacker who has already obtained the stored hash recover the plaintext password via offline brute-force or dictionary attacks. Affected devices are the Deco M5 v1 hardware revision, and successful cracking yields access to device management functions scoped to the recovered account's privileges. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; the CVSS 4.0 vector (AV:L/AC:H/PR:H) reflects that it is a post-compromise credential-recovery weakness rather than a remote entry point.
Offline administrator password recovery in Kestra OSS (versions prior to 1.3.24) stems from its BasicAuth component storing the admin credential as a fast SHA-512 hash. An attacker who already holds read access to the backing PostgreSQL database can extract that hash and crack it offline at high speed, then log in as administrator; in Kubernetes deployments this further exposes the cluster ServiceAccount token and all K8s Secrets, enabling vertical privilege escalation. No public exploit identified at time of analysis and not on CISA KEV; EPSS data was not provided.
Weak password hashing in QloApps through 1.7.0 enables credential compromise because Tools::encrypt() in classes/Tools.php hashes passwords with unsalted MD5 concatenated with a static cookie key, allowing offline brute-force recovery of customer and employee credentials. The risk is amplified by an 8-character auto-generated password used during guest-to-customer conversion in classes/Customer.php, making cracked hashes practically trivial. No public exploit identified at time of analysis, but the upstream fix in commit 64e9722 replaces MD5 with the PasswordHashing class for credential storage.