# CVE-2024-25415: Code injection in n/a

> Attackers can execute arbitrary PHP code by injecting payloads into language files in CE Phoenix e-commerce software.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-pq2x-v8q9-52vx

## What is CVE-2024-25415?

CVE-2024-25415 is a high-severity code injection vulnerability in n/a, published on 16 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A remote code execution (RCE) vulnerability in /admin/define_language.php of CE Phoenix v1.0.8.20 allows attackers to execute arbitrary PHP code via injecting a crafted payload into the file english.php.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Phoenixcart Ce Phoenix Cart.

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

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

## Is CVE-2024-25415 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-47289](https://insights.sbomify.com/CVE-2025-47289/): Stored XSS in CE Phoenix Cart Testimonials Allows Account Takeover if Missing HttpOnly Flag (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25415 is a high-severity code injection vulnerability in n/a, published on 16 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25415 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-25415/ (Markdown: https://insights.sbomify.com/CVE-2024-25415/index.md)
```

## Sources

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

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