dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-39518

HIGH · 7.1 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Subscriber Insecure Direct Object References (IDOR) in EventPrime <= 4.3.0.0 versions.

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 versions up to 4.3.0.0 contain an Insecure Direct Object Reference (IDOR) vulnerability allowing subscriber-level users to access or modify data belonging to other users. This horizontal privilege escalation occurs because the plugin fails to properly validate object ownership before granting access to sensitive event data.

MitigationUpgrade EventPrime to a version newer than 4.3.0.0; alternatively, implement proper authorization checks on all data access endpoints to verify the requesting user has rights to the requested object.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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. Confirm EventPrime plugin is installed
    Locate the EventPrime plugin directory in the WordPress wp-content/plugins folder, or list installed plugins via WordPress admin or wp-cli command: wp plugin list --status=active
    Affected if EventPrime plugin is present in the installation
  2. Identify installed EventPrime version
    Check the main plugin file (event-prime.php) for the Version header, or run: wp plugin get event-prime --field=version
    Affected if Version is 4.3.0.0 or lower (any version up to and including 4.3.0.0)
  3. Verify subscriber user role exists
    In WordPress admin, go to Users > Roles, or query the wp_options table for wp_user_roles, or use wp-cli: wp role list
    Affected if Subscriber role is active and present in the site
  4. Confirm subscriber role has event access capabilities
    Inspect the EventPrime plugin capabilities assigned to the subscriber role by examining the role metadata in wp_options table under the wp_capabilities key, or check if subscribers can access event-related admin pages or frontend endpoints
    Affected if Subscriber role has create_events, edit_events, or read_events capabilities enabled
  5. Test for missing object ownership validation
    Using a subscriber-level user account, attempt to access an event ID belonging to a different user via the plugin's API endpoint (typically /wp-json/em/v1/events or similar), or inspect the plugin code for missing ownership checks in event retrieval functions
    Affected if Subscriber can view, modify, or delete events created by other users without authorization failure

The environment is affected if EventPrime plugin version 4.3.0.0 or lower is installed AND subscriber-level users exist with access to event functionality, allowing them to access other users event data without proper ownership 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade EventPrime to a version newer than 4.3.0.0; alternatively, implement proper authorization checks on all data access endpoints to verify the requesting user has rights to the requested object.

Recommended fix Moderate confidence

Latest version of EventPrime (greater than 4.3.0.0)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate EventPrime and check if an update is available
  4. 4. If an update is available, update EventPrime to the latest version available in the WordPress repository
  5. 5. After updating, verify the plugin is functioning correctly
  6. 6. Test that subscriber-level users can no longer access unauthorized data via IDOR

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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