Media Library AssistantWordPress extension · Davidlingren
CVE-2020-11732
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 · uneditedThe Media Library Assistant plugin before 2.82 for Wordpress suffers from a Local File Inclusion vulnerability in mla_gallery link=download.
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 confidenceThe Media Library Assistant WordPress plugin before version 2.82 contains a Local File Inclusion (LFI) vulnerability in the mla_gallery shortcode functionality with the link=download parameter. This allows unauthenticated attackers to read arbitrary files on the server by manipulating file path inputs.
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
< 2.82CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Media Library Assistant plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and locate 'Media Library Assistant' in the list. Note whether it appears as installed and active.Affected if The plugin is present and active in the WordPress installation
-
Identify the installed plugin versionIn the Plugins list, click on the plugin details for Media Library Assistant and locate the version number displayed in the plugin metadata.Affected if The version number is less than 2.82 (for example, 2.80, 2.81, or any version below 2.82)
-
Verify mla_gallery shortcode existsCheck if the plugin includes shortcode functionality by searching for 'mla_gallery' in the plugin files, typically found in the main plugin file or shortcode handler files.Affected if The mla_gallery shortcode is registered and available in the installation
-
Test for vulnerable parameter accessibilityAttempt to access a page or post containing the mla_gallery shortcode with the link=download parameter, for example: [mla_gallery link=download]. If the shortcode processes this parameter, the vulnerability may be present.Affected if The shortcode accepts and processes the link=download parameter without proper validation
If the plugin is active, version is below 2.82, and the mla_gallery shortcode with link=download parameter is accessible, the installation is likely affected by CVE-2020-11732.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data2.82
Upgrade to Media Library Assistant version 2.82 or later. If immediate upgrade is not possible, consider disabling the plugin or implementing web application firewall rules to block path traversal patterns in request parameters.
Fix this in Media Library Assistant
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-11732 in production — separate from our analysis above.
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.
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.
- 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