Starter TemplatesWordPress extension · Brainstormforce

CVE-2023-41804

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-07
Fix available
A fix is available. Upgrade to 3.2.5 or later.
See remediation →
60/100
Remediation priority · Elevated
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.This issue affects Starter Templates — Elementor, WordPress & Beaver Builder 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 · moderate confidence

A Server-Side Request Forgery (SSRF) vulnerability exists in the Brainstorm Force Starter Templates plugin for WordPress. The vulnerability allows an attacker to induce the application to make HTTP requests to arbitrary domains, potentially enabling internal service enumeration or data exfiltration.

MitigationUpgrade to version 3.2.5 or later. If unable to upgrade immediately, restrict network access to the WordPress instance 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.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Starter TemplatesWordPress extension
Affected:< 3.2.5

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Brainstormforce Starter Templates' or check the file wp-content/plugins/starter-templates/ for existence
    Affected if The plugin folder exists in the WordPress installation
  2. Check the installed version
    In WordPress admin, go to Plugins > Installed Plugins and click on the plugin to view its version, or read the main plugin file header in wp-content/plugins/starter-templates/
    Affected if The version number displayed is less than 3.2.5 or no version is shown and the plugin appears outdated
  3. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify the Starter Templates plugin shows as 'Active'
    Affected if The plugin is active and reachable via web requests
  4. Inspect network logs for suspicious requests
    Review server access logs or web application firewall logs for outgoing HTTP requests from the WordPress server to unusual or internal IP addresses originating from the plugin's endpoints
    Affected if Outbound requests from the server are being made to arbitrary or internal domains that were not initiated by administrators

You are affected if the Brainstormforce Starter Templates plugin version is below 3.2.5 and the plugin is active on your WordPress site.

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
Upgrade available Upgrade to 3.2.5 or later
Fixed in 3.2.5
Interim mitigation

Upgrade to version 3.2.5 or later. If unable to upgrade immediately, restrict network access to the WordPress instance and monitor for suspicious outbound requests.

Recommended fix High confidence

3.2.5

  1. 1. Backup your WordPress site database and files
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Find the Starter Templates plugin (by Brainstorm Force)
  4. 4. Click Update Now to upgrade to version 3.2.5 or later
  5. 5. Verify the update completed successfully

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

Fix this in Starter Templates Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-41804 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