CVE-2026-2561
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 was found in JingDong JD Cloud Box AX6600 up to 4.5.1.r4533. This affects the function web_get_ddns_uptime of the file /jdcapi of the component jdcweb_rpc. Performing a manipulation results in Remote Privilege Escalation. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceRemote privilege escalation vulnerability in JingDong JD Cloud Box AX6600 routers (up to v4.5.1.r4533) affecting the web_get_ddns_uptime function in the /jdcapi endpoint of the jdcweb_rpc component. The specific vulnerability type (e.g., command injection, broken access control) is not disclosed in available materials, but it allows an attacker to escalate privileges, likely to administrator level, through the web interface.
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.5.1.r4533CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelConfirm the target device is a JingDong JD Cloud Box AX6600 by checking the device label, web interface, or SNMP inventoryAffected if Device is not an AX6600 model, then it is not affected by this specific CVE
-
Check firmware versionAccess the device web interface, CLI, or check system info page to determine the installed firmware version. Compare against the affected range <= 4.5.1.r4533Affected if Firmware version is 4.5.1.r4533 or earlier (including unpatched versions)
-
Verify jdcweb_rpc component accessibilityAttempt to access the jdcweb_rpc service on the device. This is typically exposed on the web management port. Check if the service responds to requestsAffected if The jdcweb_rpc component is exposed and reachable on the network
-
Confirm DDNS feature statusCheck device settings or configuration files for DDNS (Dynamic DNS) feature status. The vulnerability is in the web_get_ddns_uptime functionAffected if DDNS feature is enabled on the device
-
Test /jdcapi endpoint exposureAttempt to access the /jdcapi endpoint without authentication. The vulnerable web_get_ddns_uptime function resides hereAffected if The /jdcapi endpoint is accessible from the network without authentication
The device is affected if it is an AX6600 running firmware <= 4.5.1.r4533, has the jdcweb_rpc component accessible, and exposes the /jdcapi endpoint with DDNS enabled.
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 dataSince the vendor did not respond and no patch is available, mitigate by restricting network access to the device's management interface (ideally placing it behind a VPN or firewall), disabling remote web management if the feature exists, and considering device replacement if remote exploitation is a concern.
- 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-2026-2561 — 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-2026-2561 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