dbcve.org
Beauty Parlour Management SystemApplication · Phpgurukul

CVE-2025-11505

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-08
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. Impacted is an unknown function of the file /admin/new-appointment.php. The manipulation of the argument delid leads to sql injection. It is possible to initiate 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 at /admin/new-appointment.php. The 'delid' parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL commands. A public exploit exists, and the critical CVSS score of 9.8 indicates potential for complete system compromise.

MitigationImplement parameterized queries or prepared statements for all database operations involving the delid parameter. Apply input validation and escaping, then conduct a full code audit for additional 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. Confirm PHPGurukul Beauty Parlour Management System is installed
    Identify the application by checking for typical installation directories or by accessing the homepage and inspecting the page source for 'Beauty Parlour Management System' or 'PHPGurukul' branding
    Affected if The application is present on the server
  2. Verify the installed version is 1.1
    Check the application version by reviewing any version file, footer text, or admin dashboard about section. Compare against the affected version range
    Affected if The installed version is exactly 1.1
  3. Locate the vulnerable script
    Check if the file /admin/new-appointment.php exists in the web root directory
    Affected if The file /admin/new-appointment.php is present on the server
  4. Verify admin interface is accessible
    Attempt to access the /admin/ directory or login page to confirm the administrative interface is reachable
    Affected if The admin panel is accessible without additional authentication barriers
  5. Inspect the delid parameter handling
    Review the source code of /admin/new-appointment.php and search for any usage of the 'delid' parameter in database queries without prepared statements
    Affected if The 'delid' parameter is used in SQL queries without parameterization

You are affected if PHPGurukul Beauty Parlour Management System version 1.1 is installed, the file /admin/new-appointment.php exists, and the delid parameter is handled in SQL queries without proper sanitization.

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

Implement parameterized queries or prepared statements for all database operations involving the delid parameter. Apply input validation and escaping, then conduct a full code audit for additional SQL injection vulnerabilities.

Recommended fix Moderate confidence

Contact PHPGurukul for latest patched version (version > 1.1)

  1. 1. Contact PHPGurukul official support channels to confirm if a patched version of Beauty Parlour Management System is available beyond version 1.1
  2. 2. If a newer version exists, download it from the official phpgurukul.com source only (do not use third-party mirrors)
  3. 3. Before upgrading, perform a full backup of the existing application database and files
  4. 4. Review the new version's changelog or release notes to confirm SQL injection fixes are included
  5. 5. Deploy the upgraded version in a staging environment first
  6. 6. Test the /admin/new-appointment.php functionality, particularly any operations using the delid parameter
  7. 7. After testing, deploy the upgrade to production
  8. 8. If no upgrade is available from the vendor, consider deploying a WAF (Web Application Firewall) rule to filter SQL injection attempts on the delid parameter
Caveat Minor - review any database schema changes between versions during staging testing

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

Fix this in Beauty Parlour Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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