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

> Attackers can execute arbitrary code by injecting payloads into the Static Pages Content field in PluXml Blog.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 25 Jan 2024
- **Updated:** 30 May 2025
- **Also known as:** GHSA-r3xx-hr64-gmm2, UBUNTU-CVE-2024-22636

## What is CVE-2024-22636?

CVE-2024-22636 is a high-severity code injection vulnerability in n/a, published on 25 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PluXml Blog v5.8.9 was discovered to contain a remote code execution (RCE) vulnerability in the Static Pages feature. This vulnerability is exploited via injecting a crafted payload into the Content field.

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

It affects 1 product.


Products: Pluxml Pluxml.

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

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

## Is CVE-2024-22636 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-18185](https://insights.sbomify.com/CVE-2020-18185/): Code injection in n/a (critical 9.8)
- [CVE-2022-25018](https://insights.sbomify.com/CVE-2022-25018/): Code injection in n/a (high 8.8)
- [CVE-2012-2227](https://insights.sbomify.com/CVE-2012-2227/): Path traversal in n/a (high 7.5)
- [CVE-2007-3432](https://insights.sbomify.com/CVE-2007-3432/): File upload in n/a (high 7.5)
- [CVE-2025-67436](https://insights.sbomify.com/CVE-2025-67436/): Code injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22636 is a high-severity code injection vulnerability in n/a, published on 25 Jan 2024. 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-2024-22636 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-22636/ (Markdown: https://insights.sbomify.com/CVE-2024-22636/index.md)
```

## Sources

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

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