dbcve.org
CWE-328Weakness · CWE-328

CVE-2026-41879

HIGH · 8.2 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 →
91/100
Remediation priority · Urgent
Remotely reachable No privileges 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 stores superadmin credentials using a non-salted nested MD5 hash. This allows an attacker who obtain password hash to decode superadmin credentials. Critically, this password cannot be changed except by modifying the configuration file. This issue was fixed in version v3.17-2000.

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 stores superadmin credentials using a weak, non-salted nested MD5 hash algorithm. An attacker who obtains the password hash can easily crack it to recover the plaintext superadmin credentials. Critically, this password cannot be changed through normal application interfaces and requires direct modification of the configuration file.

MitigationUpgrade to version v3.17-2000 or later which implements proper password hashing. Until upgraded, restrict access to the configuration file containing the credentials and monitor for unauthorized access.

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

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/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. Locate R-SOFT DMS installation
    Search for R-SOFT DMS installation directories or check common installation paths. Look for application files related to document management system.
    Affected if R-SOFT DMS is installed on the system
  2. Identify configuration file with credentials
    Find configuration files that store superadmin credentials. These are typically in config, settings, or data directories within the R-SOFT DMS installation. Look for files containing user= or password= entries with hash values.
    Affected if A configuration file containing superadmin credential hashes is found
  3. Examine password hash format
    Open the configuration file and inspect the password hash value. Check if the hash exhibits a nested MD5 pattern (e.g., md5(md5(password))) or similar weak hashing structure without salt.
    Affected if The stored password hash uses non-salted nested MD5 or similar weak hashing algorithm
  4. Determine installed version
    Check the installed R-SOFT DMS version by examining version files, about dialog, or application metadata. Compare against the fixed version v3.17-2000.
    Affected if Installed version is below v3.17-2000 or version cannot be determined
  5. Verify password change restriction
    Attempt to change the superadmin password through the application web interface or admin panel. Note if the option is missing, disabled, or returns an error indicating the password cannot be changed via normal means.
    Affected if The superadmin password cannot be changed through standard application interfaces

The environment is affected if R-SOFT DMS is installed with a version below v3.17-2000 and the configuration file contains superadmin credentials stored using non-salted nested MD5 hashing.

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.17-2000 or later which implements proper password hashing. Until upgraded, restrict access to the configuration file containing the credentials and monitor for unauthorized access.

Recommended fix High confidence

v3.17-2000

  1. 1. Identify the current version of R-SOFT DMS installed in your environment
  2. 2. If the current version is below v3.17-2000, download R-SOFT DMS version v3.17-2000 or later from the official vendor
  3. 3. Before upgrading, backup the current configuration and database to prevent data loss
  4. 4. Install the upgraded version v3.17-2000 following the vendor's standard upgrade procedure
  5. 5. After upgrade, verify that the new version uses proper password hashing (salted hashes, not nested MD5)
  6. 6. As a security best practice, change the superadmin password after the upgrade to ensure credentials are hashed with the new secure method
  7. 7. Verify the application functions normally after the upgrade
Caveat Review release notes for v3.17-2000 to check for any configuration changes or migration requirements that may affect your deployment

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-41879 — 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-41879 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