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

CVE-2026-1889

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-21
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 Outgrow plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' attribute of the 'outgrow' shortcode in all versions up to, and including, 2.1. This is 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 Outgrow WordPress plugin up to version 2.1 contains a stored XSS vulnerability in its shortcode handler. The plugin fails to properly sanitize and escape the 'id' attribute of the [outgrow] shortcode, allowing authenticated users with contributor-level permissions to inject malicious JavaScript that executes when other users access affected pages.

MitigationUpdate the Outgrow plugin to a version beyond 2.1 that implements proper input sanitization and output escaping for shortcode attributes. Until patched, audit existing content using the outgrow shortcode and restrict contributor-level user permissions.

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 Outgrow plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Outgrow' in the installed plugins list, or check for the /wp-content/plugins/outgrow/ directory via file system or hosting file manager
    Affected if The Outgrow plugin directory exists in the WordPress installation
  2. Check the installed version
    In the WordPress Plugins admin page, click on the Outgrow plugin to view its details, or locate and open the plugin header file (typically outgrow.php or readme.txt) to read the Version field
    Affected if The version is 2.1 or lower (versions 2.2 and above are patched)
  3. Search for [outgrow] shortcode usage
    In WordPress admin, search for content containing '[outgrow' or query the wp_posts and wp_postmeta tables in the database for posts with that shortcode string in post_content
    Affected if Any page, post, or widget content contains the [outgrow] shortcode
  4. Inspect shortcode for id attribute
    Examine the shortcode instances found - look specifically for [outgrow id="value"] or [outgrow id='value'] patterns in the content
    Affected if The [outgrow] shortcode is used with an id attribute present

You are affected if the Outgrow plugin version is 2.1 or lower AND your WordPress site contains content using the [outgrow] shortcode with an id attribute, which could contain unsanitized JavaScript from contributor-level users.

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 Outgrow plugin to a version beyond 2.1 that implements proper input sanitization and output escaping for shortcode attributes. Until patched, audit existing content using the outgrow shortcode and restrict contributor-level user permissions.

Recommended fix Moderate confidence

Latest version on WordPress.org repository (version higher than 2.1)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Outgrow plugin
  4. Check if an update is available and install the latest version
  5. After updating, verify the plugin is running on a version newer than 2.1

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
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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