# CVE-2026-124570: SourceCodester Online Leave Management System Employee Avatar Upload Extension Master.php cross site scripting


- **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
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-3ff5-847p-xj2r

## What is CVE-2026-124570?

CVE-2026-124570 is a medium-severity vulnerability in SourceCodester Online Leave Management System, published on 9 Nov 2026. 

### Official description

A vulnerability was detected in SourceCodester Online Leave Management System 1.0. Affected is an unknown function of the file app/classes/Master.php of the component Employee Avatar Upload Extension. Performing a manipulation of the argument employee avatar filename results in cross site scripting. Remote exploitation of the attack is possible. The exploit is now public and may be used.

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-124570?


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

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

## Is CVE-2026-124570 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124570 is a medium-severity vulnerability in SourceCodester Online Leave Management System, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124570 exists.

Affected product: SourceCodester Online Leave 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-124570/ (Markdown: https://insights.sbomify.com/CVE-2026-124570/index.md)
```

## Sources

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

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