Media Library Assistant < 3.42 - Bulk Attachment Deletion via CSRF
CVSS score
—
EPSS probability
—
Risk score
—
Published
2 h ago
Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
DayBreach AI Explanation
Verified against sourcesSources read
2
Source agreement
Tam uyum
Evidence confidence
%63
Short explanation
Versions of the Media Library Assistant plugin prior to 3.42 only validate the CSRF nonce on the bulk‑action handler when the nonce field is present; if the field is omitted the check is skipped. This allows a logged‑in user with the Author role or higher to send a forged request that bulk‑trashes or deletes attachments.
When a permitted user role can delete media files in bulk, it can lead to loss of site content and possible service disruption.
What should be done?
- Apply vendor update when available
- Enforce strict CSRF checks for all bulk actions
- Limit Author role permissions if unnecessary
- Monitor media library activity for unexpected deletions
- Deploy WAF rule to block crafted bulk‑action requests
Chain of evidence and sources
Media Library Assistant eklentisinin 3.42 öncesi sürümleri, CSRF nonce alanı yoksa doğrulamayı atlar (S0, S1).
CVE‑2026‑113485 için aktif istismar raporlanmamıştır (S0).
Yama durumu resmi kaynaklarda doğrulanamadı; durum UNKNOWN olarak değerlendirilmiştir (S0).
Show the technical text from the sources
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.
This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.
IMPACT: Affected Products and Software
Affected Products
The following products are affected by CVE-2026-113485 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.
| ID | VENDOR | PRODUCT | ACTION |
|---|---|---|---|
| 1 | Unknown | Media Library Assistant | View |
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| The sources have not yet published a verified CVSS metric. | ||||
Patch and Remediation Guide
Solution & Remediation Advisory
İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.
Public exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-113485 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-113485 weaknesses.
Official Sources and Advisories
Yama durumu bilinmiyor
Similar Vulnerabilities
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-113485"