CVE-2025-10807
BaseFortify
Publication date: 2025-09-22
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-10807 is a SQL injection vulnerability in Campcodes Online Beauty Parlor Management System 1.0, specifically in the file /admin/edit-customer-detailed.php. It occurs due to improper handling of the 'editid' parameter, allowing attackers to manipulate SQL queries. This flaw can be exploited remotely without authentication, potentially compromising the system's confidentiality, integrity, and availability. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to remotely execute arbitrary SQL commands on the affected system, leading to unauthorized access to sensitive data, modification or deletion of data, and potential disruption of system availability. Because it can be exploited without authentication and a public exploit exists, it poses a significant security risk. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable URL path `/admin/edit-customer-detailed.php` and testing the `editid` parameter for SQL injection. Attackers may use Google Dorking with the query `inurl:admin/edit-customer-detailed.php` to identify vulnerable targets. You can use tools like curl or wget to send crafted requests to the URL with various SQL injection payloads in the `editid` parameter to test for vulnerability. For example, a command like `curl -v 'http://targetsite/admin/edit-customer-detailed.php?editid=1'` can be used to check the response, and then try injecting SQL payloads such as `1' OR '1'='1` to observe if the system is vulnerable. [1]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been published for this vulnerability. The recommended immediate step is to replace the affected software with an alternative product. Additionally, restricting access to the vulnerable URL, applying web application firewalls (WAF) to filter malicious input, and monitoring for exploitation attempts can help reduce risk until a patch or fix is available. [1]