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

CVE-2026-8869

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-27
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 Mutual Funds Data plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title' shortcode attribute in versions up to, and including, 1.2.1. This is due to insufficient input sanitization and output escaping on the user supplied 'title' attribute in the mfd_shortcode() function, which is concatenated directly into the HTML output within a <caption> element. This makes it possible for authenticated attackers, with Contributor-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 Mutual Funds Data WordPress plugin fails to sanitize and escape the 'title' attribute in its mfd_shortcode() function, allowing stored XSS. An authenticated attacker with Contributor+ access can inject malicious JavaScript via [mfd title='<script>...</script>'], which executes in the <caption> HTML element whenever pages containing the shortcode are accessed.

MitigationUpdate to a patched version when available, or add proper input sanitization (like sanitize_text_field()) and output escaping (like esc_html() or esc_attr()) to the title attribute in the mfd_shortcode() function.

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. Identify if Mutual Funds Data plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Mutual Funds Data' or 'mfd' in the plugin list. Alternatively, check the wp-content/plugins directory for a folder named 'mutual-funds-data' or similar.
    Affected if The plugin is installed and active in the WordPress environment
  2. Check the plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on the Mutual Funds Data plugin to view its version number. Compare this to any patched version that may have been released.
    Affected if The installed version lacks the security fix for sanitizing and escaping the title attribute
  3. Search for usage of the mfd shortcode with title attribute
    In WordPress admin, go to Posts or Pages and search for content containing '[mfd' shortcode. Alternatively, query the wp_posts table in the database for posts containing the pattern 'mfd title='.
    Affected if The shortcode [mfd title='...'] is present in any published content
  4. Inspect the rendered HTML for unescaped title content
    View a page containing the [mfd] shortcode in a browser, right-click and inspect the element. Look for the <caption> element where the title attribute value should appear. Check if the raw title value (including any script tags) is present without HTML encoding.
    Affected if The title value appears unescaped in the HTML (e.g., <script> tags are visible in the page source rather than being rendered as text)
  5. Verify the mfd_shortcode function for missing escaping
    Access the plugin source file containing mfd_shortcode() (typically in the main plugin PHP file). Search for the code that handles the 'title' attribute. Check if sanitize_text_field() or esc_html() / esc_attr() is applied before outputting the title value.
    Affected if The title attribute is output directly without sanitization or escaping functions, allowing injected HTML/JavaScript to be rendered

A user is affected if the Mutual Funds Data plugin is installed, the [mfd title='...'] shortcode is used in any content, and the plugin code lacks proper sanitization and escaping for the title attribute in the mfd_shortcode() function.

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

Update to a patched version when available, or add proper input sanitization (like sanitize_text_field()) and output escaping (like esc_html() or esc_attr()) to the title attribute in the mfd_shortcode() function.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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