Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-108109 – Account Takeover via OTP Brute Force – PHPNuxBill through 2025.3.20

Be the first to know when new zero-days emerge:

Summary

CVE-2026-108109 is an account takeover vulnerability (CWE-307, Improper Restriction of Excessive Authentication Attempts) in the customer password reset flow of PHPNuxBill, an open-source PHP billing system for MikroTik hotspots. An unauthenticated remote attacker who knows a customer’s username can brute-force the 6-digit reset code and take over the account. The CVE record lists a CVSS v4.0 score of 9.3 (Critical).

Technical details

  • Root cause: The password reset flow in system/controllers/forgot.php accepts unlimited guesses of the 6-digit otp_code, with no rate limiting, throttling or lockout. The vendor advisory also notes that codes are generated with mt_rand(100000, 999999), which is not a cryptographically secure generator.
  • Trigger conditions: The attacker needs network access to the PHPNuxBill customer portal and a valid customer username. No authentication or user interaction is required.
  • Attack vector: The attacker triggers OTP generation for the victim and then submits guesses against the verification step. A wrong guess does not invalidate the code, which remains valid for 600 seconds. The advisory reports roughly 2.6 ms per request, with about 300 requests completing in around 4 seconds.
  • Impact: On a correct guess, the newly set password is returned in the HTTP response body to the unauthenticated requester. The attacker can then log in as the victim, with high impact on confidentiality and integrity of customer accounts.

Affected software

  • PHPNuxBill (hotspotbilling/phpnuxbill) through version 2025.3.20

Severity

  • CVSS v4.0: 9.3 (Critical) – CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 9.1 (Critical) – CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: The GitHub security advisory (GHSA-337r-rrrc-r559) listed no patched release at the time of research. A patch commit (c3c2a92d468af91136d747b75142ed72f10320cc) is referenced in the CVE record. Check the vendor repository for a release that includes it, and upgrade once one is available.
  • If no patch is available: The advisory recommends the following hardening:
    • Replace mt_rand() with random_int().
    • Invalidate the reset code after about 5 failed attempts.
    • Apply per-IP rate limiting to the verification endpoint.
    • Use constant-time comparison for code checks.
  • Network-level controls such as a WAF rate limit on the forgot-password endpoint, or restricting access to the customer portal, can reduce exposure. These are general measures, not vendor-documented ones.
  • Review customer accounts for unexpected password resets.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge