LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38736: SEMCMS Shop V 1.1 is vulnerable to SQL Injection via Ant_Global.php.

SEMCMS Shop V 1.1 is vulnerable to SQL Injection via Ant_Global.php.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE describes a critical SQL injection in SEMCMS Shop V 1.1 through Ant_Global.php. A remote unauthenticated attacker could potentially manipulate backend database queries. With the published CVSS 9.8 rating, successful exploitation could threaten confidentiality, integrity, and availability. The public record is sparse, so confirm exposure before acting broadly.

Executive priority

Prioritize within the current critical-vulnerability queue if SEMCMS Shop V 1.1 is present. The business concern is potential database compromise from a remote unauthenticated path. If the product is not used, document non-exposure and monitor for future vendor clarification.

Technical view

CVE-2021-38736 is categorized as CWE-89 SQL Injection affecting SEMCMS Shop V 1.1 via Ant_Global.php. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating network reachability, low complexity, no privileges, and no user interaction. The source bundle does not provide CPEs or detailed vendor remediation.

Likely exposure

Likely exposure is limited to organizations running SEMCMS Shop V 1.1, especially internet-facing deployments. The affected-product metadata in the CVE bundle is incomplete, so asset inventory and application fingerprinting are required before estimating scope.

Exploitation context

The source bundle includes a public GitHub reference and vendor-related reference, but no KEV listing and no cited source stating active exploitation. Treat this as a high-impact remotely reachable issue, not as confirmed exploited in the wild.

Researcher notes

The available record is minimal: product version, affected file, CWE, and CVSS are clear, but affected CPEs, patch status, and exploitation evidence are not. Avoid assuming broader SEMCMS versions are affected unless supported by vendor or CVE updates.

Mitigation direction

  • Identify any SEMCMS Shop V 1.1 deployments immediately.
  • Check SEMCMS vendor guidance for an official fixed version or advisory.
  • Remove public exposure until remediation is confirmed, where operationally feasible.
  • Apply least-privilege database permissions for the application account.
  • Monitor web and database logs for suspicious Ant_Global.php activity.

Validation and detection

  • Inventory web assets for SEMCMS Shop V 1.1.
  • Confirm whether Ant_Global.php exists in deployed application paths.
  • Review CVE and vendor references for remediation details.
  • Check web logs for unusual requests targeting Ant_Global.php.
  • Verify database account privileges are constrained to required operations.
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.

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-38736 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
3Source 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-38736Attack 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.