LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38737: SEMCMS v 1.1 is vulnerable to SQL Injection via Ant_Pro.php.

SEMCMS v 1.1 is vulnerable to SQL Injection via Ant_Pro.php.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical SQL injection reported in SEMCMS v1.1. A vulnerable Ant_Pro.php endpoint may allow an unauthenticated remote attacker to manipulate database queries, risking data theft, data changes, or service disruption. The source bundle does not identify a vendor patch, and CISA KEV status is false.

Executive priority

Prioritize this for rapid assessment because the score is critical and the vulnerability is remotely reachable without authentication. Business urgency depends on whether SEMCMS v1.1 is deployed, especially on public-facing websites handling customer, order, or administrative data.

Technical view

CVE-2021-38737 is a CWE-89 SQL injection in SEMCMS v1.1 via Ant_Pro.php. CVSS 3.1 is 9.8 with network access, low complexity, no privileges, and no user interaction. The listed impacts are high for confidentiality, integrity, and availability.

Likely exposure

Exposure appears limited to organizations running SEMCMS v1.1 or deployments retaining the vulnerable Ant_Pro.php code. Internet-facing SEMCMS instances would be the highest concern. The bundle does not provide CPEs, package identifiers, or affected ranges beyond v1.1.

Exploitation context

The provided sources include a public GitHub reference, but the bundle does not establish active exploitation. KEV is false. Treat this as a high-risk publicly disclosed issue, not as confirmed in-the-wild exploitation.

Researcher notes

Evidence is sparse: the CVE description names SEMCMS v1.1 and Ant_Pro.php, but affected CPEs and official fix details are not supplied. Avoid assuming broader SEMCMS versions are affected unless confirmed by vendor guidance or direct code review.

Mitigation direction

  • Inventory SEMCMS deployments and confirm whether version 1.1 is present.
  • Check vendor guidance for patched versions or official remediation.
  • Restrict public access to affected SEMCMS administration or product endpoints where feasible.
  • Back up application data before applying vendor-directed upgrades or code changes.
  • Review web application firewall coverage for SQL injection blocking as a temporary control.

Validation and detection

  • Identify internet-facing hosts running SEMCMS or related SCSHOP code.
  • Confirm whether Ant_Pro.php exists in deployed application paths.
  • Review application logs for unusual requests targeting Ant_Pro.php.
  • Verify database error exposure is disabled in production responses.
  • Document version evidence and remediation status for each affected host.
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-38737 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-38737Attack 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.