LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38217: SEMCMS v 1.2 is vulnerable to SQL Injection via SEMCMS_User.php.

SEMCMS v 1.2 is vulnerable to SQL Injection via SEMCMS_User.php.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

SEMCMS v1.2 has a critical SQL injection flaw in SEMCMS_User.php. If that component is exposed, an unauthenticated attacker may be able to interfere with the site database, risking data theft, data changes, or service disruption.

Executive priority

Treat as urgent for any exposed SEMCMS v1.2 site because compromise could affect confidentiality, integrity, and availability. Priority drops if SEMCMS is not present or the affected path is not reachable.

Technical view

CVE-2021-38217 is a CWE-89 SQL injection in SEMCMS_User.php. The CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction required. The provided sources do not name a fixed version.

Likely exposure

Exposure is most likely where SEMCMS v1.2 is internet-accessible. The CVE record names SEMCMS v1.2, but vendor, product, CPE, and version metadata are incomplete, so inventory confirmation is necessary.

Exploitation context

The issue has a public GitHub reference, but the provided sources do not show CISA KEV listing or confirmed active exploitation. Treat it as high urgency because the CVSS vector indicates unauthenticated remote exploitability.

Researcher notes

The public metadata is sparse: affected fields are not normalized and no official fix is identified in the supplied sources. Validate product lineage and version locally before asserting exposure or closure.

Mitigation direction

  • Identify any SEMCMS v1.2 deployments and prioritize them for review.
  • Check the SEMCMS project or vendor guidance for a fixed release or official workaround.
  • Restrict external access to affected SEMCMS_User.php functionality where business allows.
  • Use database least privilege for the web application account.
  • Increase monitoring for SQL errors, suspicious user requests, and database anomalies.

Validation and detection

  • Confirm whether SEMCMS v1.2 exists in production, staging, or legacy hosting.
  • Verify whether SEMCMS_User.php is reachable from untrusted networks.
  • Review application code or vendor release notes for parameterized SQL handling.
  • Check web and database logs for unusual requests around user-management paths.
  • Document current version, exposure path, compensating controls, and remediation owner.
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-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. 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-38217 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-38217Attack 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
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-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.