CVE-2025-10402
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 flaw has been found in PHPGurukul Beauty Parlour Management System 1.1. The impacted element is an unknown function of the file /admin/readenq.php. Executing manipulation of the argument delid can lead to sql injection. The attack can be executed remotely. The exploit has been published 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 · moderate confidenceSQL injection vulnerability in PHPGurukul Beauty Parlour Management System 1.1 allows remote attackers to execute arbitrary SQL queries via the `delid` parameter in /admin/readenq.php. The CVSS 9.8 indicates the vulnerability is remotely exploitable with low complexity and no authentication or user interaction required.
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.1CVSS 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.
-
Verify Beauty Parlour Management System 1.1 is installedLocate the application directory (typically in web root) and check for files or a version indicator such as a README, version in footer, or admin/login.php that identifies as PHPGurukul Beauty Parlour Management SystemAffected if The application directory contains PHPGurukul Beauty Parlour Management System files and version 1.1 is present
-
Confirm vulnerable file existsCheck for the presence of /admin/readenq.php file within the web application directory structureAffected if The file /admin/readenq.php exists in the installation
-
Verify web server accessibilityConfirm the web application is accessible over HTTP/HTTPS from a network perspectiveAffected if The application is reachable via network (local or remote)
-
Check admin panel access controlAttempt to access /admin/readenq.php directly without authentication to see if the endpoint responds without requiring loginAffected if The readenq.php endpoint responds without requiring authentication (the CVSS indicates no auth required)
-
Identify delid parameter handlingReview source code of readenq.php to locate where the delid parameter is used in SQL queries, check if it is directly concatenated into SQL statements without prepared statements or parameter bindingAffected if The delid parameter is used in dynamic SQL queries without parameterized queries or input sanitization
The environment is affected if PHPGurukul Beauty Parlour Management System version 1.1 is installed, the file /admin/readenq.php exists, and the application is network-accessible without requiring authentication to access the vulnerable endpoint.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for the `delid` parameter in readenq.php, apply input validation, and restrict access to the admin panel to authorized users. Check vendor for official patches.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10402 — 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-10402 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