dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-10093

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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 File Sharing & Download Manager – User Private Files plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'fldr_ttl' parameter in all versions up to, and including, 2.1.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 plugin 'File Sharing & Download Manager – User Private Files' fails to properly sanitize the 'fldr_ttl' parameter during input processing and does not escape output when displaying the folder title, allowing authenticated users with subscriber-level permissions to inject persistent malicious JavaScript that executes whenever other users access affected pages.

MitigationUpdate the plugin to a version beyond 2.1.6 when available; alternatively, implement proper input sanitization using functions like sanitize_text_field() and output escaping using esc_html() or esc_attr() on the 'fldr_ttl' parameter throughout the codebase.

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

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Locate the plugin installation directory
    Check the WordPress plugins folder at wp-content/plugins/ for a directory named 'file-sharing-download-manager', 'user-private-files', or similar names containing 'file sharing' or 'download manager' in the folder name. Alternatively, list installed plugins via WP-CLI: wp plugin list --status=active --field=name
    Affected if The plugin directory exists in the WordPress installation's plugin folder and the plugin is active
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually in the plugin root directory, commonly named plugin-name.php or index.php) and locate the version constant or header comment. Example path: wp-content/plugins/[plugin-folder]/[plugin-name].php. With WP-CLI: wp plugin get [plugin-name] --field=version
    Affected if The version number is at or below 2.1.6, or the version cannot be determined (older unversioned releases are likely affected)
  3. Verify subscriber-level user role exists and can access the plugin
    In WordPress admin, go to Users > All Users and confirm at least one user with the Subscriber role exists. Then check if the plugin creates any menu items or pages accessible to subscribers under the Users or Profile section, or check the plugin settings for role-based access controls using wp-cli: wp role list --fields=name | grep subscriber
    Affected if Subscriber role users exist AND the plugin provides folder/file management functionality accessible to that role (even if limited to their own files)
  4. Inspect the folder title parameter handling
    If you have access to the plugin source code, search the plugin PHP files for occurrences of 'fldr_ttl' or 'folder_title' and verify whether sanitize_text_field(), esc_html(), or esc_attr() is applied when reading this parameter and when outputting it. Use grep: grep -r 'fldr_ttl' wp-content/plugins/[plugin-folder]/
    Affected if The code reads 'fldr_ttl' without sanitize_text_field() on input OR outputs folder title without esc_html()/esc_attr() on output, indicating the vulnerability is present in the installed version

A user is affected if the plugin is installed, the version is 2.1.6 or lower (or unidentifiable), subscriber-role users exist with access to the plugin's folder management features, and the code does not sanitize/escape the fldr_ttl parameter.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 2.1.6 when available; alternatively, implement proper input sanitization using functions like sanitize_text_field() and output escaping using esc_html() or esc_attr() on the 'fldr_ttl' parameter throughout the codebase.

Recommended fix Moderate confidence

Latest version higher than 2.1.6 (check WordPress plugin repository for 2.1.7 or later)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'File Sharing & Download Manager – User Private Files'
  4. Check if an update is available and update to the latest version (version higher than 2.1.6)
  5. Verify the update was successful

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

Have this fixed 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 help mitigating

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-2026-10093 — 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-2026-10093 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