LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-3645 affects the Punnel Landing Page Builder WordPress plugin up to version 1.3.1. A low-privileged logged-in user may change the plugin’s configuration, including its API key. That can enable unauthorized changes to site content. This is mainly an integrity risk for WordPress sites using this plugin.

Executive priority

Prioritize this for WordPress environments that allow public account registration or have many low-privileged users. It is not described as remotely exploitable without any account in the narrative, but successful abuse can alter business-facing web content and products.

Technical view

The plugin’s save_config() handler for the punnel_save_config AJAX action lacks capability and nonce checks. Sources state authenticated Subscriber-level users can overwrite configuration. Because the public Punnel API checks only a POST token against the stored api_key, changing that key can enable unauthorized create, update, or delete operations on posts, pages, and products.

Likely exposure

Exposure is limited to WordPress sites with Punnel – Landing Page Builder installed at version 1.3.1 or earlier. Risk increases where untrusted users can obtain Subscriber-level accounts, such as open registration sites. Sites not using this plugin are not affected by the provided sources.

Exploitation context

The source bundle does not cite CISA KEV listing or active exploitation. The described attack requires at least authenticated Subscriber-level access, although the CVSS vector in the bundle lists PR:N. Treat the privilege requirement as a source inconsistency and validate against vendor data.

Researcher notes

Evidence is strongest for missing authorization and nonce verification in the AJAX configuration save path. The bundle’s narrative and CVSS privilege requirement disagree. No patched version is named in the provided sources, so remediation should be tied to vendor confirmation or plugin removal.

Mitigation direction

  • Inventory WordPress sites for Punnel plugin installations.
  • Identify versions up to and including 1.3.1.
  • Check vendor or WordPress plugin guidance for a fixed release.
  • If no fix is available, disable or remove the plugin.
  • Restrict untrusted user registration and review Subscriber-level accounts.
  • Rotate the Punnel API key after remediation.

Validation and detection

  • Confirm whether Punnel – Landing Page Builder is installed and active.
  • Verify the installed version against the vulnerable range.
  • Review plugin configuration for unexpected API key changes.
  • Review content changes for unauthorized post, page, or product modifications.
  • Check WordPress user accounts for unexpected low-privileged users.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3645 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-3645Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
punnelPunnel – Landing Page Builder0unaffected
Weakness

CWE details

CWE-862

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs