Skip to content

LibreNMS has Weak Password Policy

Low severity GitHub Reviewed Published Nov 18, 2025 in librenms/librenms • Updated Nov 19, 2025

Package

composer librenms/librenms (Composer)

Affected versions

< 25.11.0

Patched versions

25.11.0

Description

Summary

A Weak Password Policy vulnerability was identified in the user management functionality of the LibreNMS application. This vulnerability allows administrators to create accounts with extremely weak and predictable passwords, such as 12345678. This exposes the platform to brute-force and credential stuffing attacks.


Details

Vulnerable Component: User creation / password definition

The application fails to enforce a strong password policy when creating new users. As a result, administrators can define trivial and well-known weak passwords, compromising the authentication security of the system.


PoC

  1. Log in to the application using an Administrator account.

  2. Navigate to the user management section:

  3. Create a new user account using the password 12345678.

image

  1. The application accepts the weak password without restrictions and creates the account successfully.

image


Impact

Weak password policy vulnerabilities can have severe consequences, including:

  • Increased risk of brute-force and credential stuffing attacks

  • Unauthorized access to user or administrative accounts

  • Privilege escalation through compromised credentials

  • Degradation of the overall security posture of the platform


Mitigation

  • Enforce a strong password policy (e.g., minimum of 12 characters with uppercase, lowercase, digits, and special characters).

  • Block the use of commonly known weak passwords (e.g., 12345678, password, admin, qwerty).

References

@murrant murrant published to librenms/librenms Nov 18, 2025
Published to the GitHub Advisory Database Nov 18, 2025
Reviewed Nov 18, 2025
Published by the National Vulnerability Database Nov 18, 2025
Last updated Nov 19, 2025

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

Weaknesses

Weak Password Requirements

The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. Learn more on MITRE.

CVE ID

CVE-2025-65014

GHSA ID

GHSA-5mrf-j8v6-f45g

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.