# CVE-2026-82621: Soarkey StudentManagement/学生信息管理系统 Administrative Servlet AdminDao.java AdminDao.doGet authorization

> Remote attackers can bypass authorization in the administrative servlet by manipulating the action argument, gaining unauthorized access.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-xr3w-fgv7-rf5w

## What is CVE-2026-82621?

CVE-2026-82621 is a medium-severity authentication bypass vulnerability in Soarkey StudentManagement, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in Soarkey StudentManagement and 学生信息管理系统 up to e08f7f1d5015af407aa4cca0ada3dea189b4937e. This impacts the function AdminDao.doGet of the file code/src/service/AdminDao.java of the component Administrative Servlet. Executing a manipulation of the argument action can lead to authorization bypass. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-82621?


## How do I fix CVE-2026-82621?

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

## Is CVE-2026-82621 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82621 and fix it if it is affected.

What it is: CVE-2026-82621 is a medium-severity authentication bypass vulnerability in Soarkey StudentManagement, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82621 exists.

Affected product: Soarkey StudentManagement. 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-2026-82621/ (Markdown: https://insights.sbomify.com/CVE-2026-82621/index.md)
```

## Sources

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

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