Analyst readout for executives and security teams
Plain-English summary
CVE-2026-6629 is a remote SQL injection issue in Metasoft MetaCRM. An attacker could manipulate database queries through the MetaCRM Interface component, potentially exposing or changing CRM data. Public exploit information is referenced, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat as a high-priority CRM data risk, especially for internet-facing deployments. Prioritize inventory, exposure reduction, and monitoring while waiting for vendor guidance. Public exploit disclosure increases urgency, even without confirmed active exploitation.
Technical view
The issue affects sql.jsp in the MetaCRM Interface component, specifically use of Statement.executeUpdate with a controllable sql argument. VulDB maps it to CWE-89/CWE-74 and scores it CVSS v2 7.5: network-accessible, low complexity, no authentication, partial confidentiality, integrity, and availability impact.
Likely exposure
Organizations running Metasoft MetaCRM versions 6.0, 6.1, 6.2, 6.3, or 6.4.0 may be exposed. Risk is highest where the Interface component or sql.jsp is reachable from untrusted networks. No CPE data is provided, so validation likely requires asset and application owner review.
Exploitation context
VulDB states the exploit has been publicly disclosed and may be used. The CVE is not marked as CISA KEV in the provided bundle, and no cited source confirms active exploitation. The vendor was reportedly contacted but did not respond.
Researcher notes
Evidence is mainly from VulDB and the CVE record. The vendor reportedly did not respond, and no official patch is named. Version wording differs slightly between references, so confirm exact build exposure. No CVSS v3/v4 or CPE identifiers are provided.
Mitigation direction
- Identify all Metasoft MetaCRM deployments and affected versions.
- Check Metasoft vendor channels for an official fix or guidance.
- Restrict access to the MetaCRM Interface component to trusted networks only.
- Disable or isolate sql.jsp if business impact is acceptable.
- Increase monitoring for suspicious database and web activity.
- Apply compensating controls such as WAF rules where feasible.
Validation and detection
- Confirm whether MetaCRM versions 6.0 through 6.4.0 are deployed.
- Determine whether the Interface component and sql.jsp are reachable externally.
- Review web logs for unusual requests targeting sql.jsp.
- Review database logs for abnormal query errors or unexpected changes.
- Check whether vendor patches or advisories have appeared since disclosure.
- Document compensating controls and remaining exposure.
Public sources used
Based on public source material and reviewed before publication.
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-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-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 lookupDatabase 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 lookupCVE-2026-6629 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
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.
CVSS vector scores
1 official scoreWe 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.
AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 10 6.4 Primary CVE score Vulnerability scoring details
Base CVSS 2.0 score
7.5 HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 source CVE List V5
- VDB-358263 | Metasoft 美特软件 MetaCRM Interface sql.jsp Statement.executeUpdate sql injection CVE reference · vdb-entry, technical-description
- VDB-358263 | CTI Indicators (IOB, IOC, TTP, IOA) CVE reference · signature, permissions-required
- Submit #792615 | Beijing Meite Software Technology Co., Ltd. MetaCRM6 <6.4.0 SQL Injection CVE reference · third-party-advisory
- https://my.feishu.cn/docx/JttndUaPLoR88HxI1alcz1uencf?from=from_copylink CVE reference · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.