CVE-2025-11330
BaseFortify
Publication date: 2025-10-06
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-11330 is a critical SQL injection vulnerability in PHPGurukul Beauty Parlour Management System version 1.1. It exists in the file /admin/sales-reports-detail.php due to improper sanitization and validation of the 'fromdate' and 'todate' parameters. Attackers can manipulate these parameters to inject malicious SQL queries, which are executed by the database without proper filtering. This allows unauthorized access to the database, enabling attackers to retrieve, modify, or delete data remotely without authentication. [1, 2, 3, 4, 5]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive data, data leakage, data modification or deletion, full system compromise, and disruption of business operations. Attackers can remotely execute arbitrary SQL commands, potentially taking full control of the system and compromising its confidentiality, integrity, and availability. [1, 2, 3, 4, 5]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable parameters "fromdate" and "todate" in the /admin/sales-reports-detail.php file for SQL injection. Techniques include sending specially crafted HTTP POST requests with payloads that cause boolean-based or time-based blind SQL injection, such as using MySQL's SLEEP() function to observe response delays. Tools like sqlmap can be used to automate detection. Additionally, searching for the vulnerable URL using Google dorking with the query `inurl:admin/sales-reports-detail.php` can help identify affected targets. Example payloads include: - Boolean-based: '2025-09-30' AND 4240=4240 AND 'LZmS'='LZmS' - Time-based: '2025-09-04' AND (SELECT 9195 FROM (SELECT(SLEEP(5)))PQTQ) AND 'wRho'='wRho' Example command using sqlmap: ``` sqlmap -u "http://target/admin/sales-reports-detail.php" --data="fromdate=2025-09-04&todate=2025-09-30" --risk=3 --level=5 ``` This will test the POST parameters for SQL injection vulnerabilities. [3, 4, 5]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. - Enforce strict input validation and filtering to ensure "fromdate" and "todate" parameters conform to expected date formats. - Minimize database user permissions by avoiding use of high-privilege accounts (e.g., root or admin) for routine database operations. - If possible, replace or update the affected component to a version without this vulnerability. These steps help prevent exploitation by sanitizing inputs and limiting the impact of any potential injection. [3, 4]