dbcve.org
Pet Grooming Management SoftwareApplication · Mayurik

CVE-2025-10598

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-17
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 was identified in SourceCodester Pet Grooming Management Software 1.0. This issue affects some unknown processing of the file /admin/search_product.php. Such manipulation of the argument group_id leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might 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 SourceCodester Pet Grooming Management Software 1.0's /admin/search_product.php file. The group_id parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. With a CVSS of 9.8, this critical flaw can lead to complete database compromise, including unauthorized data exposure, modification, or deletion.

MitigationImplement parameterized queries (prepared statements) for all SQL queries using the group_id parameter, or apply proper input validation and escaping. If a patched version is available from the vendor, upgrade immediately.

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
Pet Grooming Management SoftwareApplication
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. Identify installed application and version
    Locate the SourceCodester/Mayurik Pet Grooming Management Software installation. Check for version indicators in source files, changelogs, or a version.php file. Compare the installed version to 1.0.
    Affected if The installed version is 1.0 and is the SourceCodester Pet Grooming Management Software.
  2. Locate vulnerable file
    Search the web root directory for the file /admin/search_product.php. This file should exist in the admin directory of the application.
    Affected if The file /admin/search_product.php exists in the application installation.
  3. Verify group_id parameter handling
    Open /admin/search_product.php and inspect how the group_id parameter is handled. Look for direct use of $_GET['group_id'] or $_POST['group_id'] in SQL queries without proper sanitization, prepared statements, or parameter binding.
    Affected if The group_id parameter is used directly in SQL queries without prepared statements, parameter binding, or input sanitization functions.
  4. Test for SQL injection vulnerability
    With authorization, send a crafted request to /admin/search_product.php with group_id parameter containing SQL injection payloads (e.g., group_id=1' OR '1'='1). Observe if the application returns unexpected database errors or altered query results.
    Affected if The application returns SQL syntax errors or responds differently to injection payloads, indicating unsanitized input is executed as SQL.

If the Pet Grooming Management Software version 1.0 is installed and the /admin/search_product.php file contains direct use of the group_id parameter in SQL queries without prepared statements, the environment is affected by this CVE.

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

Implement parameterized queries (prepared statements) for all SQL queries using the group_id parameter, or apply proper input validation and escaping. If a patched version is available from the vendor, upgrade immediately.

Fix this in Pet Grooming Management Software Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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