CVE-2025-51411
BaseFortify
Publication date: 2025-07-25
Last updated on: 2025-10-09
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| vishalmathur | institute-of-current-students | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a reflected Cross-Site Scripting (XSS) issue in the Institute-of-Current-Students v1.0 application, specifically in the /postquerypublic endpoint. It occurs because the application does not properly sanitize the email parameter before reflecting it back in the HTML response. An attacker can craft a malicious URL or form that includes JavaScript code in the email parameter, which then executes in the victim's browser when they visit the link or submit the form. This allows the attacker to run arbitrary scripts in the context of the victim's browser. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to several client-side attacks including session hijacking, credential theft, phishing or impersonation attacks, forced redirection to malicious sites, and malware delivery. Essentially, an attacker can steal sensitive information or manipulate the victim's browser actions by executing arbitrary JavaScript code. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted POST requests to the /postquerypublic endpoint with malicious script payloads in the email parameter and observing if the script is reflected and executed in the HTML response. For example, you can use curl to send a test payload: curl -X POST -d "email=<script>alert(1)</script>" http://target/Institute-of-Current-Students/postquerypublic -H "Content-Type: application/x-www-form-urlencoded". If the response contains the injected script without encoding, the vulnerability is present. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying server-side input validation to all form inputs, encoding all untrusted output using functions like htmlspecialchars() before rendering in HTML, setting strong Content Security Policy (CSP) headers to restrict script execution, and avoiding direct embedding of unsanitized user inputs into HTML responses. Since no vendor patch is available at disclosure, these measures help reduce the risk of exploitation. [1]