VulnerabilityPublished 4 Jan 2026Updated 23 Feb 2026

CVE-2025-15442: CRMEB · SQL Injection

Affects CRMEBSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
CRMEB	Affected =5.6.0 =5.6.1	Fixed in–
GitHubcrmeb/CRMEB`pkg:github/crmeb/CRMEB`Other threats	Affected =5.6.0 =5.6.1	Fixed in–

CPE configurations (1)

cpe:2.3:a:crmeb:crmeb:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict access to the /adminapi/export/product_list endpoint to only trusted and necessary administrative users, ideally through network segmentation and firewall rules. 2. Implement strict input validation and sanitization on the cate_id parameter at the application or web server level using web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns. 3. Enforce multi-factor authentication and strong password policies for all administrative accounts to reduce the risk of credential compromise. 4. Monitor logs for unusual queries or access patterns related to the vulnerable endpoint to detect potential exploitation attempts early. 5. If possible, upgrade to a CRMEB version that addresses this vulnerability once available or apply community-developed patches or workarounds. 6. Conduct regular security assessments and code reviews focusing on input handling in CRMEB and similar applications. 7. Limit database user permissions associated with the CRMEB application to the minimum required to reduce the impact of a successful injection.

Description

A vulnerability was determined in CRMEB up to 5.6.1. This vulnerability affects unknown code of the file /adminapi/export/product_list. This manipulation of the argument cate_id causes sql injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The impact of CVE-2025-15442 can be significant for organizations using CRMEB versions 5.6.0 and 5.6.1, especially those with sensitive customer or product data stored in the affected database. Successful exploitation could lead to unauthorized data disclosure, data tampering, or denial of service through database corruption or disruption. Since the vulnerability requires high privilege access, the primary risk involves insider threats or attackers who have already compromised administrative credentials. However, once exploited, attackers could escalate their access or move laterally within the network. This could result in loss of customer trust, regulatory penalties due to data breaches, and operational downtime. The absence of vendor patches means organizations must rely on alternative mitigations, increasing operational overhead and risk exposure. Industries such as e-commerce, retail, and service providers using CRMEB for customer relationship management are particularly vulnerable.

Summary

CVE-2025-15442 identifies a SQL injection vulnerability in the CRMEB application, specifically in versions 5.6.0 and 5.6.1. The vulnerability is located in the /adminapi/export/product_list endpoint, where the cate_id parameter is susceptible to SQL injection due to insufficient input validation or sanitization. An attacker with high privileges can remotely manipulate this parameter to execute arbitrary SQL queries against the backend database. The vulnerability does not require user interaction but does require authenticated access with elevated privileges, which limits the attack vector to insiders or compromised accounts with admin rights. The CVSS 4.0 base score is 5.1, reflecting medium severity, with network attack vector, low complexity, no user interaction, and partial impact on confidentiality, integrity, and availability. The vendor was notified but has not issued a patch or response, and no public exploits have been confirmed in the wild. This vulnerability could allow attackers to extract sensitive data, modify or delete records, or disrupt database operations, depending on the injected payload. The lack of vendor response and patch availability increases the risk for organizations relying on these CRMEB versions.

References

Community reviews

Loading reviews…