CVE-2025-11664
BaseFortify
Publication date: 2025-10-13
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 |
|---|---|---|
| campcodes | online_beauty_parlor_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-11664 is a critical SQL injection vulnerability in version 1.0 of the Complete Online Beauty Parlor Management System, specifically in the /admin/search-appointment.php file. It occurs because the 'searchdata' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely, potentially manipulating database queries to access, modify, or delete data without authorization. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive information, modification or deletion of data, and disruption of service availability. Attackers can gain comprehensive control over the system's database, compromising confidentiality, integrity, and availability. The attack can be launched remotely and does not require authentication, making it particularly severe. [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 'searchdata' parameter in the /admin/search-appointment.php file for SQL injection. One method is to use time-based blind SQL injection payloads such as: searchdata=11' AND (SELECT 8341 FROM (SELECT(SLEEP(5)))gEXj) AND 'yyqj'='yyqj&search= which causes a delay in the database response if vulnerable. Another approach is to use UNION-based SQL injection payloads to extract data, for example: searchdata=11' UNION ALL SELECT NULL,NULL,NULL,NULL,CONCAT(0x717a716a71,0x4c4d6c6d70476e795665774366416e6257615a6142766e6765695274527476665466426a6e6b6259,0x71716b7671),NULL,NULL,NULL,NULL,NULL,NULL,NULL-- -&search= Additionally, automated tools like sqlmap can be used to confirm and enumerate the vulnerability by targeting the 'searchdata' parameter. A simple command example using sqlmap would be: sqlmap -u "http://target/admin/search-appointment.php?searchdata=11" --delay=5 --technique=T This tests for time-based SQL injection by injecting payloads and observing delays. [1]
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 on the 'searchdata' parameter to ensure inputs conform to expected formats. - Minimize database user privileges by avoiding use of high-privilege accounts (such as root or admin) for routine database operations. - Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. Applying these mitigations immediately is essential to protect system security and maintain data integrity. [1]