dbcve.org
Wp FlyboxWordPress extension · Wp Flybox Project

CVE-2023-38381

HIGH · 8.8 CVSS v3.1 Published 2023-10-03
Fix available
A fix is available. Upgrade to after 6.46 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 Cyle Conoly WP-FlyBox plugin <= 6.46 versions.

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 WP-FlyBox WordPress plugin versions 6.46 and below allows attackers to induce authenticated users to perform unintended administrative actions by tricking them into visiting malicious links or pages.

MitigationUpdate WP-FlyBox to the latest version which should include proper CSRF token validation, and ensure all plugin actions use WordPress nonces for request validation.

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
Wp FlyboxWordPress extension
Affected:<= 6.46

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. Confirm WP-FlyBox plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'WP-FlyBox' or 'Wp Flybox Project Wp Flybox' in the plugins list and note the version number displayed.
    Affected if Plugin is installed and version is 6.46 or lower (or version field is empty/unavailable indicating an old installation)
  2. Check plugin file header for version
    Access the plugin directory via file manager or FTP (typically wp-content/plugins/wp-flybox/). Open the main plugin PHP file (often wp-flybox.php or similar) and locate the 'Version' field in the plugin header comment at the top of the file.
    Affected if The version declared in the plugin header is 6.46 or below
  3. Identify admin action handlers in plugin code
    Examine the main plugin PHP file for action hooks handling admin requests (search for 'add_action' calls with 'admin_post_', 'wp_ajax_', or plugin-specific custom action names).
    Affected if The plugin registers admin action handlers without WordPress nonce verification (missing wp_verify_nonce, check_admin_referer, or nonce_field in forms)
  4. Inspect plugin settings forms for nonce fields
    In the WordPress admin, access the WP-FlyBox settings page. View the page source (right-click > View Page Source) or examine plugin PHP files to see if forms include a nonce field (input type='hidden' name='_wpnonce' or similar).
    Affected if Plugin settings forms or admin action URLs lack _wpnonce or _wp_http_referer hidden fields
  5. Review AJAX endpoints for CSRF protection
    Search plugin PHP files for 'wp_ajax_' action hooks. Check if each handler function includes a call to check_admin_referer, wp_verify_nonce, or wp_create_nonce before processing the request.
    Affected if AJAX endpoints exist but do not validate nonces before processing administrative actions

You are affected if the WP-FlyBox plugin version is 6.46 or below AND the plugin code lacks WordPress nonce validation in its administrative action handlers or forms.

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 6.46
Interim mitigation

Update WP-FlyBox to the latest version which should include proper CSRF token validation, and ensure all plugin actions use WordPress nonces for request validation.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version > 6.46)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate WP-FlyBox (also labeled as WP-FlyBox by Cyle Conoly)
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, manually download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is functioning correctly and test the affected functionality

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

Fix this in Wp Flybox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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