CVE-2026-2820
SQL Injection in Fujian Smart Platform Enables Remote Exploits
Publication date: 2026-02-20
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 |
|---|---|---|
| fuzhou_yinda_yunchuang_information_technology_co_ltd | smart_integrated_management_platform_system | From 7.0 (inc) to 7.5 (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?
[{'type': 'paragraph', 'content': 'CVE-2026-2820 is a critical SQL injection vulnerability found in Fujian Smart Integrated Management Platform System versions up to 7.5. It exists in the file /Module/CRXT/Controller/XAccessPermissionPlus.ashx and is caused by improper sanitization of the DeviceIDS parameter.'}, {'type': 'paragraph', 'content': "This flaw allows an attacker to inject malicious SQL commands remotely without any authentication, potentially compromising the system's database."}, {'type': 'paragraph', 'content': 'The vulnerability corresponds to CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) and can be exploited easily due to a publicly available proof-of-concept exploit.'}] [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing remote attackers to execute arbitrary SQL queries on your system without authentication.
Such exploitation can lead to unauthorized access to sensitive database information, compromising confidentiality, integrity, and availability of your system.
Because the attack can be launched remotely and easily, it significantly increases the risk of data breaches, data manipulation, or denial of service.
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 can be detected by testing the endpoint /Module/CRXT/Controller/XAccessPermissionPlus.ashx for SQL injection via the DeviceIDS parameter.'}, {'type': 'paragraph', 'content': 'Since a proof-of-concept exploit is publicly available on GitHub, it can be used to verify if the system is vulnerable by sending crafted requests that manipulate the DeviceIDS argument to trigger SQL injection.'}, {'type': 'paragraph', 'content': 'Typical detection commands would involve sending HTTP requests with SQL injection payloads to the vulnerable endpoint and observing the responses for anomalies or time delays indicative of blind SQL injection.'}, {'type': 'list_item', 'content': 'Use curl or similar tools to send requests to the vulnerable endpoint, for example: curl -X GET "http://target/Module/CRXT/Controller/XAccessPermissionPlus.ashx?DeviceIDS=1\' OR \'1\'=\'1"'}, {'type': 'list_item', 'content': 'Use the publicly available proof-of-concept script from the GitHub repository to automate detection.'}] [1, 3, 4]
What immediate steps should I take to mitigate this vulnerability?
No known mitigations or countermeasures have been identified for this vulnerability.
It is suggested to consider replacing the affected product versions (up to 7.5) with a secure alternative or updated version once available.
In the meantime, restricting access to the vulnerable endpoint, implementing web application firewalls (WAF) to detect and block SQL injection attempts, and monitoring network traffic for suspicious activity may help reduce risk.