Security readout for executives and security teams
Plain-English summary
A vulnerable Metform WordPress plugin could let an attacker trick an administrator into changing the site's HubSpot integration. If successful, form leads and contacts could be routed to an attacker-controlled HubSpot account. This is a data exposure and integrity issue, not a server takeover based on the provided sources.
Executive priority
Treat this as a moderate-priority remediation for lead-generating WordPress sites. It can affect sales pipeline confidentiality and data integrity, but the known attack path requires administrator interaction and the provided sources do not confirm active exploitation.
Technical view
CVE-2023-6788 is a CSRF flaw in Metform Elementor Contact Form Builder through 3.8.1, tied to missing or incorrect nonce validation in the HubSpot contents function. The CVSS 3.1 score is 5.4, requiring user interaction by an administrator and allowing limited confidentiality and integrity impact.
Likely exposure
Exposure is most likely on WordPress sites running Metform versions up to and including 3.8.1 with HubSpot integration enabled or configured. The business risk is higher for sites collecting sales leads, customer inquiries, or regulated contact data through Metform forms.
Exploitation context
The sources do not show CISA KEV listing or active exploitation evidence. Exploitation requires tricking a site administrator into performing an action such as clicking a link, after which HubSpot token-related options could be changed to connect an attacker-controlled HubSpot account.
Researcher notes
Primary evidence points to missing or incorrect nonce validation in the HubSpot loader code and a WordPress Trac changeset addressing that area. The provided bundle does not independently name a fixed version, so validation should rely on vendor release guidance and installed-code review.
Mitigation direction
- Identify WordPress sites running Metform and prioritize versions at or below 3.8.1.
- Check vendor and WordPress plugin guidance for the fixed Metform release.
- Upgrade Metform away from affected versions when a vendor-fixed build is available.
- Review HubSpot integration settings for unexpected accounts or token changes.
- Rotate HubSpot credentials if unauthorized integration changes are suspected.
Validation and detection
- Inventory Metform plugin versions across managed WordPress sites.
- Confirm whether each site uses the Metform HubSpot integration.
- Review Metform settings for unexpected HubSpot account connections.
- Check lead delivery paths for recent unexplained destination changes.
- Monitor administrator activity around the publication and remediation dates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-352: 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 lookupCVE-2023-6788 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/30fd2425-ee48-4777-91c1-03906d63793a?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/metform/trunk/core/integrations/crm/hubspot/loader.php#L87CVE reference
- https://plugins.trac.wordpress.org/changeset/3011284/metform/trunk/core/integrations/crm/hubspot/loader.phpCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.