# CVE-2024-26521: Cross-site scripting in n/a

> Remote attackers can execute arbitrary code and escalate privileges via HTML injection in CE Phoenix e-commerce software.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 12 Mar 2024
- **Updated:** 27 Aug 2024
- **Also known as:** GHSA-xjqv-qgm4-c2mr

## What is CVE-2024-26521?

CVE-2024-26521 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Mar 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

HTML Injection vulnerability in CE Phoenix v1.0.8.20 and before allows a remote attacker to execute arbitrary code, escalate privileges, and obtain sensitive information via a crafted payload to the english.php component.

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

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


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

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

## Is CVE-2024-26521 being exploited?

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

Public exploit code:

- Html Injection vulnearbility in CE-Phoenix-v1.0.8.20 where malicious HTML code is inserted into a website. This can lead to a variety of issues, from minor website defacement to serious data breaches. (github_poc): https://github.com/hackervegas001/CVE-2024-26521

## Fix prompt for AI coding agents

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

What it is: CVE-2024-26521 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Mar 2024. 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-2024-26521 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-2024-26521/ (Markdown: https://insights.sbomify.com/CVE-2024-26521/index.md)
```

## Sources

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

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