dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25312

HIGH · 7.5 CVSS v3.1 Published 2026-03-19
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 Metagauss EventPrime eventprime-event-calendar-management allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects EventPrime: from n/a through <= 4.2.8.3.

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

The EventPrime WordPress plugin has a missing authorization vulnerability that allows attackers to access functionality without proper permission checks. This is due to incorrectly configured access control security levels that fail to validate whether users have appropriate privileges before executing sensitive operations.

MitigationImplement proper authorization checks on all sensitive functions and endpoints, enforce capability checks, and update to the latest patched version when available. Review and harden the access control configuration.

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. Verify EventPrime plugin installation status
    Navigate to WordPress admin > Plugins and confirm whether the EventPrime plugin is installed and active
    Affected if EventPrime plugin is installed and active on the WordPress site
  2. Identify installed EventPrime version
    In WordPress admin > Plugins, locate EventPrime and note the version number displayed
    Affected if The installed version falls within any known vulnerable version range for this CVE
  3. Confirm sensitive functions are accessible without authorization
    Test access to EventPrime administrative functions, event management endpoints, or booking operations using a low-privilege user account (subscriber or contributor role) or unauthenticated request
    Affected if Low-privilege or unauthenticated users can access, modify, or delete event data, bookings, or administrative settings that should require elevated privileges
  4. Review user role and capability assignments
    Check WordPress user roles at Users > Roles or via wp_capabilities usermeta table to see which roles EventPrime defines and whether proper capability checks are enforced
    Affected if EventPrime grants excessive capabilities to low-privilege roles or fails to validate capabilities before executing sensitive operations
  5. Audit access control configuration
    Access control settings are missing, misconfigured, or allow public/unauthenticated access to protected features

A site is affected if EventPrime plugin is active and sensitive operations can be executed by users lacking proper privileges, indicating missing authorization checks.

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

Implement proper authorization checks on all sensitive functions and endpoints, enforce capability checks, and update to the latest patched version when available. Review and harden the access control configuration.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version higher than 4.2.8.3)

  1. 1. Log in to the WordPress admin dashboard where EventPrime plugin is installed
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the EventPrime plugin in the list
  4. 4. Check the current version number displayed under the plugin name
  5. 5. If the installed version is 4.2.8.3 or lower, update the plugin to the latest available version
  6. 6. To update: click 'Update Now' if an update is available, or manually download the latest version from the WordPress plugin repository and upload it
  7. 7. After updating, verify the new version number in the plugins list
  8. 8. Test critical functionality (event creation, booking flows, admin access controls) to ensure the update did not break existing features
Caveat Standard risk: always backup site and test updates on staging environment before applying to production

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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