Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure logged-in Editor+ to attacker page
-
ExploitBrowser auto-submits forged Empty Trash request
-
ExecutionMissing CSRF nonce check lets request pass
-
ImpactPermanently delete all trashed attachments
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the victim be a logged-in user with the Editor role or above and that they visit or interact with attacker-controlled content while that WordPress session is active - this is the UI:R user-interaction requirement. The specific flaw is that the plugin's 'Empty Trash' media action does not verify a CSRF nonce, so any cross-origin request issued with the victim's session is honored. Meaningful impact additionally depends on the site actually having trashed media attachments present, since only trashed attachments are destroyed. Limiting factors: the attacker needs no account but cannot act alone - they must successfully trick a privileged (Editor+) user; the affected plugin must be installed and running a version before 3.42; and impact is confined to deletion of already-trashed attachments rather than live media or other data. |
| Impact | Signals are consistent and point to a genuine but moderate-priority issue rather than an urgent one. The CVSS 3.1 base score is 6.5 (Medium) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N - network-reachable, low complexity, no attacker privileges, but requiring victim interaction, with impact scored as integrity-only (permanent deletion of trashed attachments). EPSS is very low at 0.11% (1st percentile), indicating no meaningful mass-exploitation signal, and there is no CISA KEV listing and no confirmed public exploit, so active exploitation is not indicated. The vuln.today decision label is 'this_month,' which aligns with the low EPSS and absence of KEV: patch in a normal cycle rather than as an emergency. One point of tension worth noting: the CVSS vector records PR:N (unauthenticated) because the attacker themselves needs no account, but the described impact only occurs against a logged-in Editor-or-above victim who is socially engineered into issuing the forged request - so 'unauthenticated' describes the attacker, not the privilege context of the action. Additionally, the real-world damage is bounded to attachments already in the trash (items a user had already marked for removal), which makes the I:H rating arguably generous relative to practical impact. |
| Exploit ScenarioDerived | An attacker crafts a malicious web page or email containing a hidden auto-submitting request that targets the plugin's Empty Trash media endpoint. When a logged-in Editor or administrator of the target WordPress site visits that page in the same browser session, their authenticated cookies cause the forged request to execute, permanently deleting every trashed attachment on the site. No public exploit is identified at the time of analysis, though a public advisory (WPScan) describes the flaw. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Cross-site request forgery in the WordPress plugin Media Library Assistant before 3.42 allows a remote attacker to permanently delete every trashed attachment on a site by luring a logged-in Editor-or-higher user to attacker-controlled content. The Empty Trash media action performs no CSRF nonce check, so a forged cross-origin request issued in the victim's active WordPress session is honored. No public exploit code or active exploitation has been identified at time of analysis (EPSS ~0.11%), and impact is scoped to media already in the trash rather than live library items; the vendor has released 3.42 to address the flaw.
RemediationAI
Update the Media Library Assistant plugin to version 3.42 or later, which is the vendor-released patch; the upgrade is the complete fix because the release adds the missing nonce verification to the Empty Trash media action. Apply it through the WordPress plugin updater or by deploying the 3.42 package from the vendor, and verify the installed version afterwards, since no official patched version below 3.42 exists. Vendor and record details are at https://wpscan.com/vulnerability/29f5c90d-564a-4844-bf8e-b72243da5a0a/ and https://nvd.nist.gov/vuln/detail/CVE-2026-113486. During the update window the practical exposure is bounded by the attack's own prerequisites: only attachments already in the trash can be destroyed, so permanently emptying the media trash promptly and keeping the number of Editor-or-above accounts to those who genuinely need it limits what a successful forged request could remove, though neither measure substitutes for the 3.42 upgrade. The vendor-priority signal for this CVE is 'this_month' rather than immediate action.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-352 (cross-site request forgery) in the WordPress plugin Media Library Assistant, which extends the WordPress media library with bulk attachment management, shortcodes and gallery features. The plugin's Empty Trash media action is reachable over HTTP but does not validate a WordPress nonce before performing the permanent-deletion operation, so the request's authenticity is inferred from the browser-supplied session cookie alone. Because the action mutates state (irreversible deletion of trashed attachments), the missing nonce removes the standard WordPress defense that ties a request to the user who initiated it. The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N reflects that no attacker account is needed but that the attacker cannot act alone: the request only succeeds inside an authenticated Editor-or-above session, which is the UI:R requirement, and the resulting integrity impact is high with no confidentiality or availability component. The exact request handler and parameter names involved are not described in the available sources.
Know when WordPress gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Classic CSRF: attacker needs no privileges (PR:N) but must trick a logged-in Editor+ (UI:R); permanent deletion of trashed attachments is an integrity/data-loss impact (I:H), with no confidentiality effect.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The Media Library Assistant WordPress plugin before 3.42 does not verify a CSRF nonce on its Empty Trash media action, so a forged cross-site request can cause a logged-in user with the Editor role or above to permanently delete every trashed attachment on the site.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-111724
GHSA-cr4r-w36f-j7h9
NVD
CVE.org
EPSS
Exploit-DB