Page Builder by SiteOrigin <= 2.33.5 - Authenticated (Contributor+) Local File Inclusion
Strategic Overview
- Status
- Patched in 2.34.0
- Affected Plugin
- Page Builder by SiteOrigin
- Affected Version
<= 2.33.5- CVSS
- 8.8High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2026-2448
At a glance
CVE-2026-2448 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Page Builder by SiteOrigin WordPress plugin, affecting versions <= 2.33.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.34.0; sites on affected versions should update now. Disclosed March 2026, reported by suyoung kim(AhnLab).
Vulnerability Overview
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.
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, integrity, availability — full site compromise territory.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Page Builder by SiteOrigin <= 2.33.5 carries this weakness at safe, and reaching it takes an account at Contributor level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Page Builder by SiteOrigin the fix is 2.34.0: builds <= 2.33.5 are affected, anything from 2.34.0 onward is not.
Remediation
Update to version 2.34.0, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Page Builder by SiteOrigin 2.34.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Page Builder by SiteOrigin
- 8.8CVE-2020-13643: Page Builder by SiteOrigin CSRF
CVE-2020-13643 - 8.8CVE-2020-13642: Page Builder by SiteOrigin CSRF
CVE-2020-13642 - 6.4CVE-2026-13295: Page Builder by SiteOrigin <= 2.34.3 Stored XSS
CVE-2026-13295 - 6.4CVE-2025-1459: Page Builder by SiteOrigin <= 2.31.4 Stored XSS
CVE-2025-1459 - 6.4CVE-2024-12240: Page Builder by SiteOrigin <= 2.31.0 Stored XSS
CVE-2024-12240 - 6.4CVE-2024-4361: Page Builder by SiteOrigin <= 2.29.15 Stored XSS
CVE-2024-4361 - 6.4CVE-2024-2202: Page Builder by SiteOrigin <= 2.29.6 Stored XSS
CVE-2024-2202 - 5.3Page Builder by SiteOrigin < 2.0.5 Reflected Cross-Site Scripting
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C