Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify public CF7 form bound to Update Profile action
-
DeliverySubmit form with admin email and user_pass key
-
ExploitBypass Ultimate Member banned-key validation in account context
-
ExecutionOverwrite target administrator password
-
PersistAuthenticate as administrator
-
ImpactFull site takeover
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK
2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires that the site has the Advanced Form Integration plugin, Ultimate Member, and Contact Form 7 all active, AND that an administrator has pre-configured a Contact Form 7 integration mapping public form inputs to the Ultimate Member 'Update Profile Field' action with the target email, field key, and value sourced from public form fields - the plugin's own advertised workflow for this action. Given that configuration, exploitation is remote and unauthenticated (PR:N): the attacker simply submits the public form with a victim's email, 'user_pass' as the field key, and a chosen value, and no submitter identity verification, ownership check, capability check, current-password reauthentication, or sensitive-key restriction is enforced (the account context explicitly bypasses Ultimate Member's banned-key validation). The decisive limiting factor is that this specific non-default integration must already exist; sites without such a form mapping are not exploitable, which is why CVSS assigns AC:H. |
| Impact | This is a genuinely high-impact flaw but with a meaningful exploitation gate, so raw CVSS 8.1 overstates the universal risk. The CVSS vector (AV:N/AC:H/PR:N/UI:N/C:H/I:H/A:H) correctly captures that a successful attack is network-based, unauthenticated, and yields full compromise - an unauthenticated attacker can reset any user's password, including Administrator, leading to full site takeover. The AC:H is doing important work: exploitation is only possible if an administrator has pre-configured a Contact Form 7 → Ultimate Member 'Update Profile Field' integration that maps public form inputs to the target email, field key, and value. No KEV listing, no EPSS score, and no public POC were provided, so exploitation status is 'no public exploit identified at time of analysis.' Signals are consistent rather than conflicting: the serious impact (I:H/C:H/A:H) is tempered by the configuration prerequisite reflected in AC:H. The practical priority is HIGH specifically for sites running this plugin alongside Ultimate Member and Contact Form 7 with the described mapping configured; for the broader install base lacking that configuration, real-world exploitability is much lower. EPSS is absent, so probabilistic exploitation likelihood could not be weighed. |
| Exploit ScenarioDerived | On a site where an administrator has published a public Contact Form 7 form wired to the plugin's Ultimate Member 'Update Profile Field' action, an unauthenticated attacker submits the form supplying an administrator's email, the field key 'user_pass', and an attacker-chosen password. The plugin resolves the user by email and writes the new password with no ownership, capability, or reauthentication check, letting the attacker log in as administrator and take over the site. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Unauthenticated password change against arbitrary WordPress accounts - including Administrator accounts - is possible through the Advanced Form Integration - Connect Forms to 300+ Apps plugin for WordPress in all versions up to and including 2.9.0, letting an attacker submit a public Contact Form 7 form carrying a victim's email address, the field key user_pass, and an attacker-chosen password value. The adfoin_ultimatememberac_send_data handler resolves the target user from the attacker-supplied email and forwards the attacker-controlled key/value pair directly to UM()->user()->update_profile() in the 'account' context, which deliberately bypasses Ultimate Member's banned-key validation and performs no sender identity verification, ownership check, capability check, current-password reauthentication, or sensitive-key restriction (CWE-287). The decisive gate is configuration, not attacker skill: an administrator must already have mapped public form inputs to the Ultimate Member 'Update Profile Field' action, which is why the assessed vector carries AC:H despite PR:N; no public exploit code has been identified at time of analysis.
RemediationAI
Vendor-released patch: update the Advanced Form Integration plugin to version 2.10.0 or later, the tag published immediately after the vulnerable 2.9.0 release (Trac changeset new=3725787 vs old=3707004), and confirm the change against the vendor advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/586fd95e-88c7-4eb8-826c-ae46a11ac21f?source=cve. If the update cannot be applied immediately, the highest-value compensating control is to remove or disable the exposure rather than rely on filtering: audit every Advanced Form Integration feed that uses the Ultimate Member 'Update Profile Field' action and delete or disable any that source the target email, field key, or value from public Contact Form 7 fields - this breaks the attack path entirely, at the cost of losing the intended profile-update automation, which must then be handled through authenticated admin-side workflows. Administrators who need to keep the automation should at minimum stop passing user-controlled data as the field key and should never allow keys such as user_pass, user_email, or role/capability meta to be mapped from public input, accepting that this weakens the integration's flexibility. Where the plugin is not actively used, deactivating and removing it removes the vulnerable code path with no functional loss. Additionally, review WordPress user accounts for unexpected password resets or email changes since deployment, enable forced password resets for Administrator accounts as a precaution, and note that no public exploit code has been identified at time of analysis - so the priority here is configuration hygiene plus patching, not emergency containment.
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 flaw sits at the intersection of three WordPress plugins: Advanced Form Integration (the connector, CPE cpe:2.3:a:nasirahmed:advanced_form_integration_-_connect_forms_to_300+_apps), Contact Form 7 (the public input surface), and Ultimate Member (the account-management backend). Advanced Form Integration's design is to take values submitted through a public form and pipe them into an action on a third-party platform - here the Ultimate Member 'Update Profile Field' action, implemented in platforms/ultimatememberac/ultimatememberac.php (notably around lines 83 and 169 of the 2.9.0 tag) and triggered from includes/triggers/cf7/cf7.php (around line 38). The handler resolves the WordPress user from an email value drawn from the form submission rather than from the authenticated session, then calls UM()->user()->update_profile() with the 'account' context. That context is significant because Ultimate Member normally enforces a banned-key list that blocks privileged meta fields such as user_pass; the account context explicitly skips that validation, so a field key of user_pass is accepted and written straight into the user record. The root cause class is CWE-287 (Improper Authentication): the plugin treats possession of a known email address as sufficient proof of identity for a credential-changing operation, so the authentication step is effectively absent. Because the vulnerable code paths are reachable from a publicly submitted form, no session, nonce, or account on the target site is required once the mapping exists - the attacker only needs to know or guess a target email address, which for an Administrator is often discoverable through author archives or public content.
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:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Remote and unauthenticated (AV:N/PR:N), but AC:H because success depends on a pre-existing non-default admin-configured form mapping outside attacker control; full account takeover gives C:H/I:H/A:H.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Advanced Form Integration - Connect Forms to 300+ Apps plugin for WordPress is vulnerable to Authentication Bypass via Unverified Password Change in all versions up to, and including, 2.9.0 The adfoin_ultimatememberac_send_data function, which powers the Ultimate Member "Update Profile Field" action, resolves the target WordPress user from an attacker-supplied email address and passes an attacker-controlled field key and value directly to UM()->user()->update_profile() in the account context - which explicitly bypasses Ultimate Member's banned-key validation - without performing any submitter identity verification, ownership check, capability check, current-password reauthentication, or restriction on sensitive keys such as user_pass. This makes it possible for unauthenticated attackers to change the password of any WordPress user account, including Administrator accounts, by submitting a public Contact Form 7 form with a target email and user_pass as the field key, enabling full site takeover. Exploitation requires an administrator to have pre-configured a Contact Form 7 integration that maps the target email, field key, and value from public form inputs to the Ultimate Member Update Profile Field action - the exact workflow the plugin's own UI advertises for this action type.
Executive ViewAI
The WordPress plugin Advanced Form Integration (versions up to and including 2.9.0) allows any party able to submit a public web form to silently replace the password on existing accounts, including site administrator accounts, on sites where it is deployed alongside Ultimate Member and Contact Form 7. Because administrator access is obtainable through an ordinary website visitor action, every affected public-facing WordPress property should be treated as reachable for full site takeover, with exposure to customer data, brand defacement, malicious content distribution and onward access to any systems the site connects to. Leadership should treat this as a live risk to externally hosted marketing, commerce and content platforms rather than an isolated plugin defect, particularly since no vendor patch is currently available.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate the Advanced Form Integration plugin or remove it from affected sites; if it must stay active, disable the integration mapping that forwards public form input to Ultimate Member's profile/account update action and remove any mapping that accepts a user_pass field or other account-sensitive keys; restrict accepted form field keys to a documented safe allowlist; disable or restrict public Contact Form 7 forms until the mapping is removed; place affected sites behind WAF or reverse-proxy rules that block form submissions containing sensitive field keys; force password resets and rotate credentials for all administrator accounts; enforce multi-factor authentication and least privilege on privileged WordPress accounts; monitor logs for anomalous password changes, new administrator accounts, or form submissions containing user_pass.
Threat Intelligence Overview
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
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 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
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-96037
GHSA-qxmg-x28h-f42m
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB