# CVE-2026-4578: code-projects Exam Form Submission update_s3.php cross site scripting

> Remote attackers can inject malicious scripts via the sname parameter in the admin update form, potentially compromising user sessions.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Mar 2026
- **Updated:** 25 Mar 2026
- **Also known as:** GHSA-fw33-9hq6-22wp

## What is CVE-2026-4578?

CVE-2026-4578 is a medium-severity cross-site scripting vulnerability in code-projects Exam Form Submission, published on 23 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability was determined in code-projects Exam Form Submission 1.0. The impacted element is an unknown function of the file /admin/update_s3.php. Executing a manipulation of the argument sname can lead to cross site scripting. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-4578 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4578 is a medium-severity cross-site scripting vulnerability in code-projects Exam Form Submission, published on 23 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4578 exists.

Affected product: code-projects Exam Form Submission. 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-4578/ (Markdown: https://insights.sbomify.com/CVE-2026-4578/index.md)
```

## Sources

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

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