CVE-2025-15214
Remote Cross-Site Scripting in Campcodes Park Ticketing System
Publication date: 2025-12-30
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 | park_ticketing_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 Park Ticketing System 1.0, specifically in the save_pricing function of the admin_class.php file. It involves the manipulation of the argument 'Name' which leads to a cross-site scripting (XSS) vulnerability. This means an attacker can inject malicious scripts remotely through this function.
How can this vulnerability impact me? :
The vulnerability allows an attacker to perform cross-site scripting attacks remotely. This can lead to the execution of malicious scripts in the context of the affected application, potentially compromising user interactions or data integrity. However, the CVSS scores indicate a low to moderate impact, with no direct confidentiality or availability impact, but some integrity impact.
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_class.php' and specifically the 'save_pricing' function that improperly sanitizes the 'Name' parameter. One method is to use Google dorking with queries like 'inurl:admin_class.php' to identify potentially vulnerable targets. Additionally, testing the input field for the 'Name' parameter by injecting typical XSS payloads and observing if they are executed or stored can help detect the vulnerability. Since the exploit requires authentication and user interaction, scanning for unusual script injections in the 'Name' parameter within the application logs or database may also help. Specific commands are not provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the affected 'admin_class.php' file and the 'save_pricing' function to trusted users only, as exploitation requires authentication. Since no known mitigations or countermeasures have been documented, it is suggested to consider replacing the affected product or component. Additionally, applying input validation and sanitization on the 'Name' parameter to neutralize malicious scripts is critical. Monitoring and removing any injected scripts from the system can also reduce risk. However, no official patches or fixes are mentioned in the resources. [1]