CVE-2026-2448 HIGH

CVE-2026-2448: Page Builder by SiteOrigin <= 2.33.5 - Authenticated (Contributor+) Local File Inclusion

Vendor Gpriday
Product Page Builder by SiteOrigin
Weakness CWE-22 · Path traversal
Published March 3, 2026
Last update April 8, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity High

CVSS vector

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

What the vulnerability does

01Description

The Page Builder by SiteOrigin plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.33.5 via the locate_template() function. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

Explanation of Vulnerability in Simple Terms

02Summary

Page Builder by SiteOrigin versions up to 2.33.5 contain a path traversal vulnerability that allows authenticated users with low privileges to read, modify, or delete arbitrary files on the server. An attacker can bypass file access restrictions by manipulating file paths, potentially exposing sensitive configuration files, database credentials, or other protected data. Sites should update immediately to a version newer than 2.33.5.

What an attacker can do

03Attacker Capabilities

Read, modify, or delete arbitrary files on the server outside the intended directory.

Potential impact on your site

04Site Impact

Sensitive files like wp-config.php, database backups, or private user data could be exposed or destroyed by a malicious user.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege user account (e.g., subscriber or contributor role) on the site.

Key dates

06Disclosure timeline

March 3, 2026 CVE published
April 8, 2026 Record updated