# CVE-2025-5721: SourceCodester Student Result Management System Profile Setting Page update_profile cross site scripting

> Remote attackers can inject malicious scripts into the profile update page, potentially stealing user sessions or executing code in victim browsers.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Jun 2025
- **Updated:** 9 Jun 2025
- **Also known as:** GHSA-h6m6-m85q-399m

## What is CVE-2025-5721?

CVE-2025-5721 is a medium-severity cross-site scripting vulnerability in SourceCodester Student Result Management System, published on 6 Jun 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as problematic, was found in SourceCodester Student Result Management System 1.0. This affects an unknown part of the file /script/academic/core/update_profile of the component Profile Setting Page. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-5721?

It affects 1 product.


Products: Razormist Student Result Management System.

## How do I fix CVE-2025-5721?

No fix has been published for CVE-2025-5721 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5721 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5721 exists.

## Other vulnerabilities in SourceCodester Student Result Management System

- [CVE-2025-5649](https://insights.sbomify.com/CVE-2025-5649/): SourceCodester Student Result Management System Register Interface new_user access control (medium 6.9)
- [CVE-2025-6475](https://insights.sbomify.com/CVE-2025-6475/): SourceCodester Student Result Management System Manage Students Module manage_students cross site scripting (medium 4.8)
- [CVE-2025-6477](https://insights.sbomify.com/CVE-2025-6477/): SourceCodester Student Result Management System System Settings Page system cross site scripting (medium 4.8)
- [CVE-2025-5726](https://insights.sbomify.com/CVE-2025-5726/): SourceCodester Student Result Management System Division System Page division-system cross site scripting (medium 4.8)
- [CVE-2025-5727](https://insights.sbomify.com/CVE-2025-5727/): SourceCodester Student Result Management System Announcement Page announcement cross site scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5721 and fix it if it is affected.

What it is: CVE-2025-5721 is a medium-severity cross-site scripting vulnerability in SourceCodester Student Result Management System, published on 6 Jun 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5721 exists.

Affected product: SourceCodester Student Result Management System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5721/ (Markdown: https://insights.sbomify.com/CVE-2025-5721/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5721
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5721
- OSV: https://osv.dev/vulnerability/CVE-2025-5721

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5721/
Summaries are generated and may contain mistakes; the official description above is the record.