Contributor-level script execution via stored content
Published Jun 22, 2023 · Updated Apr 28, 2026
Stored XSS in WPBakery Page Builder before 6.13.0 allows remote authenticated users to inject script through contributor-created content. The published record does not identify the affected field, shortcode, handler, or missing sanitization or output-encoding operation. Contributor-level access is required, and the stored payload executes when another user views the affected content, exposing that user's browser session to script actions.
Summary
What happened
Stored XSS in WPBakery Page Builder before 6.13.0 allows remote authenticated users to inject script through contributor-created content. The published record does not identify the affected field, shortcode, handler, or missing sanitization or output-encoding operation. Contributor-level access is required, and the stored payload executes when another user views the affected content, exposing that user's browser session to script actions.
The record
- CVE
- CVE-2023-31213
- Published
- Jun 22, 2023
- Updated
- Apr 28, 2026
- Vendor
- WPBakery
- Product
- WPBakery Page Builder
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 22, 2023CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <6.13.0 changes=[{"at":"6.13.0","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo