Convert ProWordPress extension · Brainstormforce
CVE-2023-36684
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 Convert Pro.This issue affects Convert Pro: from n/a through 1.7.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 confidenceMissing Authorization vulnerability in the Convert Pro WordPress plugin affecting versions up to 1.7.5. The vulnerability allows unauthenticated or unauthorized users to access sensitive functionality or perform actions that should require proper capability checks, likely due to missing capability checks on AJAX actions or admin functions.
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
Convert ProWordPress extension
< 1.7.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Check installed Convert Pro versionGo to WordPress Admin > Plugins > Installed Plugins, locate 'Convert Pro' by Brainstormforce, and note the version number displayedAffected if The version shown is lower than 1.7.6 (for example 1.7.5, 1.7.4, etc.)
-
Verify WordPress plugin is activeConfirm the Convert Pro plugin is activated in the Plugins list (status shows 'Active' beneath the plugin name)Affected if The plugin is active and the version is below 1.7.6
-
Identify AJAX endpoints lacking authorizationReview the Convert Pro plugin files for AJAX action hooks (wp_ajax_* and wp_ajax_nopriv_*) that do not include current_user_can() or similar capability checks before processing requestsAffected if Any AJAX handler found without proper capability verification before executing sensitive operations
Your environment is affected if the Convert Pro plugin is active and its installed version is any release prior to 1.7.6, as these versions contain AJAX or admin actions without authorization checks.
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 · scoped1.7.6
Update Convert Pro to the latest patched version and review all AJAX endpoints and admin actions for proper capability verification and nonce validation.
Convert Pro 1.7.6
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Find the Convert Pro plugin in the list
- Update the plugin to version 1.7.6 or later to resolve the missing authorization vulnerability
- Alternatively, download version 1.7.6 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Convert Pro
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36684 — 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-36684 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