Skip to main content
CVE-2025-7193VulnerabilityPublished

CVE-2025-7193: itsourcecode Agri-Trading Online Shopping System · SQL Injection

Affects itsourcecode Agri-Trading Online Shopping SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
itsourcecode Agri-Trading Online Shopping SystemAffected
  • =1.0
Fixed in–

AI-suggested

Since no official patches or updates are currently available from the vendor, European organizations should implement the following specific mitigations: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'supplier' parameter in /admin/suppliercontroller.php. 2) Restrict network access to the administrative interface to trusted IP addresses or VPN-only access to reduce exposure. 3) Conduct thorough input validation and sanitization at the application level, if source code access and modification are possible, to neutralize injection payloads. 4) Monitor database logs and application logs for anomalous queries or suspicious activities indicative of injection attempts. 5) Segregate the database with least privilege principles, ensuring the application account has minimal permissions to limit the impact of a successful injection. 6) Prepare incident response plans specific to SQL injection attacks, including data backup and recovery procedures. 7) Engage with the vendor for updates or patches and consider alternative platforms if remediation is delayed.

Description

A vulnerability was found in itsourcecode Agri-Trading Online Shopping System up to 1.0. It has been classified as critical. Affected is an unknown function of the file /admin/suppliercontroller.php. The manipulation of the argument supplier leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…