CVE-2025-9933
BaseFortify
Publication date: 2025-09-04
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | beauty_parlour_management_system | 1.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9933 is a critical SQL injection vulnerability in PHPGurukul Beauty Parlour Management System version 1.1. It occurs in the /admin/view-appointment.php file due to improper validation and sanitization of the 'viewid' parameter. This allows attackers to inject malicious SQL queries remotely without authentication, potentially accessing, modifying, or deleting sensitive database information. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to your database, allowing attackers to read sensitive information, manipulate or delete data, and potentially compromise the entire system. It can disrupt business operations, cause data breaches, and lead to loss of data integrity and availability. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'viewid' parameter in the /admin/view-appointment.php file for SQL injection. Example payloads to test include boolean-based blind injections (e.g., viewid=10' AND 3817=3817 AND 'vImz'='vImz), time-based blind injections using MySQL SLEEP function (e.g., viewid=10' AND (SELECT 3932 FROM (SELECT(SLEEP(5)))mwmQ) AND 'mETl'='mETl), and UNION query injections (e.g., viewid=10' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(...),NULL-- -). Automated tools like sqlmap can be used to confirm the vulnerability by targeting the viewid parameter. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering to ensure inputs conform to expected formats, and minimizing database user privileges by avoiding the use of high-privilege accounts for routine database operations. Since no known vendor mitigations exist, replacing the affected product with an alternative solution is also suggested. [2, 3]