dbcve.org
Real Media LibraryWordPress extension · Devowl

CVE-2021-34668

MEDIUM · 5.4 CVSS v3.1 Published 2021-08-30
Fix available
A fix is available. Upgrade to after 4.14.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 WordPress Real Media Library WordPress plugin is vulnerable to Stored Cross-Site Scripting via the name parameter in the ~/inc/overrides/lite/rest/Folder.php file which allows author-level attackers to inject arbitrary web scripts in folder names, in versions up to and including 4.14.1.

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 WordPress Real Media Library plugin fails to sanitize the folder name parameter in the ~/inc/overrides/lite/rest/Folder.php file, enabling stored XSS attacks where author-level users can inject malicious JavaScript into folder names that executes when viewed by other users.

MitigationSanitize and escape the folder name parameter using WordPress sanitization functions (sanitize_text_field, esc_html, esc_attr) before storage and output encoding before display. Update to patched version if available.

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
Real Media LibraryWordPress extension
Affected:<= 4.14.1

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Real Media Library plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Real Media Library' by Devowl, or check the filesystem at wp-content/plugins/real-media-library/ for the plugin directory
    Affected if The plugin is installed and the directory exists
  2. Check installed plugin version
    In WordPress admin Plugins page, find Real Media Library and note the version number displayed, or read the version from the plugin's main PHP file header (e.g., real-media-library.php)
    Affected if The version number is 4.14.1 or lower
  3. Inspect the vulnerable file for missing sanitization
    Open wp-content/plugins/real-media-library/inc/overrides/lite/rest/Folder.php and examine the code handling the folder name parameter - look for absence of sanitize_text_field, esc_html, or esc_attr functions around the name parameter
    Affected if The file contains code that processes folder names without using WordPress sanitization functions on the input
  4. Check for suspicious folder names in the database
    Query the WordPress database (wp_posts table where post_type is 'rml_folder' or similar) for folder names containing HTML tags, script tags, or JavaScript event handlers like onload, onerror, or javascript:
    Affected if Folder names in the database contain raw HTML, script tags, or event handler attributes that are not escaped
  5. Verify REST API endpoint accessibility
    Make a GET request to /wp-json/real-media-library/v1/folders or similar REST endpoints exposed by the plugin to confirm the API is accessible
    Affected if The plugin REST API endpoints respond without authentication or with author-level permissions

You are affected if the Real Media Library plugin version is 4.14.1 or lower AND the Folder.php file lacks proper sanitization AND your environment contains author-level users who could inject malicious folder names.

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 a release after 4.14.1
Interim mitigation

Sanitize and escape the folder name parameter using WordPress sanitization functions (sanitize_text_field, esc_html, esc_attr) before storage and output encoding before display. Update to patched version if available.

Fix this in Real Media Library Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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