dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-3621

CRITICAL · 9.6 CVSS v3.1 Published 2025-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
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.

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 confidence

ActADUR local server by ProTNS contains multiple critical vulnerabilities allowing remote code inclusion: command injection via improper neutralization of special elements, hard-coded credentials, improper authentication, and binding to unrestricted IP addresses. The 9.6 CVSS score reflects severe potential for remote code execution. The flaws exist in versions from v2.0.1.9 before v2.0.2.0.

MitigationUpgrade ActADUR to v2.0.2.0 or later to resolve all four vulnerabilities including command injection, hard-coded credentials, authentication weaknesses, and unrestricted IP binding.

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine ActADUR installed version
    Locate the ActADUR application on the system and retrieve its version information. This may be found in the application executable properties, an 'about' dialog, a version file, or the software's installation directory.
    Affected if The installed version is any version prior to v2.0.2.0
  2. Inspect network binding configuration
    Examine the service configuration or running process to determine which IP addresses the ActADUR server binds to. Look for binding settings in configuration files or service properties.
    Affected if The service is bound to 0.0.0.0, 'any', or all network interfaces rather than a specific localhost or internal IP address
  3. Search for hard-coded credentials
    Inspect configuration files, scripts, or application files within the ActADUR installation directory for embedded username and password strings. Look for credentials stored in plaintext or encoded formats.
    Affected if Hard-coded credentials are found embedded in the software configuration or source files
  4. Verify authentication mechanism
    Review the authentication configuration and logs to determine if the application properly validates credentials before granting access. Check if unauthenticated or improperly authenticated requests can reach protected functions.
    Affected if The application allows unauthenticated access or uses weak/improper authentication that can be bypassed

A system is affected if ActADUR version is prior to v2.0.2.0 AND the service is exposed on accessible network interfaces with the identified vulnerabilities present in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ActADUR to v2.0.2.0 or later to resolve all four vulnerabilities including command injection, hard-coded credentials, authentication weaknesses, and unrestricted IP binding.

Recommended fix High confidence

v2.0.2.0 or later

  1. Backup all ActADUR configuration files, databases, and data before initiating the upgrade
  2. Verify the current installed version of ActADUR (should be v2.0.1.9 or between v2.0.1.9 and v2.0.2.0)
  3. Obtain the v2.0.2.0 or later version of ActADUR from the official ProTNS vendor
  4. Stop the ActADUR service completely before applying the update
  5. Install or deploy ActADUR v2.0.2.0 or newer version following vendor documentation
  6. Verify the installation was successful and the service starts without errors
  7. Confirm the upgraded version matches v2.0.2.0 or higher
  8. Test that the previously vulnerable command injection functionality is now properly sanitized or restricted

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3621 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3621 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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