# CVE-2021-24820: Cost Calculator <= 1.6 - Authenticated Local File Inclusion

> Authenticated attackers can exploit path traversal in the Cost Calculator plugin to include local PHP files, potentially leading to code execution or data disclosure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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:** 28 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7pg3-r4wv-7xmh

## What is CVE-2021-24820?

CVE-2021-24820 is a medium-severity path traversal vulnerability in Unknown Cost Calculator, published on 28 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Cost Calculator WordPress plugin through 1.6 allows authenticated users (Contributor+ in versions < 1.5, and Admin+ in versions <= 1.6) to perform path traversal and local PHP file inclusion on Windows Web Servers via the Cost Calculator post's Layout

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

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

It affects 1 product.


Products: Bold-Themes Cost Calculator.

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

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

## Is CVE-2021-24820 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24820 is a medium-severity path traversal vulnerability in Unknown Cost Calculator, published on 28 Feb 2022. 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-24820 in the wild and no public exploit code.

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

## Sources

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

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