dbcve.org
InjectionWeakness · CWE-74

CVE-2026-6629

HIGH · 7.3 CVSS v3.1 Published 2026-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in Metasoft 美特软件 MetaCRM up to 6.4.0. This vulnerability affects the function Statement.executeUpdate of the file sql.jsp of the component Interface. Such manipulation of the argument sql leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in Metasoft MetaCRM's sql.jsp file allows remote attackers to manipulate the sql argument in the Statement.executeUpdate function. The vulnerability exists in the Interface component and can be exploited without authentication due to the lack of parameterized queries.

MitigationReplace dynamic SQL queries with parameterized PreparedStatement calls, implement strict input validation on all user-supplied parameters, and apply vendor patch if available. Consider web application firewall deployment as compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Metasoft MetaCRM is installed
    Search for MetaCRM installation directories on the server (common paths: /opt/metacrm, /var/www/metacrm, C:\Program Files\Metasoft\MetaCRM, or check for metacrm processes running). Check web server document roots for metacrm or metasoft directories.
    Affected if MetaCRM software is found installed on the system
  2. Locate the sql.jsp file in the Interface component
    Navigate to the web application root and look for the Interface component path (typically /interface/ or similar). Find sql.jsp in that location.
    Affected if The file sql.jsp exists within the Interface directory of the web application
  3. Inspect sql.jsp for vulnerable SQL execution patterns
    Open sql.jsp and search for 'Statement.executeUpdate' or 'Statement.execute' calls. Check if the SQL query is constructed by concatenating user-supplied parameters directly into the query string without using PreparedStatement or parameter binding.
    Affected if The code contains Statement.executeUpdate with direct string concatenation of the sql argument rather than parameterized queries
  4. Verify if the Interface component is network-accessible without authentication
    Test accessing the sql.jsp endpoint remotely (e.g., curl http://target/interface/sql.jsp). Confirm no authentication is required to reach this endpoint.
    Affected if The Interface component and sql.jsp are accessible remotely without requiring authentication
  5. Check the installed MetaCRM version if available
    Look for version information in MetaCRM configuration files, about pages, or the installation manifest. Compare against any known unaffected version ranges.
    Affected if The installed version is older than any patched version released by the vendor, or version information cannot be determined

If sql.jsp exists in the Interface component and contains Statement.executeUpdate using direct SQL concatenation without authentication protection, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized PreparedStatement calls, implement strict input validation on all user-supplied parameters, and apply vendor patch if available. Consider web application firewall deployment as compensating control.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6629 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data