LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38239: SQL Injection vulnerability in dataease before 1.2.0, allows attackers to gain sensitive information via th...

SQL Injection vulnerability in dataease before 1.2.0, allows attackers to gain sensitive information via the orders parameter to /api/sys_msg/list/1/10.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-38239 is a SQL injection issue in DataEase before 1.2.0. A remote unauthenticated attacker could use the affected API parameter to read sensitive data. The available sources do not show active exploitation, but exposed DataEase instances should be treated as high priority.

Executive priority

Patch externally reachable DataEase instances urgently within high-severity remediation timelines. Internal-only systems still need attention because the issue can expose sensitive information without authentication according to the CVSS privileges metric.

Technical view

The CVE describes CWE-89 SQL injection through the orders parameter of /api/sys_msg/list/1/10 in DataEase before 1.2.0. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges, no user interaction, high confidentiality impact, and no stated integrity or availability impact.

Likely exposure

Likely exposure is limited to organizations running DataEase before 1.2.0, especially where the web API is reachable from untrusted networks. The CVE metadata lacks CPEs and lists vendor/product as n/a, so teams must confirm exposure through inventory and version checks.

Exploitation context

CISA KEV status is false in the supplied bundle, and no cited source reports active exploitation. Public disclosure exists through the CVE record and a GitHub issue. Treat exploit status as unconfirmed, not absent.

Researcher notes

The source bundle is sparse: affected CPEs are absent and vendor/product fields are n/a, but the description identifies DataEase before 1.2.0. Avoid assuming broader affected products or confirmed exploitation. Focus validation on version, endpoint reachability, and evidence of suspicious access.

Mitigation direction

  • Upgrade affected DataEase deployments to version 1.2.0 or later.
  • Review the linked vendor issue and release guidance for any additional fixes.
  • Restrict DataEase API access to trusted networks until remediation is complete.
  • Monitor web and application logs for suspicious requests to the affected endpoint.

Validation and detection

  • Inventory all DataEase deployments and record running versions.
  • Confirm whether any instance is earlier than DataEase 1.2.0.
  • Check whether /api/sys_msg/list/1/10 is reachable from untrusted networks.
  • Review logs for unusual use of the orders parameter.
  • After updating, verify the installed version and repeat exposure checks.
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.

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-38239 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-38239Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-89

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