# CVE-2022-1694: Useful Banner Manager <= 1.6.1 - Modify banners via CSRF

> An attacker can trick a logged-in admin into modifying or deleting banners via CSRF in the Useful Banner Manager 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:** 13 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-w69g-5qh5-993v

## What is CVE-2022-1694?

CVE-2022-1694 is a medium-severity vulnerability in Unknown Useful Banner Manager, published on 13 Jun 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 Useful Banner Manager WordPress plugin through 1.6.1 does not perform CSRF checks on POST requests to its admin page, allowing an attacker to trick a logged in admin to add, modify or delete banners from the plugin by submitting a form.

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

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

It affects 1 product.


Products: Useful Banner Manager Project Useful Banner Manager.

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

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

## Is CVE-2022-1694 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1694 is a medium-severity vulnerability in Unknown Useful Banner Manager, published on 13 Jun 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-1694 in the wild and no public exploit code.

Affected product: Unknown Useful Banner Manager. 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-1694/ (Markdown: https://insights.sbomify.com/CVE-2022-1694/index.md)
```

## Sources

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

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