CVE-2025-5974
BaseFortify
Publication date: 2025-06-10
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 |
|---|---|---|
| phpgurukul | restaurant_table_booking_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?
CVE-2025-5974 is a Cross-Site Scripting (XSS) vulnerability in the PHPGurukul Restaurant Table Booking System version 1.0, specifically in the /check-status.php file. It occurs because the application improperly handles the 'searchdata' parameter, allowing attackers to inject malicious JavaScript code into the web page output. When users access the affected pages, the injected script executes in their browsers, potentially leading to unauthorized actions or data theft. [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to theft of user sessions and authentication cookies, unauthorized actions performed on behalf of authenticated users, redirection to malicious websites, webpage defacement, and delivery of malware payloads. These impacts pose significant security and privacy risks to users and can compromise the integrity of the application. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /check-status.php page for reflected cross-site scripting (XSS) via the 'searchdata' parameter. One approach is to send crafted HTTP requests with XSS payloads such as <script>alert(document.cookie)</script> in the 'searchdata' parameter and observe if the script executes or is reflected unsanitized in the response. Additionally, Google dorking with the query 'inurl:check-status.php' can help identify vulnerable instances. For example, using curl to send a POST request: curl -X POST -d "searchdata=<script>alert(document.cookie)</script>" https://targetsite/rtbs/check-status.php and checking the response for script injection. Monitoring web server logs for suspicious requests containing script tags in 'searchdata' can also help detect exploitation attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing context-aware output encoding such as HTML entity encoding on the 'searchdata' parameter to prevent script injection. Applying a strict Content Security Policy (CSP) header can reduce the impact of any XSS that occurs. Input validation and sanitization should be enforced, using allow-lists and sanitization libraries like DOMPurify. Securing session cookies by marking them as HttpOnly and Secure helps prevent theft via JavaScript. Avoid unsafe methods like innerHTML and document.write() in the application code. If possible, replace the affected product with a secure alternative. These measures help protect user security and maintain application integrity. [1]