Matan Berson

**Name of the Vulnerable Software and Affected Versions** GitHub Enterprise Server versions prior to 3.11.16 GitHub Enterprise Server versions prior to 3.12.10 GitHub Enterprise Server versions prior to 3.13.5 GitHub Enterprise Server versions prior to 3.14.2 GitHub Enterprise Server versions prior to 3.15.0 **Description** A Code Injection vulnerability was identified in GitHub Enterprise Server that allowed attackers to inject malicious code into the query selector via the `identity` property in the message handling function. This enabled the exfiltration of sensitive data by manipulating the DOM, including authentication tokens. To execute the attack, the victim must be logged into GitHub and interact with the attacker-controlled malicious webpage containing the hidden iframe. This vulnerability occurs due to an improper sequence of validation, where the origin check occurs after accepting the user-controlled `identity` property. **Recommendations** For versions prior to 3.11.16, update to version 3.11.16 or later. For versions prior to 3.12.10, update to version 3.12.10 or later. For versions prior to 3.13.5, update to version 3.13.5 or later. For versions prior to 3.14.2, update to version 3.14.2 or later. For versions prior to 3.15.0, update to version 3.15.0 or later. As a temporary workaround, consider restricting access to the message handling function until a patch is available. Avoid using the `identity` property in the query selector until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** The POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress versions up to, and including, 2.8.6 **Description** The issue is related to Reflected Cross-Site Scripting via the `msg` parameter due to insufficient input sanitization and output escaping. This allows unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. **Recommendations** For versions up to, and including, 2.8.6, consider disabling the `msg` parameter until a patch is available to prevent exploitation. Restrict access to areas where the `msg` parameter is used to minimize the risk of arbitrary web script injection. Avoid using the `msg` parameter in affected areas until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.