CVE-2025-10402
BaseFortify
Publication date: 2025-09-14
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-10402 is a critical SQL injection vulnerability in PHPGurukul Beauty Parlour Management System version 1.1, specifically in the /admin/readenq.php file. The vulnerability arises because the 'delid' parameter is not properly sanitized or validated before being used in SQL queries. This allows remote attackers to inject malicious SQL code without authentication, potentially executing arbitrary SQL commands on the database. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to the database, allowing attackers to view, modify, or delete sensitive data. It can compromise the confidentiality, integrity, and availability of the system. Attackers can exploit it remotely without authentication, potentially causing data leakage, data tampering, disruption of services, and full system compromise. [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/readenq.php file for SQL injection. One method is to use a time-based blind SQL injection payload such as: delid=2' RLIKE (SELECT 3003 FROM (SELECT(SLEEP(5)))ZOcS)-- fmOo which causes a delay in the database response if vulnerable. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:admin/readenq.php. These approaches help confirm the presence of the SQL injection flaw. [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, enforcing strict input validation and filtering on the 'delid' parameter to ensure only expected formats are accepted, and minimizing database user privileges by avoiding the use of high-privilege accounts for routine operations. Since no known mitigations are documented, replacing the affected software with an alternative product is also suggested to fully address the vulnerability. [1, 2, 3]