CVE-2024-13430

Page Builder: Pagelayer – Drag and Drop website builder <= 1.9.8 - Authenticated (Contributor+) Private Post Disclosure in pagelayer_builder_posts_shortcode

2025-03-11 00:00
Nishiv

Strategic Overview

Status
Patched in 1.9.9
Affected Plugin
Page Builder: Pagelayer – Drag and Drop website builder
Affected Version
<= 1.9.8
CVSS
4.3Medium
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2024-13430
View all Page Builder: Pagelayer – Drag and Drop website builder vulnerabilities

At a glance

CVE-2024-13430 is a medium-severity Improper Access Control vulnerability in the Page Builder: Pagelayer WordPress plugin, affecting versions <= 1.9.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.9.9; sites on affected versions should update now. Disclosed March 2025, reported by Nishiv.

Vulnerability Overview

The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.9.8 via the 'pagelayer_builder_posts_shortcode' function due to insufficient restrictions on which posts can be included. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract data from private posts that they should not have access to.

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 interaction from a victim user.

CWE-284: Improper Access Control

Page Builder: Pagelayer <= 1.9.8 carries this weakness at pagelayer_builder_posts_shortcode, and reaching it takes an account at Contributor level or above. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For Page Builder: Pagelayer the fix is 1.9.9: builds <= 1.9.8 are affected, anything from 1.9.9 onward is not.

Remediation

Update to version 1.9.9, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Page Builder: Pagelayer 1.9.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-13430https://www.wordfence.com/threat-intel/vulnerabilities/id/1de8da4c-dee7-4d59-a475-a969008aa0d4https://nvd.nist.gov/vuln/detail/CVE-2024-13430

Related records

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