Skip to content

← Public intelligence

Packagist package

derhansen/sf_event_mgt

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.3PackagistPublished

    derhansen/sf_event_mgt vulnerable to Broken Access Control in Backend Module

    CVE-2024-24751 · GHSA-4576-pgh2-g34j

    Affected
    • Packagist derhansen/sf_event_mgt >= 7.0.0, < 7.4.0
    Fixed in
    7.4.0· Vendor fix available
    Issue
    The existing access control check for events in the backend module got broken during the update of the extension to TYPO3 12.4, because the RedirectResponse from the $this-redirect() function was never handled.

    Recommended action: Upgrade to 7.4.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 4.3PackagistPublished

    Information Disclosure in TYPO3 extension sf_event_mgt

    CVE-2020-25026 · GHSA-g8rg-7rpr-cwr2

    Affected
    • Packagist derhansen/sf_event_mgt < 4.3.1; >= 5.0.0, < 5.1.1
    Fixed in
    4.3.15.1.1· Vendor fix available
    Issue
    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

    Recommended action: Upgrade to 5.1.1 or 4.3.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →