CVE-2025-15188
Cross-Site Scripting in Campcodes Admin Search-Invoices.php
Publication date: 2025-12-29
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 | complete_online_beauty_parlor_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Campcodes Complete Online Beauty Parlor Management System 1.0, specifically in the /admin/search-invoices.php file. It involves manipulation of the 'searchdata' argument, which can lead to a cross-site scripting (XSS) attack. This means an attacker can inject malicious scripts that execute in the context of the affected web application. The attack can be launched remotely and the exploit has been publicly disclosed.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to perform cross-site scripting attacks, which may lead to the execution of malicious scripts in the user's browser. This can result in unauthorized actions such as session hijacking, defacement, or redirection to malicious sites. However, the CVSS scores indicate a relatively low severity, with limited impact on confidentiality and availability, but some impact on integrity.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows attackers to execute malicious scripts that can steal sensitive information such as cookies and session tokens, and perform unauthorized actions on behalf of users. This can lead to unauthorized access and potential data breaches, which may violate data protection regulations like GDPR and HIPAA that require safeguarding personal and sensitive information. Therefore, the presence of this vulnerability could negatively impact compliance with such standards by exposing user data to unauthorized parties. [2, 3]
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 file `/admin/search-invoices.php` in the Campcodes Complete Online Beauty Parlor Management System version 1.0 and testing the `searchdata` parameter for cross-site scripting (XSS) injection. One method is to use Google dorking with the query `inurl:admin/search-invoices.php` to identify potentially vulnerable targets. Additionally, testing can be performed by injecting a proof-of-concept payload such as `<script>alert('XSS')</script>` into the `searchdata` parameter and observing if the script executes in the browser. Network or system commands are not explicitly provided, but manual or automated web application scanning tools that test for XSS vulnerabilities on the specified URL and parameter can be used. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps to mitigate this vulnerability include: 1) Properly encoding user inputs before rendering them in the web page to prevent execution of injected scripts (output encoding). 2) Enforcing strict input validation and filtering on the `searchdata` parameter to allow only expected input formats and reject or escape malicious content. 3) Implementing a strict Content Security Policy (CSP) to restrict the sources of executable scripts and prevent unauthorized script execution. 4) Setting `HttpOnly` and `Secure` flags on cookies to protect against theft via JavaScript. 5) Conducting regular security audits to detect and fix XSS and other vulnerabilities promptly. Since no known countermeasures or patches are documented, replacing the affected product with a secure alternative is also suggested. [3, 1, 2]