Security readout for executives and security teams
Plain-English summary
CVE-2024-23500 is an SSRF issue in the WordPress Kadence Blocks plugin up to 3.2.19. A logged-in low-privilege attacker may be able to make the site request internal or external resources, risking exposure of sensitive server-side information.
Executive priority
Treat this as a high-priority WordPress plugin exposure if Kadence Blocks is deployed. The business concern is possible sensitive data access through server-side requests, not confirmed mass exploitation.
Technical view
The source bundle identifies CWE-918 SSRF in StellarWP Gutenberg Blocks by Kadence Blocks, package kadence-blocks, affecting versions through 3.2.19. CVSS 3.1 is 7.7: network, low complexity, low privileges, no user interaction, scope changed, high confidentiality impact.
Likely exposure
WordPress sites running kadence-blocks through version 3.2.19 are potentially exposed, especially where lower-privileged authenticated users are present. Sites without this plugin or running unaffected versions are not indicated as exposed by the provided sources.
Exploitation context
The CVSS vector supports remote exploitation by an authenticated low-privilege user without user interaction. The bundle does not state public exploit availability or active exploitation, and KEV is false.
Researcher notes
Sources do not provide the vulnerable endpoint, request structure, fixed version, exploit proof, or IOCs. Validate exposure using plugin identity and version only, then follow vendor or Patchstack guidance.
Mitigation direction
- Inventory WordPress sites for the kadence-blocks plugin and installed version.
- Check StellarWP, Kadence Blocks, or Patchstack guidance for the fixed release.
- Update the plugin if a vendor-confirmed fixed version is available.
- If no fix is confirmed, restrict plugin access or disable it temporarily.
- Limit outbound server requests where operationally feasible.
Validation and detection
- Confirm whether each WordPress site runs kadence-blocks version 3.2.19 or earlier.
- Review plugin access for low-privileged authenticated WordPress roles.
- Check security monitoring for unusual server-side outbound requests.
- Verify remediation by confirming the installed plugin version after update.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-23500 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N3.14PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.7HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/kadence-blocks/vulnerability/wordpress-kadence-blocks-plugin-3-2-19-server-side-request-forgery-ssrf-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
- https://patchstack.com/database/vulnerability/kadence-blocks/wordpress-kadence-blocks-plugin-3-2-19-server-side-request-forgery-ssrf-vulnerability?_s_id=cveCVE reference, CVE · vdb-entry, x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.