dbcve.org
Beauty Parlour Management SystemApplication · Phpgurukul

CVE-2025-11415

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-07
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 PHPGurukul Beauty Parlour Management System 1.1. Affected by this issue is some unknown functionality of the file /admin/customer-list.php. Such manipulation of the argument delid leads to sql injection. It is possible to launch the attack 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 PHPGurukul Beauty Parlour Management System 1.1 allows remote attackers to inject malicious SQL queries through the delid parameter in /admin/customer-list.php. This could enable unauthorized database access, data exfiltration, or potentially remote code execution depending on database configuration.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in customer-list.php, apply input validation on the delid parameter, and audit other admin pages for similar SQL injection vulnerabilities.

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
Beauty Parlour Management SystemApplication
Affected:= 1.1

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 version of Beauty Parlour Management System
    Locate any version file or check the main index page for version disclosure. Common paths include /admin/ or the root directory for version.txt or version.php. Alternatively, check the page source or error messages for version information.
    Affected if The installed version is exactly 1.1 (note: other versions may not be affected)
  2. Verify the vulnerable PHP file exists
    Check if /admin/customer-list.php exists in the web root directory of the application. Use file system inspection or an HTTP request to confirm the file is present.
    Affected if The file /admin/customer-list.php exists in the deployed application
  3. Confirm the delid parameter is processed by the application
    Review the source code of customer-list.php and locate where the delid parameter is used in SQL queries. Search for GET/POST parameter handling around the delid variable.
    Affected if The delid parameter is used directly in SQL queries without prepared statements or parameterization
  4. Check if the admin interface is accessible
    Attempt to access /admin/customer-list.php via HTTP. If the page loads without authentication errors, the endpoint is reachable.
    Affected if The /admin/customer-list.php page is accessible without requiring authentication or with valid admin credentials
  5. Inspect the SQL query construction in the vulnerable file
    Open customer-list.php and examine the code around the delid parameter. Look for SQL statements that concatenate or embed the delid parameter directly into queries.
    Affected if The delid parameter is concatenated into SQL queries without sanitization or prepared statement usage

You are affected if the system is PHPGurukul Beauty Parlour Management System version 1.1, the file /admin/customer-list.php exists, and the delid parameter is processed by that file without parameterized queries.

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

Replace dynamic SQL queries with parameterized queries/prepared statements in customer-list.php, apply input validation on the delid parameter, and audit other admin pages for similar SQL injection vulnerabilities.

Fix this in Beauty Parlour Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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