Yogesh Ojha reNgine

Rengine v1.0.2 was discovered to contain a remote code execution (RCE) vulnerability via the yaml configuration function.

Rengine v1.3.0 was discovered to contain a command injection vulnerability via the scan engine function.

reNgine through 0.5 relies on a predictable directory name.

reNgine before 2.1.2 allows OS Command Injection if an adversary has a valid session ID. The attack places shell metacharacters in an api/tools/waf_detector/?url= string. The commands are executed as root via subprocess.check_output.

reNgine 2.2.0 Authenticated Command Injection via Scan Engine Configuration

Command Injection in reNgine

Business Logic And Unrestricted Project Deletion Lead To Take Over the System in reNgine

Disclosure of Sensitive User Information via API in reNgine

Stored XSS on Admin Panel When Deleting a User in reNgine

ReNgine thru 2.2.0 is vulnerable to a Stored Cross-Site Scripting (XSS) vulnerability in the Vulnerabilities module. When scanning a target with an XSS payload, the unsanitized payload is rendered in the ReNgine web UI, resulting in arbitrary JavaScript execution in the victim's browser. This can be abused to steal session cookies, perform unauthorized actions, or compromise the ReNgine administrator's account.

reNgine vulnerable to Stored Cross-Site Scripting (XSS) via DNS Record Poisoning

HTML Injection in reNgine