LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38169: Roxy-WI through 5.2.2.0 allows command injection via /app/funct.py and /api/api_funct.py.

Roxy-WI through 5.2.2.0 allows command injection via /app/funct.py and /api/api_funct.py.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Roxy-WI through version 5.2.2.0 is reported to allow command injection in application and API code paths. In business terms, affected management interfaces could let an attacker run unintended system commands if reachable and exploitable. The source bundle does not provide severity scoring, prerequisites, or confirmed exploitation.

Executive priority

Prioritize identification and containment over immediate emergency response. Command injection can be severe, but the public bundle lacks scoring, exploit confirmation, and remediation detail. Internet-facing or broadly accessible Roxy-WI instances should be assessed first.

Technical view

CVE-2021-38169 describes command injection in Roxy-WI through 5.2.2.0 via /app/funct.py and /api/api_funct.py. The record lists no CVSS, CWE, CPEs, authentication requirements, exploit complexity, or vendor remediation details. KEV is false in the supplied bundle.

Likely exposure

Likely exposure is limited to environments running Roxy-WI through 5.2.2.0, especially where the web interface or API is reachable. The bundle does not identify affected CPEs, deployment patterns, authentication state, or internet exposure data.

Exploitation context

The supplied sources do not confirm active exploitation. KEV is false, and the bundle provides no cited evidence of exploit use, public weaponization, required privileges, or attack complexity. Treat exploitability details as incomplete.

Researcher notes

The available record is sparse. Analysis is grounded in the CVE description and referenced GitHub issue only. Key missing details include vulnerable parameters, authentication requirements, fixed version, CVSS vector, and whether exploitation has been observed.

Mitigation direction

  • Inventory Roxy-WI deployments and identify any versions through 5.2.2.0.
  • Check upstream Roxy-WI guidance or release notes for fixed versions or patches.
  • Restrict access to Roxy-WI web and API endpoints to trusted administrative networks.
  • Review application logs for suspicious activity around the referenced application and API areas.

Validation and detection

  • Confirm whether Roxy-WI is installed and record the exact running version.
  • Verify whether /app/funct.py and /api/api_funct.py are present in deployed code.
  • Check whether Roxy-WI management endpoints are internet-accessible or broadly reachable internally.
  • Review vendor issue CVE references for remediation details before closing exposure.
Prepared
Confidence
medium
Sources
3

Public sources used

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-2021-38169 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
2Source 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.