CVE-2025-7925
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-07-21

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability, which was classified as problematic, has been found in PHPGurukul Online Banquet Booking System 1.0. Affected by this issue is some unknown functionality of the file /admin/login.php. The manipulation of the argument user_login/userpassword leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-07-21
Last Modified
2026-04-29
Generated
2026-05-27
AI Q&A
2025-07-21
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
phpgurukul online_banquet_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-7925 is a Reflected Cross-Site Scripting (XSS) vulnerability in PHPGurukul Online Banquet Booking System version 1.0, specifically in the /admin/login.php file. It occurs because the application improperly handles user-controllable input from the user_login and userpassword cookie parameters, reflecting them directly into the HTML output without proper sanitization or encoding. This allows an attacker to inject malicious JavaScript code that executes immediately in the victim's browser when they access the login page, potentially compromising user sessions or enabling further attacks. [1, 2, 3, 4]


How can this vulnerability impact me? :

This vulnerability can lead to arbitrary JavaScript execution in the victim's browser context. An attacker can steal session tokens or sensitive data, perform phishing attacks, redirect users to malicious sites, conduct UI redressing attacks, and bypass client-side protections. Overall, it compromises user security and the integrity of the web application, potentially allowing unauthorized actions or further exploitation. [1, 2, 4]


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

This vulnerability can be detected by testing the /admin/login.php page for reflected cross-site scripting (XSS) via the user_login and userpassword cookie parameters. You can use tools like curl or browser developer tools to send requests with crafted cookie values containing JavaScript payloads and observe if the script is reflected unsanitized in the response. For example, using curl: curl -v --cookie "user_login=><script>alert(1)</script>" https://targetsite/admin/login.php and checking if the alert script appears in the response. Additionally, Google dorking with queries like inurl:admin/login.php can help identify potentially vulnerable targets. Monitoring web server logs for suspicious cookie values or unusual requests to /admin/login.php may also help detect exploitation attempts. [3, 4]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include sanitizing and properly encoding the user_login and userpassword cookie values before reflecting them in the HTML output of /admin/login.php. Using functions like htmlspecialchars() in PHP to escape special characters can prevent script injection. Implementing a Content Security Policy (CSP) to restrict or block inline script execution can reduce the impact of any injected scripts. Avoid reflecting cookie values directly in the frontend unless absolutely necessary. Additionally, monitoring and blocking suspicious requests targeting these parameters can help reduce risk until a patch or update is applied. [4]


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