CVE-2026-2452

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-2452", "assignerOrgId": "655498c3-6ec5-4f0b-aea6-853b334d05a6", "state": "PUBLISHED", "assignerShortName": "rami.io", "dateReserved": "2026-02-13T09:57:35.371Z", "datePublished": "2026-02-16T10:16:22.027Z", "dateUpdated": "2026-02-17T17:06:21.998Z"}, "containers": {"cna": {"affected": [{"collectionURL": "https://marketplace.pretix.eu/", "defaultStatus": "unaffected", "packageName": "pretix-newsletter", "product": "pretix-newsletter", "vendor": "pretix", "versions": [{"changes": [{"at": "1.6.3", "status": "unaffected"}], "lessThan": "2.0.0", "status": "affected", "version": "1.0.0", "versionType": "python"}, {"lessThan": "2.0.1", "status": "affected", "version": "2.0.0", "versionType": "python"}]}], "descriptions": [{"lang": "en", "supportingMedia": [{"base64": false, "type": "text/html", "value": "<p>Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when <code>{name}</code>\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:</p><p>It was possible to exfiltrate information about the pretix system through specially crafted placeholder names such as <code>{{event.__init__.__code__.co_filename}}</code>.\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.</p><p>Out of caution, we recommend that you rotate all passwords and API keys contained in your <a target=\"_blank\" rel=\"nofollow\" href=\"https://docs.pretix.eu/self-hosting/config/\">pretix.cfg</a>&nbsp;file.<br></p>"}], "value": "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/ \u00a0file."}], "impacts": [{"capecId": "CAPEC-545", "descriptions": [{"lang": "en", "value": "CAPEC-545 Pull Data from System Resources"}]}, {"capecId": "CAPEC-77", "descriptions": [{"lang": "en", "value": "CAPEC-77 Manipulating User-Controlled Variables"}]}, {"capecId": "CAPEC-54", "descriptions": [{"lang": "en", "value": "CAPEC-54 Query System for Information"}]}], "metrics": [{"cvssV4_0": {"Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "attackComplexity": "HIGH", "attackRequirements": "NONE", "attackVector": "NETWORK", "baseScore": 7.5, "baseSeverity": "HIGH", "exploitMaturity": "PROOF_OF_CONCEPT", "privilegesRequired": "LOW", "providerUrgency": "RED", "subAvailabilityImpact": "HIGH", "subConfidentialityImpact": "HIGH", "subIntegrityImpact": "HIGH", "userInteraction": "NONE", "valueDensity": "NOT_DEFINED", "vectorString": "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", "vulnAvailabilityImpact": "HIGH", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnerabilityResponseEffort": "LOW"}, "format": "CVSS", "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "problemTypes": [{"descriptions": [{"cweId": "CWE-627", "description": "CWE-627 Dynamic Variable Evaluation", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"orgId": "655498c3-6ec5-4f0b-aea6-853b334d05a6", "shortName": "rami.io", "dateUpdated": "2026-02-16T10:16:22.027Z"}, "references": [{"tags": ["vendor-advisory"], "url": "https://pretix.eu/about/en/blog/20260216-release-2026-1-1/"}], "source": {"discovery": "INTERNAL"}, "title": "Unsafe variable evaluation in email templates", "workarounds": [{"lang": "en", "supportingMedia": [{"base64": false, "type": "text/html", "value": "Limit backend access to trusted users, do not use user-controlled variables in the email templates."}], "value": "Limit backend access to trusted users, do not use user-controlled variables in the email templates."}], "x_generator": {"engine": "Vulnogram 0.5.0"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-02-17T16:43:10.295791Z", "id": "CVE-2026-2452", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-02-17T17:06:21.998Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-2452", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-02-17T16:43:10.295791Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-02-17T16:43:10.936Z"}}], "cna": {"title": "Unsafe variable evaluation in email templates", "source": {"discovery": "INTERNAL"}, "impacts": [{"capecId": "CAPEC-545", "descriptions": [{"lang": "en", "value": "CAPEC-545 Pull Data from System Resources"}]}, {"capecId": "CAPEC-77", "descriptions": [{"lang": "en", "value": "CAPEC-77 Manipulating User-Controlled Variables"}]}, {"capecId": "CAPEC-54", "descriptions": [{"lang": "en", "value": "CAPEC-54 Query System for Information"}]}], "metrics": [{"format": "CVSS", "cvssV4_0": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 7.5, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "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", "exploitMaturity": "PROOF_OF_CONCEPT", "providerUrgency": "RED", "userInteraction": "NONE", "attackComplexity": "HIGH", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "subAvailabilityImpact": "HIGH", "vulnAvailabilityImpact": "HIGH", "subConfidentialityImpact": "HIGH", "vulnConfidentialityImpact": "HIGH", "vulnerabilityResponseEffort": "LOW"}, "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "affected": [{"vendor": "pretix", "product": "pretix-newsletter", "versions": [{"status": "affected", "changes": [{"at": "1.6.3", "status": "unaffected"}], "version": "1.0.0", "lessThan": "2.0.0", "versionType": "python"}, {"status": "affected", "version": "2.0.0", "lessThan": "2.0.1", "versionType": "python"}], "packageName": "pretix-newsletter", "collectionURL": "https://marketplace.pretix.eu/", "defaultStatus": "unaffected"}], "references": [{"url": "https://pretix.eu/about/en/blog/20260216-release-2026-1-1/", "tags": ["vendor-advisory"]}], "workarounds": [{"lang": "en", "value": "Limit backend access to trusted users, do not use user-controlled variables in the email templates.", "supportingMedia": [{"type": "text/html", "value": "Limit backend access to trusted users, do not use user-controlled variables in the email templates.", "base64": false}]}], "x_generator": {"engine": "Vulnogram 0.5.0"}, "descriptions": [{"lang": "en", "value": "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/ \u00a0file.", "supportingMedia": [{"type": "text/html", "value": "<p>Emails sent by pretix can utilize placeholders that will be filled with customer data. For example, when <code>{name}</code>\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:</p><p>It was possible to exfiltrate information about the pretix system through specially crafted placeholder names such as <code>{{event.__init__.__code__.co_filename}}</code>.\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.</p><p>Out of caution, we recommend that you rotate all passwords and API keys contained in your <a target=\"_blank\" rel=\"nofollow\" href=\"https://docs.pretix.eu/self-hosting/config/\">pretix.cfg</a>&nbsp;file.<br></p>", "base64": false}]}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-627", "description": "CWE-627 Dynamic Variable Evaluation"}]}], "providerMetadata": {"orgId": "655498c3-6ec5-4f0b-aea6-853b334d05a6", "shortName": "rami.io", "dateUpdated": "2026-02-16T10:16:22.027Z"}}}, "cveMetadata": {"cveId": "CVE-2026-2452", "state": "PUBLISHED", "dateUpdated": "2026-02-17T17:06:21.998Z", "dateReserved": "2026-02-13T09:57:35.371Z", "assignerOrgId": "655498c3-6ec5-4f0b-aea6-853b334d05a6", "datePublished": "2026-02-16T10:16:22.027Z", "assignerShortName": "rami.io"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"collectionURL": "https://marketplace.pretix.eu/", "defaultStatus": "unaffected", "packageName": "pretix-newsletter", "product": "pretix-newsletter", "vendor": "pretix", "versions": [{"changes": [{"at": "1.6.3", "status": "unaffected"}], "lessThan": "2.0.0", "status": "affected", "version": "1.0.0", "versionType": "python"}, {"lessThan": "2.0.1", "status": "affected", "version": "2.0.0", "versionType": "python"}]}], "source": "655498c3-6ec5-4f0b-aea6-853b334d05a6"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:pretix:newsletters:*:*:*:*:*:pretix:*:*", "matchCriteriaId": "D9C0752B-D6CB-429E-BB2A-F0B9381AE7CF", "versionEndExcluding": "1.6.3", "vulnerable": true}, {"criteria": "cpe:2.3:a:pretix:newsletters:2.0.0:*:*:*:*:pretix:*:*", "matchCriteriaId": "B4F6FD9A-DA1C-4943-82E8-F4B657FAEDB6", "vulnerable": true}, {"criteria": "cpe:2.3:a:pretix:pretix:*:*:*:*:*:*:*:*", "matchCriteriaId": "676E56F1-348F-410C-BFDD-9124BD51E34B", "versionEndExcluding": "2026.1.1", "versionStartIncluding": "4.16.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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/ \u00a0file."}, {"lang": "es", "value": "Los correos electr\u00f3nicos enviados por pretix pueden utilizar marcadores de posici\u00f3n que se rellenar\u00e1n con datos del cliente. Por ejemplo, cuando se utiliza {name} en una plantilla de correo electr\u00f3nico, se reemplazar\u00e1 con el nombre del comprador para el correo electr\u00f3nico final. Este mecanismo conten\u00eda un error de seguridad relevante:\n\nEra posible exfiltrar informaci\u00f3n sobre el sistema pretix a trav\u00e9s de nombres de marcadores de posici\u00f3n especialmente dise\u00f1ados, como {{event.__init__.__code__.co_filename}}. De esta manera, un atacante con la capacidad de controlar plantillas de correo electr\u00f3nico (normalmente cualquier usuario del backend de pretix) podr\u00eda recuperar informaci\u00f3n sensible de la configuraci\u00f3n del sistema, incluyendo incluso contrase\u00f1as de base de datos o claves API. pretix s\u00ed incluye mecanismos para evitar el uso de tales marcadores de posici\u00f3n maliciosos, sin embargo, debido a un error en el c\u00f3digo, no fueron completamente efectivos para este plugin.\n\nPor precauci\u00f3n, recomendamos que rote todas las contrase\u00f1as y claves API contenidas en su archivo pretix.cfg https://docs.pretix.eu/self-hosting/config/."}], "id": "CVE-2026-2452", "lastModified": "2026-06-17T10:30:58.833", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 2.8, "impactScore": 3.6, "source": "nvd@nist.gov", "type": "Primary"}], "cvssMetricV40": [{"cvssData": {"Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "attackComplexity": "HIGH", "attackRequirements": "NONE", "attackVector": "NETWORK", "availabilityRequirement": "NOT_DEFINED", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "exploitMaturity": "PROOF_OF_CONCEPT", "integrityRequirement": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "privilegesRequired": "LOW", "providerUrgency": "RED", "subAvailabilityImpact": "HIGH", "subConfidentialityImpact": "HIGH", "subIntegrityImpact": "HIGH", "userInteraction": "NONE", "valueDensity": "NOT_DEFINED", "vectorString": "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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:L/U:Red", "version": "4.0", "vulnAvailabilityImpact": "HIGH", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnerabilityResponseEffort": "LOW"}, "source": "655498c3-6ec5-4f0b-aea6-853b334d05a6", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-2452", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "role": "CISA Coordinator", "timestamp": "2026-02-17T16:43:10.295791Z", "version": "2.0.3"}}]}, "published": "2026-02-16T11:15:56.420", "references": [{"source": "655498c3-6ec5-4f0b-aea6-853b334d05a6", "tags": ["Patch", "Third Party Advisory"], "url": "https://pretix.eu/about/en/blog/20260216-release-2026-1-1/"}], "sourceIdentifier": "655498c3-6ec5-4f0b-aea6-853b334d05a6", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-627"}], "source": "655498c3-6ec5-4f0b-aea6-853b334d05a6", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[1.0.0,1.6.3)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[1.6.3,2.0.0)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[2.0.0,2.0.1)"}}], "product": "pretix-newsletter", "vendor": "pretix"}], "analysis": {"en": {"generated_at": "2026-04-17T19:07:35.061294+00:00", "value": {"mitigation_remediation": ["Upgrade pretix to the latest release (2026.1.1 or newer) where the placeholder validation issue is fixed.", "Restrict backend editor access so that only trusted administrators can create or modify newsletter templates.", "Ensure that templates do not contain user\u2011controlled variables; use safe placeholders only or disable the newsletter plugin if not required.", "Rotate all passwords and API keys listed in the pretix.cfg configuration file to mitigate potential credential compromise."], "summary": {"action": "Apply Patch", "impact": "Information Disclosure"}, "threat_synthesis": {"affected_systems": "pretix\u2019s newsletter component (pretix-newsletter) is affected. All versions of the pretix platform that include the newsletter plugin before the 2026.1.1 release are vulnerable. The vulnerability is present in versions such as 2.0.0 and earlier, and any instance where the newsletter plugin is enabled.", "description_and_impact": "Emails in pretix use placeholders that can be populated with user data. The bug allows attackers who can create or edit email templates to place arbitrary Python attributes, causing the system to expose sensitive configuration details such as database credentials and API keys. This results in full disclosure of critical secrets stored in the pretix.cfg file.", "risk_and_exploitability": "The CVSS score of 7.5 indicates high risk, yet the EPSS score is below 1%, suggesting the chance of exploitation is currently low. The flaw is not listed in the CISA KEV catalog, meaning there is no confirmed public exploitation. Attackers would need access to the backend to alter templates, thus the risk is greatest for instances with lax administrative controls. If the vulnerability is exploited, attackers could read the entire pretix.cfg file, leading to credential compromise and potentially full system takeover."}}}}, "created": "2026-02-17T08:49:53.493823+00:00", "updated": "2026-04-17T19:15:26.250633+00:00", "vendors": ["pretix", "pretix$PRODUCT$pretix-newsletter"]}