dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2024-6000

HIGH · 7.1 CVSS v3.1 Published 2024-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable

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
The FooEvents for WooCommerce plugin for WordPress is vulnerable to unauthorized arbitrary file uploads due to an improper capability setting on the 'display_ticket_themes_page' function in versions up to, and including, 1.19.20. This makes it possible for authenticated attackers with contributor-level capabilities or above, to upload arbitrary files on the affected site's server which may make remote code execution possible. This was partially patched in 1.19.20, and fully patched in 1.19.21.

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

The FooEvents for WooCommerce plugin for WordPress has an arbitrary file upload vulnerability caused by improper capability checks on the 'display_ticket_themes_page' function. Authenticated attackers with contributor-level or higher privileges can upload arbitrary files to the server, potentially achieving remote code execution. The issue affects versions up to 1.19.20, with partial mitigation in 1.19.20 and full patching in 1.19.21.

MitigationUpdate the FooEvents for WooCommerce plugin to version 1.19.21 or later to remediate this vulnerability. If immediate updating is not possible, consider restricting contributor-level access or disabling the ticket themes functionality until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:H/PR:L/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. Check installed FooEvents for WooCommerce plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'FooEvents for WooCommerce' - the version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file (e.g., /wp-content/plugins/fooevents-woocommerce/fooevents.php) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 1.19.20 or earlier.
  2. Verify contributor-level or higher user roles exist
    In WordPress admin, go to Users > All Users and review the role column. Contributor role and above (Contributor, Author, Editor, Administrator) can access the vulnerable function.
    Affected if Any user account has Contributor, Author, Editor, or Administrator role.
  3. Confirm ticket themes functionality is accessible
    The vulnerability is in the 'display_ticket_themes_page' function. Log in as a Contributor-level user and attempt to access the ticket themes settings page (typically under FooEvents > Ticket Themes in the admin menu).
    Affected if The ticket themes page loads without permission errors for contributor-level accounts.

A user is affected if the FooEvents for WooCommerce plugin version is 1.19.20 or earlier AND any user with Contributor-level access or higher exists on the site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the FooEvents for WooCommerce plugin to version 1.19.21 or later to remediate this vulnerability. If immediate updating is not possible, consider restricting contributor-level access or disabling the ticket themes functionality until the patch can be applied.

Recommended fix High confidence

1.19.21 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'FooEvents for WooCommerce' plugin in the list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.19.21 or later.
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or from the vendor.
  6. 6. Deactivate and delete the existing plugin, then upload and install the new version.
  7. 7. After installation, activate the plugin.
  8. 8. Verify the update was successful by checking the plugin version in the plugins list.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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