dbcve.org
Futurio ExtraWordPress extension · Futuriowp

CVE-2023-40201

HIGH · 8.8 CVSS v3.1 Published 2023-10-03
Fix available
A fix is available. Upgrade to after 1.8.4 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 FuturioWP Futurio Extra plugin <= 1.8.4 versions leads to activation of arbitrary plugin.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Futurio Extra WordPress plugin versions 1.8.4 and below allows remote attackers to trick authenticated administrators into activating arbitrary plugins via crafted requests, due to missing or improper nonce validation on plugin activation actions.

MitigationUpdate Futurio Extra to the latest version; ensure all plugin activation actions include proper anti-CSRF nonce verification and implement SameSite cookie attributes.

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
Futurio ExtraWordPress extension
Affected:<= 1.8.4

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 Futurio Extra plugin is installed
    Navigate to WordPress Admin > Plugins > Installed Plugins and look for 'Futurio Extra' in the list, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins'
    Affected if Futurio Extra appears in the list of active plugins
  2. Determine installed version of Futurio Extra
    In WordPress Admin > Plugins > Installed Plugins, click on the plugin details link for Futurio Extra to view the version number, or query: SELECT option_value FROM wp_options WHERE option_name = 'futurio_extra_version'
    Affected if Version displayed is 1.8.4 or lower, or version cannot be determined (older install)
  3. Compare version against affected range
    Document the exact version number found and compare against the affected range: versions 1.8.4 and below are vulnerable
    Affected if Installed version is 1.8.4 or any version lower (e.g., 1.8.3, 1.8.2, 1.7.x, etc.)
  4. Inspect plugin activation code for nonce validation
    Access the plugin files via FTP or file manager, locate the plugin activation handler functions (typically in the main plugin file or includes/admin folder), and verify if wp_verify_nonce or check_admin_referer is called before activating plugins
    Affected if The plugin activation action handlers lack nonce validation logic, allowing CSRF exploitation

A user is affected if Futurio Extra version 1.8.4 or lower is installed and the plugin activation functions do not implement anti-CSRF nonce verification.

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.8.4
Interim mitigation

Update Futurio Extra to the latest version; ensure all plugin activation actions include proper anti-CSRF nonce verification and implement SameSite cookie attributes.

Recommended fix Moderate confidence

Futurio Extra version 1.8.5 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate Futurio Extra plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, navigate to Dashboard > Updates to check for and apply any available updates
  6. 6. After updating, verify the plugin is functioning correctly on the site

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

Fix this in Futurio Extra 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-40201 — 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-40201 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