CVE-2025-6125
BaseFortify
Publication date: 2025-06-16
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 | rail_pass_management_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-6125 is a Cross-Site Scripting (XSS) vulnerability in the PHPGurukul Rail Pass Management System 1.0, specifically in the /admin/aboutus.php file. The vulnerability occurs because the 'pagedes' parameter accepts user input that is embedded directly into the HTML output without proper encoding or sanitization. This allows attackers to inject malicious JavaScript code that executes in the context of users' browsers when they visit the affected page. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have several impacts: attackers can steal user sessions and authentication cookies, perform unauthorized actions on behalf of authenticated users, redirect users to malicious websites, deface web pages, and deliver malware payloads. It can compromise user accounts, expose sensitive information, and allow manipulation of application functionality. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the /admin/aboutus.php page of the PHPGurukul Rail Pass Management System 1.0 is vulnerable to reflected Cross-Site Scripting (XSS) via the 'pagedes' parameter. One detection method is to send a crafted request with a JavaScript payload in the 'pagedes' parameter and observe if it is executed or reflected unsanitized in the response. Additionally, Google dorking can be used to identify vulnerable targets by searching for "inurl:admin/aboutus.php". Example command using curl to test the vulnerability: curl -X POST -d "pagedes=<script>alert('XSS')</script>" https://target-domain/rpms/admin/aboutus.php -v [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing context-aware output encoding such as HTML entity encoding for the 'pagedes' parameter, applying a strict Content Security Policy (CSP) header to reduce XSS impact, enforcing input validation and sanitization using allow-lists and libraries like DOMPurify, securing session cookies by marking them as HttpOnly and Secure, and enforcing HTTPS. Additionally, avoid unsafe methods like innerHTML and document.write(), and consider using modern frameworks with built-in XSS protections. If possible, replace the affected component with a secure alternative. [1, 2]