CVE-2025-10459
BaseFortify
Publication date: 2025-09-15
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-10459 is a critical SQL injection vulnerability in the PHPGurukul Beauty Parlour Management System version 1.1, specifically in the /admin/all-appointment.php file. The vulnerability arises because the 'delid' parameter is not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating the database by reading, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, data leakage, data tampering, full system control by attackers, and potential disruption of services. Since exploitation does not require authentication, attackers can remotely execute arbitrary SQL commands, compromising the confidentiality, integrity, and availability of the system. [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 'delid' parameter in the /admin/all-appointment.php file for SQL injection. A time-based blind SQL injection payload such as `delid=222' RLIKE SLEEP(5)-- jLLy` can be used to observe delays indicating vulnerability. Tools like sqlmap can automate detection by targeting this parameter. Additionally, searching for the vulnerable URL using Google dorking with the query `inurl:admin/all-appointment.php` can help identify affected systems. [1, 2]
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, rigorously validating and filtering all user inputs to ensure they conform to expected formats, and restricting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. Applying secure coding practices to prevent SQL injection and replacing the affected product if possible are also recommended. [1, 2, 3]