CVE-2025-9919
BaseFortify
Publication date: 2025-09-03
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 |
|---|---|---|
| 1000projects | beauty_parlour_management_system | 1.0 |
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-9919 is a critical SQL injection vulnerability in the Beauty Parlour Management System 1.0, specifically in the /admin/bwdates-reports-details.php file. The vulnerability occurs because the 'fromdate' and 'todate' parameters are not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially accessing, modifying, or deleting sensitive data in the database. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to the database, allowing attackers to retrieve sensitive information, alter or delete data, and potentially disrupt the system's availability. Exploitation can result in data leakage, data tampering, and full system compromise or service disruption, all without requiring any authentication. [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 vulnerable parameter 'fromdate' in the URL /admin/bwdates-reports-details.php for SQL injection. Example commands include using time-based blind SQL injection payloads such as: curl -X POST -d "fromdate=1' AND (SELECT SLEEP(5)) AND 'ImUS'='ImUS" -d "todate=1" -d "submit=submit" http://target/admin/bwdates-reports-details.php or using sqlmap to automate detection: sqlmap -u "http://target/admin/bwdates-reports-details.php" --data="fromdate=1&todate=1&submit=submit" --risk=3 --level=5 --batch. Additionally, Google dorking with the query inurl:admin/bwdates-reports-details.php can help identify potentially vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'fromdate' and 'todate' parameters to ensure they conform to expected formats, and minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. Regular security audits should be conducted to detect and remediate vulnerabilities promptly. If possible, replacing the affected software with a secure alternative is recommended. [2, 3]