# CVE-2023-0722: Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_save_state

> Attackers can trick administrators into modifying folder structures via forged requests due to missing nonce validation in the Wicked Folders plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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:** 8 Feb 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-gj4v-r24j-fq69

## What is CVE-2023-0722?

CVE-2023-0722 is a medium-severity vulnerability in wickedplugins Wicked Folders – Folder Organizer for Pages, Posts, and Custom Post Types, published on 8 Feb 2023. 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 Wicked Folders plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.18.16. This is due to missing or incorrect nonce validation on the ajax_save_state function. This makes it possible for unauthenticated attackers to invoke this function via forged request granted they can trick a site administrator into performing an action such as clicking on a link leading them to perform actions intended for administrators such as changing the folder structure maintained by the plugin.

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

## Which versions are affected by CVE-2023-0722?

It affects 1 product.


Products: Wickedplugins Wicked Folders.

## How do I fix CVE-2023-0722?

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

## Is CVE-2023-0722 being exploited?

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

## Other vulnerabilities in wickedplugins Wicked Folders – Folder Organizer for Pages, Posts, and Custom Post Types

- [CVE-2021-24919](https://insights.sbomify.com/CVE-2021-24919/): Wicked Folders < 2.18.10 - Subscriber+ SQL Injection (high 8.8)
- [CVE-2023-0729](https://insights.sbomify.com/CVE-2023-0729/): Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_save_sort_order (medium 5.4)
- [CVE-2023-0684](https://insights.sbomify.com/CVE-2023-0684/): Wicked Folders <= 2.18.16 - Missing Authorization via ajax_unassign_folders (medium 5.4)
- [CVE-2023-0685](https://insights.sbomify.com/CVE-2023-0685/): Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_unassign_folders (medium 5.4)
- [CVE-2023-0711](https://insights.sbomify.com/CVE-2023-0711/): Wicked Folders <= 2.18.16 - Missing Authorization via ajax_save_state (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0722 and fix it if it is affected.

What it is: CVE-2023-0722 is a medium-severity vulnerability in wickedplugins Wicked Folders – Folder Organizer for Pages, Posts, and Custom Post Types, published on 8 Feb 2023. 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-2023-0722 in the wild and no public exploit code.

Affected product: wickedplugins Wicked Folders – Folder Organizer for Pages, Posts, and Custom Post Types. 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-2023-0722/ (Markdown: https://insights.sbomify.com/CVE-2023-0722/index.md)
```

## Sources

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

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