dbcve.org
EventprimeWordPress extension · Metagauss

CVE-2024-24832

HIGH · 7.5 CVSS v3.1 Published 2024-03-23
Fix available
A fix is available. Upgrade to 3.4.0 or later.
See remediation →
84/100
Remediation priority · High
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.9.

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

Missing Authorization vulnerability in Metagauss EventPrime plugin allows unauthenticated or unauthorized users to access functionality they should not have access to, due to missing capability checks or authentication requirements on certain operations.

MitigationUpdate EventPrime to the latest version which implements proper authorization checks. If no update is available, restrict access to affected endpoints via server-side configuration as a temporary measure.

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.4.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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. Locate EventPrime plugin version
    Check the plugin header file (usually eventprime.php in wp-content/plugins/eventprime-event-booking/) or view the installed plugins list in WordPress admin under Plugins > Installed Plugins. The version is listed in the plugin metadata.
    Affected if The displayed version is lower than 3.4.0 or the version cannot be determined (plugin may be outdated/customized).
  2. Identify publicly accessible EventPrime endpoints
    Review your web server access logs for requests to EventPrime-related URLs. Common patterns include paths containing '/eventprime/', '/events/', '/bookings/', or '/ep-'. Use grep or log analysis tools to enumerate exposed endpoints.
    Affected if EventPrime endpoints are accessible without requiring WordPress login credentials (no authentication token or session required).
  3. Test authorization on sensitive operations
    Attempt to perform privileged actions (such as creating, modifying, or deleting events, venues, or bookings) using a web request from an incognito browser window or via curl without providing valid authentication credentials.
    Affected if The operations complete successfully without returning an authorization error (401/403 HTTP response).
  4. Verify capability checks exist in plugin code
    Examine EventPrime PHP files for current_user_can() or wp_get_current_user() calls before executing sensitive functions. Check common action handlers in includes/ or admin/ directories within the plugin folder.
    Affected if No capability verification is found before sensitive operations, or the plugin version is confirmed below 3.4.0.

You are affected if the installed EventPrime version is below 3.4.0 AND sensitive plugin endpoints or operations can be accessed without authentication or proper 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 3.4.0 or later
Fixed in 3.4.0
Interim mitigation

Update EventPrime to the latest version which implements proper authorization checks. If no update is available, restrict access to affected endpoints via server-side configuration as a temporary measure.

Recommended fix Moderate confidence

EventPrime version 3.4.0

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the EventPrime plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.4.0
  5. 5. Alternatively, navigate to Dashboard > Updates and select EventPrime to update
  6. 6. After updating, verify the version number matches 3.4.0 or higher
  7. 7. Test critical event management functionality to confirm normal operation

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

Fix this in Eventprime Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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