dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-41877

MEDIUM · 5.1 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 →
55/100
Remediation priority · Elevated
Remotely reachable 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 Stored XSS in file upload functionality. Authenticated attacker can inject arbitrary HTML and JS into the name of the file being uploaded, which will be executed when visiting file list or upload status by other users. This issue was fixed in version v3.19-2832 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 fails to properly sanitize filenames during the upload process, allowing an authenticated attacker to embed malicious HTML and JavaScript code into the file name. This payload is stored and rendered without output encoding when other users view the file list or upload status, leading to Stored XSS execution in their browser sessions.

MitigationUpgrade to version v3.19-2832 or v3.17-2580. Until then, implement output encoding on all filename displays and consider restricting file upload permissions to trusted users only.

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
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N/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 and version
    Locate the R-SOFT DMS application and check its version information, typically found in the application settings, about page, or version file within the installation directory
    Affected if The installed version is older than v3.19-2832 or v3.17-2580, or if version information cannot be determined but the product is R-SOFT DMS
  2. Verify file upload functionality is accessible
    Log in as an authenticated user and confirm the file upload feature is enabled and accessible in the DMS interface
    Affected if File upload capability is available to authenticated users in the current environment
  3. Inspect filename rendering in file list view
    Upload a test file with a benign filename containing special characters (e.g., <script>test</script>) and view the file list or upload status page to see if the characters render as plain text or are executed as code
    Affected if The filename appears rendered as HTML or JavaScript rather than being displayed as encoded plain text
  4. Check for output encoding implementation
    Review the application code that handles filename display in file list and upload status views to verify if output encoding functions are applied before rendering filenames
    Affected if No output encoding (HTML escaping) is applied to filenames before they are rendered in the browser

You are affected if R-SOFT DMS is running and the installed version is before v3.19-2832 or v3.17-2580, AND the file upload feature is accessible to authenticated users, AND filenames are rendered without HTML encoding in the file list or upload status views.

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 to version v3.19-2832 or v3.17-2580. Until then, implement output encoding on all filename displays and consider restricting file upload permissions to trusted users only.

Recommended fix Moderate confidence

v3.19-2832 or v3.17-2580 (or later releases)

  1. 1. Identify the current installed version of R-SOFT DMS by accessing the application admin panel or checking system information
  2. 2. If running version v3.19-2831 or earlier, plan to upgrade to v3.19-2832 or later
  3. 3. If running version v3.17-2579 or earlier on the v3.17 branch, upgrade to v3.17-2580 or later
  4. 4. Before upgrading, backup the current installation and database
  5. 5. Perform the upgrade following the vendor's standard upgrade procedure
  6. 6. Verify the upgrade was successful by logging in and confirming the version number
  7. 7. Test the file upload functionality to confirm the XSS vulnerability is remediated

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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