# CVE-2020-25026: Information Disclosure in TYPO3 extension sf_event_mgt

> An attacker can access participant and event data via email due to broken access control in the TYPO3 event management extension.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** Yes
- **Published:** 2 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g8rg-7rpr-cwr2

## What is CVE-2020-25026?

CVE-2020-25026 is a medium-severity missing authorization vulnerability in n/a, published on 2 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The sf_event_mgt (aka Event management and registration) extension before 4.3.1 and 5.x before 5.1.1 for TYPO3 allows Information Disclosure (participant data, and event data via email) because of Broken Access Control.

## Which versions are affected by CVE-2020-25026?

4 open source packages ship an affected version, including derhansen/sf_event_mgt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `derhansen/sf_event_mgt` | Packagist | All versions | 4.3.1 |
| `derhansen/sf_event_mgt` | Packagist | All versions | 4.3.1 |
| `derhansen/sf_event_mgt` | Packagist | From 5.0.0 | 5.1.1 |
| `derhansen/sf_event_mgt` | Packagist | From 5.0.0 | 5.1.1 |

Products: Derhansen Event Management and Registration.

## How do I fix CVE-2020-25026?

Upgrade derhansen/sf_event_mgt to a fixed version for your release line: 4.3.1 or 5.1.1.

## Is CVE-2020-25026 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-24751](https://insights.sbomify.com/CVE-2024-24751/): Broken Access Control in Backend Module in sf_event_mgt (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25026 and fix it if it is affected.

What it is: CVE-2020-25026 is a medium-severity missing authorization vulnerability in n/a, published on 2 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25026 in the wild and no public exploit code.

Affected packages and fixed versions:
- derhansen/sf_event_mgt (Packagist): affected all versions; fixed in 4.3.1
- derhansen/sf_event_mgt (Packagist): affected all versions; fixed in 4.3.1
- derhansen/sf_event_mgt (Packagist): affected from 5.0.0; fixed in 5.1.1
- derhansen/sf_event_mgt (Packagist): affected from 5.0.0; fixed in 5.1.1

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

## Sources

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

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