dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-30057

CRITICAL · 9.4 CVSS v4.0 Published 2025-08-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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
In UHCRTFDoc, the filename parameter can be exploited to execute arbitrary code via command injection into the system() call in the ConvertToPDF function.

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

Command injection vulnerability in UHCRTFDoc's ConvertToPDF function allows arbitrary code execution via the filename parameter being passed unsanitized to a system() call.

MitigationImplement strict input validation and sanitization on the filename parameter before use in system() calls, or replace system() calls with safer API alternatives that do not involve shell 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
Adjacent
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Locate UHCRTFDoc installation
    Search for UHCRTFDoc files in common installation directories (e.g., /opt/, /usr/local/, or project dependencies). Check for assemblies or DLLs named UHCRTFDoc.dll or similar. If a .NET project, inspect the referenced packages in the project file (.csproj) or packages.config for UHCRTFDoc.
    Affected if UHCRTFDoc library is present in the environment or project dependencies
  2. Identify UHCRTFDoc version
    Check the version of the UHCRTFDoc DLL/assembly by right-clicking the file and selecting Properties > Details, or use a tool like dotPeek/ILSpy to inspect the assembly version attribute. If using a package manager (NuGet), run 'dotnet list package' or check the .csproj file for the version number.
    Affected if The installed version cannot be compared to a patched version (no version range provided, but newer versions should be verified)
  3. Verify ConvertToPDF function usage
    Search codebases for calls to ConvertToPDF method. Use grep or IDE search for 'ConvertToPDF' to find all invocations. Inspect the call sites to see how the filename parameter is being passed.
    Affected if Code calls ConvertToPDF and passes a user-controlled or external filename value to it
  4. Inspect filename parameter handling
    At the ConvertToPDF call site, examine what value is passed as the filename argument. Trace the data flow: is it from user input (request parameters, CLI arguments, file uploads), external APIs, or hardcoded values?
    Affected if The filename argument originates from untrusted input without validation
  5. Check for unsafe system call usage
    If source code is available, decompile or inspect the UHCRTFDoc ConvertToPDF method to confirm it invokes system() or equivalent shell execution. Look for Process.Start, ShellExecute, or runtime.exec calls using the filename.
    Affected if The ConvertToPDF implementation uses system() or similar shell execution with unsanitized input

If UHCRTFDoc is present, ConvertToPDF is called with a filename derived from untrusted input, and the implementation uses shell execution without sanitization, the environment is vulnerable to CVE-2025-30057.

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

Implement strict input validation and sanitization on the filename parameter before use in system() calls, or replace system() calls with safer API alternatives that do not involve shell command execution.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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