# CVE-2025-3037: yzk2356911358 StudentServlet-JSP cross-site request forgery

> A cross-site request forgery vulnerability in StudentServlet-JSP allows remote attackers to perform unauthorized actions on behalf of authenticated users.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Mar 2025
- **Updated:** 1 Apr 2025
- **Also known as:** GHSA-5945-5998-27h6

## What is CVE-2025-3037?

CVE-2025-3037 is a medium-severity vulnerability in yzk2356911358 StudentServlet-JSP, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been found in yzk2356911358 StudentServlet-JSP cc0cdce25fbe43b6c58b60a77a2c85f52d2102f5/d4d7a0643f1dae908a4831206f2714b21820f991 and classified as problematic. This vulnerability affects unknown code. The manipulation leads to cross-site request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2025-3037 being exploited?

There is no known exploitation of CVE-2025-3037 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3037 is a medium-severity vulnerability in yzk2356911358 StudentServlet-JSP, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-3037 in the wild and no public exploit code.

Affected product: yzk2356911358 StudentServlet-JSP. 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-3037/ (Markdown: https://insights.sbomify.com/CVE-2025-3037/index.md)
```

## Sources

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

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