CVE-2025-9974
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe unified WEBUI application of the ONT/Beacon device contains an input handling flaw that allows authenticated users to trigger unintended system-level command execution. Due to insufficient validation of user-supplied data, a low-privileged authenticated attacker may be able to execute arbitrary commands on the underlying ONT/Beacon operating system, potentially impacting the confidentiality, integrity, and availability of the device.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCommand injection vulnerability in the unified WEBUI of ONT/Beacon devices where insufficient input validation allows authenticated low-privilege users to execute arbitrary operating system commands through the web interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if device is ONT or Beacon modelCheck device model/number via web interface login page, device label, or SNMP/sysinfo query. Look for 'ONT' or 'Beacon' in the model identifier.Affected if Device model contains 'ONT' or 'Beacon' in the product name/number
-
Confirm WEBUI is accessibleAttempt to access the device web management interface via HTTP/HTTPS on common ports (80, 443, 8080). Check if the unified WEBUI login page loads.Affected if WEBUI is exposed and responds with authentication prompt
-
Verify user authentication statusCheck if low-privilege user accounts exist or can be created in the WEBUI user management section. Log in with a non-administrator account to confirm limited access.Affected if Authenticated low-privilege users can access the WEBUI interface
-
Check for vulnerable input parametersInspect WEBUI forms and parameters using browser developer tools or proxy. Look for parameters that may be passed to system commands (e.g., ping, traceroute, diagnostics, config inputs).Affected if WEBUI accepts user-supplied parameters in fields that could be used for command injection (ping host, diagnostic tools, config fields)
-
Compare firmware version to available updatesCheck current firmware version in WEBUI status/system info page or via SNMP OID. Note that no specific version ranges are listed for this CVE.Affected if Unable to determine fixed version or running outdated firmware without CVE-specific patch
A user is affected if they have an ONT or Beacon device with the unified WEBUI enabled and accessible to authenticated low-privilege users who can submit input to potentially vulnerable web parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input sanitization and validation on all user-supplied parameters in the WEBUI application, preferably using allowlist validation and avoiding any dynamic command construction. Consider applying vendor firmware updates when available.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9974 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9974 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data