# CVE-2026-60025: Joomla Extension - joomdonation.com - User enumeration in Events Booking < 5.8.0

> Attackers can exploit missing CSRF protection in the file upload endpoint to perform unauthorized actions on behalf of users.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-3g7p-grjw-p9pj

## What is CVE-2026-60025?

CVE-2026-60025 is a high-severity vulnerability in joomdonation.com Events Booking extension for Joomla, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Joomla Extension - joomdonation.com - User enumeration in Events Booking < 5.8.0 - The Joomla extension Events Booking prior version 5.8.0 had an frontend file upload endpoint that lacked CSRF protection.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-60025 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60025 is a high-severity vulnerability in joomdonation.com Events Booking extension for Joomla, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-60025 in the wild and no public exploit code.

Affected product: joomdonation.com Events Booking extension for Joomla. 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-60025/ (Markdown: https://insights.sbomify.com/CVE-2026-60025/index.md)
```

## Sources

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

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