LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10879: rConfig before 3.9.5 allows command injection by sending a crafted GET request to lib/crud/search.crud.php...

rConfig before 3.9.5 allows command injection by sending a crafted GET request to lib/crud/search.crud.php since the nodeId parameter is passed directly to the exec function without being escaped.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-10879 is a command-injection flaw in rConfig before 3.9.5. A crafted request to a search endpoint can cause unescaped input to reach an operating-system command. For leadership, treat exposed or business-critical rConfig systems as urgent because compromise could affect the host running the tool.

Executive priority

Prioritize remediation for exposed rConfig systems this cycle. Command injection can turn a web application flaw into host compromise, and public exploit information increases practical risk even without confirmed active exploitation.

Technical view

The CVE states that lib/crud/search.crud.php passes the nodeId GET parameter directly to exec without escaping. A public Exploit Database entry exists, but the source bundle does not show CISA KEV listing or confirmed active exploitation. A fix is referenced in the rConfig GitHub commit and the affected range is before 3.9.5.

Likely exposure

Exposure is limited to organizations running rConfig versions before 3.9.5, especially where the rConfig web interface is reachable by untrusted users. The bundle does not identify specific packaged distributions, CPEs, authentication requirements, or internet-wide exposure levels.

Exploitation context

There is public exploit information on Exploit Database, so defenders should assume attackers can learn the issue. The provided sources do not prove active exploitation in the wild, and KEV is false in the bundle.

Researcher notes

The available evidence is concise but specific: vulnerable file, parameter, sink, affected version boundary, fix commit, and public exploit listing. Missing details include CVSS, CWE, authentication prerequisites, and vendor advisory context, so validation should avoid assumptions beyond the cited sources.

Mitigation direction

  • Upgrade affected rConfig deployments to 3.9.5 or later where applicable.
  • Review the referenced rConfig commit and vendor guidance before applying changes.
  • Restrict rConfig web access to trusted administrative networks.
  • Monitor for suspicious requests to lib/crud/search.crud.php.
  • Investigate affected hosts for post-compromise activity if exposure existed.

Validation and detection

  • Inventory all rConfig instances and record exact versions.
  • Confirm any version before 3.9.5 is treated as affected.
  • Check whether the rConfig web interface is internet-accessible or broadly reachable.
  • Review web logs for unusual requests targeting search.crud.php and nodeId.
  • Verify remediation by confirming the upgraded version and reduced access paths.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-10879 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.