dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-41876

HIGH · 8.7 CVSS v4.0 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable Zero-click 6 weeks old

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
R-SOFT DMS is vulnerable to OS Command Injection in konwertujAction() function. The document converter executes shell commands using unsanitized file paths and format parameters. This allows an authenticated attacker to execute arbitrary system commands with the privileges of the web server user. This issue was fixed in version v3.19-2752 and v3.17-2580.

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

R-SOFT DMS contains an OS command injection vulnerability in the konwertujAction() function of its document converter. The function passes unsanitized file paths and format parameters directly to shell command execution, allowing authenticated users to inject arbitrary OS commands that execute with the web server user's privileges.

MitigationApply vendor patches v3.19-2752 or v3.17-2580 to remediate the command injection vulnerability. As this requires authentication, prioritize restricting converter function access to minimal necessary roles and monitor for unusual command patterns.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/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. Identify R-SOFT DMS installation
    Search for R-SOFT DMS in installed programs, running services, or common installation directories. Look for processes or services containing 'r-soft' or 'dms' in their name.
    Affected if R-SOFT DMS software is found on the system
  2. Determine installed version
    Locate version information in the application (typically in About, Help, or system information pages) or check installation logs and registry entries if applicable.
    Affected if Version is lower than v3.19-2752 or v3.17-2580 (or if version cannot be determined and the application is present)
  3. Verify document converter is enabled
    Check if the document converter functionality is accessible in the DMS interface. Look for conversion features, document processing options, or konwertuj-related endpoints in the application.
    Affected if The document converter function is available and accessible to users
  4. Check authentication and access controls
    Review user role configurations and confirm whether authenticated users can access the converter function. Verify if the konwertujAction endpoint is exposed without proper authorization restrictions.
    Affected if Authenticated users can access the converter function without restricted role limitations
  5. Inspect converter function configuration
    If accessible, examine the application configuration files or web endpoints for the konwertujAction function. Check if file path and format parameters are passed directly to system calls.
    Affected if The function accepts file paths or format parameters without sanitization visible in configuration

The system is affected if R-SOFT DMS is installed with a version below v3.19-2752 or v3.17-2580 and the document converter function is accessible to authenticated users.

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

Apply vendor patches v3.19-2752 or v3.17-2580 to remediate the command injection vulnerability. As this requires authentication, prioritize restricting converter function access to minimal necessary roles and monitor for unusual command patterns.

Recommended fix High confidence

v3.19-2752 (recommended) or v3.17-2580

  1. 1. Identify the current version of R-SOFT DMS currently installed
  2. 2. If running version v3.19 or later, verify the exact build number is v3.19-2752 or higher
  3. 3. If running v3.17 series, verify the exact build number is v3.17-2580 or higher
  4. 4. If running an older version, plan upgrade to v3.19-2752 (recommended) or v3.17-2580
  5. 5. Before upgrading, backup the current installation and configuration
  6. 6. Perform the upgrade following vendor documentation
  7. 7. After upgrade, verify the konwertujAction() function is no longer vulnerable to command injection
  8. 8. Test that the document conversion functionality still works correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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