Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost attacker-controlled web page
-
ExploitLure authenticated Author-or-above victim to visit
-
ExecutionForge bulk-action request omitting nonce field
-
ImpactTrash or delete Media Library 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 a victim who is a logged-in Media Library Assistant user holding the Author role or above, who must be tricked into interacting with an attacker-controlled request (UI:R) while their WordPress session is active. The specific trigger is a forged request to the Media Library bulk-action handler that OMITS the CSRF nonce field entirely - because the plugin validates the nonce only when its field is present, a request without the field skips validation. Limiting factors that reduce real-world risk: the targeted account must have Author-level privileges or higher, the session must be authenticated at the time, user interaction is required, and only plugin versions before 3.42 are affected. |
| Impact | This is a moderate, not urgent, issue. The CVSS 3.1 base score of 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N) reflects a network-reachable CSRF with integrity-only impact and no confidentiality or availability loss. The signals are internally consistent and point away from mass exploitation: EPSS is 0.11% (1st percentile), there is no CISA KEV listing, and the vuln.today priority label is 'this_month' rather than act_now or emergency. One nuance must be flagged explicitly: CVSS marks PR:N (attacker needs no privileges), which is standard for CSRF because the attacker weaponizes the victim's session - but the description makes clear that exploitation only succeeds if the tricked victim is a logged-in user holding the Author role or above. So while the attacker is unauthenticated, a privileged, authenticated victim and user interaction (UI:R) are both required, which materially narrows the realistic attack surface. The impact is bounded to trashing or deleting media attachments (I:H, A:N), i.e. data loss/manipulation within the Media Library, not code execution or data theft. Overall this is a legitimate medium-priority patch item, not a high-CVSS/low-real-risk false alarm, but the combination of very low EPSS, no KEV, required victim privilege, and required interaction argues against emergency treatment. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing a forged request targeting the Media Library Assistant bulk-action handler, deliberately omitting the CSRF nonce field so the plugin's present-only nonce check is bypassed. The attacker lures a logged-in WordPress user with the Author role or above to visit the page while authenticated; the browser submits the forged request and attachments are moved to trash or deleted. No public exploit identified at time of analysis, though the mechanism is described in the WPScan advisory. |
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 (versions before 3.42) allows an attacker to craft a forged bulk-action request that omits the CSRF nonce field entirely, skipping the plugin's conditional validation and causing a logged-in user with the Author role or above to trash or delete media attachments. Per the assessed vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N), the attacker is unauthenticated, but exploitation only succeeds when a privileged victim with an active WordPress session is induced into issuing the forged request. There is no public exploit identified at time of analysis, EPSS is 0.11% (1st percentile), and the issue carries a this_month priority - a moderate, not urgent, integrity-only risk.
RemediationAI
Vendor-released patch: upgrade Media Library Assistant to version 3.42 or later - this is the only complete fix identified in the available sources, and the WPScan advisory (https://wpscan.com/vulnerability/d2705c60-8d84-4e96-89df-628cdc814058/) is the authoritative vendor reference. Because exploitation depends on a logged-in Author-or-higher session being induced to submit a forged bulk-action request, prioritize the update on sites where low-trust or numerous Author-level accounts exist and where attachment deletion would be disruptive; no alternative workaround or compensating control is described in the available sources, so patching is the recommended course rather than relying on account hardening alone. Given the this_month priority, EPSS of 0.11% (1st percentile) and no known public exploit, this can be scheduled into the normal monthly maintenance window rather than treated as an emergency.
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 a classic CWE-352 cross-site request forgery in the WordPress plugin Media Library Assistant's bulk-action handler. WordPress plugins conventionally protect state-changing admin actions with a nonce (via check_admin_referer() or wp_verify_nonce()) tied to the user's session; here the plugin performs that check only when the nonce field is present in the request, so a request that simply omits the field bypasses validation altogether and the bulk action proceeds. Because WordPress authenticates the request via the victim's existing session cookie, the action executes with the victim's privileges - meaning the blast radius is bounded by the targeted account's capabilities, which in this case must be Author or higher to reach the Media Library bulk operations. Affected versions are Media Library Assistant 0 through 3.41 (fixed in 3.42, EUVD range ">=0, <3.42"); no CPE strings were supplied, so product identification relies on the plugin name and version range. The impact is integrity-only (I:H) with no confidentiality or availability component, and successful exploitation requires user interaction (UI:R) - the trigger mechanism beyond the omitted nonce field is not otherwise 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 holds no privileges (PR:N) but needs a privileged victim to interact (UI:R); impact is deletion/trashing of attachments, so integrity-only (I:H), no confidentiality or availability loss.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The Media Library Assistant WordPress plugin before 3.42 does not consistently validate its CSRF nonce on the Media Library bulk-action handler, checking the nonce only when its field is present, so a forged request that omits the field can cause a logged-in user with the Author role or above to trash or delete attachments.
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-111723
GHSA-vj27-pxm6-rv65
NVD
CVE.org
EPSS
Exploit-DB