Page Builder by SiteOrigin < 2.38.0 - Contributor+ Stored XSS via panels_info.class
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.38.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The Page Builder by SiteOrigin plugin for WordPress is affected, allowing users with contributor-level access or higher to inject malicious scripts that are stored and then run in the browsers of higher-privileged users, such as editors or administrators, when they open the affected post. This could let an attacker act with those users' permissions, such as taking over their session or changing site content.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The Page Builder by SiteOrigin WordPress plugin before 2.38.0 does not sanitize or escape a widget property before storing it and outputting it in the page builder interface, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks against higher-privileged users who open the affected post in the editor.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Unknown Page Builder by SiteOrigin
fixed in 2.38.0