# CVE-2026-13169: Eventin < 4.1.21 - Contributor+ Arbitrary Event Modification, Deletion and Ownership Takeover via IDOR

> Contributors can modify, delete, or take ownership of events created by other users, including administrators, due to missing ownership checks.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 19 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-f556-jv65-29j9

## What is CVE-2026-13169?

CVE-2026-13169 is a high-severity missing authorization vulnerability in Unknown Eventin, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Eventin  WordPress plugin before 4.1.21 does not properly verify ownership of events before allowing them to be modified, deleted, or reassigned to a different author, allowing users with contributor-level access and above to alter, delete, or take over events created by other users including administrators.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-13169 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13169 is a high-severity missing authorization vulnerability in Unknown Eventin, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13169 in the wild and no public exploit code.

Affected product: Unknown Eventin. 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-13169/ (Markdown: https://insights.sbomify.com/CVE-2026-13169/index.md)
```

## Sources

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

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