How severe is GHSA-g8rg-7rpr-cwr2?

GHSA-g8rg-7rpr-cwr2 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-g8rg-7rpr-cwr2?

GHSA-g8rg-7rpr-cwr2 affects the following packages: derhansen/sf_event_mgt (Packagist), derhansen/sf_event_mgt (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-g8rg-7rpr-cwr2?

Update derhansen/sf_event_mgt to 4.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g8rg-7rpr-cwr2 is resolved across your whole dependency graph.

How do I detect GHSA-g8rg-7rpr-cwr2 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for derhansen/sf_event_mgt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-g8rg-7rpr-cwr2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-g8rg-7rpr-cwr2?

O3 pinpoints whether GHSA-g8rg-7rpr-cwr2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-g8rg-7rpr-cwr2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g8rg-7rpr-cwr2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-g8rg-7rpr-cwr2 published, and has it been updated?

GHSA-g8rg-7rpr-cwr2 was published on September 2, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-g8rg-7rpr-cwr2

MEDIUM

GHSA-g8rg-7rpr-cwr2 is a medium-severity (CVSS 4.3) vulnerability in derhansen/sf_event_mgt. O3 Security confirms whether GHSA-g8rg-7rpr-cwr2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Information Disclosure in TYPO3 extension sf_event_mgt

Also known asCVE-2020-25026

Published

Sep 2, 2020

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐘derhansen/sf_event_mgt🐘derhansen/sf_event_mgt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

A missing access check in the backend module allows an authenticated backend user to export participant data for events which the user does not have access to, resulting in Information Disclosure.

Another missing access check in the backend module allows an authenticated backend user to send emails to event participants for events which the user does not have access to, resulting in Broken Access Control.

External reference: https://typo3.org/security/advisory/typo3-ext-sa-2020-017

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`derhansen/sf_event_mgt`	all versions	4.3.1
🐘Packagist	`derhansen/sf_event_mgt`	≥ 5.0.0&&< 5.1.1	5.1.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for derhansen/sf_event_mgt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update derhansen/sf_event_mgt to 4.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g8rg-7rpr-cwr2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-g8rg-7rpr-cwr2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g8rg-7rpr-cwr2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A missing access check in the backend module allows an authenticated backend user to export participant data for events which the user does not have access to, resulting in Information Disclosure. Another missing access check in the backend module allows an authenticated backend user to send emails to event participants for events which the user does not have access to, resulting in Broken Access Control. External reference: [https://typo3.org/security/advisory/typo3-ext-sa-2020-017](https://typo3.org/security/advisory/typo3-ext-sa-2020-017)

O3 Security · Impact-Aware SCA

Is GHSA-g8rg-7rpr-cwr2 in your dependencies?

O3 detects GHSA-g8rg-7rpr-cwr2 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works