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

CVE-2026-4353

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-22
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 CI HUB Connector plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' attribute of the `cihub_metadata` shortcode in all versions up to, and including, 1.2.106 due to insufficient input sanitization and output escaping. 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 CI HUB Connector WordPress plugin fails to sanitize the 'id' attribute in the cihub_metadata shortcode before storing it and fails to escape the value when outputting it, allowing stored XSS injection by authenticated contributors.

MitigationAdd proper input sanitization (e.g., sanitize_text_field) to the 'id' attribute in the shortcode handler and implement output escaping (e.g., esc_attr) when rendering the value.

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 CI HUB Connector plugin is installed
    Go to WordPress Admin > Plugins and look for 'CI HUB Connector' in the installed plugins list. Note the installed version displayed next to the plugin name.
    Affected if The plugin is not installed or not active.
  2. Identify the installed plugin version
    In the Plugins list, click on the plugin name or view details to find the version number. Compare this version against any known fixed version releases.
    Affected if The installed version is older than the version that includes the fix for CVE-2026-4353.
  3. Search for cihub_metadata shortcode usage
    Use WordPress admin search or query the wp_posts table in the database for content containing the shortcode pattern: [cihub_metadata. Look for any instances that include an 'id' attribute.
    Affected if The shortcode with an 'id' attribute exists in any published post, page, or custom post type content.
  4. Inspect shortcode handler for sanitization
    Access the plugin files via file manager or FTP. Locate the shortcode handler function (commonly in includes/ or main plugin file). Search for the 'id' attribute handling within the cihub_metadata shortcode function. Check if sanitize_text_field or similar sanitization is applied to the id parameter.
    Affected if The 'id' attribute is processed without sanitization functions like sanitize_text_field, sanitize_html_class, or absint.
  5. Inspect shortcode output for escaping
    In the same shortcode handler file, locate where the id attribute value is output/displayed. Check if esc_attr, esc_html, or similar escaping functions are used when rendering the id value.
    Affected if The id value is output directly without escaping functions like esc_attr or esc_html.

You are affected if the CI HUB Connector plugin is installed, contains the vulnerable shortcode handler lacking sanitization and escaping, and the cihub_metadata shortcode with an id attribute 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

Add proper input sanitization (e.g., sanitize_text_field) to the 'id' attribute in the shortcode handler and implement output escaping (e.g., esc_attr) when rendering the value.

Recommended fix High confidence

CI HUB Connector plugin version 1.2.107 or later

  1. Upgrade the CI HUB Connector plugin for WordPress to version 1.2.107 or later
  2. After upgrading, verify that the `cihub_metadata` shortcode functions correctly with valid 'id' attributes
  3. Confirm that arbitrary script injection is no longer possible through the 'id' parameter

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
  • 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-4353 — 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-4353 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