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

CVE-2026-34887

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Extend Themes Kubio AI Page Builder allows Stored XSS.This issue affects Kubio AI Page Builder: from n/a through 2.7.0.

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 · moderate confidence

Stored XSS vulnerability in Extend Themes Kubio AI Page Builder allows attackers to inject malicious scripts through unsanitized user inputs that get stored and executed when other users view the affected content. The vulnerability stems from improper neutralization of input during web page generation.

MitigationUpdate Kubio AI Page Builder to a version beyond 2.7.0 where the vulnerability has been patched; until then, disable the affected component or implement output escaping at all user input points.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

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 Kubio AI Page Builder is installed
    Navigate to WordPress admin dashboard and check the Plugins or Theme section to verify Kubio AI Page Builder is present and active
    Affected if Kubio AI Page Builder is not installed or not active in the WordPress environment
  2. Identify the installed version number
    In the WordPress admin, locate the version information for Kubio AI Page Builder in the plugin/theme details panel, or check the plugin file header via file system access if available
    Affected if The installed version is 2.7.0 or any earlier version; versions beyond 2.7.0 contain the patch
  3. Determine if AI-generated content features are in use
    Review pages or posts created using Kubio's AI content generation or AI-assisted input features; check whether any user-provided text inputs are processed through Kubio
    Affected if AI content generation or user input fields within Kubio are actively used to create or modify content
  4. Inspect stored content for unsanitized script tags
    Examine the database or page content for unexpected script tags, javascript: URIs, or event handler attributes (onload, onerror, onclick, etc.) in fields that accept user input through Kubio
    Affected if Stored content contains unescaped HTML script tags or JavaScript event handlers that were injected via Kubio input fields

A user is affected if Kubio AI Page Builder versions 2.7.0 or earlier are installed with AI content input features actively used, and unsanitized script tags exist in stored 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Kubio AI Page Builder to a version beyond 2.7.0 where the vulnerability has been patched; until then, disable the affected component or implement output escaping at all user input points.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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