# CVE-2026-84743: Missing authorization in The Events Calendar

> Low-privilege users can modify, trash, or take ownership of other users' event records due to missing capability checks in REST routes.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-gjgg-4qh2-m6v7

## What is CVE-2026-84743?

CVE-2026-84743 is a low-severity missing authorization vulnerability in Unknown The Events Calendar, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Events Calendar WordPress plugin before 6.17.5 does not perform a per-object capability check on one family of its REST write routes, allowing users with a low-privilege role such as contributor to modify, unpublish, trash and take ownership of records belonging to other users, including administrators.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-84743?


## How do I fix CVE-2026-84743?

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

## Is CVE-2026-84743 being exploited?

There is no known exploitation of CVE-2026-84743 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84743 and fix it if it is affected.

What it is: CVE-2026-84743 is a low-severity missing authorization vulnerability in Unknown The Events Calendar, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84743 in the wild and no public exploit code.

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-2026-84743/ (Markdown: https://insights.sbomify.com/CVE-2026-84743/index.md)
```

## Sources

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

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