CVE-2026-104749 — WordPress
HIGHCVE-2026-104749 is a high-severity (CVSS 7.5) Improper Privilege Management vulnerability. No vendor fix is recorded yet; mitigation options are listed below.
The Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation plugin for WordPress is vulnerable to Privilege Escalation via Log Re-execution in all versions…
Description
The Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation plugin for WordPress is vulnerable to Privilege Escalation via Log Re-execution in all versions up to, and including, 2.10.6 The vulnerability exists because IntegrationHandler::executeWithCapture() stores raw, attacker-controlled field values — including user_pass and user_email — verbatim into wp_btcbi_log.field_data on anonymous front-end requests with no capability check, and LogHandler::reexecute() feeds that stored payload back through Flow::execute() inside the replaying administrator's session without validating the identity that originally produced the data, causing RegistrationController::updateUser() to resolve the target user ID to the administrator and write the attacker-supplied password via wp_update_user(). This makes it possible for unauthenticated attackers to overwrite the administrator's password and fully take over the administrator account. Exploitation requires that an administrator has configured a flow mapping a user-supplied form field to the user_pass parameter of the WP User Registration "Update User" action, and that the administrator subsequently clicks "Re-execute" on the failure log row produced by the anonymous submission from the plugin's log screen.
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-104749 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2026-104749 in your dependencies?
Find it across , including transitive dependencies.