CVE-2026-2822
SQL Injection in JeecgBoot Backend Interface Enables Remote Attack
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 |
|---|---|---|
| jeecg | jeecg_boot | to 3.9.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
How can this vulnerability impact me? :
This vulnerability allows remote attackers to execute arbitrary SQL commands on the affected system.
- Unauthorized access to sensitive data.
- Modification or deletion of data, impacting data integrity.
- Potential disruption of system availability.
Because the exploit can be executed remotely without authentication, it poses a significant risk to systems using the affected JeecgBoot versions.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-2822 is a SQL injection vulnerability in JeecgBoot versions up to 3.9.1, specifically in the backend interface at the file path /jeecgboot/sys/dict/loadDict/airag_app,1,create_by.'}, {'type': 'paragraph', 'content': "The vulnerability arises from improper handling of the 'keyword' argument, allowing attackers to manipulate SQL commands due to insufficient neutralization of special characters."}, {'type': 'paragraph', 'content': 'This flaw enables remote attackers to execute arbitrary SQL commands without authentication, potentially compromising the confidentiality, integrity, and availability of the system.'}] [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'The vulnerability exists in the backend interface endpoint `/jeecgboot/sys/dict/loadDict/airag_app,1,create_by` of JeecgBoot versions up to 3.9.1 and involves SQL injection via the `keyword` argument.'}, {'type': 'paragraph', 'content': 'Detection can involve monitoring for unusual or suspicious SQL queries targeting this endpoint, especially those manipulating the `keyword` or `create_by` parameters.'}, {'type': 'paragraph', 'content': 'Since no specific detection commands or tools are provided, general approaches include using web application firewalls (WAF) with SQL injection detection rules, or running manual tests with crafted payloads to check for SQL injection responses.'}, {'type': 'paragraph', 'content': 'Example commands for manual testing might include sending HTTP requests with SQL injection payloads to the vulnerable endpoint, such as using curl:'}, {'type': 'list_item', 'content': 'curl -G \'http://<target>/jeecgboot/sys/dict/loadDict/airag_app,1,create_by\' --data-urlencode "keyword=\' OR \'1\'=\'1"'}, {'type': 'list_item', 'content': 'curl -G \'http://<target>/jeecgboot/sys/dict/loadDict/airag_app,1,create_by\' --data-urlencode "keyword=admin\'--"'}, {'type': 'paragraph', 'content': 'Responses indicating SQL errors or unexpected data may confirm the presence of the vulnerability.'}] [1, 3]
What immediate steps should I take to mitigate this vulnerability?
No specific mitigations or countermeasures have been identified for this vulnerability.
The recommended immediate step is to replace or upgrade the affected component or product to a version that is not vulnerable.
In the absence of a patch, consider restricting access to the vulnerable backend interface, applying web application firewall rules to block SQL injection attempts, and monitoring logs for suspicious activity.