CVE-2025-48733
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 · uneditedDuraComm SPM-500 DP-10iN-100-MU lacks access controls for a function that should require user authentication. This could allow an attacker to repeatedly reboot 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 · moderate confidenceThe DuraComm SPM-500 DP-10iN-100-MU device lacks access controls on a function that should require user authentication, allowing an unauthenticated attacker to repeatedly reboot the device. This is an authentication bypass vulnerability on a critical operational function.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device model and firmware versionAccess the device web interface or CLI and locate the system information or about page to confirm the exact model number (SPM-500 DP-10iN-100-MU) and note the installed firmware versionAffected if The device model matches SPM-500 DP-10iN-100-MU and the firmware is unpatched or of unknown version
-
Confirm device management interface is network accessibleVerify whether the device HTTP/HTTPS management interface is reachable from network segments that contain untrusted users or systems (ping test, port scan on 80/443)Affected if The device management interface is exposed to untrusted networks without firewall filtering
-
Test reboot function for authentication bypassUsing a tool like curl or a browser, send a POST request to the device reboot endpoint (commonly /reboot, /admin/reboot, or similar) without providing any authentication credentialsAffected if The device accepts and processes the reboot request without requiring login credentials, returning a success response or initiating a reboot
-
Check for authentication enforcement on sensitive functionsReview the device configuration or attempt to access other administrative functions (factory reset, configuration backup/restore) without authentication to determine if access controls are consistently appliedAffected if Multiple sensitive functions respond without authentication or return 200 OK without requiring login
You are affected if you have a DuraComm SPM-500 DP-10iN-100-MU device with an unpatched firmware version, and the device reboot function can be triggered without any authentication credentials.
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 dataApply vendor-supplied firmware patch when available; until then, restrict network access to the device via firewall or place on isolated network segment to limit attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48733 — 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-48733 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