Contact Form 7 AWeber Extension <= 0.1.42 - Missing Authorization to Authenticated (Subscriber+) Log Reset
Strategic Overview
- Status
- Patched in 0.1.43
- Affected Plugin
- Connect Contact Form 7 and AWeber
- Affected Version
<= 0.1.42- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-12167
At a glance
CVE-2025-12167 is a medium-severity Missing Authorization vulnerability in the Connect Contact Form 7 and AWeber WordPress plugin, affecting versions <= 0.1.42. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 0.1.43; sites on affected versions should update now. Disclosed November 2025, reported by Legion Hunter.
Vulnerability Overview
The Contact Form 7 AWeber Extension plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wp_ajax_aweber_logreset' AJAX endpoint in all versions up to, and including, 0.1.42. This makes it possible for authenticated attackers, with Subscriber-level access and above, to reset the AWeber logs.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Connect Contact Form 7 and AWeber <= 0.1.42 carries this weakness at wp_ajax_aweber_logreset, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Connect Contact Form 7 and AWeber the fix is 0.1.43: builds <= 0.1.42 are affected, anything from 0.1.43 onward is not.
Remediation
Update to version 0.1.43, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Connect Contact Form 7 and AWeber 0.1.43 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C