# CVE-2022-2233: Banner Cycler <= 1.4 - Cross-Site Request Forgery to Cross-Site Scripting

> Unauthenticated attackers can inject malicious scripts via CSRF if an administrator clicks a link, requiring a plugin update to fix.

- **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:** 6 Sep 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7r9g-mrcm-864m

## What is CVE-2022-2233?

CVE-2022-2233 is a high-severity vulnerability in jkriddle Banner Cycler, published on 6 Sep 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 Banner Cycler plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including 1.4. This is due to missing nonce protection on the pabc_admin_slides_postback() function found in the ~/admin/admin.php file. This makes it possible for unauthenticated attackers to inject malicious web scripts into the page, granted they can trick a site’s administrator into performing an action such as clicking on a link

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

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

It affects 1 product.


Products: Banner Cycler Project Banner Cycler.

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

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

## Is CVE-2022-2233 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2233 is a high-severity vulnerability in jkriddle Banner Cycler, published on 6 Sep 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-2233 in the wild and no public exploit code.

Affected product: jkriddle Banner Cycler. 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-2233/ (Markdown: https://insights.sbomify.com/CVE-2022-2233/index.md)
```

## Sources

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

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