{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-47409 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-47409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-47409 is a critical missing authorization vulnerability in n/a, published on 14 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-47409 and fix it if it is affected.\n\nWhat it is: CVE-2022-47409 is a critical missing authorization vulnerability in n/a, published on 14 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-47409 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2022-47409/ (Markdown: https://insights.sbomify.com/CVE-2022-47409/index.md)","id":"CVE-2022-47409","markdown":"https://insights.sbomify.com/CVE-2022-47409/index.md","name":"CVE-2022-47409","record":{"aliases":["GHSA-74rq-j853-45qx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"TYPO3 newsletter plugin","requires_auth":"none","summary":"Attackers can unsubscribe all users by manipulating subscription UIDs due to missing authorization checks in the delete action.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fp_newsletter","vendor":"fp_newsletter_project"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:N/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"An issue was discovered in the fp_newsletter (aka Newsletter subscriber management) extension before 1.1.1, 1.2.0, 2.x before 2.1.2, 2.2.1 through 2.4.0, and 3.x before 3.2.6 for TYPO3. Attackers can unsubscribe everyone via a series of modified subscription UIDs in deleteAction operations.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Missing authorization in n/a","id":"CVE-2022-47409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"\"Newsletter subscriber management\" (fp_newsletter) TYPO3 extension leaks subscriber data","id":"CVE-2022-47410"},"packages":[],"prev":{"headline":"Multiple vulnerabilities in extension \"Newsletter subscriber management\" (fp_newsletter)","id":"CVE-2022-47408"},"products":["n/a"],"published":"2022-12-14","related":[{"cvss_score":9.1,"headline":"Multiple vulnerabilities in extension \"Newsletter subscriber management\" (fp_newsletter)","id":"CVE-2022-47408","kev_date_added":null,"published":"2022-12-14"},{"cvss_score":9.1,"headline":"\"Newsletter subscriber management\" (fp_newsletter) TYPO3 extension leaks subscriber data","id":"CVE-2022-47410","kev_date_added":null,"published":"2022-12-14"},{"cvss_score":9.1,"headline":"\"Newsletter subscriber management\" (fp_newsletter) TYPO3 extension leaks subscriber data","id":"CVE-2022-47411","kev_date_added":null,"published":"2022-12-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-21","vendors":["n/a"]},"summary":"Attackers can unsubscribe all users by manipulating subscription UIDs due to missing authorization checks in the delete action.","url":"https://insights.sbomify.com/CVE-2022-47409/"}