VulnerabilityPublished 14 Jul 2025

CVE-2025-7590: PHPGurukul Dairy Farm Shop Management System · SQL Injection

Affects PHPGurukul Dairy Farm Shop Management SystemSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PHPGurukul Dairy Farm Shop Management System	Affected =1.3	Fixed in–

AI-suggested

Immediate code review and sanitization: Organizations should audit the edit-category.php file and any other input handling code to ensure proper parameter validation and use of parameterized queries or prepared statements to prevent SQL injection.
Implement Web Application Firewall (WAF) rules: Deploy WAFs with custom rules to detect and block suspicious SQL injection payloads targeting the 'categorycode' parameter.
Restrict database permissions: Limit the database user privileges used by the application to only necessary operations, minimizing potential damage from injection attacks.
Monitor logs and alerts: Enable detailed logging of web application requests and database queries to detect anomalous activities indicative of exploitation attempts.
Patch management: Engage with PHPGurukul or community resources to obtain or develop patches addressing this vulnerability. Until official patches are available, consider temporary mitigations such as disabling the vulnerable functionality if feasible.
Network segmentation: Isolate the affected application servers from critical internal networks to reduce lateral movement risk if compromise occurs.

Description

A vulnerability, which was classified as critical, has been found in PHPGurukul Dairy Farm Shop Management System 1.3. This issue affects some unknown processing of the file edit-category.php. The manipulation of the argument categorycode leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the PHPGurukul Dairy Farm Shop Management System version 1.3, this vulnerability could lead to unauthorized access or modification of database records related to product categories. Although the system targets dairy farm shop management, compromised data integrity could disrupt inventory management, pricing, and sales reporting, potentially causing operational disruptions and financial losses. Confidential customer or supplier data exposure appears limited based on available information, but any data manipulation could undermine trust and compliance with data protection regulations such as GDPR. The medium severity rating suggests the impact is moderate; however, organizations relying heavily on this system for critical business functions may experience more significant operational impacts. The absence of known exploits reduces immediate risk, but the public disclosure increases the likelihood of future exploitation attempts.

Summary

CVE-2025-7590 is a SQL Injection vulnerability identified in version 1.3 of the PHPGurukul Dairy Farm Shop Management System, specifically within the edit-category.php file. The vulnerability arises from improper sanitization or validation of the 'categorycode' parameter, which is directly used in SQL queries. This flaw allows an unauthenticated remote attacker to inject malicious SQL code, potentially manipulating the database queries executed by the application. The vulnerability does not require user interaction or authentication, increasing the risk of exploitation. Although the CVSS 4.0 score rates this vulnerability as medium (5.3), the attack vector is network-based with low attack complexity and no privileges or user interaction needed, indicating a relatively straightforward exploitation path. The impact on confidentiality, integrity, and availability is limited (low), suggesting that while the attacker can manipulate some data, the scope and severity of damage are constrained. No known exploits are currently reported in the wild, and no official patches have been released yet. The vulnerability disclosure is recent, with public details available since July 14, 2025.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2025, 09:31 UTC

Technical details

References

Community reviews

Related threats