dbcve.org
Beauty Parlour Management SystemApplication · Phpgurukul

CVE-2025-9933

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-04
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 has been found in PHPGurukul Beauty Parlour Management System 1.1. Affected by this issue is some unknown functionality of the file /admin/view-appointment.php. Such manipulation of the argument viewid leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public 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 · high confidence

SQL injection vulnerability in PHPGurukul Beauty Parlour Management System 1.1 allows remote attackers to inject arbitrary SQL queries via the viewid parameter in /admin/view-appointment.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the viewid parameter in view-appointment.php, and audit the entire application 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 the installed version of PHPGurukul Beauty Parlour Management System
    Locate the application directory and check version files, README, or any version identifier within the codebase. Common locations include a version.php file, changelog, or the main index file.
    Affected if The installed version is 1.1 exactly, as this is the only affected version listed.
  2. Verify the vulnerable file exists
    Check if the file /admin/view-appointment.php exists in the web application directory.
    Affected if The file exists, indicating the vulnerable component is present in the environment.
  3. Inspect the view-appointment.php source code for the viewid parameter handling
    Open /admin/view-appointment.php and locate the code handling the 'viewid' parameter. Search for SQL queries that incorporate this parameter directly without using prepared statements or parameter binding.
    Affected if The code shows direct insertion of the 'viewid' parameter into SQL queries without sanitization, parameterized queries, or prepared statements.
  4. Check if user input reaches the vulnerable parameter
    Trace how the 'viewid' parameter is received (via GET or POST) and confirm it flows directly to the database query without validation or escaping.
    Affected if The viewid parameter is taken directly from user input and used in the SQL query without any input validation or escaping.
  5. Confirm admin panel access to the vulnerable endpoint
    Determine if the /admin/ directory is accessible without authentication or if authentication can be bypassed, as the attack requires reaching view-appointment.php.
    Affected if The admin panel or specifically view-appointment.php is accessible, allowing an attacker to supply the malicious viewid parameter.

If PHPGurukul Beauty Parlour Management System version 1.1 is installed and the /admin/view-appointment.php file contains unparameterized SQL queries using the 'viewid' parameter, the environment is affected by CVE-2025-9933.

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 for the viewid parameter in view-appointment.php, and audit the entire application for similar SQL injection vulnerabilities.

Fix this in Beauty Parlour Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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