# CVE-2026-120341: mathurvishal CloudClassroom-PHP-Project studentdetails.php redirect


- **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
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-xj65-2697-58c2

## What is CVE-2026-120341?

CVE-2026-120341 is a medium-severity vulnerability in mathurvishal CloudClassroom-PHP-Project, published on 2 Nov 2026. 

### Official description

A security vulnerability has been detected in mathurvishal CloudClassroom-PHP-Project. Impacted is an unknown function of the file studentdetails.php. The manipulation leads to execution after redirect. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-705 (Incorrect Control Flow Scoping), CWE-698 (Execution After Redirect (EAR))

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


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

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

## Is CVE-2026-120341 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120341 is a medium-severity vulnerability in mathurvishal CloudClassroom-PHP-Project, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120341 exists.

Affected product: mathurvishal CloudClassroom-PHP-Project. 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-120341/ (Markdown: https://insights.sbomify.com/CVE-2026-120341/index.md)
```

## Sources

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

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