Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-6075

HIGH · 8.1 CVSS v3.1 Published 2026-05-29

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

88/100

Remediation priority · High

Remotely reachable No privileges

Official description

NVD · unedited

The Media Library Assistant plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.35 This is due to missing nonce verification on the bulk action handlers in the settings tab handlers. This makes it possible for unauthenticated attackers to trick an administrator into performing bulk delete, edit, or purge operations on plugin settings and attachment metadata via a forged request.

Technical summary

dbcve analysis · high confidence

The Media Library Assistant WordPress plugin versions up to 3.35 lack nonce verification on bulk action handlers in the settings tab, allowing unauthenticated attackers to forge requests that trick administrators into performing bulk delete, edit, or purge operations on plugin settings and attachment metadata.

MitigationUpgrade to version 3.36 or later, which should include proper nonce verification. Alternatively, disable bulk action functionality in the settings until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if Media Library Assistant plugin is installed

Check your WordPress installation's wp-content/plugins directory for the media-library-assistant folder, or look for the plugin in the WordPress admin under Plugins > Installed Plugins

Affected if The plugin folder media-library-assistant exists in the plugins directory
Determine the installed plugin version

Locate the main plugin file (media-library-assistant.php) and check the Version header in the plugin comments at the top of the file, or view the version in WordPress admin under Plugins > Installed Plugins > Media Library Assistant

Affected if The reported version number is 3.35 or lower (any version up to and including 3.35)
Verify bulk action handlers exist in plugin settings

Access the Media Library Assistant settings in WordPress admin under Settings > Media Library Assistant, then navigate to the Tabs or Settings subpages where bulk operations are available (such as MLA Settings tab or bulk edit/purge options)

Affected if Bulk action dropdown menus or buttons for delete, edit, or purge operations are present on any settings subpage

You are affected if Media Library Assistant plugin is installed with version 3.35 or lower and the plugin settings contain accessible bulk action handlers for delete, edit, or purge operations.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade to version 3.36 or later, which should include proper nonce verification. Alternatively, disable bulk action functionality in the settings until the patch can be applied.

Recommended fix Moderate confidence

Version 3.36 or later

1. Navigate to the WordPress admin dashboard
2. Go to Plugins > Installed Plugins
3. Locate the Media Library Assistant plugin
4. If an update is available, click 'Update Now'
5. After updating, verify the new version is 3.36 or later
6. Test bulk operations in the plugin settings to confirm functionality works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA2.0 h

10.0 hours of engineering $1,780

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-6075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6075 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-6075?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 8.1 High

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

A high-priority fix

Have this fixed 10 hrs · Moderate

Typical engagement from $1,780

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-6075 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References