dbcve.org
MetacrmApplication · Metasoft

CVE-2025-7873

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-20
Fix available
A fix is available. Upgrade to after 6.4.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 was found in Metasoft 美特软件 MetaCRM up to 6.4.2. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file mcc_login.jsp. The manipulation of the argument workerid 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 · high confidence

SQL injection vulnerability in MetaCRM mcc_login.jsp where the workerid parameter is not properly sanitized before being used in database queries. An attacker can manipulate SQL queries by injecting malicious SQL code through this parameter, potentially allowing unauthorized access to the database, data exfiltration, or complete system compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the workerid parameter. Apply input validation and implement least-privilege database accounts. Deploy a WAF as a temporary compensating control until the code fix is implemented.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MetacrmApplication
Affected:<= 6.4.2

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
High
Integrity
High
Availability
High

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

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 Metasoft Metacrm installation and version
    Locate the Metacrm installation directory and check the version information, typically found in version files, about pages, or the application header/footer. Compare your installed version against the affected range: <= 6.4.2
    Affected if Metasoft Metacrm version 6.4.2 or lower is installed
  2. Locate mcc_login.jsp file
    Search the web application directory for the file mcc_login.jsp. Common paths may include /login/, /auth/, or the root web directory. Verify the file exists in your deployment
    Affected if The file mcc_login.jsp exists in the web application
  3. Examine workerid parameter handling in mcc_login.jsp
    Open mcc_login.jsp in a text editor or decompiler and search for occurrences of 'workerid' parameter usage. Look for how the parameter is retrieved (request.getParameter) and whether it is used directly in SQL queries or passed through proper sanitization/parameterization
    Affected if The workerid parameter is used in SQL queries without parameterized binding or input validation
  4. Verify SQL query construction method
    Review the database query code in mcc_login.jsp. Look for string concatenation or statement building that incorporates the workerid value directly into SQL (e.g., 'SELECT... WHERE workerid=' + workerid) versus using PreparedStatement with parameter placeholders
    Affected if Dynamic SQL construction with direct string concatenation is used for the workerid parameter

You are affected if Metasoft Metacrm version 6.4.2 or lower is installed and the mcc_login.jsp file uses the workerid parameter in SQL queries without parameterized prepared statements.

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
Upgrade available Upgrade to a release after 6.4.2
Interim mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements for the workerid parameter. Apply input validation and implement least-privilege database accounts. Deploy a WAF as a temporary compensating control until the code fix is implemented.

Fix this in Metacrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7873 — 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-2025-7873 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