dbcve.org
EventprimeWordPress extension · Metagauss

CVE-2024-43223

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 4.0.4.0 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 EventPrime Events EventPrime allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects EventPrime: from n/a through 4.0.3.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 · moderate confidence

This is a Missing Authorization (Broken Access Control) vulnerability in the EventPrime Events WordPress plugin. The plugin fails to properly enforce authorization checks on certain event management functions, allowing authenticated users (or potentially unauthenticated attackers depending on the specific endpoint) to access or modify events they should not have permissions to access. The vulnerability stems from incorrectly configured access control security levels.

MitigationUpdate to a patched version of EventPrime when available. Until then, implement the principle of least privilege by restricting user roles to only the minimum permissions required for their tasks, and consider using a Web Application Firewall to help block exploitation attempts.

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.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
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. Verify EventPrime plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'EventPrime' or 'Metagauss Eventprime' in the list of active plugins.
    Affected if The EventPrime plugin appears in the installed plugins list.
  2. Check installed EventPrime version
    In WordPress admin, go to Plugins > Installed Plugins, find EventPrime, and note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/eventprime/functions.php or the main plugin file for the 'Version' comment.
    Affected if The installed version number is less than 4.0.4.0.
  3. Review WordPress user roles with event management capabilities
    Use a role editor plugin or WP-CLI command 'wp role list' to enumerate existing roles. Check if any custom roles or low-privilege users (such as Subscribers) have been granted capabilities like 'manage_events', 'edit_events', or 'delete_events'.
    Affected if Users with Subscriber, Contributor, or Author roles possess event management capabilities they should not normally have.
  4. Inspect event management endpoints for access control
    Use a security scanning tool or manually test API endpoints such as /wp-json/eventprime/v1/events or admin-ajax.php?action=ep_ajax with a low-privilege user account to see if unauthorized event creation, modification, or deletion is possible.
    Affected if A user with Subscriber-level access can create, edit, or delete events that they did not create.

You are affected if the EventPrime plugin is installed with a version lower than 4.0.4.0 AND low-privilege users can access or modify events outside their authorized scope.

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.0 or later
Fixed in 4.0.4.0
Interim mitigation

Update to a patched version of EventPrime when available. Until then, implement the principle of least privilege by restricting user roles to only the minimum permissions required for their tasks, and consider using a Web Application Firewall to help block exploitation attempts.

Recommended fix Moderate confidence

EventPrime version 4.0.4.0 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate EventPrime Events plugin.
  4. 4. If an update to version 4.0.4.0 or later is available, click 'Update Now' to install the patched version.
  5. 5. After updating, verify the plugin is running version 4.0.4.0 or higher under Plugins > Installed Plugins.
  6. 6. Test that event management functionality continues to work 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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