dbcve.org
Dairy Farm Shop Management SystemApplication · Phpgurukul

CVE-2025-5574

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 classified as critical has been found in PHPGurukul Dairy Farm Shop Management System 1.3. This affects an unknown part of the file /add-company.php. The manipulation of the argument companyname leads to sql injection. It is possible to initiate the attack 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 companyname parameter in /add-company.php. The application fails to properly sanitize user input before using it in database queries, enabling attackers to manipulate SQL statements, potentially exfiltrating data, modifying database contents, or escalating privileges.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) and implement proper input validation on the companyname parameter. Apply least-privilege principles to database accounts to limit impact of successful exploitation.

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 PHPGurukul Dairy Farm Shop Management System is installed
    Check for the presence of the application files in the web server root directory. Common paths include /var/www/html/, /htdocs/, or C:\inetpub\wwwroot\. Look for files such as index.php, header.php, or the /add-company.php file mentioned in the CVE.
    Affected if The application files are found on the server
  2. Verify the exact version is 1.3
    Inspect the application for a version identifier. Check README.txt, version.php, or any about/version page within the application. Compare the installed version against the affected range: version 1.3.
    Affected if The installed version is exactly 1.3
  3. Confirm the vulnerable file exists
    Locate the file /add-company.php in the web application directory. This is the specific file containing the vulnerable code that processes the companyname parameter.
    Affected if The file add-company.php exists in the application
  4. Check if the add-company functionality is accessible
    Attempt to access the add-company.php endpoint via HTTP/HTTPS to determine if the feature is enabled and reachable. For example: GET /add-company.php or /dairy-farm-shop/add-company.php depending on installation path.
    Affected if The endpoint returns a valid page (200 OK) indicating the feature is accessible
  5. Inspect the source code for dynamic SQL usage
    Examine the add-company.php file source code. Look for SQL queries that concatenate or embed the companyname parameter directly into query strings without using parameterized queries or prepared statements.
    Affected if The code constructs SQL queries using string concatenation with the companyname parameter rather than bound parameters

A user is affected if they are running PHPGurukul Dairy Farm Shop Management System version 1.3 with the add-company.php feature accessible and the code contains unsanitized SQL query construction using the companyname parameter.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries (prepared statements) and implement proper input validation on the companyname parameter. Apply least-privilege principles to database accounts to limit impact of successful exploitation.

Recommended fix Moderate confidence

Check vendor for version > 1.3 (no specific fixed version named in source material)

  1. Check PHPGurukul's official website (phpgurukul.com) or their GitHub repository for the latest version of Dairy Farm Shop Management System
  2. If a version newer than 1.3 is available, download and install it to obtain the SQL injection fix
  3. If no newer version is available, apply parameterized queries (prepared statements) to the /add-company.php file for the companyname parameter
  4. Alternatively, implement input validation and output encoding for the companyname field before database queries
  5. Ensure the web server runs with minimal database privileges to limit SQL injection impact
  6. Apply web application firewall (WAF) rules as an interim mitigation if immediate patching is not possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dairy Farm Shop Management 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-2025-5574 — 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-2025-5574 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