dbcve.org
Flexible Checkout FieldsWordPress extension · Wpdesk

CVE-2024-31267

HIGH · 8.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 4.1.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Missing Authorization vulnerability in WP Desk Flexible Checkout Fields for WooCommerce.This issue affects Flexible Checkout Fields for WooCommerce: from n/a through 4.1.2.

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

Missing Authorization vulnerability in WP Desk Flexible Checkout Fields for WooCommerce plugin allows attackers to access or modify checkout field settings without proper authentication or capability checks. The plugin fails to validate user permissions before allowing access to sensitive configuration functions.

MitigationUpgrade to version 4.1.3 or later which includes proper authorization checks. Until then, restrict admin access and monitor for unauthorized changes to checkout field configurations.

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
Flexible Checkout FieldsWordPress extension
Affected:< 4.1.3

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

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

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

  1. Check the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Flexible Checkout Fields. Note the version number displayed.
    Affected if The displayed version is earlier than 4.1.3 (e.g., 4.1.2, 4.1.1, 4.0.x, etc.)
  2. Inspect plugin file for version constant
    Access the plugin directory via FTP or file manager. Open the main plugin file (typically flexible-checkout-fields/includes/class-flexible-checkout-fields.php) and locate the version definition.
    Affected if The version defined in the file is below 4.1.3
  3. Verify checkout field settings accessibility
    Attempt to access the plugin settings page (usually at /wp-admin/admin.php?page=flexible-checkout-fields-settings) while logged out or as a non-administrator user.
    Affected if Settings page loads or returns data without requiring authentication or proper capability checks (manage_woocommerce or similar)
  4. Review checkout field configuration for unauthorized changes
    Export or view the current checkout field settings via the plugin interface or database table (wp_options keys containing 'flexible_checkout_fields'). Compare against known baseline configurations.
    Affected if Checkout field settings have been modified or created without documented admin changes, or contain unexpected custom fields
  5. Check WordPress access logs for plugin API endpoints
    Review server access logs for POST/GET requests to /wp-json/flexible-checkout-fields/ or admin-ajax.php?action=flexible_checkout_fields endpoints originating from unexpected IP addresses or without valid session cookies.
    Affected if Requests to plugin endpoints appear in logs without proper WordPress authentication cookies or from unauthorized users

The environment is affected if the plugin version is below 4.1.3 AND the checkout field settings are accessible without proper WordPress capability 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 4.1.3 or later
Fixed in 4.1.3
Interim mitigation

Upgrade to version 4.1.3 or later which includes proper authorization checks. Until then, restrict admin access and monitor for unauthorized changes to checkout field configurations.

Recommended fix Moderate confidence

4.1.3

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate "Flexible Checkout Fields for WooCommerce" in the plugin list
  4. Click "Update now" if an update is available, or manually download version 4.1.3 from the WordPress plugin repository and upload it
  5. Verify the plugin updated successfully by checking the version number
  6. Test WooCommerce checkout functionality to ensure fields and settings work correctly
  7. Clear any caching plugins or server-side caches if applicable

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

Fix this in Flexible Checkout Fields Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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