# CVE-2025-3621: Remote Code Execution in ProTNS ActADUR


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 15 Jul 2025
- **Updated:** 15 Jul 2025
- **Also known as:** GHSA-655x-v2mw-gj38

## What is CVE-2025-3621?

CVE-2025-3621 is a critical vulnerability in ProTNS ActADUR, published on 15 Jul 2025. 

### Official description

Vulnerabilities* in ActADUR local server product, developed and maintained by ProTNS, allows Remote Code Inclusion on host systems. 

* vulnerabilities:
  *  

Improper Neutralization of Special Elements used in a Command ('Command Injection')
  *  Use of Hard-coded Credentials
  *  Improper Authentication
  *  Binding to an Unrestricted IP Address

The vulnerability has been rated as critical.This issue affects ActADUR: from v2.0.1.9 before v2.0.2.0., hence updating to version v2.0.2.0. or above is required.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-287 (Improper Authentication), CWE-1327 (Binding to an Unrestricted IP Address)

## Which versions are affected by CVE-2025-3621?


## How do I fix CVE-2025-3621?

No fix has been published for CVE-2025-3621 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3621 being exploited?

There is no known exploitation of CVE-2025-3621 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3621 and fix it if it is affected.

What it is: CVE-2025-3621 is a critical vulnerability in ProTNS ActADUR, published on 15 Jul 2025. 
Exploitation: There is no known exploitation of CVE-2025-3621 in the wild and no public exploit code.

Affected product: ProTNS ActADUR. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3621/ (Markdown: https://insights.sbomify.com/CVE-2025-3621/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3621
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3621
- OSV: https://osv.dev/vulnerability/CVE-2025-3621

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3621/
Summaries are generated and may contain mistakes; the official description above is the record.