CVE-2026-12409

Landing Page Builder <= 1.5.3.6 - Cross-Site Request Forgery to ulpb_admin_data AJAX Action

2026-07-15 13:45
M.Fahad Khan

Strategic Overview

Status
Patched in 1.5.3.7
Affected Version
<= 1.5.3.6
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-12409
View all Landing Page Builder – Coming Soon page, Maintenance Mode, Lead Page, WordPress Landing Pages vulnerabilities

At a glance

CVE-2026-12409 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Landing Page Builder WordPress plugin, affecting versions <= 1.5.3.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.5.3.7; sites on affected versions should update now. Disclosed July 2026, reported by M.Fahad Khan.

Vulnerability Overview

The Landing Page Builder – Coming Soon page, Maintenance Mode, Lead Page, WordPress Landing Pages plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.5.3.6. This is due to missing or incorrect nonce validation on the ulpb_admin_ajax function. This makes it possible for unauthenticated attackers to create, update, retitle, or change the post status, slug, and type of arbitrary posts and write ULPB_DATA post meta via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This attack requires the victim to hold an editor-level or administrator session, as the wp_ajax_ulpb_admin_data action enforces a capability check that the forged request must satisfy by inheriting the logged-in user's session cookies.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Landing Page Builder <= 1.5.3.6 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Landing Page Builder the fix is 1.5.3.7: builds <= 1.5.3.6 are affected, anything from 1.5.3.7 onward is not.

Remediation

Update to version 1.5.3.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Landing Page Builder: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Landing Page Builder 1.5.3.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C