# CVE-2020-26799: Cross-site scripting in n/a

> An unauthenticated attacker can execute arbitrary scripts in the victim's browser via reflected XSS in Luxcal, potentially stealing user data.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2025
- **Updated:** 21 Jul 2025
- **Also known as:** GHSA-vpmc-2x8r-gfmc

## What is CVE-2020-26799?

CVE-2020-26799 is a critical cross-site scripting vulnerability in n/a, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A reflected cross-site scripting (XSS) vulnerability was discovered in index.php on Luxcal 4.5.2 which allows an unauthenticated attacker to steal other users' data.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2020-26799?


## How do I fix CVE-2020-26799?

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

## Is CVE-2020-26799 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26799 and fix it if it is affected.

What it is: CVE-2020-26799 is a critical cross-site scripting vulnerability in n/a, published on 21 Jul 2025. 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-2020-26799 exists.

Affected product: n/a. 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-2020-26799/ (Markdown: https://insights.sbomify.com/CVE-2020-26799/index.md)
```

## Sources

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

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