CVE-2025-66848
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 · uneditedJD Cloud NAS routers AX1800 (4.3.1.r4308 and earlier), AX3000 (4.3.1.r4318 and earlier), AX6600 (4.5.1.r4533 and earlier), BE6500 (4.4.1.r4308 and earlier), ER1 (4.5.1.r4518 and earlier), and ER2 (4.5.1.r4518 and earlier) contain an unauthorized remote command execution vulnerability.
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 confidenceMultiple JD Cloud NAS router models (AX1800, AX3000, AX6600, BE6500, ER1, ER2) contain an unauthenticated remote command execution vulnerability allowing attackers to execute arbitrary system commands on affected devices without any authentication credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.3.1.r4308<= 4.3.1.r4318<= 4.5.1.r4533<= 4.4.1.r4308<= 4.5.1.r4518<= 4.5.1.r4518CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the router modelCheck the device label, web management interface, or CLI output to confirm the exact model (AX1800, AX3000, AX6600, BE6500, ER1, or ER2)Affected if The model is one of the six affected models listed in the CVE
-
Check the installed firmware versionAccess the router's web interface or CLI and locate the firmware version information. Compare it against the affected version ranges: AX1800 <= 4.3.1.r4308, AX3000 <= 4.3.1.r4318, AX6600 <= 4.5.1.r4533, BE6500 <= 4.4.1.r4308, ER1 <= 4.5.1.r4518, ER2 <= 4.5.1.r4518Affected if The firmware version falls within or below the specified version for your model
-
Verify remote management exposureCheck router network settings to determine if the web management interface (HTTP/HTTPS on ports 80/443 or custom ports) is accessible from WAN/external networks. Look for 'Remote Management', 'Remote Access', or 'WAN Access' settings.Affected if Remote management or administration access is enabled and the interface is reachable from outside the local network
You are affected if you own one of the six listed models AND your firmware version is at or below the specified threshold AND your management interface is exposed to untrusted networks.
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 dataUpdate firmware to versions newer than those specified (4.3.1.r4309 for AX1800, 4.3.1.r4319 for AX3000, 4.5.1.r4534 for AX6600, 4.4.1.r4309 for BE6500, 4.5.1.r4519 for ER1/ER2). If patches unavailable, restrict network access to management interfaces and monitor for compromise indicators.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66848 — 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-66848 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