Skip to main content

The Post Grid EUVDEUVD-2026-85800

| CVE-2026-84151 LOW
Cross-site Scripting (XSS) (CWE-79)
2026-09-24 WPScan GHSA-93v8-jc63-2mm4
3.5
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Contributor-level account
  2. Delivery
    Submit post with iframe/style/input markup
  3. Exploit
    Plugin skips kses stripping site-wide
  4. Execution
    Malicious HTML stored in content
  5. Impact
    Visitor 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.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

The Post Grid 0 <7.9.5

Affected Packages

euvd the_post_grid fix: 7.9.5

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

Vendor (WPScan) PRIMARY 3.5 LOW
AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
vuln.today AI 5.4 MEDIUM

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.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

4
CVSS changed
Sep 24, 2026 - 11:22 NVD
3.5 (None) 3.5 (LOW)
Patch available
Sep 24, 2026 - 07:01 EUVD
CVE Published
Sep 24, 2026 - 06:00 cve.org
LOW 3.5
CVE Published
Sep 24, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.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

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Medium
popular WordPress post-grid/layout plugin, common but not universal
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +18
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy