LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1883: Wicked Folders <= 4.1.0 - Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary Folder Deletion

The Wicked Folders – Folder Organizer for Pages, Posts, and Custom Post Types plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.1.0 via the delete_folders() function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete arbitrary folders created by other users.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1883 affects the Wicked Folders WordPress plugin through version 4.1.0. A logged-in user with Contributor or higher privileges can delete folders created by other users. This is not a public unauthenticated takeover issue, but it can disrupt site content organization and workflows where lower-privileged accounts exist.

Executive priority

Treat as a routine but timely WordPress plugin remediation. Prioritize sites with many contributors or shared editorial workflows. The main risk is unauthorized deletion of organizational folders, not full site compromise based on current sources.

Technical view

The plugin has an insecure direct object reference in delete_folders() caused by missing validation on a user-controlled key. Authenticated Contributor+ users can target arbitrary folders owned by other users. CVSS 3.1 is 4.3: network-accessible, low complexity, low privileges, no user interaction, integrity impact only.

Likely exposure

WordPress sites running Wicked Folders – Folder Organizer for Pages, Posts, and Custom Post Types version 4.1.0 or earlier are potentially exposed, especially where Contributor, Author, Editor, or Administrator accounts are broadly assigned.

Exploitation context

The provided sources do not indicate active exploitation, and this CVE is not listed as CISA KEV. Exploitation requires an authenticated account with Contributor-level access or higher, limiting exposure compared with unauthenticated plugin vulnerabilities.

Researcher notes

This is CWE-639 authorization bypass/IDOR in delete_folders(). Evidence points to missing object ownership or authorization validation around a user-controlled key. Public sources provide impact and a WordPress Trac changeset, but no confirmed exploitation or detailed fixed version in the supplied bundle.

Mitigation direction

  • Identify sites using Wicked Folders and record installed versions.
  • Update the plugin according to WordPress or vendor guidance.
  • If no safe update is available, restrict Contributor+ access to trusted users.
  • Review and reduce unnecessary WordPress accounts and roles.
  • Back up site data before applying plugin changes.

Validation and detection

  • Check whether Wicked Folders is installed on each WordPress site.
  • Confirm installed versions are not 4.1.0 or earlier.
  • Review plugin changelog or WordPress Trac for the referenced fix.
  • Audit recent folder deletion activity by non-admin users.
  • Verify Contributor users cannot delete folders owned by others after remediation.
Prepared
Confidence
high
Sources
4

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 · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2026-1883 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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
3Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-1883Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.