CVE-2026-3645 json
Punnel <= 1.3.1 - Missing Authorization to Authenticated (Subscriber+) Settings Update via 'punnel_save_config' AJAX Action
published 7mo ago modified 4mo ago also EUVD-2026-14170
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-3645 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- punnel Punnel – Landing Page Builder
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/b6f54ca4-297f-44e8-8bb3-25cdc52f94ff?source=cve
- plugins.trac.wordpress.org /browser/punnel-landing-page-builder/trunk/punnel.php#L410
- plugins.trac.wordpress.org /browser/punnel-landing-page-builder/tags/1.3.1/punnel.php#L410
- plugins.trac.wordpress.org /browser/punnel-landing-page-builder/trunk/punnel.php#L403
- plugins.trac.wordpress.org /browser/punnel-landing-page-builder/tags/1.3.1/punnel.php#L403
- plugins.trac.wordpress.org /browser/punnel-landing-page-builder/trunk/punnel.php#L179
- plugins.trac.wordpress.org /browser/punnel-landing-page-builder/tags/1.3.1/punnel.php#L179
- plugins.trac.wordpress.org /browser/punnel-landing-page-builder/trunk/punnel.php#L118
- plugins.trac.wordpress.org /browser/punnel-landing-page-builder/tags/1.3.1/punnel.php#L118
- plugins.trac.wordpress.org /browser/punnel-landing-page-builder/trunk/punnel.php#L156
- plugins.trac.wordpress.org /browser/punnel-landing-page-builder/tags/1.3.1/punnel.php#L156
Sources
- CVE List CVE-2026-3645
- NVD CVE-2026-3645
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.