Wicked Folders at a glance
- 22 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Mar 14, 2026.
- Ranked #1211 by popularity on WordPress.org (20,000+ active installs).
- The latest version is 4.2.0 (released Nov 5, 2026). The most recent security fix shipped in 4.1.1.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Wicked Folders version
Enter the Wicked Folders version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Wicked Folders”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Wicked Folders”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (4.2.0). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Wicked Folders vulnerabilities
Wicked Folders <= 4.1.0 - Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary Folder Deletion
Missing authorization · CVE-2026-1883
Affected versions: ≤ 4.1.0
Fixed in: 4.1.1
Severity: Medium 4.3 · Disclosed Mar 14, 2026
Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_add_folder
Cross-site request forgery (CSRF) · CVE-2023-0724
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Missing Authorization on ajax_move_object
Missing authorization · CVE-2023-0712
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_save_state
Cross-site request forgery (CSRF) · CVE-2023-0722
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Missing Authorization on ajax_add_folder
Missing authorization · CVE-2023-0713
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Missing Authorization on ajax_save_folder
Missing authorization · CVE-2023-0718
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Missing Authorization via ajax_delete_folder
Missing authorization · CVE-2023-0717
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Missing Authorization on ajax_edit_folder
Missing authorization · CVE-2023-0716
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_save_folder_order
Cross-site request forgery (CSRF) · CVE-2023-0730
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Cross-Site Request Forgery on ajax_save_folder
Cross-site request forgery (CSRF) · CVE-2023-0728
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_edit_folder
Cross-site request forgery (CSRF) · CVE-2023-0726
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_delete_folder
Cross-site request forgery (CSRF) · CVE-2023-0727
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_clone_folder
Cross-site request forgery (CSRF) · CVE-2023-0725
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Missing Authorization on ajax_save_folder_order
Missing authorization · CVE-2023-0720
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Missing Authorization on ajax_save_sort_order
Missing authorization · CVE-2023-0719
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_save_sort_order
Cross-site request forgery (CSRF) · CVE-2023-0729
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Missing Authorization on ajax_clone_folder
Missing authorization · CVE-2023-0715
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Missing Authorization via ajax_save_state
Missing authorization · CVE-2023-0711
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Cross-Site Request Forgery on ajax_move_object
Cross-site request forgery (CSRF) · CVE-2023-0723
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 7, 2023
Wicked Folders <= 2.18.16 - Missing Authorization via ajax_unassign_folders
Missing authorization · CVE-2023-0684
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 6, 2023
Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_unassign_folders
Cross-site request forgery (CSRF) · CVE-2023-0685
Affected versions: ≤ 2.18.16
Fixed in: 2.18.17
Severity: Medium 5.4 · Disclosed Feb 6, 2023
Wicked Folders <= 2.18.9 - Subscriber+ SQL Injection
SQL injection · CVE-2021-24919
Affected versions: ≤ 2.18.9
Fixed in: 2.18.10
Severity: High 8.8 · Disclosed Dec 30, 2021
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Wicked Folders <= 4.1.0 - Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary Folder DeletionMissing authorization · CVE-2026-1883 | ≤ 4.1.0 | 4.1.1 | Medium 4.3 | Mar 14, 2026 |
| Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_add_folderCross-site request forgery (CSRF) · CVE-2023-0724 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Missing Authorization on ajax_move_objectMissing authorization · CVE-2023-0712 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_save_stateCross-site request forgery (CSRF) · CVE-2023-0722 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Missing Authorization on ajax_add_folderMissing authorization · CVE-2023-0713 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Missing Authorization on ajax_save_folderMissing authorization · CVE-2023-0718 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Missing Authorization via ajax_delete_folderMissing authorization · CVE-2023-0717 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Missing Authorization on ajax_edit_folderMissing authorization · CVE-2023-0716 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_save_folder_orderCross-site request forgery (CSRF) · CVE-2023-0730 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Cross-Site Request Forgery on ajax_save_folderCross-site request forgery (CSRF) · CVE-2023-0728 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_edit_folderCross-site request forgery (CSRF) · CVE-2023-0726 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_delete_folderCross-site request forgery (CSRF) · CVE-2023-0727 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_clone_folderCross-site request forgery (CSRF) · CVE-2023-0725 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Missing Authorization on ajax_save_folder_orderMissing authorization · CVE-2023-0720 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Missing Authorization on ajax_save_sort_orderMissing authorization · CVE-2023-0719 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_save_sort_orderCross-site request forgery (CSRF) · CVE-2023-0729 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Missing Authorization on ajax_clone_folderMissing authorization · CVE-2023-0715 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Missing Authorization via ajax_save_stateMissing authorization · CVE-2023-0711 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Cross-Site Request Forgery on ajax_move_objectCross-site request forgery (CSRF) · CVE-2023-0723 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 7, 2023 |
| Wicked Folders <= 2.18.16 - Missing Authorization via ajax_unassign_foldersMissing authorization · CVE-2023-0684 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 6, 2023 |
| Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_unassign_foldersCross-site request forgery (CSRF) · CVE-2023-0685 | ≤ 2.18.16 | 2.18.17 | Medium 5.4 | Feb 6, 2023 |
| Wicked Folders <= 2.18.9 - Subscriber+ SQL InjectionSQL injection · CVE-2021-24919 | ≤ 2.18.9 | 2.18.10 | High 8.8 | Dec 30, 2021 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Mar 14, 2026.
Most common weaknesses in Wicked Folders
Missing authorization
11 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Cross-site request forgery (CSRF)
10 issues
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
SQL injection
1 issue
Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.
Frequently asked questions
Is Wicked Folders safe to use?
Wicked Folders is a well-known plugin with 20,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (4.2.0) and turn on automatic updates.
How do I find which version of Wicked Folders my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.