dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-14204

MEDIUM · 6.3 CVSS v3.1 Published 2025-12-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability has been found in TykoDev cherry-studio-TykoFork 0.1. This issue affects the function redirectToAuthorization of the file /.well-known/oauth-authorization-server of the component OAuth Server Discovery. Such manipulation of the argument authorizationUrl leads to os command injection. The attack can be executed remotely. The exploit has been disclosed to the public and may be used.

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 confidence

OS command injection vulnerability in the OAuth Server Discovery feature of cherry-studio-TykoFork v0.1. The redirectToAuthorization function in /.well-known/oauth-authorization-server improperly handles the authorizationUrl parameter, allowing remote attackers to inject and execute arbitrary OS commands via crafted input.

MitigationSanitize and validate the authorizationUrl parameter using allowlist validation; replace any direct system command execution with parameterized APIs or safe libraries; implement proper output encoding for redirects.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Identify if cherry-studio-TykoFork v0.1 is installed
    Locate the application binary or package. Check the installed version by running the application with a version flag (e.g., --version) or examining the package metadata. Compare your version against v0.1.
    Affected if The installed version is cherry-studio-TykoFork v0.1 (or a version within the same release line) and the OAuth Server Discovery feature is enabled.
  2. Verify the OAuth Server Discovery endpoint is accessible
    Attempt to access the /.well-known/oauth-authorization-server endpoint on your instance (e.g., curl http://localhost:PORT/.well-known/oauth-authorization-server or the equivalent base URL).
    Affected if The endpoint returns a response, indicating the OAuth Server Discovery feature is active and could be processing the authorizationUrl parameter.
  3. Inspect application logs for command injection indicators
    Review application log files (typically in /var/log, a logs directory within the application, or stdout/stderr output) for entries containing suspicious commands, shell metacharacters, or unexpected execution patterns around the oauth-authorization-server endpoint.
    Affected if Logs show execution of system commands with user-supplied input, shell operators, or unexpected binary/script invocations originating from the authorizationUrl parameter.
  4. Check for unexpected outbound network connections or processes
    Monitor network connections (e.g., using netstat, ss, or process monitoring tools) for the application process executing outbound connections to unknown hosts, or observe for newly spawned shell processes during OAuth operations.
    Affected if The application spawns shell processes or makes network calls that correspond to injected commands from the authorizationUrl parameter.

You are affected if cherry-studio-TykoFork v0.1 is running with the OAuth Server Discovery endpoint (/.well-known/oauth-authorization-server) accessible and the authorizationUrl parameter is being processed without sanitization, allowing arbitrary command execution.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Sanitize and validate the authorizationUrl parameter using allowlist validation; replace any direct system command execution with parameterized APIs or safe libraries; implement proper output encoding for redirects.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14204 — 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-14204 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