CVE-2026-15100: Post Grid Gutenberg Blocks <= 5.0.32 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'searchnoresult' Block Attribute
The Post Grid Gutenberg Blocks – PostX plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'searchnoresult' Block Attribute in all versions up to, and including, 5.0.32 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is particularly concerning in a cross-privilege scenario where a Contributor creates a pending or draft post containing the malicious block attribute, which then executes arbitrary JavaScript in the browser session of an Editor or Administrator who previews that post.
Security readout for executives and security teams
Plain-English summary
A logged-in WordPress contributor can place malicious script content in a PostX block. The script may run when an editor, administrator, or visitor opens the affected page, potentially enabling actions or data access within that user’s browser session.
Executive priority
Prioritize remediation on sites allowing external, shared, or weakly governed contributor accounts. Treat administrator preview workflows as sensitive because stored scripts may execute with a privileged browser session. This is important but not an unauthenticated or confirmed actively exploited emergency.
Technical view
Post Grid Gutenberg Blocks – PostX through version 5.0.32 insufficiently sanitizes and escapes the Advanced Search block’s 'searchnoresult' attribute. This permits contributor-level or higher users to store JavaScript that executes when affected content is viewed or previewed. CVSS 3.1 is 6.4, with cross-scope confidentiality and integrity impact.
Likely exposure
Exposure is limited to WordPress sites running PostX 5.0.32 or earlier where potentially untrusted users have contributor-level or greater access. Risk increases when editors or administrators preview contributor-created drafts or pending posts. The supplied evidence does not identify other affected products.
Exploitation context
Exploitation requires an authenticated contributor-level or higher account but reportedly needs no victim interaction beyond accessing or previewing the injected page. This enables a cross-privilege attack against editors or administrators. The CVE is not in KEV, and the supplied sources provide no evidence of active exploitation.
Researcher notes
The weakness is classified as CWE-79 stored cross-site scripting. The supplied references identify relevant Advanced_Search.php output paths and block handling code, plus a repository changeset. However, the bundle does not explicitly name a fixed version or describe the changeset’s security effect, so remediation claims beyond checking vendor guidance are unsupported.
Mitigation direction
Inventory WordPress sites and identify PostX installations at version 5.0.32 or earlier.
Check vendor guidance for a confirmed fixed release, then update through approved change controls.
Temporarily remove unnecessary contributor access and restrict content creation to trusted accounts.
Apply additional review controls to contributor-created Advanced Search blocks until remediation is confirmed.
Validation and detection
Confirm the installed PostX version on every WordPress instance.
Review contributor, author, editor, and administrator accounts for unexpected or unnecessary access.
Inspect pending, draft, and published content for unusual Advanced Search block attributes.
Review relevant audit records for suspicious contributor edits followed by privileged-user previews.
After remediation, verify vendor guidance confirms the installed version is unaffected.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.