Missing AuthorizationWeakness · CWE-862

CVE-2026-10029

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-18

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The Event Koi Lite – Events Calendar, Event Management, RSVP, and Tickets plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.3.13.1 via the get_events. This makes it possible for unauthenticated attackers to extract sensitive data including virtual meeting URLs, physical location data, latitude/longitude coordinates, Google Maps links, and RSVP configuration belonging to draft, pending, and private events that are otherwise inaccessible via public URLs.

Technical summary

dbcve analysis · high confidence

The Event Koi Lite WordPress plugin exposes sensitive event data through its get_events function. Unauthenticated attackers can retrieve draft, pending, and private events containing virtual meeting URLs, physical addresses, GPS coordinates, Google Maps links, and RSVP settings that should not be publicly accessible.

MitigationUpdate the plugin to a patched version once available, or implement access control logic in the get_events function to filter out non-public events and require authentication for sensitive metadata retrieval.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm Event Koi Lite plugin is installed

In WordPress admin, go to Plugins > Installed Plugins and look for 'Event Koi Lite', or check the file system at /wp-content/plugins/event-koi-lite/ for the plugin directory

Affected if The plugin 'Event Koi Lite' is found in the WordPress installation
Identify the installed plugin version

Check the plugin header in /wp-content/plugins/event-koi-lite/event-koi-lite.php for the 'Version' field, or view the plugin details in WordPress admin Plugins page

Affected if The version number cannot be compared to a patched version because no fixed version is specified in available advisories
Locate the get_events function endpoint

Search plugin files for 'get_events' function and identify if it is exposed as a WordPress AJAX hook (wp_ajax_get_events) or REST API endpoint, typically in the main plugin PHP file

Affected if The get_events function exists and is registered as a publicly accessible WordPress action or REST endpoint
Verify unauthenticated access to the endpoint

Send an HTTP request to the identified endpoint (such as /wp-admin/admin-ajax.php?action=get_events or /wp-json/event-koi/v1/events) without authentication headers

Affected if The endpoint returns event data without requiring login credentials (HTTP 200 response with JSON data)
Check for sensitive event visibility

Examine the API response for private, draft, or pending events and verify if fields like meeting URLs, physical addresses, GPS coordinates, or RSVP settings are exposed in the response

Affected if The response includes draft, pending, or private events containing virtual meeting URLs, physical addresses, GPS coordinates, Google Maps links, or RSVP settings that should require authentication

Your environment is affected if the Event Koi Lite plugin is installed and its get_events function is accessible without authentication, exposing private/draft events with sensitive metadata.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the plugin to a patched version once available, or implement access control logic in the get_events function to filter out non-public events and require authentication for sensitive metadata retrieval.

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-10029 — 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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10029 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-10029?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

Need this fixed?

Have this fixed 11 hrs · Moderate

Typical engagement from $1,930

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-10029 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References