# CVE-2026-5210: SourceCodester Leave Application System file inclusion

> Remote attackers can exploit a file inclusion vulnerability in the page argument to read sensitive files or execute code.

- **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:** 31 Mar 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-54mj-887p-jvcm

## What is CVE-2026-5210?

CVE-2026-5210 is a medium-severity path traversal vulnerability in SourceCodester Leave Application System, published on 31 Mar 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 SourceCodester Leave Application System 1.0. This affects an unknown part. Performing a manipulation of the argument page results in file inclusion. Remote exploitation of the attack is possible. The exploit is now public and may be used.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-5210 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5210 is a medium-severity path traversal vulnerability in SourceCodester Leave Application System, published on 31 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5210 exists.

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

## Sources

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

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