# CVE-2022-24239: File upload in n/a

> An attacker can upload malicious files via the attachments.awp endpoint in ACEweb Online Portal, potentially leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-5h88-x8r9-rm43

## What is CVE-2022-24239?

CVE-2022-24239 is a critical vulnerability in n/a, published on 27 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ACEweb Online Portal 3.5.065 was discovered to contain an unrestricted file upload vulnerability via attachments.awp.

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

## Which versions are affected by CVE-2022-24239?

It affects 1 product.


Products: Aceware Aceweb Online Portal.

## How do I fix CVE-2022-24239?

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

## Is CVE-2022-24239 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-24240](https://insights.sbomify.com/CVE-2022-24240/): SQL injection in n/a (critical 9.8)
- [CVE-2022-24241](https://insights.sbomify.com/CVE-2022-24241/): Path traversal in n/a (high 7.5)
- [CVE-2022-24581](https://insights.sbomify.com/CVE-2022-24581/): Server-side request forgery in n/a (high 7.5)
- [CVE-2022-24238](https://insights.sbomify.com/CVE-2022-24238/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24239 and fix it if it is affected.

What it is: CVE-2022-24239 is a critical vulnerability in n/a, published on 27 May 2022. 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-2022-24239 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-2022-24239/ (Markdown: https://insights.sbomify.com/CVE-2022-24239/index.md)
```

## Sources

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

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