# CVE-2024-1295: The Events Calendar (Free < 6.4.0.1, Pro < 6.4.0.1) - Contributor+ Arbitrary Events Access

> Contributors can access unauthorized event details like drafts and password-protected entries due to missing authorization checks in The Events Calendar plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-66gp-w3xm-x3cc

## What is CVE-2024-1295?

CVE-2024-1295 is a medium-severity missing authorization vulnerability in Unknown The Events Calendar, published on 14 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The events-calendar-pro WordPress plugin before 6.4.0.1, The Events Calendar WordPress plugin before 6.4.0.1 does not prevent users with at least the contributor role from leaking details about events they shouldn't have access to. (e.g. password-protected events, drafts, etc.)

## Which versions are affected by CVE-2024-1295?

It affects 1 product.


Products: Tri the Events Calendar.

## How do I fix CVE-2024-1295?

No fix has been published for CVE-2024-1295 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-1295 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1295 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1295 and fix it if it is affected.

What it is: CVE-2024-1295 is a medium-severity missing authorization vulnerability in Unknown The Events Calendar, published on 14 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1295 exists.

Affected product: Unknown The Events Calendar. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1295/ (Markdown: https://insights.sbomify.com/CVE-2024-1295/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1295
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1295
- OSV: https://osv.dev/vulnerability/CVE-2024-1295

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1295/
Summaries are generated and may contain mistakes; the official description above is the record.