# CVE-2024-47946: OS Command Execution through Arbitrary File Upload

> Authenticated attackers can upload malicious PNG files containing PHP code to execute arbitrary commands on the Scan2Net server.

- **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:** 10 Dec 2024
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-7g6h-cq22-rqv6

## What is CVE-2024-47946?

CVE-2024-47946 is a high-severity vulnerability in Image Access GmbH Scan2Net, published on 10 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

If the attacker has access to a valid Poweruser session, remote code execution is possible because specially crafted valid PNG files with injected PHP content can be uploaded as desktop backgrounds or lock screens. After the upload, the PHP script is available in the web root. The PHP code executes once the uploaded file is accessed. This allows the execution of arbitrary PHP code and OS commands on the device as "www-data".

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2024-47946 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47946 is a high-severity vulnerability in Image Access GmbH Scan2Net, published on 10 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47946 in the wild and no public exploit code.

Affected product: Image Access GmbH Scan2Net. 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-47946/ (Markdown: https://insights.sbomify.com/CVE-2024-47946/index.md)
```

## Sources

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

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