CVE-2026-4289
SQL Injection in Tiandy Easy7 Platform Allows Remote Exploit
Publication date: 2026-03-17
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 |
|---|---|---|
| tiandy | easy7_integrated_management_platform | to 7.17.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-4289 is a critical SQL injection vulnerability in the Tiandy Easy7 Integrated Management Platform up to version 7.17.0. It exists in the endpoint /rest/preSetTemplate/getRecByTemplateId, specifically through manipulation of the ID argument.
The vulnerability arises because the ID parameter is not properly sanitized, allowing attackers to inject malicious SQL commands remotely without authentication.
This flaw enables attackers to bypass database security constraints and extract sensitive data such as administrative credentials and system configurations using various SQL injection techniques including Union-based, Boolean-based, and Time-based methods.
The vulnerability has been publicly disclosed, with proof-of-concept exploits available, and the vendor has not provided any patches or mitigations.
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': "This vulnerability can have severe impacts including unauthorized remote access to the system's database."}, {'type': 'list_item', 'content': 'Attackers can extract sensitive information such as administrative credentials and system configurations.'}, {'type': 'list_item', 'content': 'The confidentiality, integrity, and availability of the affected system can be compromised.'}, {'type': 'list_item', 'content': 'Because the exploit requires no authentication and is easy to execute, it increases the risk of widespread attacks.'}, {'type': 'paragraph', 'content': 'Due to the lack of vendor response and patches, affected users may need to consider replacing the product to mitigate risk.'}] [2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability exists in the Tiandy Easy7 Integrated Management Platform endpoint /rest/preSetTemplate/getRecByTemplateId through manipulation of the ID parameter leading to SQL injection.'}, {'type': 'paragraph', 'content': 'Detection can involve monitoring HTTP requests to this endpoint for suspicious or malformed ID parameters that may indicate SQL injection attempts.'}, {'type': 'paragraph', 'content': 'Common detection methods include using web application firewalls (WAF) with SQL injection detection rules or running manual tests with payloads designed to trigger SQL errors.'}, {'type': 'paragraph', 'content': 'Example commands to test for SQL injection might include sending crafted HTTP requests with payloads such as:\n- Using curl to test for SQL injection:\ncurl -X GET "http://<target>/rest/preSetTemplate/getRecByTemplateId?id=1\' OR \'1\'=\'1"\n- Using sqlmap to automate detection:\nsqlmap -u "http://<target>/rest/preSetTemplate/getRecByTemplateId?id=1" --batch'}] [2, 3]
What immediate steps should I take to mitigate this vulnerability?
There are no patches or countermeasures provided by the vendor Tiandy Technologies Co., Ltd. for this vulnerability.
Immediate mitigation steps include restricting access to the vulnerable endpoint, for example by implementing network-level controls such as firewall rules to limit access only to trusted IPs.
Deploying a web application firewall (WAF) with SQL injection detection and prevention capabilities can help block exploitation attempts.
Consider replacing the affected product or upgrading to a version that addresses this vulnerability once available.
Monitoring logs for suspicious activity and applying strict input validation on the ID parameter, if possible, are also recommended.