LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38243: xunruicms up to v4.5.1 was discovered to contain a remote code execution (RCE) vulnerability in /index.php.

xunruicms up to v4.5.1 was discovered to contain a remote code execution (RCE) vulnerability in /index.php. This vulnerability allows attackers to execute arbitrary code via a crafted GET request.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-38243 is a critical remote code execution issue in xunruicms up to v4.5.1. An unauthenticated attacker could execute arbitrary code through a crafted GET request to /index.php, potentially taking over the web application or server context.

Executive priority

Prioritize within the emergency vulnerability queue for any exposed xunruicms deployment. The business risk is potential application takeover, data compromise, service disruption, and lateral movement from a public web server.

Technical view

The CVE describes CWE-94 improper control of code generation in /index.php, reachable over the network with low complexity and no privileges or user interaction. The CVSS v3.1 score is 9.8 with high confidentiality, integrity, and availability impact. Normalized affected vendor/product and CPE data are not provided.

Likely exposure

Organizations running xunruicms version 4.5.1 or earlier are the stated exposure group. Risk is highest where the application and /index.php are internet-facing. Source metadata does not provide CPEs, package names, hosting patterns, or a definitive fixed version.

Exploitation context

The CVE references a public GitHub repository about xunruicms RCE, but the bundle does not establish active exploitation. The issue is not marked as CISA KEV in the provided data. Treat public-facing instances as urgent because unauthenticated RCE has severe impact.

Researcher notes

Core severity and vulnerability class are clear, but public metadata is thin. The source bundle names xunruicms up to v4.5.1 and /index.php, yet lacks normalized affected products, CPEs, patch details, and verified exploitation status.

Mitigation direction

  • Inventory all xunruicms deployments and identify versions.
  • Check vendor or project guidance for a fixed release or mitigation.
  • Remove, isolate, or restrict internet exposure for affected instances.
  • Review access controls around /index.php while remediation is pending.
  • Monitor web logs for suspicious crafted GET requests to /index.php.

Validation and detection

  • Confirm whether xunruicms is deployed in production, staging, or legacy hosts.
  • Verify whether any deployed version is 4.5.1 or earlier.
  • Check whether /index.php is reachable from untrusted networks.
  • Review recent web logs for unusual GET requests targeting /index.php.
  • Document evidence gaps because CPE and fixed-version data are absent.
Prepared
Confidence
medium
Sources
3

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.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
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-38243 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2021-38243Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.