# CVE-2026-13390: The Events Calendar < 6.16.5.1 - Unauthenticated Event Aggregator Import Status Manipulation

> Unauthenticated attackers can manipulate Event Aggregator import statuses and store arbitrary content due to missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-h677-jwp7-x89g

## What is CVE-2026-13390?

CVE-2026-13390 is a medium-severity missing authorization vulnerability in Unknown The Events Calendar, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Events Calendar WordPress plugin before 6.16.5.1 does not perform an authorization check on one of its Event Aggregator import REST API routes and skips an integrity check for a particular status value, allowing unauthenticated attackers to mark existing import records as failed and to store arbitrary content in a hidden comment record.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-13390 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13390 is a medium-severity missing authorization vulnerability in Unknown The Events Calendar, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13390 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-2026-13390/ (Markdown: https://insights.sbomify.com/CVE-2026-13390/index.md)
```

## Sources

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

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