# CVE-2022-0499: Sermon Browser <= 0.45.22 - Arbitrary File Upload via CSRF

> Attackers can trick admins into uploading malicious PHP files via CSRF, leading to remote code execution on the WordPress site.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-j8w4-5x7j-f9rc

## What is CVE-2022-0499?

CVE-2022-0499 is a high-severity vulnerability in Unknown Sermon Browser, published on 28 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Sermon Browser WordPress plugin through 0.45.22 does not have CSRF checks in place when uploading Sermon files, and does not validate them in any way, allowing attackers to make a logged in admin upload arbitrary files such as PHP ones.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Sermon Browser Project Sermon Browser.

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

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

## Is CVE-2022-0499 being exploited?

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

## Other vulnerabilities in Unknown Sermon Browser

- [CVE-2016-10897](https://insights.sbomify.com/CVE-2016-10897/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0499 is a high-severity vulnerability in Unknown Sermon Browser, published on 28 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-0499 in the wild and no public exploit code.

Affected product: Unknown Sermon Browser. 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-0499/ (Markdown: https://insights.sbomify.com/CVE-2022-0499/index.md)
```

## Sources

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

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