Description
The MetForm WordPress plugin before 4.3.1 does not properly restrict access to a debug file it writes to the web root on every form submission when its HubSpot Forms integration is enabled, allowing unauthenticated attackers to read upstream API response data, including correlation identifiers and cookies.
Published: 2026-10-03
Score: 3.7 Low
EPSS: < 1% Very Low
KEV: No
Impact: Information Disclosure
Action: Patch
AI Analysis

Impact

The MetForm WordPress plugin, versions 2.2.1 through 4.3.0, can be configured to enable a HubSpot Forms integration. When this integration is active, the plugin writes a debug file to the web‑root on every form submission. The file contains upstream API response data, including correlation identifiers and cookies, and is accessible without authentication. An attacker can read this file, potentially revealing sensitive request details, session tokens, or other data that could facilitate further compromise.

Affected Systems

WordPress sites that have the MetForm plugin installed in versions before 4.3.1 and have the HubSpot Forms integration enabled are affected. Site administrators should be aware that any user able to access the site root can read this debug file.

Risk and Exploitability

The vulnerability is exploitable from any public internet‑reachable server that hosts the affected WordPress installation, as it requires no authentication. While EPSS data is not available and the vulnerability is not listed in the CISA KEV catalog, the risk of sensitive information leakage remains significant. An attacker can simply request the debug file directly via HTTP GET, making the attack straightforward and likely to succeed if the file is reachable. The potential confidentiality impact is high because the file exposes session cookie data and correlation identifiers.

Generated by OpenCVE AI on October 3, 2026 at 07:24 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the MetForm plugin to version 4.3.1 or later, which removes the insecure debug file.
  • If the HubSpot Forms integration is not required, disable it in the plugin settings.
  • Restrict access to files in the web‑root by configuring the web server or adding .htaccess rules to deny anonymous read access to the debug file location.

Generated by OpenCVE AI on October 3, 2026 at 07:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 03 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sat, 03 Oct 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200

Sat, 03 Oct 2026 06:15:00 +0000

Type Values Removed Values Added
Description The MetForm WordPress plugin before 4.3.1 does not properly restrict access to a debug file it writes to the web root on every form submission when its HubSpot Forms integration is enabled, allowing unauthenticated attackers to read upstream API response data, including correlation identifiers and cookies.
Title MetForm 2.2.1 - 4.3.0 - Unauthenticated Debug File Disclosure via HubSpot Forms Integration
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-10-03T15:12:21.948Z

Reserved: 2026-09-08T14:33:20.926Z

Link: CVE-2026-86834

cve-icon Vulnrichment

Updated: 2026-10-03T15:01:39.876Z

cve-icon NVD

Status : Received

Published: 2026-10-03T06:16:44.013

Modified: 2026-10-03T16:16:39.793

Link: CVE-2026-86834

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-03T07:30:20Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor