dbcve.org
Media Library AssistantWordPress extension · Davidlingren

CVE-2024-2871

HIGH · 7.7 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 3.14 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

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.

NVD · unedited
The Media Library Assistant plugin for WordPress is vulnerable to SQL Injection via the plugin's shortcode(s) in all versions up to, and including, 3.13 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor access or higher, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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.

dbcve analysis · high confidence

The Media Library Assistant WordPress plugin versions up to 3.13 contains a SQL injection vulnerability in its shortcode functionality. The vulnerability stems from insufficient escaping of user-supplied parameters combined with lack of prepared statements in the underlying SQL queries, allowing authenticated contributors or higher to inject malicious SQL commands and extract sensitive database information.

MitigationUpdate the Media Library Assistant plugin to version 3.14 or later which contains the security patch. Additionally, review user roles and permissions to ensure only trusted users have contributor-level access or higher.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Media Library AssistantWordPress extension
Affected:< 3.14

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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.

dbcve checks

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

  1. Verify Media Library Assistant plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Media Library Assistant' in the list. Note the installed version number displayed below the plugin name.
    Affected if Plugin is installed and version is below 3.14 (e.g., 3.13, 3.12, etc.)
  2. Confirm shortcode usage in content
    Search WordPress posts, pages, or custom post types for the presence of MLA shortcodes such as [mla_gallery], [mla_tag_cloud], [mla_term_list], or other [mla_*] shortcode tags using the WordPress editor or by querying the wp_posts table.
    Affected if Any MLA shortcode is present in published content, enabling the vulnerable code path
  3. Check for authenticated contributor-level or higher users
    Navigate to WordPress admin > Users and review the user list. Identify any users assigned the Contributor, Author, Editor, or Administrator role who have access to create or edit content containing shortcodes.
    Affected if At least one user with Contributor-level or higher access exists, as this privilege is required to exploit the SQL injection
  4. Inspect server logs for suspicious SQL patterns
    Review web server error logs and WordPress debug logs (if enabled) for unusual SQL syntax or database errors originating from MLA shortcode processing, which may indicate exploitation attempts.
    Affected if Unusual SQL error messages or query patterns appear in logs related to MLA functionality

A user is affected if the Media Library Assistant plugin version is below 3.14 AND shortcodes are in use AND at least one authenticated user with Contributor-level access or higher exists in the system.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.14 or later
Fixed in 3.14
Interim mitigation

Update the Media Library Assistant plugin to version 3.14 or later which contains the security patch. Additionally, review user roles and permissions to ensure only trusted users have contributor-level access or higher.

Recommended fix High confidence

Media Library Assistant version 3.14

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Media Library Assistant' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 3.14 of the plugin
  5. Verify the update completed successfully by checking the plugin version

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

Fix this in Media Library Assistant Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2871 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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