CVE-2025-15443
SQL Injection in CRMEB /adminapi/product_export Allows Remote Exploit
Publication date: 2026-01-04
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | crmeb | to 5.6.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-15443 is a SQL injection vulnerability in CRMEB versions up to 5.6.1. It occurs in the /adminapi/product/product_export endpoint, where the cate_id parameter is improperly handled, allowing an attacker to inject malicious SQL commands. This vulnerability requires authentication with backend access and can be exploited remotely. The exploit is publicly available, and the vulnerability affects the confidentiality, integrity, and availability of the system. [2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to severe impacts including data leakage, privilege escalation, and complete compromise of the database. It affects the confidentiality, integrity, and availability of the affected system, potentially allowing attackers to execute arbitrary SQL queries and manipulate or access sensitive data. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `/adminapi/product/product_export` endpoint for SQL injection via the `cate_id` parameter. Since the exploit is publicly available as a proof-of-concept on GitHub, you can use tools like curl or specialized SQL injection testing tools to send crafted requests to this endpoint and observe for SQL errors or unexpected behavior. For example, a command using curl might be: curl -X POST 'http://target/adminapi/product/product_export' -d 'cate_id=1 OR 1=1' -H 'Authorization: Bearer <token>' (assuming authentication is required). Monitoring logs for unusual SQL errors or unexpected database responses related to this endpoint can also help detect exploitation attempts. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint `/adminapi/product/product_export` to only trusted and authenticated users, implementing strict input validation and sanitization on the `cate_id` parameter, and monitoring for suspicious activity. Since no patches or vendor responses are available, consider disabling or replacing the affected component if possible. Applying Web Application Firewall (WAF) rules to block SQL injection patterns targeting this endpoint can also help reduce risk. [3]