Agri Trading Online Shopping SystemApplication · Adonesevangelista

CVE-2025-6489

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-22
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 has been found in itsourcecode Agri-Trading Online Shopping System 1.0 and classified as critical. This vulnerability affects unknown code of the file /transactionsave.php. The manipulation of the argument del leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may 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 allows remote attackers to inject malicious SQL queries via the 'del' parameter in the /transactionsave.php file. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to unauthorized data access, modification, or full database compromise.

MitigationImmediately implement prepared statements/parameterized queries for the 'del' parameter in transactionsave.php. Restrict network access to the affected system until the patch is applied, given the public exploit availability and critical CVSS score.

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. Confirm product installation
    Identify if itsourcecode Agri-Trading Online Shopping System is deployed by checking the web root directory for the application files or reviewing installed web applications.
    Affected if The application is installed and accessible on the server.
  2. Verify application version
    Check the application version by reviewing any version files, README files, or meta information within the Agri-Trading Online Shopping System installation directory.
    Affected if Version is 1.0.
  3. Locate vulnerable script
    Search for the presence of transactionsave.php in the web application's directory structure, typically found in the web root or a main application folder.
    Affected if transactionsave.php exists in the application.
  4. Inspect the del parameter handling
    Open transactionsave.php and examine how the 'del' parameter is processed. Look for SQL queries that incorporate the 'del' parameter directly into the query string without using prepared statements or parameter binding.
    Affected if The 'del' parameter is used in a dynamic SQL query without parameterized queries or input sanitization.
  5. Review database user privileges
    If the application uses a database service, review the database user configured for the application to determine if it has excess privileges beyond what the application requires.
    Affected if The database user has administrative or elevated privileges that could be exploited.

You are affected if the Agri-Trading Online Shopping System version 1.0 is installed, transactionsave.php exists, and the 'del' parameter is handled in SQL queries without parameterized prepared statements.

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

Immediately implement prepared statements/parameterized queries for the 'del' parameter in transactionsave.php. Restrict network access to the affected system until the patch is applied, given the public exploit availability and critical CVSS score.

Fix this in Agri Trading Online Shopping System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-6489 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