CVE-2025-5970
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-06-10

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was found in PHPGurukul Restaurant Table Booking System 1.0 and classified as problematic. Affected by this issue is some unknown functionality of the file /admin/add-subadmin.php. The manipulation of the argument fullname leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-10
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-06-10
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
phpgurukul restaurant_table_booking_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-5970 is a Cross-Site Scripting (XSS) vulnerability in the PHPGurukul Restaurant Table Booking System version 1.0, specifically in the /admin/add-subadmin.php file. The vulnerability occurs because the 'fullname' parameter is not properly sanitized or validated, allowing attackers to inject malicious JavaScript code. This code executes in the context of the victim's browser when they visit the affected page, potentially compromising user accounts and application integrity. [1, 2, 3]


How can this vulnerability impact me? :

Exploitation of this vulnerability can lead to theft of user sessions and authentication cookies, unauthorized actions performed on behalf of authenticated users, redirection of users to malicious websites, defacement of web pages, and delivery of malware payloads. It compromises user security and the integrity of the application, potentially allowing attackers to manipulate application functionality and steal sensitive information. [1, 3]


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

This vulnerability can be detected by identifying the presence of the vulnerable PHPGurukul Restaurant Table Booking System version 1.0, specifically the /admin/add-subadmin.php page. Attackers can use Google dorking with the query "inurl:admin/add-subadmin.php" to find vulnerable targets. Additionally, testing for the vulnerability involves sending crafted requests with malicious JavaScript payloads in the "fullname" parameter to see if the input is reflected unsanitized in the response, indicating a cross-site scripting flaw. For example, a POST request injecting `<script>alert(document.cookie)</script>` into the fullname parameter can be used to test for exploitation. Network or system detection commands could include using curl or similar tools to send such requests and observe responses. Example command: `curl -X POST -d "fullname=<script>alert(document.cookie)</script>" https://targetsite.com/admin/add-subadmin.php` and check if the script is reflected in the response. [2, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: 1) Implement context-aware output encoding such as HTML entity encoding for all user inputs reflected in the HTML output, especially the "fullname" parameter. 2) Apply a strict Content Security Policy (CSP) header to reduce the impact of any injected scripts. 3) Enforce input validation and sanitization using allow-lists and libraries like DOMPurify. 4) Secure session cookies by marking them as HttpOnly and Secure to prevent JavaScript access and ensure HTTPS transmission. 5) Use modern frameworks that provide built-in DOM sanitization and avoid unsafe methods like innerHTML and document.write(). If possible, replace the affected product with a secure alternative as no known countermeasures or patches are documented. [1, 3, 2]


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