dbcve.org
EventprimeWordPress extension · Metagauss

CVE-2024-8369

MEDIUM · 5.3 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 4.0.4.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The EventPrime – Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to unauthorized access to Private or Password-protected events due to missing authorization checks in all versions up to, and including, 4.0.4.3. This makes it possible for unauthenticated attackers to view private or password-protected events.

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 EventPrime WordPress plugin fails to enforce authorization checks when retrieving event data, allowing unauthenticated users to access private or password-protected events by directly querying the events system without proper capability verification.

MitigationUpdate the EventPrime plugin to version 4.0.4.4 or later which includes proper authorization validation before exposing private or password-protected event content.

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:< 4.0.4.4

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify EventPrime plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'EventPrime' or 'Metagauss Eventprime'. Note the installed version number displayed.
    Affected if The plugin is installed with a version lower than 4.0.4.4
  2. Confirm presence of private or password-protected events
    In WordPress admin, go to Events > All Events and review the visibility status of each event. Check for events marked as 'Private' or 'Password Protected' in the visibility column.
    Affected if Any events exist with visibility set to 'Private' or 'Password Protected' in the EventPrime events list
  3. Test unauthorized access to event data
    Using a browser or tool like curl in an incognito window (not logged in to WordPress), directly query the events system endpoint such as /wp-json/ep_events/list or similar EventPrime API endpoint to retrieve event details.
    Affected if Private or password-protected event details are returned in the response without requiring authentication
  4. Inspect event visibility settings in database
    Query the WordPress database: SELECT ID, post_title, post_status, meta_key FROM wp_posts p LEFT JOIN wp_postmeta m ON p.ID = m.post_id WHERE post_type = 'em_event' AND (post_status = 'private' OR meta_key = 'event_private')
    Affected if Events with post_status 'private' or event_private meta value 'true' are present in the database

Your environment is affected if EventPrime version is below 4.0.4.4 AND private or password-protected events exist in the system, allowing unauthenticated access to event details through direct API queries.

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.0.4.4 or later
Fixed in 4.0.4.4
Interim mitigation

Update the EventPrime plugin to version 4.0.4.4 or later which includes proper authorization validation before exposing private or password-protected event content.

Recommended fix High confidence

EventPrime plugin version 4.0.4.4

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins
  3. Find the EventPrime plugin and click Update now
  4. Alternatively, go to Plugins > Add New > Upload and upload version 4.0.4.4 or later from wordpress.org
  5. Verify the plugin version shows 4.0.4.4 or higher after update
  6. Test that private and password-protected events now properly require authorization

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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