Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor-level account
-
DeliverySubmit post with iframe/style/input markup
-
ExploitPlugin skips kses stripping site-wide
-
ExecutionMalicious HTML stored in content
-
ImpactVisitor or admin renders phishing/spoofed form
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated account with at least the WordPress Contributor role on a site running The Post Grid before 7.9.5; the flaw exists because the plugin expands the WordPress allowed-HTML (kses) list beyond its own shortcodes and applies it site-wide to all post content. Exploitation is limited by: (1) the attacker needing a Contributor-or-higher account (the CVSS vector states PR:H, though the description implies the lower Contributor tier suffices); (2) required user interaction (UI:R) - a visitor or reviewing administrator must load the page for the stored markup to render; and (3) the impact ceiling being HTML injection only - iframe/style/input elements, not script execution - so outcomes are phishing/defacement/form-spoofing rather than code execution. |
| Impact | This is a low-to-moderate severity stored HTML-injection issue, not a critical priority. WPScan/NVD score it CVSS 3.1 3.5 (AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N), and every corroborating signal points to constrained real-world risk: SSVC returns Exploitation=none, Automatable=no, Technical Impact=partial; there is no EPSS score and no CISA KEV listing. Public exploit code exists (WPScan), but that is proof-of-concept availability, not evidence of active exploitation. One notable conflict: the CVSS vector uses PR:H, yet the description states the flaw is reachable by 'Contributor role and above' - Contributor is a low-privilege authenticated role, which normally maps to PR:L, so the vendor's PR:H appears to understate reachability (more roles qualify than PR:H implies). Additionally, because the injected markup renders to unrelated site visitors and to administrators reviewing content, a scope change (S:C) is arguable rather than the S:U the vendor chose. The impact ceiling is genuinely limited: only iframe/style/input elements are permitted (script tags remain stripped), so this enables phishing frames, CSS defacement and spoofed input forms - HTML injection - rather than full JavaScript execution. Net: a real but modest issue best treated as a routine patch, weighted up slightly because it lowers the bar to a widely-held authenticated role. |
| Exploit ScenarioDerived | An attacker who has (or registers/obtains) a Contributor account on a WordPress site running The Post Grid submits a post containing iframe, style, or input markup that the plugin's site-wide expansion of the allowed-HTML list no longer strips. When any visitor - or an administrator reviewing the pending post - loads the content, the injected iframe/form renders, enabling a convincing phishing overlay or credential-harvesting form. Public PoC detail is available via WPScan, and no user interaction beyond simply viewing the page is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 24, 2026
Stored HTML injection in The Post Grid WordPress plugin before version 7.9.5 lets authenticated users with at least the Contributor role persist iframe, style and input elements that WordPress normally strips, because the plugin widens the site-wide allowed-HTML (kses) list instead of limiting the expansion to its own shortcodes. The saved markup renders for every visitor to the affected post and for administrators previewing it, enabling phishing frames, CSS defacement and spoofed input forms, though it stops short of script execution. Publicly available exploit code exists (reported via WPScan), but there is no confirmed active exploitation according to the CISA SSVC record (exploitation: none), and this is a low-to-moderate severity issue rather than a critical priority.
RemediationAI
Vendor-released patch: 7.9.5 - upgrade The Post Grid to version 7.9.5 or later, which scopes the kses allowlist expansion back to the plugin's own markup; this is the only complete fix. References for the fix are the WPScan advisory at https://wpscan.com/vulnerability/6601a305-a76f-40fe-8d78-c6a33a66d5f3/ and the NVD record at https://nvd.nist.gov/vuln/detail/CVE-2026-84151. If an immediate upgrade is not possible, disabling or removing the plugin neutralizes the widened filter, but it also breaks every existing Post Grid shortcode and listing layout until the plugin is reinstalled. A narrower compensating control is to restrict Contributor-or-higher accounts to trusted users and to audit existing posts for unexpected iframe, style or input tags; both steps reduce the attack surface but do not change the plugin's global kses behavior, so they are temporary mitigations only and carry the side effect of disrupting normal editorial workflows. Because exploitation requires an authenticated author to plant the stored markup plus a visitor or administrator to load the page, site owners should also review recent posts for embedded frames or styling they did not author.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Post Grid is a WordPress plugin that renders post listings through its own shortcodes, and this flaw sits in how it interacts with WordPress' kses HTML sanitization layer. Instead of adding its permitted tags only while processing its shortcodes, the vulnerable versions append iframe, style and input elements to the global allowed-HTML array, so the widened whitelist applies to every piece of post content on the site, including content authored by low-privileged users. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically a stored HTML-injection variant of the sanitization weakness: filtering does occur, but the allowlist is both too permissive and mis-scoped. The realistic impact ceiling is markup injection (framing, styling, form spoofing) because script tags and JavaScript event attributes remain outside the expanded list and therefore still get stripped; the NVD vector assigns PR:H while our independent assessment uses PR:L, matching the description that Contributor-level accounts, not only higher roles, are sufficient. The CPE entry cpe:2.3:a:unknown:the_post_grid:*:*:*:*:*:*:*:* records the vendor as unknown, which is a data-quality gap rather than a scope limitation, and CISA's SSVC decision record classifies exploitation as none, automatable as no, and technical impact as partial.
Know when The Post Grid gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
Contributor role is low-privilege so PR:L (not vendor's PR:H); stored content renders to other visitors/admins so S:C; HTML injection without script yields C:L/I:L, A:N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Post Grid WordPress plugin before 7.9.5 does not limit an expansion of the WordPress allowed-HTML list to its own markup and applies it site-wide, allowing users with the Contributor role and above to store iframe, style and input elements that are normally stripped from their content, leading to HTML injection (phishing frames, CSS defacement and spoofed input forms) that renders to any visitor and to administrators reviewing the content.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in The Post Grid
View allThe Post Grid WordPress plugin before 7.5.0 does not sanitise and escape some of its Grid settings, which could allow hi
Cross-Site Request Forgery (CSRF) vulnerability in RadiusTheme The Post Grid plugin <= 7.2.7 versions. Rated high severi
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in RadiusTheme The Po
Stored cross-site scripting in the WordPress plugin The Post Grid (RadiusTheme), affecting all versions through 7.9.5, a
Stored cross-site scripting in The Post Grid WordPress plugin (RadiusTheme) affects versions up to and including 7.9.5,
The The Post Grid - Shortcode, Gutenberg Blocks and Elementor Addon for Post Grid plugin for WordPress is vulnerable to
The The Post Grid - Shortcode, Gutenberg Blocks and Elementor Addon for Post Grid plugin for WordPress is vulnerable to
EUVD-2026-85800
GHSA-93v8-jc63-2mm4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB