CVE-2026-3645
Received Received - Intake
Missing Authorization in Punnel WordPress Plugin Allows Config Overwrite

Publication date: 2026-03-21

Last updated on: 2026-03-21

Assigner: Wordfence

Description
The Punnel – Landing Page Builder plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.3.1. The save_config() function, which handles the 'punnel_save_config' AJAX action, lacks any capability check (current_user_can()) and nonce verification. This makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the plugin's entire configuration including the API key via a POST request to admin-ajax.php. Once the API key is known (because the attacker set it), the attacker can use the plugin's public API endpoint (sniff_requests() at /?punnel_api=1) — which only validates requests by comparing a POST token against the stored api_key — to create, update, or delete arbitrary posts, pages, and products on the site.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-21
Last Modified
2026-03-21
Generated
2026-06-16
AI Q&A
2026-03-21
EPSS Evaluated
2026-06-14
NVD
CVE-2026-3645
EUVD
EUVD-2026-14170
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
punnel punnel to 1.3.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The Punnel – Landing Page Builder plugin for WordPress has a vulnerability called Missing Authorization in all versions up to and including 1.3.1. Specifically, the save_config() function, which handles the 'punnel_save_config' AJAX action, does not perform any capability checks or nonce verification. This means that authenticated users with Subscriber-level access or higher can send a POST request to admin-ajax.php to overwrite the plugin's entire configuration, including the API key.

After the attacker sets the API key, they can use the plugin's public API endpoint (sniff_requests() at /?punnel_api=1), which only validates requests by comparing a POST token against the stored API key, to create, update, or delete arbitrary posts, pages, and products on the WordPress site.

Impact Analysis

This vulnerability allows an attacker with minimal privileges (Subscriber-level access) to take control over the plugin's configuration by changing the API key. Once they have control, they can manipulate the site's content by creating, updating, or deleting posts, pages, and products arbitrarily.

Such unauthorized modifications can lead to content defacement, loss of data integrity, disruption of business operations, and potential damage to the website's reputation.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-3645. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart