CVE-2024-1381

Page Builder Sandwich – Front End WordPress Page Builder Plugin <= 5.1.0 - Sensitive Information Exposure

2024-03-04 00:00
Krzysztof Zając

Strategic Overview

Status
Unpatched
Affected Version
<= 5.1.0
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-1381
View all Page Builder Sandwich – Front End WordPress Page Builder Plugin vulnerabilities

At a glance

CVE-2024-1381 is a medium-severity Missing Authorization vulnerability in the Page Builder Sandwich WordPress plugin, affecting versions <= 5.1.0. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed March 2024, reported by Krzysztof Zając.

Vulnerability Overview

The Page Builder Sandwich – Front End WordPress Page Builder Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.1.0. This makes it possible for authenticated attackers, with subscriber access and higher, to extract sensitive user or configuration data.

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. A successful exploit has high impact on confidentiality.

CWE-862: Missing Authorization

Reaching this weakness in Page Builder Sandwich <= 5.1.0 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for Page Builder Sandwich yet, so installs running <= 5.1.0 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

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