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

CVE-2026-9714

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-29
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 Simple Divi Shortcode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' parameter of the [showmodule] shortcode in versions up to, and including, 1.2 This is due to insufficient input sanitization and output escaping in the showmodule_shortcode() function, which concatenates the 'id' shortcode attribute directly into a dynamically constructed shortcode string without applying esc_attr() or any escaping, allowing an attacker to break out of the attribute context and inject arbitrary HTML. 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 Simple Divi Shortcode plugin for WordPress versions up to 1.2 contains a stored XSS vulnerability in the showmodule_shortcode() function. The 'id' parameter from the [showmodule] shortcode is concatenated directly into a dynamically constructed shortcode string without any sanitization or escaping (missing esc_attr()), allowing authenticated attackers with contributor-level access to break out of the attribute context and inject arbitrary HTML/JavaScript.

MitigationApply sanitize_text_field() to the 'id' parameter on input and use esc_attr() when concatenating it into the dynamic shortcode string to prevent attribute breakout and ensure proper output escaping.

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. Confirm plugin installation
    Go to WordPress admin > Plugins and look for 'Simple Divi Shortcode' in the installed plugins list
    Affected if Plugin is installed and active
  2. Check installed version
    In Plugins list, click on the plugin details or check the plugin header in /wp-content/plugins/simple-divi-shortcode/ for the Version defined
    Affected if Version is 1.2 or lower (the vulnerability affects up to 1.2)
  3. Locate vulnerable function
    Access the plugin files via FTP or file manager, open the main plugin PHP file and search for function showmodule_shortcode()
    Affected if Function exists and contains the [showmodule] shortcode handler
  4. Inspect code for missing escaping
    Within showmodule_shortcode(), locate where the 'id' shortcode attribute is used. Check if it is wrapped with esc_attr() or other sanitization before being inserted into the shortcode string
    Affected if The 'id' parameter is used without esc_attr() or output escaping (vulnerable code pattern: do_shortcode("[showmodule id=" . $id . "]") or similar)
  5. Check for shortcode usage
    Search WordPress posts/pages content for [showmodule] shortcode usage by querying wp_posts table or using a search plugin
    Affected if The [showmodule] shortcode with an 'id' attribute is present in any published content

You are affected if the Simple Divi Shortcode plugin version 1.2 or lower is installed, the showmodule_shortcode() function lacks esc_attr() on the 'id' parameter, and the shortcode is actively used in site content.

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

Apply sanitize_text_field() to the 'id' parameter on input and use esc_attr() when concatenating it into the dynamic shortcode string to prevent attribute breakout and ensure proper output escaping.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version > 1.2)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Simple Divi Shortcode plugin
  4. Check if the current version is 1.2 or below
  5. If vulnerable, update the plugin to the latest available version from the WordPress plugin repository
  6. After updating, verify the plugin version is above 1.2

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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