CVE-2025-14991
Unknown Unknown - Not Provided
Cross-Site Scripting in Campcodes Beauty Parlor Admin Panel

Publication date: 2025-12-21

Last updated on: 2026-04-29

Assigner: VulDB

Description
A weakness has been identified in Campcodes Complete Online Beauty Parlor Management System 1.0. The affected element is an unknown function of the file /admin/bwdates-reports-details.php. Executing a manipulation of the argument fromdate can lead to cross site scripting. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-21
Last Modified
2026-04-29
Generated
2026-05-06
AI Q&A
2025-12-21
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
campcodes complete_online_beauty_parlor_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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?

CVE-2025-14991 is a cross-site scripting (XSS) vulnerability in Campcodes Complete Online Beauty Parlor Management System version 1.0. It exists in the file /admin/bwdates-reports-details.php, specifically in the handling of the 'fromdate' parameter. The system does not properly validate or encode this user input, allowing attackers to inject malicious JavaScript code that executes in the victim's browser. This can be exploited remotely but requires some user interaction and an enhanced level of authentication. The vulnerability compromises data integrity by enabling execution of malicious scripts within the web application context. [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can lead to theft of cookies, session tokens, and other sensitive information from users. Attackers can perform unauthorized actions on behalf of the victim, deface web pages, redirect users to malicious sites, and potentially gain full control over the victim's browser. These impacts compromise user data and system security, making it critical to remediate the issue promptly. [2, 3]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by identifying instances of the vulnerable file `/admin/bwdates-reports-details.php` on your web server and testing the `fromdate` parameter for cross-site scripting (XSS) by injecting typical XSS payloads such as `<script>alert('XSS')</script>`. You can use Google dorking with queries like `inurl:admin/bwdates-reports-details.php` to find potentially vulnerable targets. Additionally, manual or automated web application scanners that test for reflected XSS vulnerabilities on the `fromdate` parameter can be used. Example commands include using curl or wget to send requests with XSS payloads, or using tools like OWASP ZAP or Burp Suite to test the parameter. For example: `curl -G 'http://targetsite/admin/bwdates-reports-details.php' --data-urlencode "fromdate=<script>alert('XSS')</script>"` and observe if the script executes or is reflected unsanitized in the response. [1, 2]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: 1) Implement proper output encoding for the `fromdate` parameter to ensure user input is treated as text and not executable code, tailored to the context (HTML, JavaScript, CSS, URL). 2) Enforce strict input validation and filtering to accept only expected formats and reject or escape malicious content such as script tags and event handlers. 3) Deploy a strict Content Security Policy (CSP) to limit sources of executable scripts and block unauthorized inline or external scripts. 4) Set Secure and HttpOnly flags on sensitive cookies to prevent JavaScript access and ensure transmission only over HTTPS. 5) Conduct regular security audits to identify and fix XSS and other vulnerabilities promptly. If possible, replace the affected component with an alternative product as no known countermeasures are documented. These steps help protect user data and maintain system security. [2, 1]


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows cross-site scripting (XSS) attacks that can lead to theft of sensitive information and unauthorized actions, it could potentially result in violations of data protection requirements under such regulations if exploited. Immediate remediation is recommended to protect user data and maintain system security. [1, 2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart