{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-2452 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2452 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2452 is a high-severity vulnerability in pretix-newsletter, published on 16 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-2452 and fix it if it is affected.\n\nWhat it is: CVE-2026-2452 is a high-severity vulnerability in pretix-newsletter, published on 16 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-2452 in the wild and no public exploit code.\n\nAffected product: pretix-newsletter. 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-2026-2452/ (Markdown: https://insights.sbomify.com/CVE-2026-2452/index.md)","id":"CVE-2026-2452","markdown":"https://insights.sbomify.com/CVE-2026-2452/index.md","name":"CVE-2026-2452","record":{"aliases":["GHSA-mv9g-vp7w-xq67"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"pretix newsletter plugin","requires_auth":"low_privilege","summary":"Attackers with backend access can exfiltrate sensitive system configuration data, including passwords and API keys, via crafted email template placeholders.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rami.io","cpe":[{"product":"newsletters","vendor":"pretix"},{"product":"pretix","vendor":"pretix"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/RE:L/U:Red","version":"4.0"},"cwes":[{"id":"CWE-627","name":"Dynamic Variable Evaluation"}],"description":"Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when {name}\n is used in an email template, it will  be replaced with the buyer's \nname for the final email. This mechanism contained a security-relevant bug:\n\nIt was possible to exfiltrate information about the pretix system through specially crafted placeholder names such as {{event.__init__.__code__.co_filename}}.\n This way, an attacker with the ability to control email templates \n(usually every user of the pretix backend) could retrieve sensitive \ninformation from the system configuration, including even database \npasswords or API keys. pretix does include mechanisms to prevent the usage of such \nmalicious placeholders, however due to a mistake in the code, they were \nnot fully effective for this plugin.\n\nOut of caution, we recommend that you rotate all passwords and API keys contained in your  pretix.cfg https://docs.pretix.eu/self-hosting/config/  file.","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":"Unsafe variable evaluation in email templates","id":"CVE-2026-2452","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"DoS in Calls plugin via malformed msgpack in websocket request.","id":"CVE-2026-2454"},"packages":[],"prev":{"headline":"Unsafe variable evaluation in email templates","id":"CVE-2026-2451"},"products":["pretix-newsletter"],"published":"2026-02-16","related":[],"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":"2026-02-17","vendors":["pretix"]},"summary":"Attackers with backend access can exfiltrate sensitive system configuration data, including passwords and API keys, via crafted email template placeholders.","url":"https://insights.sbomify.com/CVE-2026-2452/"}