Axel Minck

**Name of the Vulnerable Software and Affected Versions** Opigno TinCan Question Type versions 7.X-1.0 through 7.X-1.2 **Description** The issue is related to improper neutralization of directives in statically saved code, also known as 'Static Code Injection', which allows PHP Local File Inclusion. This can potentially be exploited to access sensitive files on the server. **Recommendations** For Opigno TinCan Question Type versions 7.X-1.0 through 7.X-1.2, update to version 7.X-1.3 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Opigno Learning path versions 0.0.0 through 3.1.2 **Description** The issue is related to improper neutralization of directives in statically saved code, also known as 'static code injection', which allows for PHP Local File Inclusion. This can enable a remote attacker to execute arbitrary code. The vulnerability is associated with errors in input data processing during code syntax analysis. **Recommendations** For Opigno Learning path versions 0.0.0 through 3.1.2, update to a version newer than 3.1.2 to resolve the issue. As a temporary workaround, consider restricting access to sensitive files and directories to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Opigno module versions 0.0.0 through 3.1.2 **Description** The issue is related to improper neutralization of directives in statically saved code, also known as 'Static Code Injection', which can lead to PHP Local File Inclusion. This allows a remote attacker to execute arbitrary code. **Recommendations** For Opigno module versions 0.0.0 through 3.1.2, update to version 3.1.2 or later to resolve the issue. As a temporary workaround, consider restricting access to the Opigno module until a patch is applied.