Security readout for executives and security teams
Plain-English summary
This is a WordPress plugin issue where an attacker could trick an administrator into clicking a malicious link and cause Wicked Folders to change its folder structure. It is not described as remote takeover, but it can alter admin-managed content organization and may expose limited information.
Executive priority
Handle during normal vulnerability management, with faster action for sites where many administrators manage content or where WordPress admin sessions are heavily used. This is moderate urgency because it requires administrator interaction and has limited stated impact.
Technical view
Wicked Folders through 2.18.16 lacks proper nonce validation in ajax_edit_folder, creating a CSRF condition. The attacker does not need WordPress credentials, but exploitation requires administrator interaction. CVSS 3.1 is 5.4 with low confidentiality and integrity impact and no availability impact.
Likely exposure
Exposure is limited to WordPress sites running Wicked Folders versions up to and including 2.18.16. Sites without the plugin, or with versions outside the affected range, are not indicated as affected by the supplied sources.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Successful abuse depends on social engineering a logged-in administrator into performing an action, such as following a crafted link.
Researcher notes
The strongest evidence identifies missing or incorrect nonce validation in ajax_edit_folder. The supplied affected metadata is sparse and partly inconsistent, so validate against Wordfence, CVE, and plugin repository history before asserting exact fixed-version boundaries.
Mitigation direction
- Inventory WordPress sites for Wicked Folders and record installed versions.
- Upgrade Wicked Folders beyond 2.18.16 if vendor guidance confirms the fixed release.
- Restrict administrator sessions to trusted devices and reduce unnecessary admin access.
- Monitor vendor, Wordfence, and WordPress plugin guidance for confirmed remediation details.
Validation and detection
- Confirm whether Wicked Folders is installed on each WordPress site.
- Check the installed plugin version against the affected range through 2.18.16.
- Review whether ajax_edit_folder includes proper nonce validation in the deployed code.
- Check recent administrative changes to Wicked Folders folder structures for unexpected activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2023-0726 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/51b88442-3961-42e2-8ff4-7726819a7f0f?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/wicked-folders/tags/2.18.16/lib/class-wicked-folders-ajax.phpCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=2860994%40wicked-folders%2Ftrunk&old=2805161%40wicked-folders%2Ftrunk&sfp_email=&sfph_mail=CVE reference
- https://www.wordfence.com/threat-intel/vulnerabilities/id/51b88442-3961-42e2-8ff4-7726819a7f0fCVE reference · x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.