Starter TemplatesWordPress extension · Brainstormforce
CVE-2023-41805
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 · uneditedMissing Authorization vulnerability in Brainstorm Force Premium Starter Templates, Brainstorm Force Starter Templates astra-sites.This issue affects Premium Starter Templates: from n/a through 3.2.5; Starter Templates: from n/a through 3.2.5.
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 confidenceA missing authorization vulnerability in the Brainstorm Force Starter Templates WordPress plugins (Premium Starter Templates and astra-sites, through version 3.2.5) allows authenticated users to access functionality or resources that should require higher privilege levels. The exact attack vector and impacted endpoints are not detailed in the available information, but the CVSS 6.5 indicates this is an authenticated access control bypass.
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
< 3.2.6CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin is installedCheck WordPress plugin directory for 'starter-templates', 'premium-starter-templates', or 'astra-sites' folders in wp-content/plugins/Affected if Any of these Brainstorm Force starter template plugins are present
-
Check installed versionLook up the plugin version in WordPress admin under Plugins > Installed Plugins, or read the main plugin PHP file header for 'Version:' fieldAffected if Version is lower than 3.2.6
-
Audit user rolesReview WordPress users list and check for untrusted or unknown accounts with Contributor, Author, Editor, or Administrator rolesAffected if There are untrusted users with contributor-level or higher access
System is affected if Brainstorm Force Starter Templates plugin version is below 3.2.6 and the site has untrusted authenticated users with contributor-level or higher permissions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.2.6
Upgrade to version 3.2.6 or later which contains the authorization fix. If immediate patching is not possible, restrict user registration and ensure only trusted users have contributor-level or higher permissions on the WordPress site.
Starter Templates 3.2.6 or later
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in WordPress admin
- Find the 'Starter Templates' plugin (by Brainstorm Force)
- Update the plugin to version 3.2.6 or later
- Verify the update was successful by checking the plugin version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Starter Templates
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41805 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-41805 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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