PHPNuxBill Authentication Bypass: Critical Flaw Enables Unauthenticated Account Hijacking in Versions Through 2025.3.20
A critical vulnerability in PHPNuxBill allows attackers to bypass password reset protections and hijack customer accounts without authentication.

Key points
- CVE-2026-108109 carries a CVSS score of 9.3, rated as critical severity.
- The flaw affects PHPNuxBill versions through 2025.3.20, including HotspotBilling.
- Attackers can brute-force the six-digit OTP code without account lockout.
A critical security flaw in the PHPNuxBill billing platform allows unauthenticated attackers to take over customer accounts by exploiting weaknesses in the password reset mechanism. The vulnerability, tracked as CVE-2026-108109, has been assigned a CVSS score of 9.3, indicating severe risk according to the National Vulnerability Database. This issue impacts all versions of PHPNuxBill up to and including 2025.3.20.
The risk
The vulnerability resides in the system/controllers/forgot.php file, which handles customer password reset requests. According to the NVD record, an attacker who knows a valid customer username can attempt to guess the six-digit one-time password (OTP) code. The application does not enforce attempt limits or account lockouts during this process.
This lack of rate limiting enables unlimited brute-force attacks against the OTP code. Once the correct code is guessed, the attacker can view the newly set password directly in the HTTP response. This allows the attacker to immediately hijack the associated account. The weakness is classified under CWE-307, which relates to incorrect default permissions or improper implementation of security controls.
Who is exposed
Organizations using PHPNuxBill for billing or hotspot management are exposed to this threat. The NVD record explicitly lists HotspotBilling and PHPNuxBill versions up to 2025.3.20 as affected products. Small businesses and service providers that rely on this platform for customer management face direct risk. Any customer account with a known username is a potential target for takeover. Attackers do not need prior credentials to initiate the attack, only the username. This lowers the barrier for entry for malicious actors targeting billing systems.
Cost and compliance
The National Vulnerability Database rates this issue as critical with a CVSS score of 9.3. No financial impact data is provided in the source material. Compliance implications are not detailed in the NVD record. Organizations must assess the risk based on the critical severity rating and the ease of exploitation. The absence of attempt limits violates common security best practices for authentication flows. This may affect adherence to security standards that require protection against brute-force attacks.
What to watch
Monitor the official PHPNuxBill channels for a patched version that addresses CVE-2026-108109. Review logs for unusual password reset activity, particularly multiple failures from single IP addresses. Verify that your current installation is not version 2025.3.20 or earlier. Check for any unofficial patches or workarounds that may introduce instability. Ensure that customer usernames are not publicly exposed where possible to reduce the attack surface.
Background: Authentication bypass vulnerabilities
Authentication bypass vulnerabilities arise from logic flaws, improper session handling, and misconfigured permissions. These mistakes let attackers access data without valid credentials. Fixing them requires strict input validation, secure session management, and regular vulnerability scanning to identify weak points before exploitation.
Read the full guide: Authentication Bypass Mistakes That Leave Systems Exposed
What to do and how to stay safe: PHPNuxBill
- Implement rate limiting on password reset endpoints to restrict the number of OTP attempts per username within a specific time window.
- Configure web application firewalls to block repeated requests to the forgot.php controller from single source IP addresses.
- Enable monitoring alerts for high volumes of password reset requests to detect brute-force activity in real time.
- Once the vendor provides an update, apply the patch immediately to resolve the underlying vulnerability in the code.
Step-by-step guide: Vulnerability Prioritization: Fix What Actually Matters First
General security guidance from the SecOps Signal newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-108109?
It is a critical account takeover vulnerability in PHPNuxBill that allows unauthenticated attackers to brute-force password reset codes.
Which versions of PHPNuxBill are affected?
All versions of PHPNuxBill through 2025.3.20 are affected, including HotspotBilling editions.
How do attackers exploit this flaw?
Attackers guess the six-digit OTP code without limit, then read the new password from the HTTP response to hijack the account.



