CVE-2026-3645 MEDIUM

CVE-2026-3645: Punnel <= 1.3.1 - Missing Authorization to Authenticated (Subscriber+) Settings Update via 'punnel_save_config' AJAX Action

Vendor Punnel
Product Punnel – Landing Page Builder
Weakness CWE-862 · Missing authorization
Published March 21, 2026
Last update April 8, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Punnel – Landing Page Builder versions 1.3.1 and earlier lack proper authorization checks, allowing unauthenticated attackers to modify data on the site. The vulnerability requires no user interaction and can be exploited over the network. Site administrators should update to a version newer than 1.3.1 to remediate this issue.

What an attacker can do

03Attacker Capabilities

Modify site data without authentication or permission.

Potential impact on your site

04Site Impact

Unauthorized changes to landing pages, forms, or other builder content without admin approval.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

March 21, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE