dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-42669

HIGH · 7.5 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 EventPrime allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects EventPrime: from n/a through 4.3.2.0.

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

EventPrime plugin for WordPress has a missing authorization vulnerability where the application fails to properly enforce access control checks for certain operations. This allows authenticated users to exploit incorrectly configured security level permissions, potentially allowing them to perform actions outside their intended privilege level. The vulnerability stems from insufficient validation of user roles/permissions before executing sensitive operations.

MitigationImplement proper role-based access control (RBAC) checks at all sensitive endpoints, ensuring users can only access resources and perform actions permitted by their assigned security level. Validate user permissions server-side before executing any privileged operations.

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
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. Identify EventPrime installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate EventPrime. Note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/event-prime/includes/event-prime.php for the 'Version' field.
    Affected if EventPrime is installed and the version is unknown or unpatched (compare against any available fixed version from the vendor).
  2. Check WordPress user roles with EventPrime capabilities
    Navigate to Users > Roles in WordPress admin, or inspect the wp_options table for 'wp_user_roles' and 'eventprime_roles' entries. Look for custom roles created by EventPrime and their assigned capabilities.
    Affected if Multiple user roles exist with elevated capabilities (such as event creation, attendee management, or settings modification) assigned to roles other than Administrator.
  3. Inspect access control configuration for sensitive operations
    Check EventPrime settings at EventPrime > Settings > General or Access Control. Look for options controlling who can create events, manage bookings, view attendee data, or access reporting.
    Affected if Access control settings allow authenticated users with subscriber, contributor, or custom low-privileged roles to perform sensitive operations like creating events, editing others events, or accessing attendee information.
  4. Verify permission validation in key functionality
    Using browser developer tools or a WordPress user role testing plugin, attempt to access EventPrime admin pages (events, bookings, attendees, reports) while logged in as a non-administrator user with EventPrime-assigned capabilities.
    Affected if Non-administrator users can access admin-level pages or perform actions (create/edit/delete events, view bookings, export attendee data) that should require higher privileges.
  5. Review database access control records
    Query the WordPress database: SELECT * FROM wp_options WHERE option_name LIKE 'eventprime_%' AND option_name LIKE '%access%' or '%capability%' to find stored access control configurations.
    Affected if Database records show capability assignments that grant sensitive operation permissions to roles other than administrator.

Your environment is affected if EventPrime is installed, has multiple user roles configured with EventPrime capabilities, and those capabilities allow lower-privileged authenticated users to access sensitive operations without proper permission validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper role-based access control (RBAC) checks at all sensitive endpoints, ensuring users can only access resources and perform actions permitted by their assigned security level. Validate user permissions server-side before executing any privileged operations.

Have this fixed 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 help mitigating

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-2026-42669 — 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-2026-42669 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