LiveActive security incident?Get immediate response
CVE Record

CVE-2019-2730: Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Security: Privileges).

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Security: Privileges). Supported versions that are affected are 5.6.44 and prior and 5.7.18 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.0 Base Score 2.7 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This Oracle MySQL Server issue can let an already highly privileged network-accessible attacker make unauthorized changes to some database data. It is an integrity-risk vulnerability, not described as exposing data or causing outages. Business urgency depends on whether affected MySQL versions remain in use and who has privileged database access. Exposure is likely limited to environments still running the named Oracle MySQL Server versions and allowing privileged users network access through MySQL-supported protocols. The bundle does not identify other affected products beyond Oracle MySQL Server. Handle as scheduled remediation unless affected databases hold critical regulated data or privileged database access is broadly reachable. The issue has low CVSS severity, but it can affect data integrity in outdated MySQL deployments. Mitigation focus: Inventory MySQL Server versions and flag 5.6.44 or earlier and 5.7.18 or earlier.; Review Oracle July 2019 CPU guidance for the applicable corrected release path.; Move affected systems to vendor-supported, non-affected MySQL versions..

Prepared

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.

cve · low confidence lookup

CVE-2019-2730 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationMySQL Server5.6.44 and prior, 5.7.18 and priorListed
Weakness

CWE details

No CWE listed

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