dbcve.org
CartflowsWordPress extension · Brainstormforce

CVE-2023-36685

HIGH · 8.8 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to after 1.11.12 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Brainstorm Force US LLC CartFlows Pro allows Cross Site Request Forgery.This issue affects CartFlows Pro: from n/a through 1.11.12.

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

Cross-Site Request Forgery (CSRF) vulnerability in CartFlows Pro WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings, creating or deleting checkout flows, or other administrative operations. The lack of proper nonce validation on state-changing actions enables attackers to forge requests on behalf of logged-in users.

MitigationImplement anti-CSRF tokens (nonce validation) on all administrative actions and enforce proper Origin/Referer header checks. Update to the latest version when available and audit admin accounts for any unauthorized changes.

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
CartflowsWordPress extension
Affected:<= 1.11.12

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

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

  1. Verify CartFlows plugin is installed
    Locate the CartFlows plugin directory in wp-content/plugins/ and check for the main plugin file (cartflows.php or similar). Use WP CLI: wp plugin list --name=cartflows or inspect the plugin header in the main PHP file to confirm the plugin is active on the WordPress site.
    Affected if CartFlows plugin is not found or not active on the WordPress installation.
  2. Check installed CartFlows version
    Read the version number from the plugin's main PHP file header or from the plugin's readme.txt file in the wp-content/plugins/cartflows/ directory. Compare this version against the affected range: <= 1.11.12.
    Affected if The installed version is 1.11.12 or any earlier version.
  3. Identify admin action endpoints without nonce protection
    Examine the CartFlows plugin PHP files for admin action handlers (functions handling $_POST or $_GET requests). Search for state-changing functions like settings updates, flow creation/deletion, or checkout modifications. Look for missing wp_verify_nonce or check_admin_referer calls before processing these requests.
    Affected if Admin action handlers in the plugin code do not include nonce verification functions before processing requests.
  4. Test CSRF vulnerability on state-changing admin actions
    With administrator authentication, craft a malicious HTML form or script that submits a state-changing request (e.g., modifying plugin settings, creating/deleting a flow) without a valid nonce token. Send the request from an external context and verify the action executes without rejection.
    Affected if The state-changing admin action completes successfully without requiring a valid nonce token tied to the authenticated session.

A WordPress site is affected if CartFlows plugin version 1.11.12 or earlier is installed and admin actions lack proper nonce validation, allowing attackers to forge authenticated administrative requests.

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 a release after 1.11.12
Interim mitigation

Implement anti-CSRF tokens (nonce validation) on all administrative actions and enforce proper Origin/Referer header checks. Update to the latest version when available and audit admin accounts for any unauthorized changes.

Recommended fix Moderate confidence

CartFlows Pro version 1.11.13 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate CartFlows Pro in the plugin list
  4. Check if an update is available and update to the latest version
  5. Alternatively, download the latest version from the WordPress plugin repository or your account at CartFlows and upload/install it
  6. Verify the update was successful and test critical workflows

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

Fix this in Cartflows Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36685 — 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-36685 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