CVE-2026-90498

7.3

lenve · vhr

The lenve vhr application contains a vulnerability where default credentials are set during installation, allowing unauthenticated attackers to gain administrative access.

Executive summary

The lenve vhr application is vulnerable to unauthorized administrative access due to the use of hardcoded default credentials in the database initialization script.

Vulnerability

The application utilizes default credentials (specifically for the admin user) defined in the vhr.sql initialization script, which requires no authentication to exploit via the /doLogin endpoint.

Business impact

Successful exploitation grants an attacker full administrative control over the application. This compromise can lead to unauthorized data access, modification of user records, and potential system-wide disruption. With a CVSS score of 7.3, this high-severity flaw presents a significant risk to the integrity and confidentiality of the platform.

Remediation

Immediate Action: Manually change the default passwords for all administrative and standard accounts immediately. Ensure that the database initialization scripts are modified to remove or randomize these default credentials before deployment.

Proactive Monitoring: Review authentication logs for repeated login attempts, especially those targeting the admin user account. Monitor for unauthorized access patterns originating from unknown or suspicious IP addresses.

Compensating Controls: Implement a Web Application Firewall (WAF) to block unauthorized access attempts to the /doLogin endpoint. Restrict network access to the login portal to authorized IP ranges only.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists as detailed in the security advisory by ArrestX.

Analyst recommendation

Organizations currently running lenve vhr 1.0-SNAPSHOT must take immediate action to rotate all default credentials. Because no vendor-supplied patch is currently available, it is imperative to enforce strong, unique passwords for all accounts and restrict administrative access to trusted network segments to mitigate the risk of unauthorized system takeover.

More lenve CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by huluwa888 (VulDB User), with VulDB CNA Team (coordinator), per the CVE Program record.