{"answers":{"affected":"4 open source packages ship an affected version, including derhansen/sf_event_mgt. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25026 in the wild and no public exploit code.","fix":"Upgrade derhansen/sf_event_mgt to a fixed version for your release line: 4.3.1 or 5.1.1.","what":"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."},"fix_prompt":"Check this codebase for CVE-2020-25026 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2020-25026 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- derhansen/sf_event_mgt (Packagist): affected all versions; fixed in 4.3.1\n- derhansen/sf_event_mgt (Packagist): affected all versions; fixed in 4.3.1\n- derhansen/sf_event_mgt (Packagist): affected from 5.0.0; fixed in 5.1.1\n- derhansen/sf_event_mgt (Packagist): affected from 5.0.0; fixed in 5.1.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-25026/ (Markdown: https://insights.sbomify.com/CVE-2020-25026/index.md)","id":"CVE-2020-25026","markdown":"https://insights.sbomify.com/CVE-2020-25026/index.md","name":"CVE-2020-25026","record":{"aliases":["GHSA-g8rg-7rpr-cwr2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 extension","requires_auth":"low_privilege","summary":"An attacker can access participant and event data via email due to broken access control in the TYPO3 event management extension.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"event_management_and_registration","vendor":"derhansen"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information Disclosure in TYPO3 extension sf_event_mgt","id":"CVE-2020-25026","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":4,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2020-25031"},"packages":[{"ecosystem":"Packagist","fixed":["4.3.1"],"introduced":["0"],"last_affected":[],"package":"derhansen/sf_event_mgt","purl":null,"source":"GHSA-g8rg-7rpr-cwr2"},{"ecosystem":"Packagist","fixed":["4.3.1"],"introduced":["0"],"last_affected":[],"package":"derhansen/sf_event_mgt","purl":"pkg:composer/derhansen/sf_event_mgt","source":"GHSA-g8rg-7rpr-cwr2"},{"ecosystem":"Packagist","fixed":["5.1.1"],"introduced":["5.0.0"],"last_affected":[],"package":"derhansen/sf_event_mgt","purl":null,"source":"GHSA-g8rg-7rpr-cwr2"},{"ecosystem":"Packagist","fixed":["5.1.1"],"introduced":["5.0.0"],"last_affected":[],"package":"derhansen/sf_event_mgt","purl":"pkg:composer/derhansen/sf_event_mgt","source":"GHSA-g8rg-7rpr-cwr2"}],"prev":{"headline":"Incorrect Authorization in TYPO3 extension","id":"CVE-2020-25025"},"products":["n/a"],"published":"2020-09-02","related":[{"cvss_score":4.3,"headline":"Broken Access Control in Backend Module in sf_event_mgt","id":"CVE-2024-24751","kev_date_added":null,"published":"2024-02-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can access participant and event data via email due to broken access control in the TYPO3 event management extension.","url":"https://insights.sbomify.com/CVE-2020-25026/"}