# CVE-2025-4796: Eventin <= 4.0.34 - Authenticated (Contributor+) Privilege Escalation via User Email Change/Account Takeover

> Authenticated contributors can escalate privileges to administrator by changing arbitrary user emails, leading to account takeover.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 8 Aug 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-gr9c-3qfv-9cxq

## What is CVE-2025-4796?

CVE-2025-4796 is a high-severity vulnerability in arraytics Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered), published on 8 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Eventin plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 4.0.34. This is due to the plugin not properly validating a user's identity or capability prior to updating their details like email in the 'Eventin\Speaker\Api\SpeakerController::update_item' function. This makes it possible for unauthenticated attackers with contributor-level and above permissions to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.

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

## Which versions are affected by CVE-2025-4796?

It affects 1 product.


Products: Themewinter Eventin.

## How do I fix CVE-2025-4796?

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

## Is CVE-2025-4796 being exploited?

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

Public exploit code:

- Eventin <= 4.0.34 - Authenticated (Contributor+) Privilege Escalation via User Email Change/Account Takeover (github_poc): https://github.com/Nxploited/CVE-2025-4796
- eventin <= 4.0.34 - privilege escalation via user email change / account takeover for authenticated contributor+ (github_poc): https://github.com/AnotherSec/CVE-2025-4796

## Other vulnerabilities in arraytics Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered)

- [CVE-2025-47539](https://insights.sbomify.com/CVE-2025-47539/): WordPress Eventin plugin <= 4.0.26 - Privilege Escalation Vulnerability (critical 9.8)
- [CVE-2025-1770](https://insights.sbomify.com/CVE-2025-1770/): Path traversal in Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered) (high 8.8)
- [CVE-2024-7149](https://insights.sbomify.com/CVE-2024-7149/): Path traversal in Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered) (high 8.8)
- [CVE-2025-47445](https://insights.sbomify.com/CVE-2025-47445/): WordPress Eventin plugin <= 4.0.26 - Arbitrary File Download Vulnerability (high 7.5)
- [CVE-2025-3419](https://insights.sbomify.com/CVE-2025-3419/): Event Manager, Events Calendar, Tickets, Registrations – Eventin <= 4.0.26 - Unauthenticated Arbitrary File Read (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4796 and fix it if it is affected.

What it is: CVE-2025-4796 is a high-severity vulnerability in arraytics Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered), published on 8 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4796 in the wild and no public exploit code.

Affected product: arraytics Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered). 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-2025-4796/ (Markdown: https://insights.sbomify.com/CVE-2025-4796/index.md)
```

## Sources

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

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