Dairy Farm Shop Management SystemApplication · Phpgurukul

CVE-2025-5576

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-04
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, 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 /bwdate-report-details.php. The manipulation of the argument fromdate/todate leads to sql injection. The attack may 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 PHPGurukul Dairy Farm Shop Management System 1.3 allows remote attackers to inject malicious SQL queries via the fromdate and todate parameters in /bwdate-report-details.php. The application fails to properly sanitize user input before using it in database queries, enabling attackers to manipulate query logic, extract sensitive data, or potentially execute arbitrary commands.

MitigationImmediate remediation requires replacing dynamic SQL queries with parameterized queries or prepared statements in /bwdate-report-details.php for both fromdate and todate parameters. Until the patch is applied, network-level web application firewall rules can provide temporary protection.

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
Dairy Farm Shop Management SystemApplication
Affected:= 1.3

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 the installed version of PHPGurukul Dairy Farm Shop Management System
    Locate and inspect version files, README files, or check the admin dashboard for the software version. Compare your installed version to the affected range (= 1.3).
    Affected if The installed version is exactly 1.3
  2. Verify the vulnerable script exists in the webroot
    Check for the presence of the file bwdate-report-details.php in the web-accessible directory. This file handles date-based reporting functionality.
    Affected if The file /bwdate-report-details.php exists on the server and is web-accessible
  3. Confirm the application accepts date parameters without input validation
    Review the source code of bwdate-report-details.php to verify whether the fromdate and todate parameters are directly used in SQL queries without prepared statements or input sanitization.
    Affected if The fromdate and todate parameters are handled in SQL queries without parameterized queries or sanitization functions
  4. Check if the web application is exposed to untrusted networks
    Determine if the web server hosting this application is accessible from the internet or untrusted internal networks.
    Affected if The application is reachable remotely and the vulnerable endpoint is exposed

You are affected if you are running version 1.3 of PHPGurukul Dairy Farm Shop Management System and the bwdate-report-details.php file is present and accessible, as the fromdate and todate parameters lack SQL injection protection.

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

Immediate remediation requires replacing dynamic SQL queries with parameterized queries or prepared statements in /bwdate-report-details.php for both fromdate and todate parameters. Until the patch is applied, network-level web application firewall rules can provide temporary protection.

Fix this in Dairy Farm Shop Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5576 — 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-5576 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