# CVE-2022-50944: Aero CMS 0.0.1 PHP Code Injection via posts.php

> Authenticated attackers can execute arbitrary PHP code by uploading malicious files to the Aero CMS admin posts endpoint.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-377g-gwp8-j5fx

## What is CVE-2022-50944?

CVE-2022-50944 is a high-severity code injection vulnerability in MegaTKC Aero CMS, published on 10 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Aero CMS 0.0.1 contains a PHP code injection vulnerability that allows authenticated attackers to execute arbitrary PHP code by uploading malicious files through the image parameter. Attackers can upload PHP files with embedded code to the admin posts.php endpoint with source=add_post parameter, and the uploaded files are executed by the server.

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

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


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

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

## Is CVE-2022-50944 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50944 is a high-severity code injection vulnerability in MegaTKC Aero CMS, published on 10 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50944 exists.

Affected product: MegaTKC Aero CMS. 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-50944/ (Markdown: https://insights.sbomify.com/CVE-2022-50944/index.md)
```

## Sources

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

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