LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0724: Wicked Folders <= 2.18.16 - Cross-Site Request Forgery via ajax_add_folder

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_add_folder 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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue lets an attacker trick a logged-in WordPress administrator into causing Wicked Folders to change folder data without proper request verification. It requires user interaction and supplied sources do not show active exploitation. Business impact is mainly content-organization tampering and limited data exposure.

Executive priority

Treat as a near-term WordPress hygiene issue, not an emergency based on supplied evidence. Prioritize sites where Wicked Folders is installed, administrators are numerous, or content organization affects publishing, compliance, or customer-facing workflows.

Technical view

CVE-2023-0724 is a CSRF flaw in Wicked Folders for WordPress through 2.18.16. The ajax_add_folder function has missing or incorrect nonce validation, allowing an unauthenticated attacker to induce an administrator’s browser to perform administrator-intended folder actions.

Likely exposure

Exposure is limited to WordPress sites running Wicked Folders through version 2.18.16. Risk is higher where administrators stay logged in and can be lured to attacker-controlled links or pages. The stated impact is limited confidentiality and integrity impact, with no availability impact.

Exploitation context

The supplied sources require administrator interaction and do not identify KEV listing or active exploitation. The attacker must trick an administrator into performing an action, such as clicking a link, that sends a forged request to the WordPress site.

Researcher notes

Root cause is missing or incorrect nonce validation on ajax_add_folder, mapped to CWE-352. Validate exposure by version and code path, but avoid assuming broader WordPress compromise. The source bundle does not provide exploit telemetry or a named fixed version.

Mitigation direction

  • Inventory WordPress sites for the Wicked Folders plugin and installed version.
  • Update Wicked Folders according to WordPress plugin or vendor guidance.
  • Restrict administrator sessions to trusted devices and reduce unnecessary persistent logins.
  • Educate administrators to avoid unsolicited links while authenticated to WordPress.

Validation and detection

  • Confirm whether Wicked Folders is installed on each WordPress site.
  • Verify any installed version is not 2.18.16 or earlier.
  • Review plugin changelog or vendor advisory for the nonce validation fix.
  • Check logs for unexpected folder-structure changes around administrator sessions.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-0724 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-0724Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wickedpluginsWicked Folders – Folder Organizer for Pages, Posts, and Custom Post Types0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.