EUVD-2026-51689
GHSA-j262-2rh9-xjv4
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconIdentify WordPress site with Bit Integrations ≤2.9.0
-
DeliverySubmit crafted request to CF7/mail attachment endpoint
-
ExploitInject path traversal sequences in attachment parameter
-
InstallprocessAttachment resolves traversed path without sanitization
-
C2Read arbitrary server file contents
-
ExecuteExtract wp-config.php database credentials
-
ImpactEscalate to full site compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions are required beyond the target WordPress site having the Bit Integrations plugin installed and active in any version up to and including 2.9.0. The CVSS vector (PR:N/AC:L/UI:N) confirms exploitation is unauthenticated and requires no user interaction. The attack surface is network-accessible via standard WordPress HTTP endpoints (likely wp-ajax.php or form submission handlers tied to Contact Form 7 triggers). Exploitation is limited to sites with the Bit Integrations plugin actively installed and enabled - sites not running this plugin are not affected. The impact is restricted to file reads (no write or code execution directly from this flaw); exploitation is read-only but can expose credentials enabling further attack steps. |
| Impact | The CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) accurately reflects the real-world risk: this is a trivially exploitable, network-reachable, unauthenticated file-read with high confidentiality impact. The attack requires no privileges, no user interaction, and low complexity - making it highly automatable and suitable for mass scanning. EPSS data was not provided in the input, so exploitation probability cannot be quantified precisely; however, path traversal vulnerabilities of this class on WordPress plugins are routinely scanned and exploited within days of disclosure. KEV status is not confirmed, and no POC code has been identified in the provided data, but the absence of a KEV listing should not reduce urgency given the zero-prerequisite attack profile. The primary limiting factor is that only sites running Bit Integrations ≤2.9.0 are affected; WordPress sites without this plugin are not at risk. The impact is read-only (I:N, A:N), but file disclosure at this level routinely enables full site compromise via credential extraction from wp-config.php. |
| Exploit ScenarioDerived | An unauthenticated attacker identifies a WordPress site running Bit Integrations ≤2.9.0 via plugin fingerprinting or HTTP response headers. The attacker submits a crafted Contact Form 7 form submission or triggers the mail action endpoint, injecting a traversal payload (e.g., ../../../../etc/passwd or ../../../../wp-config.php) into the attachment path parameter processed by processAttachment. The server returns the file contents, exposing database credentials or other secrets that can be used to escalate to full site or server compromise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 01, 2026
Unauthenticated directory traversal in the Bit Integrations WordPress plugin (all versions through 2.9.0) allows remote attackers to read arbitrary files from the server via the processAttachment function. The flaw resides in mail action handling (MailController.php) and Contact Form 7 trigger processing (CF7Controller.php), exposing sensitive server files such as wp-config.php, .env files, and credentials to any unauthenticated network attacker. No public exploit or CISA KEV listing has been identified at the time of analysis, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) and EPSS-independent attack simplicity make this a high-priority patching target for affected installations.
RemediationAI
The primary fix is to update the Bit Integrations plugin to any version released after 2.9.0 - an upstream code fix has been committed per the WordPress SVN changeset at https://plugins.trac.wordpress.org/changeset?reponame=&old=3605525%40bit-integrations&new=3605525%40bit-integrations; however, the exact released fixed version number is not confirmed in the available input data and should be verified in the WordPress plugin repository before updating. As an interim compensating control, administrators who cannot immediately patch should consider disabling the plugin entirely, as no targeted workaround (e.g., disabling only the attachment processing feature) is configurable without code modification. Blocking direct access to the plugin's AJAX endpoints via WAF rules or by restricting access to wp-admin and wp-ajax.php can reduce exposure but may break legitimate plugin functionality. The Wordfence advisory at the URL above should be consulted for any updated remediation guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Bit Integrations plugin (CPE: cpe:2.3:a:bitpressadmin:bit_integrations_-_form_integration,_webhook,_spreadsheets,_crm,_lms_&_email_automation:*:*:*:*:*:*:*:*) is a WordPress automation plugin providing form-to-CRM, webhook, spreadsheet, LMS, and email automation workflows. The root cause is CWE-22 (Path Traversal): the processAttachment function in backend/Actions/Mail/MailController.php (lines 59 and 123) and the Contact Form 7 integration layer (backend/Triggers/CF7/CF7Controller.php line 127, Hooks.php line 11) fail to canonicalize or restrict file paths supplied during attachment processing. An attacker can inject directory traversal sequences (e.g., ../../) into the attachment path parameter to escape the intended directory and reach arbitrary locations on the server filesystem. Because the plugin integrates with CF7 form submissions, the traversal may be triggerable through standard form submission endpoints without any authentication.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-reachable unauthenticated file read with no interaction required; read-only impact justifies I:N and A:N, S:U as no scope change occurs.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Bit integrations - Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.9.0 via the processAttachment function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.
Articles & Coverage 1
Executive ViewAI
The Bit Integrations WordPress plugin (all versions through 2.9.0) exposes sensitive server files-including database credentials and API keys-to any unauthenticated internet user through a directory traversal vulnerability. Organizations running WordPress with this plugin face immediate credential theft and unauthorized database access risk. Inventory and containment actions are required within 24 hours to prevent data exfiltration.
Disable Bit Integrations plugin on all affected WordPress instances immediately; implement WAF rules to block HTTP requests containing 'MailController' or 'CF7Controller' in the URL path; restrict file-level access to wp-config.php and .env files via host permissions (644 mode minimum); enable and actively monitor WordPress access logs for suspicious directory traversal patterns; implement host-based file integrity monitoring on configuration files; restrict WordPress admin endpoints to known IP ranges if operationally feasible.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Exploit-DB