LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1908: Integration with Hubspot Forms <= 1.2.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes

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.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1908 affects the WordPress plugin Integration with Hubspot Forms. A logged-in user with Contributor or higher rights could place a malicious HubSpot form shortcode that runs script in visitors’ browsers when the page is viewed. This is not reported as actively exploited in the provided sources.

Executive priority

Treat as a moderate-priority web application issue. It requires a logged-in content user, but successful abuse could affect visitors or administrators viewing compromised content. Prioritize sites with many content contributors or external marketing users.

Technical view

The flaw is stored cross-site scripting in the hubspotform shortcode attributes, caused by insufficient sanitization and output escaping. Sources describe affected versions as all releases up to and including 1.2.2. CVSS is 6.4, network exploitable, low complexity, requiring low privileges, with changed scope and limited confidentiality/integrity impact.

Likely exposure

Exposure is limited to WordPress sites using Integration with Hubspot Forms <= 1.2.2 where untrusted or less-trusted users have Contributor-level or higher accounts. Sites without the plugin, without affected versions, or without such user roles are less exposed.

Exploitation context

An attacker needs authenticated WordPress access at Contributor level or above. The stored script would execute when a user views the injected page. The provided bundle marks KEV as false and includes no cited evidence of active exploitation.

Researcher notes

The source data is clear on the vulnerability class, required privilege, shortcode vector, and CVSS score. It does not identify a fixed version or confirm exploitation. The affected-version metadata is inconsistent, so rely on the narrative statement and vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the Integration with Hubspot Forms plugin.
  • Identify installed plugin versions and prioritize versions <= 1.2.2.
  • Review vendor or WordPress plugin guidance for an updated fixed release.
  • Restrict Contributor-level access to trusted users until remediated.
  • Review content containing hubspotform shortcodes for suspicious attributes.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Check the installed plugin version against <= 1.2.2.
  • List users with Contributor, Author, Editor, or Administrator roles.
  • Review pages and posts using the hubspotform shortcode.
  • Check security logs for unusual edits by lower-privileged users.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1908 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2026-1908Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
minnurIntegration with Hubspot Forms0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.