# CVE-2021-43258: File upload in n/a

> Authenticated attackers can upload malicious PHP files via email attachments in ChurchInfo, leading to remote code execution on the server.

- **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:** 23 Nov 2022
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-f3cp-c532-v8rx

## What is CVE-2021-43258?

CVE-2021-43258 is a high-severity vulnerability in n/a, published on 23 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CartView.php in ChurchInfo 1.3.0 allows attackers to achieve remote code execution through insecure uploads. This requires authenticated access tot he ChurchInfo application. Once authenticated, a user can add names to their cart, and compose an email. Uploading an attachment for the email stores the attachment on the site in the /tmp_attach/ folder where it can be accessed with a GET request. There are no limitations on files that can be attached, allowing for malicious PHP code to be uploaded and interpreted by the server.

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

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

It affects 1 product.


Products: Churchdb Churchinfo.

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

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

## Is CVE-2021-43258 being exploited?

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

Public exploit code:

- ChurchInfo 1.2.13-1.3.0 Authenticated RCE (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-43258 is a high-severity vulnerability in n/a, published on 23 Nov 2022. 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-2021-43258 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-2021-43258/ (Markdown: https://insights.sbomify.com/CVE-2021-43258/index.md)
```

## Sources

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

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