dbcve.org
RconfigApplication

CVE-2020-15715

CRITICAL · 9.9 CVSS v3.1 Published 2020-07-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
rConfig 3.9.5 could allow a remote authenticated attacker to execute arbitrary code on the system, because of an error in the search.crud.php script. An attacker could exploit this vulnerability using the nodeId parameter.

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

rConfig 3.9.5 contains a code injection vulnerability in search.crud.php where the nodeId parameter is not properly sanitized, allowing an authenticated remote attacker to execute arbitrary OS commands on the underlying system.

MitigationUpgrade to the patched version of rConfig that addresses this vulnerability, or implement strict input validation/sanitization on the nodeId parameter in search.crud.php to prevent command injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RconfigApplication
Affected:= 3.9.5

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
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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 rConfig installation and version
    Identify the installed rConfig version by accessing the application's about page, checking the footer, or inspecting version files in the web directory. Common paths include /about.php or version information in the main index file.
    Affected if The installed version is exactly 3.9.5
  2. Locate search.crud.php file
    Check for the presence of search.crud.php in the web root or subdirectories of the rConfig installation. This file is required for the vulnerability to be exploitable.
    Affected if search.crud.php exists in the rConfig web directory
  3. Verify web application accessibility
    Determine if the rConfig web interface is accessible over HTTP/HTTPS from the network. Check firewall rules, network exposure, and listen addresses.
    Affected if The rConfig web interface is externally accessible or accessible to untrusted networks
  4. Check authentication configuration
    Review the application's user authentication settings and database to determine if default credentials are in use or if the application allows authenticated access.
    Affected if An attacker can obtain valid authentication credentials to access the application

A user is affected if they have rConfig version 3.9.5 installed with the search.crud.php file present and the web interface accessible to an attacker who can obtain valid credentials.

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 the patched version of rConfig that addresses this vulnerability, or implement strict input validation/sanitization on the nodeId parameter in search.crud.php to prevent command injection.

Recommended fix High confidence

rConfig 3.9.6 or latest stable release

  1. 1. Back up the rConfig database and configuration files before performing any upgrade
  2. 2. Download the latest stable version of rConfig from the official website (www.rconfig.com)
  3. 3. Replace the existing rConfig installation files with the new version
  4. 4. Run any database migration scripts included in the upgrade package
  5. 5. Verify the installation by logging into the web interface
  6. 6. Test that the search.crud.php functionality works correctly with proper authentication
  7. 7. Confirm no unauthorized code execution is possible via the nodeId parameter
Caveat Review release notes for any database schema changes or configuration requirements before upgrading

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

Fix this in Rconfig Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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