CVE-2026-15514
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 · uneditedA weakness has been identified in Metasoft 美特软件 MetaCRM up to 6.4.0 Beta06. This vulnerability affects the function RPCService.query of the file /customizemt/xkq/rpc.jsp of the component PHPRPC Remote Call Interface. Executing a manipulation of the argument phprpc_args can lead to sql injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. 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 confidenceSQL injection vulnerability in Metasoft MetaCRM's PHPRPC Remote Call Interface. The RPCService.query function in /customizemt/xkq/rpc.jsp fails to properly sanitize the phprpc_args parameter, allowing remote attackers to inject malicious SQL queries.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Metasoft MetaCRM installationConfirm that the target system runs Metasoft MetaCRM by checking application files, headers, or error pages that reference the product name.Affected if The system is not running Metasoft MetaCRM, then it is not affected by this specific CVE.
-
Locate the vulnerable RPC endpointCheck for the presence of the file /customizemt/xkq/rpc.jsp in the web root directory. This file contains the RPCService.query function that handles the phprpc_args parameter.Affected if The file /customizemt/xkq/rpc.jsp does not exist on the system, then the vulnerability is not present.
-
Confirm PHPRPC interface is exposedAttempt to access the RPC endpoint directly by sending a request to /customizemt/xkq/rpc.jsp. Verify that the PHPRPC Remote Call Interface is reachable and responding.Affected if The endpoint is not accessible or returns a 404 error, then the attack surface does not exist.
-
Check if query function accepts user inputInspect the RPCService.query function logic within rpc.jsp to determine if the phprprc_args parameter is passed directly to database queries without parameterized handling.Affected if The application uses parameterized queries or prepared statements for all phprpc_args handling, then the SQL injection vulnerability is mitigated.
A system is affected if it runs Metasoft MetaCRM, has the /customizemt/xkq/rpc.jsp file exposed, and does not use parameterized queries when processing the phprpc_args parameter in the RPCService.query function.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement parameterized queries or prepared statements for all database operations in RPCService.query. If no vendor patch is available, consider deploying a WAF rule to block SQL injection patterns in the phprpc_args parameter as a temporary mitigation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15514 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15514 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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