dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-25110

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 Metagauss Event Kikfyre kikfyre-events-calendar-tickets allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Event Kikfyre: from n/a through <= 2.1.8.

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

Missing authorization vulnerability in the Kikfyre Events Calendar Tickets WordPress plugin allows unauthenticated attackers to access functionality that should require proper access control checks. The vulnerability stems from incorrectly configured access control security levels in the plugin, potentially enabling unauthorized users to perform actions or access data they should not have permission to view or modify.

MitigationApply the latest available plugin update which should include proper capability checks and authorization validation for all sensitive functions. If no patch exists, conduct a code audit to identify all endpoints/functions missing authorization and implement WordPress capability checks (e.g., current_user_can()) before executing 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 if Kikfyre Events Calendar plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for a folder containing 'kikfyre' or 'events-calendar' in the name, or query the wp_options table for option_name 'active_plugins' and search for the plugin entry
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin is listed in active_plugins option
  2. Determine the installed plugin version
    Open the main plugin file (usually the primary PHP file in the plugin folder) and look for a version constant or header comment containing 'Version:'
    Affected if The version is known and can be compared to patched versions, or the version cannot be determined indicating an outdated installation
  3. Verify WordPress capability checks are present in plugin AJAX handlers
    Examine PHP files in the plugin folder for AJAX action hooks (add_action calls with 'wp_ajax_' or 'wp_ajax_nopriv_' prefixes) and check if they call current_user_can() or a custom capability check before executing sensitive operations
    Affected if AJAX endpoints exist that handle sensitive data or privileged actions without any capability verification before processing the request
  4. Check if admin functionality is exposed without authentication
    Review plugin PHP files for functions that modify data, access user/ticket information, or perform administrative actions and verify if these functions are reachable via direct file inclusion or admin-ajax without proper auth validation
    Affected if Sensitive functions can be invoked without requiring administrator-level permissions or authentication tokens

A user is affected if the Kikfyre Events Calendar Tickets plugin is installed and its sensitive functions/endpoints lack proper WordPress capability checks (current_user_can), allowing unauthenticated access to privileged operations

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

Apply the latest available plugin update which should include proper capability checks and authorization validation for all sensitive functions. If no patch exists, conduct a code audit to identify all endpoints/functions missing authorization and implement WordPress capability checks (e.g., current_user_can()) before executing privileged operations.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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