CVE-2025-13658
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 · uneditedA vulnerability in Longwatch devices allows unauthenticated HTTP GET requests to execute arbitrary code via an exposed endpoint, due to the absence of code signing and execution controls. Exploitation results in SYSTEM-level privileges.
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 confidenceLongwatch devices contain an unauthenticated HTTP endpoint that accepts arbitrary code execution requests due to missing code signing and execution validation controls. An attacker can send a specially crafted HTTP GET request to achieve code execution with SYSTEM-level privileges.
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
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Longwatch devices on your networkReview your asset inventory or use network scanning to identify devices running Longwatch software or firmware. Check device labels, management interfaces, or DHCP records for 'Longwatch' identifiers.Affected if Longwatch devices are present in the environment
-
Determine the installed Longwatch versionAccess the device management interface or check system files/registry (depending on deployment) for the firmware or software version number. Compare against any version information provided by Longwatch release notes.Affected if The installed version is within the affected range (if known) or cannot be determined to be patched
-
Verify HTTP service exposureScan the network or check firewall rules to determine if the device HTTP service (typically port 80/443) is accessible from untrusted networks or the internet. Use 'nmap -p 80,443 <target>' or similar port scanning.Affected if The HTTP endpoint is reachable from unauthenticated or untrusted network segments
-
Test for unauthenticated endpoint accessSend a basic HTTP GET request to common Longwatch paths (such as / or /cgi-bin/) without providing credentials. Observe if the device responds without requiring authentication.Affected if The device accepts and processes HTTP requests without authentication credentials
-
Check for code execution capabilityIf the endpoint responds, examine whether the device allows command execution through URL parameters or HTTP body. Review any available logs for suspicious execution attempts.Affected if The HTTP interface permits execution of system commands or scripts without validation
You are affected if Longwatch devices are present and their HTTP interface is accessible without authentication, allowing potential remote code execution with SYSTEM privileges.
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 dataIsolate affected devices on restricted network segments immediately; contact Longwatch for patched firmware implementing code signing verification and authenticated execution controls.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13658 — 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-13658 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