Quick answers
- Is CVE-2026-15514 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15514 being exploited in the wild.
- How severe is CVE-2026-15514?
- High severity, with a CVSS score of 7.3, published 13 July 2026.
- Which products and versions are affected?
- Metasoft MetaCRM up to 6.4.0 Beta06.
- Is there a fix for CVE-2026-15514?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-15514 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-15514?
- Check whether you run Metasoft MetaCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A SQL injection vulnerability exists in Metasoft MetaCRM versions up to and including 6.4.0 Beta06. The flaw is located within the RPCService.query function of the /customizemt/xkq/rpc.jsp file, which is part of the PHPRPC Remote Call Interface component. The vulnerability is triggered by insufficient sanitization of the 'phprpc_args' argument. A remote, unauthenticated attacker can exploit this by sending specially crafted RPC requests to execute arbitrary SQL queries against the backend database. Public exploit code has been released, increasing the likelihood of active exploitation. As of the advisory date, the vendor has not responded to disclosure attempts, and no official patch is available.
Affected products
- Metasoft 美特软件 MetaCRM up to 6.4.0 Beta06
Timeline
- 2026-07-13: advisory: Initial disclosure by VulDB/NVD
- 2026-07-13: disclosed: Public exploit made available