CVE-2025-70995
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 · uneditedAn issue in Aranda Service Desk Web Edition (ASDK API 8.6) allows authenticated attackers to achieve remote code execution due to improper validation of uploaded files. An authenticated user can upload a crafted web.config file by sending a crafted POST request to /ASDKAPI/api/v8.6/item/addfile, which is processed by the ASP.NET runtime. The uploaded configuration file alters the execution context of the upload directory, enabling compilation and execution of attacker-controlled code (e.g., generation of an .aspx webshell). This allows remote command execution on the server without user interaction beyond authentication, impacting both On-Premise and SaaS deployments. The vendor has fixed the issue in Aranda Service Desk V8 8.30.6.
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 confidenceAuthenticated attackers can achieve RCE in Aranda Service Desk Web Edition (ASDK API 8.6) by uploading a crafted web.config file to /ASDKAPI/api/v8.6/item/addfile. The malicious web.config alters the upload directory's execution context, allowing the ASP.NET runtime to compile and execute attacker-controlled .aspx code (webshells), enabling full remote command execution.
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
- 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.
-
Verify ASDK API installation and versionLocate the ASDK API installation directory and check the version information in the application manifest, assembly info, or version file. Common paths include the IIS web root where ASDKAPI is deployed.Affected if The installed version is 8.6 or falls within the 8.x range before 8.30.6
-
Confirm the vulnerable upload endpoint existsCheck if the endpoint /ASDKAPI/api/v8.6/item/addfile is accessible on the web server. This can be verified via direct HTTP request or by examining the deployed API routing configuration.Affected if The ASDK API is exposed and the v8.6 item/addfile endpoint responds to requests (indicates the vulnerable code path exists)
-
Inspect upload directory configurationLocate the directory where the file upload feature stores files (typically within the ASDK API deployment). Check the web.config file in that directory for handler mappings and execution permissions.Affected if The upload directory allows script execution (e.g., handlers for .aspx, .asp are not explicitly disabled) and permits .config files to be uploaded
-
Verify .config file upload is not blockedExamine the file validation logic in the ASDK API (check controller code or upload handler configuration) to determine if .config file extensions are rejected during upload.Affected if .config files are not explicitly rejected by the upload validation logic, allowing malicious web.config files to be uploaded
-
Scan for existing malicious web.config in upload directoriesSearch the application's upload directories for any web.config files that may have been uploaded. Inspect their content for suspicious handler modifications or execution settings.Affected if A web.config file exists in an upload directory with modified handler mappings or execution permissions that enable ASP.NET code compilation
If the Aranda Service Desk version is 8.6 or an earlier 8.x version, the ASDK API with the file upload endpoint is exposed, and upload directories permit script execution or allow .config uploads, the environment is affected by CVE-2025-70995.
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.
dbcve · scopedUpgrade to Aranda Service Desk V8 8.30.6 or later. As a compensating control, disable script execution in upload directories, implement strict allowlist-based file validation to reject .config files, and restrict file upload functionality to minimal required users.
Aranda Service Desk V8 8.30.6
- 1. Verify current Aranda Service Desk version by checking the application or contacting the administrator
- 2. Schedule a maintenance window for the upgrade process
- 3. Back up the current Aranda Service Desk installation and database
- 4. Upgrade Aranda Service Desk to version 8.30.6 or later
- 5. Verify the upgrade was successful and the application is functioning correctly
- 6. Confirm the vulnerability is remediated by testing file upload functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70995 — 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-70995 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