CVE-2025-9752
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 security vulnerability has been detected in D-Link DIR-852 1.00CN B09. Impacted is the function soapcgi_main of the file soap.cgi of the component SOAP Service. Such manipulation of the argument service leads to os command injection. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. This vulnerability only affects products that are no longer supported by the maintainer.
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 confidenceOS command injection vulnerability in D-Link DIR-852 router's SOAP Service (soap.cgi). The soapcgi_main function fails to properly sanitize the 'service' argument before passing it to system calls, allowing remote attackers to execute arbitrary OS commands. This is a critical pre-authentication flaw requiring no 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= 1.00cn_b09CVSS 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.
-
Confirm D-Link DIR-852 modelLog into the router web interface or check the device label to verify the model number is DIR-852Affected if The device is not a D-Link DIR-852, this CVE does not apply
-
Check firmware versionNavigate to router Status or Management page to view the installed firmware versionAffected if Firmware version is 1.00cn_b09, matching the affected version exactly
-
Verify SOAP service accessibilityAttempt to access soap.cgi endpoint (typically at http://<device_ip>/soap.cgi) or check router administration settings for SOAP/UPnP service statusAffected if The SOAP service is enabled and the soap.cgi endpoint responds to requests
-
Test service parameter injection pointIf soap.cgi is accessible, send a crafted request with a test payload in the 'service' parameter (e.g., service=`id` or service=$(whoami)) and observe if command output is returnedAffected if The device executes and returns output from commands injected via the service parameter, confirming the vulnerability is present and exploitable
A defender is affected if they have a D-Link DIR-852 router running firmware version 1.00cn_b09 with the SOAP service enabled and accessible, and the soap.cgi endpoint reflects command injection in the service parameter.
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 this is an end-of-life product with no vendor patch available, recommended mitigations include: immediately isolating the device from untrusted networks, disabling SOAP service if possible, or replacing with a supported device. Implement network segmentation and firewall rules to block external access to the device's management interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9752 — 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-9752 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