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

CVE-2026-1908

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 Integration with Hubspot Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'hubspotform' shortcode in all versions up to, and including, 1.2.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 Integration with Hubspot Forms WordPress plugin versions up to 1.2.2 contains a stored XSS vulnerability in the 'hubspotform' shortcode. Due to insufficient input sanitization and output escaping on user-supplied attributes, authenticated attackers with Contributor-level permissions or higher can inject malicious JavaScript that persists in pages and executes when users access those pages.

MitigationUpdate to a patched version of the plugin once available, or remove/disable the plugin until a fix can be applied. For immediate mitigation, review and remove any malicious shortcode injections in existing content.

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 the Integration with Hubspot Forms plugin is installed
    Log in to the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate the 'Integration with Hubspot Forms' plugin in the list
    Affected if The plugin is present on the site
  2. Determine the installed plugin version
    In the Plugins list, click on the plugin name to view its details, or check the plugin header comment in the main plugin file (typically in /wp-content/plugins/hubspot-forms-integration/ or similar)
    Affected if The displayed version is 1.2.2 or lower (the vulnerability affects versions up to 1.2.2)
  3. Search for hubspotform shortcode usage in content
    Use the WordPress admin search or query the wp_posts table in the database for occurrences of the shortcode '[hubspotform' in post_content, page_content, or custom post type content
    Affected if The shortcode is found in any published content
  4. Inspect shortcode attributes for suspicious content
    Examine each instance of the hubspotform shortcode and review all attribute values (such as portal_id, form_id, or any custom attributes) for unusual characters like <, >, ", ', or javascript: patterns that may indicate injected payloads
    Affected if Any hubspotform shortcode contains attribute values with encoded or raw HTML/JavaScript code
  5. Review recent content authored by Contributor-level users
    In the WordPress admin, go to Posts > All Posts and filter or sort by author role, or query the database to identify posts created by users with the Contributor role since the plugin was installed
    Affected if There are posts or pages created by users who have Contributor-level permissions that contain the hubspotform shortcode

A site is affected if the Integration with Hubspot Forms plugin version 1.2.2 or lower is installed AND the hubspotform shortcode is present in any content with potentially malicious attribute values.

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 to a patched version of the plugin once available, or remove/disable the plugin until a fix can be applied. For immediate mitigation, review and remove any malicious shortcode injections in existing content.

Recommended fix Moderate confidence

Latest version of the Integration with Hubspot Forms plugin (version higher than 1.2.2)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Integration with Hubspot Forms' plugin
  4. Check if an update is available and update to the latest version
  5. Verify the update was applied successfully

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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