CVE-2025-10836
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 · uneditedA weakness has been identified in SourceCodester Pet Grooming Management Software 1.0. Affected is an unknown function of the file /admin/print1.php. Executing manipulation of the argument ID can lead to sql injection. The attack can be launched remotely. The exploit has been made available to the public and could be exploited.
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 confidenceA SQL injection vulnerability exists in SourceCodester Pet Grooming Management Software 1.0 within the /admin/print1.php file. The ID parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. The CVSS 9.8 score indicates this vulnerability can be exploited remotely with high impact, potentially allowing database exposure or privilege escalation.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Pet Grooming Management Software installationLocate the web application's document root and verify the presence of the /admin/ directory structure, specifically looking for print1.php in the admin folder.Affected if The file /admin/print1.php exists in the web application directory.
-
Verify the affected versionCheck the application's version number. This is version 1.0 of Mayurik Pet Grooming Management Software. Look for a version file, about page, or metadata that displays the installed version.Affected if The installed version is 1.0.
-
Inspect the vulnerable file for the ID parameterExamine the source code of /admin/print1.php and locate any SQL query that uses the ID parameter without proper parameterization or input sanitization.Affected if The file contains dynamic SQL queries that incorporate the ID parameter directly into SQL statements without prepared statements or escaping.
-
Check web server logs for exploitation attemptsReview access logs for the web server hosting the application. Look for requests to /admin/print1.php that contain SQL injection payloads in the ID parameter, such as single quotes, UNION SELECT, or boolean-based injection patterns.Affected if Suspicious SQL injection patterns are found in requests to /admin/print1.php.
The environment is affected if Pet Grooming Management Software version 1.0 is installed and the /admin/print1.php file contains unsanitized SQL queries using the ID parameter.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement parameterized queries or prepared statements for all database operations involving the ID parameter. Alternatively, use proper input validation and escaping functions if dynamic SQL is unavoidable. Restrict database permissions to the minimum required for the application.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10836 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10836 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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