CVE-2025-6473
BaseFortify
Publication date: 2025-06-22
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 |
|---|---|---|
| fabian | school_fees_payment_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-6473 is a Stored Cross-Site Scripting (XSS) vulnerability in the School Fees Payment System version 1.0, specifically in the /fees.php file. It occurs because the 'transcation_remark' parameter accepts user input without proper validation or sanitization. This allows attackers to inject malicious JavaScript code that is stored on the server and later executed in the browsers of users who view the affected pages, enabling actions like stealing cookies or manipulating front-end behavior. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to persistent session hijacking, theft of sensitive data, website defacement, distribution of client-side malware, and full user compromise. Attackers can execute arbitrary scripts in users' browsers without needing authentication, potentially compromising user security and data integrity. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'transcation_remark' parameter in the /fees.php file for stored cross-site scripting (XSS). A proof-of-concept involves sending a POST request with a script payload, such as `<script>alert(1)</script>`, to /fees.php and checking if the script executes when the data is later displayed. Additionally, vulnerable targets can be identified using Google dorking with the query "inurl:fees.php". Example command to test via curl: `curl -X POST -d "transcation_remark=<script>alert(1)</script>" http://targetsite/fees.php` and then verify if the script runs in the front-end display (e.g., /report.php). [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps to mitigate this vulnerability include validating and sanitizing all user inputs, especially the 'transcation_remark' parameter, to prevent injection of malicious scripts. Additionally, properly encode or escape output data before rendering it on the front end to prevent script execution. Applying input validation, output encoding, and implementing security filters will protect data integrity and user security. If possible, consider replacing the affected product with a secure alternative. [2, 3]