dbcve.org
Media Library AssistantWordPress extension · Davidlingren

CVE-2018-20982

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 2.74 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 before 2.74 for WordPress has XSS via the Media/Assistant or Settings/Media Library assistant admin submenu screens.

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

Cross-site scripting (XSS) vulnerability in the media-library-assistant WordPress plugin before version 2.74 allows authenticated attackers (with admin-level access) to inject malicious JavaScript through the Media/Assistant or Settings/Media Library assistant admin submenu screens.

MitigationUpdate the media-library-assistant plugin to version 2.74 or later, or uninstall the plugin if not needed.

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:< 2.74

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Media Library Assistant' in the list of active plugins
    Affected if The plugin appears in the installed plugins list and is activated
  2. Retrieve installed version number
    In the Plugins list, click on the plugin name or view details for 'Media Library Assistant' to display the version number
    Affected if The displayed version number is less than 2.74 (for example, 2.73, 2.70, etc.)
  3. Verify admin access exists
    Confirm you have administrator-level access to the WordPress dashboard
    Affected if You can log in as an administrator user to the WordPress site
  4. Check for vulnerable admin screens
    Navigate to Media > Assistant or Settings > Media Library Assistant in the WordPress admin panel
    Affected if These admin submenu screens are accessible and functional (the vulnerability exists in these specific screens when the plugin version is below 2.74)

You are affected if the Media Library Assistant plugin is installed with a version number below 2.74 and you have administrator access to the WordPress admin dashboard.

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.

From vendor data
Upgrade available Upgrade to 2.74 or later
Fixed in 2.74
Interim mitigation

Update the media-library-assistant plugin to version 2.74 or later, or uninstall the plugin if not needed.

Fix this in Media Library Assistant Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-20982 — 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-2018-20982 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