● High · CVSS 8.8

How to Fix CVE-2026-2448: Path traversal in Page Builder by SiteOrigin

Q: What is the CVSS score for CVE-2026-2448?

8.8 (High). Vector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`.

Q: Where is the official advisory for CVE-2026-2448?

The vendor advisory is at [https://www.wordfence.com/threat-intel/vulnerabilities/id/deeeb78d-1757-44ec-968b-968d919b84f1?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/deeeb78d-1757-44ec-968b-968d919b84f1?source=cve). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2448.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-2448 is a path traversal in gpriday Page Builder by SiteOrigin. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	8.8 (High)
Actively exploited?	No public listing in CISA KEV
Affected	Page Builder by SiteOrigin 0 to <=2.33.5
Fixed in	See vendor advisory
Type (CWE)	CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

What is CVE-2026-2448?

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. The CVSS base score is 8.8 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://www.wordfence.com/threat-intel/vulnerabilities/id/deeeb78d-1757-44ec-968b-968d919b84f1?source=cve.

Am I affected?

Check the version of Page Builder by SiteOrigin you are running and compare it against the Affected row above (Page Builder by SiteOrigin 0 to <=2.33.5). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s page-builder-by-siteorigin 2>/dev/null | grep -i ^Version
rpm -q page-builder-by-siteorigin 2>/dev/null
command -v page-builder-by-siteorigin >/dev/null && page-builder-by-siteorigin --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*Page Builder by SiteOrigin*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Page Builder by SiteOrigin" 2>$null

How to fix CVE-2026-2448

Upgrade Page Builder by SiteOrigin to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade page-builder-by-siteorigin
dpkg -s page-builder-by-siteorigin | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh page-builder-by-siteorigin -y
# or for older releases:
sudo yum update page-builder-by-siteorigin -y
rpm -q page-builder-by-siteorigin

SUSE / openSUSE


sudo zypper refresh
sudo zypper update page-builder-by-siteorigin
rpm -q page-builder-by-siteorigin

PHP / Composer


composer update gpriday/page-builder-by-siteorigin 2>/dev/null || composer update
composer show | head -20

WordPress


# Update via WP-CLI
wp plugin update --all
wp core update

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-2448 affecting Page Builder by SiteOrigin
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-2448-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*Page Builder by SiteOrigin*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\page-builder-by-siteorigin-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Page Builder by SiteOrigin" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Page Builder by SiteOrigin" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Page Builder by SiteOrigin"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-2448 affecting Page Builder by SiteOrigin
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-2448-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s page-builder-by-siteorigin 2>/dev/null | grep -i ^Version || echo "page-builder-by-siteorigin not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q page-builder-by-siteorigin || echo "page-builder-by-siteorigin not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-2448-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/page-builder-by-siteorigin /etc/page-builder-by-siteorigin.d /etc/page-builder-by-siteorigin.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y page-builder-by-siteorigin
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y page-builder-by-siteorigin
elif command -v yum >/dev/null; then
    yum update -y page-builder-by-siteorigin
elif command -v zypper >/dev/null; then
    zypper --non-interactive update page-builder-by-siteorigin
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s page-builder-by-siteorigin 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q page-builder-by-siteorigin
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-2448" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-2448"

Disable the affected service (Linux)


sudo systemctl stop page-builder-by-siteorigin 2>/dev/null || true
sudo systemctl disable page-builder-by-siteorigin 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s page-builder-by-siteorigin 2>/dev/null | grep -i ^Version
rpm -q page-builder-by-siteorigin 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*Page Builder by SiteOrigin*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-36960: n/a (Bundle Sibling) — n/a (Bundle Sibling)
How to Fix CVE-2026-23646: Critical Vulnerability in openproject — Critical Vulnerability in openproject
How to Fix CVE-2026-4001: Code Injection RCE in Woocommerce Custom Product Addons Pro , Code Injection RCE in Woocommerce Custom Product Addons Pro
How to Fix CVE-2026-8132: SQL Injection in Leave Management System , SQL Injection in Leave Management System
How to Fix CVE-2026-4572: SQL Injection in Sales and Inventory System , SQL Injection in Sales and Inventory System

Is CVE-2026-2448 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-2448?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-2448?

8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Where is the official advisory for CVE-2026-2448?

The vendor advisory is at https://www.wordfence.com/threat-intel/vulnerabilities/id/deeeb78d-1757-44ec-968b-968d919b84f1?source=cve. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2448.

References

Official vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/deeeb78d-1757-44ec-968b-968d919b84f1?source=cve
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2448
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://plugins.trac.wordpress.org/browser/siteorigin-panels/tags/2.33.5/inc/widgets/post-loop.php#L576

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*