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

CVE-2025-14785

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-08
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 6 weeks old

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 Website Builder by SeedProd - Theme Builder, Landing Page Builder, Coming Soon Page, Maintenance Mode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `seedprodnestedmenuwidget` shortcode in all versions up to, and including, 6.20.2 due to insufficient input sanitization and output escaping on user supplied attributes. 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 SeedProd WordPress plugin's 'seedprodnestedmenuwidget' shortcode fails to properly sanitize and escape user-supplied attributes before outputting them in HTML, allowing stored XSS injection. Attackers with contributor-level access can embed malicious JavaScript in shortcode attributes that executes when other users view the affected pages.

MitigationUpgrade to plugin version 6.20.3 or later. As a temporary workaround, review pages using the seedprodnestedmenuwidget shortcode and remove or restrict usage until the patch can be applied.

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. Verify SeedProd plugin is installed
    Go to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'SeedProd' or 'SeedProd Landing Pages' in the plugin list.
    Affected if SeedProd plugin is present in the WordPress installation
  2. Check installed SeedProd version
    In the Plugins list, find SeedProd and note the version number displayed below the plugin name. Compare this to the fixed version 6.20.3.
    Affected if Installed version is lower than 6.20.3 (e.g., 6.20.2, 6.20.1, etc.)
  3. Identify use of the vulnerable shortcode
    Search WordPress posts, pages, and custom post types for the shortcode [seedprodnestedmenuwidget] using the WordPress admin search or by querying the wp_posts database table for this string.
    Affected if Pages or posts contain the [seedprodnestedmenuwidget] shortcode
  4. Inspect shortcode attributes for injection points
    Examine the shortcode usage in affected pages. The shortcode accepts user-supplied attributes that are reflected in HTML output without proper escaping.
    Affected if Shortcode attributes contain unsanitized user input that could contain HTML or JavaScript

A user is affected if SeedProd plugin versions below 6.20.3 are installed AND the seedprodnestedmenuwidget shortcode is present in any published 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

Upgrade to plugin version 6.20.3 or later. As a temporary workaround, review pages using the seedprodnestedmenuwidget shortcode and remove or restrict usage until the patch can be applied.

Recommended fix High confidence

Latest version > 6.20.2 (check wordpress.org for the current stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Website Builder by SeedProd' plugin
  4. Check if the current version is 6.20.2 or lower
  5. If vulnerable, click 'Update Now' to install the latest version, or manually download the latest version from wordpress.org and upload it

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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