CVE-2026-110506VulnerabilityPublished 28 Oct 2026

The Page Builder by SiteOrigin WordPress plugin before 2.38.0 does not sanitize or escape a widget property before

Source GCVE Database

Authoritative record:CVE-2026-110506· High

Not known to be exploited : upgrade to 2.38.0 soon.

Data as of 28 Oct 2026, 07:14 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in 2.38.0

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-mc48-45x9-jh54

What to do

Upgrade Page Builder by SiteOrigin (WordPress plugin) to 2.38.0.

Affected software

Product	Affected	Fixed in
Page Builder by SiteOrigin	Affected <2.38.0	Fixed in 2.38.0

AI-suggested

Upgrade the Page Builder by SiteOrigin WordPress plugin to version 2.38.0 or later, where this vulnerability is fixed. No other mitigation guidance is provided in the source data.

Description

The Page Builder by SiteOrigin WordPress plugin versions prior to 2.38.0 contain a vulnerability where a widget property is not properly sanitized or escaped before storage and output. This flaw allows users with contributor role or higher to perform stored cross-site scripting (XSS) attacks against users with higher privileges when they open the affected post in the editor.

Impact

Successful exploitation allows lower-privileged users (contributors and above) to execute stored XSS attacks against higher-privileged users who view or edit the affected post. This could lead to session hijacking, privilege escalation, or other malicious actions performed in the context of the higher-privileged user.

Summary

The vulnerability in the Page Builder by SiteOrigin WordPress plugin before version 2.38.0 arises from improper sanitization and escaping of a widget property before it is stored and rendered in the page builder interface. This enables users with contributor-level permissions or above to inject malicious scripts that persist in the post content. When higher-privileged users, such as editors or administrators, open the affected post in the editor, the malicious script executes, resulting in a stored cross-site scripting attack.

References

Community reviews

Loading reviews…