# CVE-2026-41877: Stored XSS in R-SOFT DMS

> Authenticated attackers can inject malicious scripts via file names in R-SOFT DMS, leading to code execution when other users view file lists.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-c9ph-5j66-3j9f

## What is CVE-2026-41877?

CVE-2026-41877 is a medium-severity cross-site scripting vulnerability in R-SOFT SERWIS DMS, published on 10 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-41877?


## How do I fix CVE-2026-41877?

No fix has been published for CVE-2026-41877 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41877 being exploited?

There is no known exploitation of CVE-2026-41877 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41877 and fix it if it is affected.

What it is: CVE-2026-41877 is a medium-severity cross-site scripting vulnerability in R-SOFT SERWIS DMS, published on 10 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41877 in the wild and no public exploit code.

Affected product: R-SOFT SERWIS DMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41877/ (Markdown: https://insights.sbomify.com/CVE-2026-41877/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41877
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41877
- OSV: https://osv.dev/vulnerability/CVE-2026-41877

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41877/
Summaries are generated and may contain mistakes; the official description above is the record.