dbcve.org
Agri Trading Online Shopping SystemApplication · Adonesevangelista

CVE-2026-2865

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in itsourcecode Agri-Trading Online Shopping System 1.0. This impacts an unknown function of the file admin/productcontroller.php of the component HTTP POST Request Handler. Performing a manipulation of the argument Product results in sql injection. The attack may be initiated remotely. The exploit has been made public and could be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in itsourcecode Agri-Trading Online Shopping System 1.0's admin/productcontroller.php. The 'Product' parameter in HTTP POST requests is not properly sanitized, allowing attackers to inject arbitrary SQL queries. The 9.8 CVSS score indicates the vulnerability is exploitable without authentication and leads to complete system compromise.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) in productcontroller.php for the Product parameter. Validate and sanitize all user inputs before database queries. Apply the principle of least privilege to database accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Agri Trading Online Shopping SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the application installation
    Search for the Agri-Trading Online Shopping System files on the web server, typically in the web root directory. Look for directories containing 'agri-trading', 'agritrading', or the vendor name 'itsourcecode'.
    Affected if The application files are found on the server in a web-accessible directory.
  2. Confirm the installed version
    Check for version information in the application, typically found in a README file, version file, or within the main index.php or configuration files. Compare the version number to the affected version 1.0.
    Affected if The installed version is 1.0.
  3. Verify the vulnerable file exists
    Locate the file admin/productcontroller.php within the application installation directory. This file handles Product-related operations and contains the vulnerable code path.
    Affected if The file admin/productcontroller.php exists in the application structure.
  4. Check for unauthenticated access to admin panel
    Attempt to access the admin directory directly via HTTP/HTTPS without authentication. The vulnerability is exploitable without credentials, so determine if the admin interface is exposed to unauthenticated users.
    Affected if The admin/productcontroller.php endpoint is reachable without authentication.
  5. Inspect the Product parameter handling
    Review the source code of admin/productcontroller.php and locate the code that processes the 'Product' parameter from HTTP POST requests. Look for dynamic SQL query construction where the Product parameter is directly concatenated into the query string.
    Affected if The Product parameter is used in a SQL query without parameterized queries or input sanitization.

A user is affected if the Agri-Trading Online Shopping System version 1.0 is installed, the file admin/productcontroller.php exists, and the application is accessible with the vulnerable Product parameter handling present in the code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries (prepared statements) in productcontroller.php for the Product parameter. Validate and sanitize all user inputs before database queries. Apply the principle of least privilege to database accounts.

Fix this in Agri Trading Online Shopping System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2865 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data