Quick answers
- Is CVE-2026-82621 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82621 being exploited in the wild.
- How severe is CVE-2026-82621?
- High severity, with a CVSS score of 7.3, published 31 August 2026.
- Which products and versions are affected?
- Soarkey StudentManagement up to commit e08f7f1d5015af407aa4cca0ada3dea189b4937e.
- Is there a fix for CVE-2026-82621?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82621 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-82621?
- Check whether you run Soarkey StudentManagement at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The AdminDao servlet in the application processes administrative actions via an unauthenticated request parameter without enforcing any session validation, authentication checks, or authorization controls. The vulnerable doGet() method switches on an "action" parameter and dispatches to handlers (query_all_user, insert_department, delete_department, etc.) without verifying caller identity or role. Attackers can exploit this by sending direct HTTP requests to /AdminDao with crafted action parameters—for example, ?action=query_all_user returns all user credentials in plaintext, and ?action=insert_department allows creation of arbitrary departments. No authentication or session cookie is required to perform these operations. The issue was reported via GitHub issue #32 in July 2026 but the maintainer has not responded or patched the vulnerability. Patches are not yet available.
Affected products
- Soarkey StudentManagement up to commit e08f7f1d5015af407aa4cca0ada3dea189b4937e
Timeline
- 2026-07-16: disclosed: Vulnerability reported via GitHub issue #32
- 2026-08-31: advisory: CVE-2026-82621 published