dbcve.org
EventprimeWordPress extension · Metagauss

CVE-2024-31275

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 3.3.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Metagauss EventPrime.This issue affects EventPrime: from n/a through 3.3.4.

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

This is a missing authorization vulnerability in the EventPrime WordPress plugin (versions through 3.3.4). The vulnerability allows unauthenticated or unauthorized users to access sensitive functionality or perform actions they should not be permitted to perform. The CVSS 9.8 indicates the flaw is easily exploitable and likely grants attackers significant privileges or access to restricted features.

MitigationApply the vendor patch/upgrade to EventPrime 3.3.5 or later, which should include proper capability checks, nonce validation, and authorization controls on affected endpoints. If a patch is unavailable, disable the plugin until fixed.

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
EventprimeWordPress extension
Affected:< 3.3.5

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

CVSS:3.1/AV:N/AC:L/PR:N/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 if EventPrime plugin is installed
    Inspect the WordPress plugins directory at wp-content/plugins/ for a folder named 'eventprime' or 'Eventprime'. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to see if EventPrime appears in the list.
    Affected if The EventPrime plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress admin plugins list.
  2. Verify EventPrime plugin version
    Open the main plugin file (typically eventprime.php in wp-content/plugins/eventprime/) and locate the version comment in the file header, or check the Version field in the plugin list within WordPress admin. If wp-cli is available, run: wp plugin list --name=eventprime --format=json
    Affected if The version displayed is a version number less than 3.3.5 (e.g., 3.3.4, 3.3.3, etc.).
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if EventPrime shows as 'Active', or use wp-cli: wp plugin is-active eventprime
    Affected if The plugin is installed and shows as Active in WordPress.
  4. Identify vulnerable endpoints (optional manual check)
    Review the site's HTTP traffic or access logs for requests to EventPrime AJAX endpoints (typically under wp-admin/admin-ajax.php?action=ep*) that originate from unauthenticated users or users lacking administrative privileges.
    Affected if Unauthenticated or non-admin users can successfully invoke EventPrime AJAX actions without receiving a 403 or capability error response.

The environment is affected if EventPrime plugin is installed, active, and running version 3.3.4 or any earlier version, as these lack proper authorization controls on certain functionality.

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 3.3.5 or later
Fixed in 3.3.5
Interim mitigation

Apply the vendor patch/upgrade to EventPrime 3.3.5 or later, which should include proper capability checks, nonce validation, and authorization controls on affected endpoints. If a patch is unavailable, disable the plugin until fixed.

Recommended fix High confidence

EventPrime version 3.3.5

  1. 1. Create a full backup of your WordPress site (database and files) before making any changes.
  2. 2. Navigate to WordPress Admin Dashboard > Plugins.
  3. 3. Locate the EventPrime plugin in the plugins list.
  4. 4. If an update is available, click 'Update Now' to update EventPrime to version 3.3.5.
  5. 5. Alternatively, download EventPrime version 3.3.5 from the official WordPress repository or the vendor website, then upload and replace the existing installation.
  6. 6. After updating, verify the installed version is 3.3.5 by checking the Plugins page.
  7. 7. Test critical event management functionality to ensure the plugin continues to operate correctly after the update.

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

Fix this in Eventprime Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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