CVE-2026-108109

waiting for further signalsZero needs more public information before it can validate it.

GHSA-337r-rrrc-r559 ↗EUVD-2026-95810 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
hotspotbilling phpnuxbill <= 2025.3.20
CWE-307 Improper Restriction of Excessive Authentication Attempts
ETK-2026-1077Zero's internal tracking ID, independent of the CVE number., permanent identifier
11d 12h 04msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h09m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

PHPNuxBill through 2025.3.20 has insufficient attempt controls in its customer password-reset flow. An unauthenticated attacker who knows a customer username may repeatedly guess reset codes and take over that customer's account.

mitigation

Add rate limiting and account or reset-flow lockout controls to the password-reset endpoint, and restrict public access to it where feasible. Apply a vendor-provided update when one is released; no fixed version is recorded.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.39%31st percentile
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 14:33Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-09 14:33Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-108109

{
  "etk_id": "ETK-2026-1077",
  "cve_id": "CVE-2026-108109",
  "display_id": "CVE-2026-108109",
  "ghsa_id": "GHSA-337r-rrrc-r559",
  "euvd_id": "EUVD-2026-95810",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Password-reset OTP brute forcing in PHPNuxBill",
  "summary": "PHPNuxBill through 2025.3.20 has insufficient attempt controls in its customer password-reset flow. An unauthenticated attacker who knows a customer username may repeatedly guess reset codes and take over that customer's account.",
  "mitigation": "Add rate limiting and account or reset-flow lockout controls to the password-reset endpoint, and restrict public access to it where feasible. Apply a vendor-provided update when one is released; no fixed version is recorded.",
  "vendor": "hotspotbilling",
  "product": "phpnuxbill",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2025.3.20"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "phpnuxbill",
      "purl": null
    }
  ],
  "cwes": [
    307
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0039,
  "epss_percentile": 0.3142,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.567840383333333,
  "t0_at": "2026-10-09T14:33:32.201000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T14:33:32.201000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T14:33:32.201000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108109"
    }
  }
}

published 2026-10-09 14:45Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.