dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-32833

HIGH · 8.8 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

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 · unedited
Cudy LT300 3.0 running firmware prior to version 2.5.12 contains an OS command injection vulnerability that allows authenticated attackers to execute arbitrary commands by injecting shell metacharacters into the cbid.system.ntp.current POST parameter in the system time configuration interface. Attackers can submit malicious payloads through the NTP settings endpoint to achieve remote code execution on the underlying system.

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 confidence

The Cudy LT300 3.0 router running firmware versions prior to 2.5.12 has an OS command injection vulnerability in the NTP settings endpoint. Authenticated attackers can inject arbitrary OS commands through the cbid.system.ntp.current POST parameter by embedding shell metacharacters, achieving remote code execution on the device.

MitigationUpdate the Cudy LT300 3.0 firmware to version 2.5.12 or later to patch the command injection vulnerability. Restrict administrative access to trusted users and networks until the update is applied.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Check the router label or log into the admin web interface to confirm the exact model is Cudy LT300 3.0
    Affected if Device is not a Cudy LT300 3.0 router
  2. Check the installed firmware version
    Log into the router admin interface and navigate to System or Status settings to view the firmware version, or check via CLI if SSH/telnet is enabled
    Affected if Firmware version is prior to 2.5.12 (e.g., 2.5.11, 2.5.10, etc.)
  3. Verify NTP settings feature is accessible
    In the router admin interface, navigate to System or Time settings to confirm the NTP configuration page exists and is accessible with admin credentials
    Affected if The NTP settings endpoint is present and reachable with valid admin login
  4. Confirm admin authentication is required
    Verify that accessing the NTP settings requires authentication (the CVE states authenticated attackers can exploit)
    Affected if Admin credentials are configured and allow access to NTP settings

A user is affected if they have a Cudy LT300 3.0 router running firmware version 2.5.11 or earlier with the NTP settings feature accessible via admin authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Cudy LT300 3.0 firmware to version 2.5.12 or later to patch the command injection vulnerability. Restrict administrative access to trusted users and networks until the update is applied.

Recommended fix Moderate confidence

Firmware version 2.5.12 or later for Cudy LT300 3.0

  1. 1. Log in to the Cudy LT300 3.0 router admin interface with administrator credentials
  2. 2. Navigate to System > Time Settings (or equivalent NTP configuration page)
  3. 3. Download the firmware version 2.5.12 or later from the official Cudy support website (www.cudy.com)
  4. 4. In the admin interface, go to System > Firmware Upgrade or similar section
  5. 5. Upload the downloaded firmware file and initiate the upgrade process
  6. 6. Wait for the upgrade to complete and the device to reboot
  7. 7. Verify the firmware version has been updated to 2.5.12 or later
  8. 8. Confirm the NTP settings functionality works correctly
Caveat Review Cudy release notes for version 2.5.12 to check for any configuration changes or feature modifications that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32833 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32833 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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