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

CVE-2026-3600

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-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

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 Investi plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'investi-announcements-accordion' shortcode's 'maximum-num-years' attribute in all versions up to, and including, 1.0.26. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes. Specifically, the 'maximum-num-years' attribute value is read directly from shortcode attributes and interpolated into a double-quoted HTML attribute without any escaping (no esc_attr(), htmlspecialchars(), or similar). 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 Investi WordPress plugin fails to escape the 'maximum-num-years' shortcode attribute when rendering it in HTML. The attribute value is directly interpolated into a double-quoted HTML attribute context without any sanitization (e.g., esc_attr()), allowing an attacker to break out of the attribute and inject arbitrary JavaScript.

MitigationUpdate the Investi plugin to a version beyond 1.0.26 when available, or apply a code fix to escape the 'maximum-num-years' attribute using esc_attr() before output.

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 Investi plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate the Investi plugin. Note the installed version number.
    Affected if The plugin is installed and the version is lower than 1.0.27 or the version cannot be determined.
  2. Search for vulnerable shortcode usage in content
    Query the WordPress database for posts, pages, or custom post types containing the string 'investi-announcements-accordion'. Use WP_Query, grep the database dump, or search via a plugin like Search Regex.
    Affected if The shortcode 'investi-announcements-accordion' is found in any published content.
  3. Check for the vulnerable attribute in shortcodes
    Examine each instance of the 'investi-announcements-accordion' shortcode found in content. Look for the presence of the 'maximum-num-years' attribute.
    Affected if The 'maximum-num-years' attribute is present in any shortcode usage and is populated with untrusted/user-controlled input.
  4. Verify attribute is unescaped in output
    View a page containing the shortcode with a 'maximum-num-years' attribute. View the page source and locate the HTML element where this attribute should appear. Check if the value is wrapped in double quotes but not escaped (no ", no HTML entities for quotes, no esc_attr output).
    Affected if The 'maximum-num-years' value appears as raw text inside a double-quoted HTML attribute without proper escaping.

A user is affected if the Investi plugin is installed with a version below 1.0.27 AND the 'investi-announcements-accordion' shortcode with a 'maximum-num-years' attribute is in use on their site.

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 the Investi plugin to a version beyond 1.0.26 when available, or apply a code fix to escape the 'maximum-num-years' attribute using esc_attr() before output.

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-3600 — 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-3600 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