CVE-2026-2865
SQL Injection in itsourcecode Agri-Trading productcontroller.php Allows Remote Exploit
Publication date: 2026-02-21
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 |
|---|---|---|
| adonesevangelista | agri-trading_online_shopping_system | 1.0 |
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?
[{'type': 'paragraph', 'content': "CVE-2026-2865 is a vulnerability in the itsourcecode Agri-Trading Online Shopping System version 1.0, specifically in the file admin/productcontroller.php. It involves SQL Injection caused by improper handling and sanitization of user input in the 'product' parameter during HTTP POST requests."}, {'type': 'paragraph', 'content': 'This flaw allows remote attackers to send crafted POST requests that manipulate SQL commands, enabling unauthorized database access and modification. The vulnerability also includes broken access control due to lack of authentication and session validation, allowing attackers to bypass security checks and perform administrative actions without credentials.'}, {'type': 'list_item', 'content': "Improper input sanitization in the 'product' parameter."}, {'type': 'list_item', 'content': 'Remote exploitation via HTTP POST requests without authentication.'}, {'type': 'list_item', 'content': 'Broken access control due to missing session validation.'}] [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the backend database, allowing attackers to exfiltrate sensitive data and modify product records.
Attackers can perform administrative actions such as adding, updating, or deleting product data without valid credentials, potentially disrupting service and compromising system integrity.
- Unauthorized database access and data exfiltration.
- Modification or tampering of product records.
- Potential full administrative control over product data.
- Risk of service disruption and loss of business continuity.
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 monitoring for HTTP POST requests targeting the vulnerable endpoint `admin/productcontroller.php` with suspicious or crafted payloads in the `product` parameter that may indicate SQL injection attempts.'}, {'type': 'paragraph', 'content': 'One detection method is to use web application firewall (WAF) logs or intrusion detection systems (IDS) to identify unusual POST requests containing SQL syntax or commands.'}, {'type': 'paragraph', 'content': 'Additionally, attackers can be identified by searching for access attempts using Google dorking queries such as `inurl:admin/productcontroller.php` to find exposed vulnerable endpoints.'}, {'type': 'paragraph', 'content': 'Suggested commands for detection include using tools like curl or wget to simulate POST requests with SQL injection payloads to test the endpoint, for example:'}, {'type': 'list_item', 'content': 'curl -X POST -d "product=\' OR \'1\'=\'1" http://targetsite/admin/productcontroller.php'}, {'type': 'list_item', 'content': 'curl -X POST -d "product=\'; SLEEP(5); -- " http://targetsite/admin/productcontroller.php'}, {'type': 'paragraph', 'content': 'Monitoring server logs for abnormal query execution times or error messages related to SQL syntax errors can also help detect exploitation attempts.'}] [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input.
Enforce strict input validation and filtering on the `product` parameter to ensure only expected data formats are accepted.
Implement robust session management and authentication checks to verify user identity before processing sensitive requests, preventing unauthorized access.
Minimize database user permissions by avoiding the use of high-privilege accounts for routine operations to limit the impact of a potential exploit.
Conduct regular security audits and code reviews to detect and remediate vulnerabilities promptly.
If immediate code fixes are not possible, consider restricting access to the vulnerable endpoint via network controls such as firewalls or IP whitelisting.