# CVE-2025-3419: Event Manager, Events Calendar, Tickets, Registrations – Eventin <= 4.0.26 - Unauthenticated Arbitrary File Read

> Unauthenticated attackers can read arbitrary files on the server via the proxy_image function in the Eventin WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 8 May 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2gcx-5j95-fccj

## What is CVE-2025-3419?

CVE-2025-3419 is a high-severity path traversal vulnerability in arraytics Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered), published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Event Manager, Events Calendar, Tickets, Registrations – Eventin plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 4.0.26 via the proxy_image() function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. CVE-2025-47445 is a duplicate of this vulnerability.

Weakness: CWE-73 (External Control of File Name or Path)

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

It affects 1 product.


Products: Themewinter Eventin.

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

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

## Is CVE-2025-3419 being exploited?

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

Public exploit code:

- The Eventin plugin (<= 4.0.26) for WordPress contains an unauthenticated arbitrary file read vulnerability (github_poc): https://github.com/Yucaerin/CVE-2025-3419

## 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-4796](https://insights.sbomify.com/CVE-2025-4796/): Eventin <= 4.0.34 - Authenticated (Contributor+) Privilege Escalation via User Email Change/Account Takeover (high 8.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)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3419 is a high-severity path traversal vulnerability in arraytics Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered), published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3419 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-3419/ (Markdown: https://insights.sbomify.com/CVE-2025-3419/index.md)
```

## Sources

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

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