# CVE-2026-13168: Eventin < 4.1.20 - Contributor+ Customer PII Disclosure via REST API

> Contributor-level users can access other customers' personal data via the REST API in the Eventin WordPress 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:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-prg9-j2xv-c876

## What is CVE-2026-13168?

CVE-2026-13168 is a medium-severity vulnerability in Unknown Eventin, published on 12 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.20 does not properly restrict access to stored customer records, allowing users with contributor-level access and above to read other customers' personal data such as names and email addresses.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-13168 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13168 is a medium-severity vulnerability in Unknown Eventin, published on 12 Aug 2026. 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-2026-13168 exists.

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

## Sources

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

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