dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2023-34370

HIGH · 7.1 CVSS v3.1 Published 2024-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Server-Side Request Forgery (SSRF) vulnerability in Brainstorm Force Starter Templates — Elementor, WordPress & Beaver Builder Templates, Brainstorm Force Premium Starter Templates.This issue affects Starter Templates — Elementor, WordPress & Beaver Builder Templates: from n/a through 3.2.4; Premium Starter Templates: from n/a through 3.2.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Server-Side Request Forgery (SSRF) vulnerability in Brainstorm Force Starter Templates WordPress plugins (versions through 3.2.4) allows remote attackers to make the server perform arbitrary network requests, potentially accessing internal services, bypassing firewalls, or exfiltrating data.

MitigationUpdate to a version newer than 3.2.4 when available. As an interim measure, restrict network access to the affected plugin endpoints and monitor for suspicious outbound requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Starter Templates plugin is installed
    Locate the plugin directory in wp-content/plugins/ and look for a folder named 'starter-templates' or similar Brainstorm Force plugin directories
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Determine installed version
    Open the main plugin file (usually plugin-name.php) and locate the 'Version:' header in the plugin comment block, or check the WordPress plugin admin page for the installed version number
    Affected if The reported version is 3.2.4 or lower, or if no version is displayed (plugin may be outdated)
  3. Confirm plugin is active
    Log into WordPress admin, go to Plugins > Installed Plugins, and verify whether Starter Templates is activated
    Affected if The plugin shows as 'Active' - an inactive plugin cannot be exploited via SSRF requests
  4. Check for suspicious outbound requests
    Review server access logs and network traffic for unusual outbound HTTP/HTTPS requests originating from the web server, particularly to internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x) or unexpected external domains
    Affected if Outbound requests from the server show patterns matching SSRF exploitation (internal IPs, unusual destinations, high frequency)
  5. Inspect plugin endpoint exposure
    Test whether the WordPress AJAX endpoint (wp-admin/admin-ajax.php) responds to plugin-specific actions by checking for action parameters related to template imports or remote fetches
    Affected if Plugin AJAX actions are accessible without authentication or with low-privilege user access

You are affected if Starter Templates plugin is installed, active, and running version 3.2.4 or lower, with exposed AJAX endpoints that accept remote URL parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a version newer than 3.2.4 when available. As an interim measure, restrict network access to the affected plugin endpoints and monitor for suspicious outbound requests.

Recommended fix Moderate confidence

Version 3.2.5 or later (latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Starter Templates — Elementor, WordPress & Beaver Builder Templates' plugin (or Premium Starter Templates)
  4. Check the current version is 3.2.4 or below
  5. Update the plugin to the latest available version (after 3.2.4)
  6. Verify the update completed successfully
  7. Test that the plugin functionality works as expected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34370 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data