# CVE-2024-21515: Cross site scripting in opencart

> Reflected XSS in OpenCart admin log route allows attackers to steal tokens or execute code if admin directory path is known.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:L/VA:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Jun 2024
- **Updated:** 14 Jan 2025
- **Also known as:** BIT-opencart-2024-21515, GHSA-qx44-885h-7p56

## What is CVE-2024-21515?

CVE-2024-21515 is a low-severity cross-site scripting vulnerability in opencart/opencart, published on 22 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

This affects versions of the package opencart/opencart from 4.0.0.0. A reflected XSS issue was identified in the filename parameter of the admin tool/log route. An attacker could obtain a user's token by tricking the user to click on a maliciously crafted URL. The user is then prompted to login and redirected again upon authentication with the payload automatically executing. If the attacked user has admin privileges, this vulnerability could be used as the start of a chain of exploits like Zip Slip or arbitrary file write vulnerabilities in the admin functionality.

**Notes:**

1) This is only exploitable if the attacker knows the name or path of the admin directory. The name of the directory is "admin" by default but there is a pop-up in the dashboard warning users to rename it.

2) The fix for this vulnerability is incomplete. The redirect is removed so that it is not possible for an attacker to control the redirect post admin login anymore, but it is still possible to exploit this issue in admin if the user is authenticated as an admin already.

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

## Which versions are affected by CVE-2024-21515?

3 open source packages ship an affected version, including opencart/opencart and opencart. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `opencart/opencart` | Packagist | From 4.0.0.0 | None |
| `opencart/opencart` | Packagist | From 4.0.0.0 | None |
| `opencart` | Bitnami | From 4.0.0-0 | None |

Products: Opencart Opencart.

## How do I fix CVE-2024-21515?

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

## Is CVE-2024-21515 being exploited?

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

## Other vulnerabilities in opencart/opencart

- [CVE-2023-40834](https://insights.sbomify.com/CVE-2023-40834/): Auth bypass in n/a (critical 9.8)
- [CVE-2014-3990](https://insights.sbomify.com/CVE-2014-3990/): Deserialization in n/a (critical 9.8)
- [CVE-2024-58341](https://insights.sbomify.com/CVE-2024-58341/): OpenCart Core 4.0.2.3 SQL Injection via search Parameter (high 8.8)
- [CVE-2023-47444](https://insights.sbomify.com/CVE-2023-47444/): Code injection in n/a (high 8.8)
- [CVE-2018-13067](https://insights.sbomify.com/CVE-2018-13067/): OpenCart Cross-Site Request Forgery (CSRF) (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-21515 and fix it if it is affected.

What it is: CVE-2024-21515 is a low-severity cross-site scripting vulnerability in opencart/opencart, published on 22 Jun 2024. An attacker can exploit it over the internet without logging in, 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-2024-21515 exists.

Affected packages and fixed versions:
- opencart/opencart (Packagist): affected from 4.0.0.0; no fix listed
- opencart/opencart (Packagist): affected from 4.0.0.0; no fix listed
- opencart (Bitnami): affected from 4.0.0-0; no fix listed

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-2024-21515/ (Markdown: https://insights.sbomify.com/CVE-2024-21515/index.md)
```

## Sources

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

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