CVE-2025-5725
BaseFortify
Publication date: 2025-06-06
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 |
|---|---|---|
| munyweki | student_result_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-5725 is a cross-site scripting (XSS) vulnerability in SourceCodester Student Result Management System 1.0, specifically in the Grading System Page at /script/academic/grading-system. It occurs due to improper neutralization of the user-controllable 'Remark' argument, allowing attackers to inject and execute malicious scripts in other users' browsers. Exploitation requires authentication and user interaction and can be done remotely. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious scripts in the context of your users' browsers, potentially compromising data integrity and user trust. It may lead to unauthorized actions performed on behalf of authenticated users or theft of sensitive information. The attack requires user interaction and authentication but can be launched remotely. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves testing the 'Remark' argument in the /script/academic/grading-system page for cross-site scripting (XSS) by injecting typical XSS payloads and observing if they are executed. Since the vulnerability requires authentication and user interaction, manual testing or automated scanning tools that support authenticated XSS testing can be used. Specific commands are not provided in the resources, but using tools like curl or browser-based testing with payloads such as <script>alert(1)</script> in the 'Remark' parameter may help detect the issue. [1]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been identified for this vulnerability. The suggested immediate step is to replace the affected product with an alternative that is not vulnerable. Since the vulnerability requires authentication and user interaction, limiting access to trusted users and monitoring for suspicious activity may help reduce risk temporarily. [1]