CVE-2026-6075
CSRF flaw in WordPress Media Library Assistant (<=3.35) allows bulk admin actions via forged requests.
Is CVE-2026-6075 being exploited?
Not confirmed. CVE-2026-6075 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-6075?
CVE-2026-6075 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-6075?
Not known from our data. No patch reference has been recorded for CVE-2026-6075, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-6075 affect?
CVE-2026-6075 affects WordPress, Media Library Assistant plugin (<=3.35). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-6075?
Update to patched version; ensure nonce checks; monitor admin bulk actions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
CSRF enables attacker to trigger admin bulk delete/edit/purge of plugin settings and attachment metadata.
Patch when possible
- affected<= 3.35
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.