# CVE-2022-2091: Cache Images < 3.2.1 - Image Upload / Import via CSRF

> Attackers can force logged-in users to upload images via CSRF due to missing nonce checks in the Cache Images WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **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:** 11 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6x76-cmjp-cf89

## What is CVE-2022-2091?

CVE-2022-2091 is a medium-severity vulnerability in Unknown Cache Images, published on 11 Jul 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 Cache Images WordPress plugin before 3.2.1 does not implement nonce checks, which could allow attackers to make any logged user upload images via a CSRF attack.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Cache Images Project Cache Images.

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

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

## Is CVE-2022-2091 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2091 is a medium-severity vulnerability in Unknown Cache Images, published on 11 Jul 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-2091 in the wild and no public exploit code.

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

## Sources

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

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