dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-2448

HIGH · 8.8 CVSS v3.1 Published 2026-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Page Builder by SiteOrigin WordPress plugin contains a Local File Inclusion vulnerability in the locate_template() function, allowing authenticated users with Contributor-level access or higher to include and execute arbitrary files on the server, leading to PHP code execution.

MitigationUpdate the Page Builder by SiteOrigin plugin to a version newer than 2.33.5. Additionally, restrict file upload capabilities and review user role permissions to limit contributor-level access until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Page Builder by SiteOrigin plugin is installed
    Navigate to WordPress Admin > Plugins and locate 'Page Builder by SiteOrigin' in the list of installed plugins, or inspect the plugin directory at /wp-content/plugins/siteorigin-panels/
    Affected if The plugin is present in the installation
  2. Determine installed plugin version
    In WordPress Admin > Plugins, click on the plugin to view its details and note the version number displayed, or read the 'Version:' field from the plugin's main PHP file header at /wp-content/plugins/siteorigin-panels/siteorigin-panels.php
    Affected if The installed version is 2.33.5 or earlier (the vulnerability was fixed in versions newer than 2.33.5)
  3. Confirm plugin is active
    In WordPress Admin > Plugins, verify that Page Builder by SiteOrigin shows as 'Active' rather than 'Inactive' or 'Network Active'
    Affected if The plugin is active and the vulnerable version is installed
  4. Identify users with Contributor-level access or higher
    In WordPress Admin > Users, review the role column for each user account to identify any users assigned the Contributor role, Author role, Editor role, or Administrator role. Alternatively, query the wp_usermeta table for entries where meta_key equals 'wp_capabilities' and meta_value contains 'contributor', 'author', 'editor', or 'administrator'
    Affected if At least one user account with Contributor-level access or higher exists on the site
  5. Check for custom template files that could be included
    Examine the /wp-content/themes/ directory and any custom theme files for includes or require statements that leverage the plugin's locate_template() function. Also review the plugin's template loading behavior in the siteorigin-panels.php file for vulnerable include patterns
    Affected if Custom template files exist and the vulnerable locate_template() function is in use with user-controllable input

You are affected if the Page Builder by SiteOrigin plugin is installed, active, and running version 2.33.5 or earlier while having at least one user with Contributor-level access or higher.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Page Builder by SiteOrigin plugin to a version newer than 2.33.5. Additionally, restrict file upload capabilities and review user role permissions to limit contributor-level access until the patch is applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2448 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2448 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data