dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-41878

HIGH · 7.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 →
77/100
Remediation priority · High
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 Insecure Direct Object Reference (IDOR) attack in multiple file download endpoints. The application fetches files from the database by ID and serves them to whoever requests them, relying only on session authentication, meaning any valid user can access any file. This issue was fixed in version v3.19-2862 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 file download endpoints are vulnerable to IDOR because they fetch files by database ID without verifying user authorization. Any authenticated user can download any file in the system by knowing or guessing file IDs, as the application only validates session authentication rather than checking file ownership or access permissions.

MitigationUpgrade to version v3.19-2862 or v3.17-2580, which implement proper authorization checks to verify user permissions before serving files.

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:N/VA:N/SC:N/SI:N/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. Confirm R-SOFT DMS installation and version
    Locate the R-SOFT DMS installation directory and check the version file, software about page, or help menu. Compare the installed version against the fixed versions v3.19-2862 and v3.17-2580.
    Affected if The installed version is lower than v3.17-2580 or v3.19-2862 (if using the 3.17 or 3.19 branch respectively).
  2. Identify file download endpoint URLs
    Review web application traffic or application documentation to locate file download endpoints. Common patterns include URLs with parameters like 'download.do', 'fileDownload', 'getFile', or similar indicating database ID-based file retrieval.
    Affected if File download endpoints exist that accept a file ID parameter without an object ownership check in the request flow.
  3. Test authorization bypass on file download
    Using an authenticated user account with limited access, attempt to access file download URLs by manipulating the file ID parameter to reference files owned by other users or accessible only to different groups.
    Affected if A low-privilege user can successfully download files they should not have access to by changing the file ID parameter.
  4. Verify session-only authentication on file endpoints
    Use browser developer tools or a proxy to intercept a file download request. Observe whether the request includes only a session cookie/token without additional authorization tokens or permission parameters.
    Affected if The download request relies solely on session authentication without passing or validating file-level access permissions.

A user is affected if R-SOFT DMS version is below v3.17-2580 or v3.19-2862 AND file download endpoints can be accessed by any authenticated user to retrieve files outside their authorized scope.

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-2862 or v3.17-2580, which implement proper authorization checks to verify user permissions before serving files.

Recommended fix High confidence

R-SOFT DMS v3.19-2862 or v3.17-2580

  1. 1. Identify the currently installed version of R-SOFT DMS in your environment
  2. 2. Review release notes for versions v3.19-2862 and v3.17-2580 to confirm they contain the IDOR security fix
  3. 3. Create a backup of the current R-SOFT DMS installation including database and configuration files
  4. 4. Schedule a maintenance window for the upgrade process
  5. 5. Upgrade R-SOFT DMS to version v3.19-2862 (recommended for latest stable) or v3.17-2580 (if maintaining older release line)
  6. 6. Verify the upgrade was successful by checking the application version
  7. 7. Test file download functionality to confirm the IDOR fix is working correctly
  8. 8. Confirm that users can only access files they are authorized to download

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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