CVE-2026-24380
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 · uneditedMissing 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.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 confidenceMissing Authorization vulnerability in EventPrime plugin allows attackers to access or perform actions they shouldn't be able to due to incorrectly configured access control security levels. The plugin fails to properly verify user permissions before allowing access to certain functionality, potentially allowing lower-privileged users to perform administrative or restricted actions.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify EventPrime plugin installationNavigate to WordPress admin dashboard, go to Plugins section, and locate EventPrime in the list of installed plugins. Note whether it is installed and currently activated.Affected if EventPrime plugin is installed and active on the WordPress site
-
Check installed plugin versionIn the WordPress plugins list, click on the EventPrime plugin to view its details, or check the plugin header in the main plugin file to find the version number.Affected if A version of EventPrime is installed (version information needed to determine specific vulnerability range)
-
Verify user role capability configurationGo to WordPress admin > Users > Roles (or use a role manager plugin) to review what capabilities are assigned to each user role, particularly subscriber, contributor, and editor roles.Affected if Lower-privileged roles (subscriber, contributor) have administrative or restricted capabilities assigned
-
Test access to restricted endpointsUsing a lower-privileged user account (subscriber level), attempt to access EventPrime administrative functions or endpoints directly via URL or API request without proper authentication escalation.Affected if Lower-privileged users can access or execute administrative functions they should not have permission to access
-
Review EventPrime access control settingsIn EventPrime settings (Events > Settings > General or similar), look for access control, permission, or role-based configuration options and verify they properly restrict sensitive operations.Affected if Access control settings are missing, misconfigured, or allow lower roles to perform administrative actions
The environment is affected if the EventPrime plugin is installed and allows users with lower privilege levels to access or perform administrative or restricted actions without proper authorization verification.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks (capability/permission verification) on all sensitive functions and endpoints within the plugin. Verify that all user roles have appropriate access controls enforced.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-24380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24380 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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