# CVE-2021-24453: Include Me <= 1.2.1 - Authenticated Remote Code Execution (RCE) via LFI log poisoning

> Authenticated attackers can exploit path traversal in the Include Me plugin to achieve remote code execution via log poisoning.

- **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:** 19 Jul 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f2j9-593v-67w7

## What is CVE-2021-24453?

CVE-2021-24453 is a high-severity path traversal vulnerability in Unknown Include Me, published on 19 Jul 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Include Me WordPress plugin through 1.2.1 is vulnerable to path traversal / local file inclusion, which can lead to Remote Code Execution (RCE) of the system due to log poisoning and therefore potentially a full compromise of the underlying structure

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-24453?

It affects 1 product.


Products: Include Me Project Include Me.

## How do I fix CVE-2021-24453?

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

## Is CVE-2021-24453 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24453 and fix it if it is affected.

What it is: CVE-2021-24453 is a high-severity path traversal vulnerability in Unknown Include Me, published on 19 Jul 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24453 in the wild and no public exploit code.

Affected product: Unknown Include Me. 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-2021-24453/ (Markdown: https://insights.sbomify.com/CVE-2021-24453/index.md)
```

## Sources

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

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