dbcve.org
Beauty Parlour Management SystemApplication · Phpgurukul

CVE-2025-10403

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-14
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. This affects an unknown function of the file /admin/view-enquiry.php. The manipulation of the argument viewid leads to sql injection. The attack is possible to be carried out 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 · moderate confidence

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

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries, implement strict input validation on the viewid parameter, and apply the principle of least privilege to database accounts.

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
    Locate the application files on the web server. Check for typical installation directories such as /var/www/html, /www/html, or C:\xampp\htdocs. Look for files or directories containing 'beauty-parlour' or 'parlour' in the name.
    Affected if The application is present on the server
  2. Verify the installed version is 1.1
    Check version information in the application. Look for a version.php file, README file, or footer/installation files that typically display the version. Compare the found version against the affected range (= 1.1).
    Affected if The installed version is exactly 1.1
  3. Locate the vulnerable file
    Navigate to the /admin directory and confirm that view-enquiry.php exists. The full path is typically /admin/view-enquiry.php relative to the application root.
    Affected if The file /admin/view-enquiry.php exists in the installation
  4. Check if admin panel is accessible
    Attempt to access the admin login page at /admin/ or determine if the admin section is exposed. The vulnerability requires access to the admin functionality.
    Affected if The admin panel endpoint is accessible without additional authentication restrictions or authentication has been bypassed
  5. Inspect the viewid parameter usage in view-enquiry.php
    Open /admin/view-enquiry.php and examine how the viewid parameter is handled. Search for $_GET['viewid'] or $_REQUEST['viewid'] usage in SQL queries without prepare(), bindParam(), or input sanitization functions.
    Affected if The viewid parameter is used directly in SQL queries without prepared statements or sanitization

The environment is affected if PHPGurukul Beauty Parlour Management System version 1.1 is installed, the file /admin/view-enquiry.php exists, and the viewid parameter is processed in SQL queries without parameterized queries or input validation.

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 prepared statements/parameterized queries, implement strict input validation on the viewid parameter, and apply the principle of least privilege to database accounts.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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