CVE-2025-11288
BaseFortify
Publication date: 2025-10-05
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 |
|---|---|---|
| crmeb | crmeb | to 5.6 (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-11288 is a SQL injection vulnerability in CRMEB versions up to 5.6, specifically in the GET parameter 'cate_id' of the /adminapi/product/product endpoint. The vulnerability occurs because the 'cate_id' parameter is not properly sanitized before being used in SQL queries, allowing attackers to manipulate the SQL commands executed by the backend database. This can be exploited remotely without authentication, enabling attackers to execute arbitrary SQL commands, potentially leading to unauthorized data access or modification. [1, 2]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to disclosure of sensitive database information such as database names, table names, user credentials, API keys, and configuration data. Attackers can manipulate SQL queries to extract or alter data, potentially causing data exfiltration and further compromise of the application. The vulnerability affects the confidentiality, integrity, and availability of the system, and because it can be exploited remotely without authentication, it poses a significant security risk. [1, 2]
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 endpoint with the GET parameter cate_id for SQL injection. Automated tools like sqlmap can be used to confirm the injection, using payloads such as syntax error probes (e.g., cate_id=%E9%8E%88%27%22%5C%28) and MySQL error-based payloads like AND updatexml(1,concat(0x7e,(select database()),0x7e),1). Example command with sqlmap: sqlmap -u "http://target/adminapi/product/product?cate_id=1" --batch --dbms=mysql --technique=BE --level=5 --risk=3. Monitoring for SQL errors or behavioral differences in responses when manipulating cate_id can also indicate the vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include validating and coercing the cate_id parameter to an integer on the server side, rejecting any non-numeric input. Use parameterized queries or prepared statements instead of string concatenation for SQL queries. Disable detailed SQL error messages in production environments and log errors internally. Enforce least-privilege access controls on the database and admin APIs. Additionally, implement input sanitization and deploy Web Application Firewall (WAF) rules to block SQL injection patterns and monitor for anomalous queries. If possible, consider replacing the affected CRMEB product version as no official patches are available. [1, 2]