# CVE-2026-10619: sayan365 student-management-system improper authentication

> Remote attackers can bypass authentication in the student management system, potentially gaining unauthorized access to protected endpoints.

- **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:** 2 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-4849-p72j-5rw9

## What is CVE-2026-10619?

CVE-2026-10619 is a medium-severity authentication bypass vulnerability in sayan365 student-management-system, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in sayan365 student-management-system up to 7f3c9ce7d410332335c2affac93a385485051800. This impacts an unknown function. The manipulation results in improper authentication. The attack can be executed remotely. The exploit is now public and may be used. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. Multiple endpoints are affected. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-10619 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10619 is a medium-severity authentication bypass vulnerability in sayan365 student-management-system, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10619 in the wild and no public exploit code.

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

## Sources

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

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