CVE-2025-12167

4.3 MEDIUM

📋 TL;DR

The Contact Form 7 AWeber Extension plugin for WordPress has an authorization vulnerability that allows authenticated users with Subscriber-level access or higher to reset AWeber logs without proper permission checks. This affects all WordPress sites using this plugin up to version 0.1.42. The vulnerability stems from a missing capability check on the 'wp_ajax_aweber_logreset' AJAX endpoint.

💻 Affected Systems

Products:
  • Contact Form 7 AWeber Extension for WordPress
Versions: All versions up to and including 0.1.42
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress with the vulnerable plugin installed and at least one authenticated user account.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could repeatedly reset AWeber logs to hide evidence of other malicious activities, potentially covering up data exfiltration or other security incidents.

🟠

Likely Case

Malicious users or compromised accounts resetting AWeber logs to disrupt monitoring or hide unauthorized activities.

🟢

If Mitigated

Limited to log tampering without direct data access or system compromise.

🌐 Internet-Facing: MEDIUM - WordPress sites are typically internet-facing, but exploitation requires authenticated access.
🏢 Internal Only: LOW - Internal-only WordPress instances have reduced exposure, but authenticated users could still exploit.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires sending a crafted AJAX request to the vulnerable endpoint. No special tools needed beyond basic web request capabilities.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 0.1.43 or later

Vendor Advisory: https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3390662%40integrate-contact-form-7-and-aweber&new=3390662%40integrate-contact-form-7-and-aweber&sfp_email=&sfph_mail=

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'Contact Form 7 AWeber Extension'. 4. Click 'Update Now' if available. 5. Alternatively, download version 0.1.43+ from WordPress plugin repository and manually update.

🔧 Temporary Workarounds

Disable vulnerable AJAX endpoint

all

Remove or block access to the vulnerable 'wp_ajax_aweber_logreset' endpoint

Add to theme's functions.php or custom plugin: remove_action('wp_ajax_aweber_logreset', 'aweber_logreset_callback');

Temporary plugin deactivation

linux

Disable the plugin until patched

wp plugin deactivate integrate-contact-form-7-and-aweber

🧯 If You Can't Patch

  • Implement strict user role management and review all Subscriber-level accounts
  • Monitor WordPress AJAX logs for suspicious requests to aweber_logreset endpoint

🔍 How to Verify

Check if Vulnerable:

Check plugin version in WordPress admin under Plugins → Installed Plugins. If version is 0.1.42 or lower, you are vulnerable.

Check Version:

wp plugin get integrate-contact-form-7-and-aweber --field=version

Verify Fix Applied:

Verify plugin version is 0.1.43 or higher. Test by attempting AJAX request to /wp-admin/admin-ajax.php?action=aweber_logreset with Subscriber credentials - should return permission error.

📡 Detection & Monitoring

Log Indicators:

  • Multiple POST requests to /wp-admin/admin-ajax.php with action=aweber_logreset
  • Unusual log clearing events in AWeber integration logs

Network Indicators:

  • AJAX requests to aweber_logreset endpoint from non-admin users
  • Unusual spike in admin-ajax.php requests

SIEM Query:

source="wordpress.log" AND (uri_path="/wp-admin/admin-ajax.php" AND query_string="*action=aweber_logreset*")

🔗 References

📤 Share & Export