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

> Remote attackers can execute arbitrary code via PHP payloads in the QR demo application due to unnecessary shipped files.

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

## What is CVE-2024-39165?

CVE-2024-39165 is a critical code injection vulnerability in n/a, published on 4 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

QR/demoapp/qr_image.php in Asial JpGraph Professional through 4.2.6-pro allows remote attackers to execute arbitrary code via a PHP payload in the data parameter in conjunction with a .php file name in the filename parameter. This occurs because an unnecessary QR/demoapp folder.is shipped with the product.

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

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


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

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

## Is CVE-2024-39165 being exploited?

There is no known exploitation of CVE-2024-39165 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39165 is a critical code injection vulnerability in n/a, published on 4 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-39165 in the wild and no public exploit code.

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

## Sources

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

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