Stored Iframe Injection & Permanent Open Redirection - Zero Day

Jerry Shah (Jerry)
5 min readMay 18



An iFrame is a way to embed a webpage within another webpage. It’s like a small window that shows content from a different website.

Open redirection vulnerability allows attackers to redirect users from a legitimate website to an attacker’s controlled website.


We have found a very unique vulnerability in Discourse platform using which an attacker can redirect any user from Discourse to any website that attacker wants. We got the CVE for identifying this vulnerability which is CVE-2022-46180. The vulnerability was in discourse-mermaid-theme-component that was allowing to load the iframe in the topic creation and comment section of any created topic and the iframe was stored in the comment section. Initially when we injected the iframe the impact was low because it was only affecting the Integrity from the CIA triangle but then we chained it with the open redirection attack the severity went to medium because now Integrity and Availability both are affected from CIA triangle.

To achieve redirection we created a small script that redirects the user from the original website to another website upon visiting. It mainly happened because of the function we used in the script.

Anatomy of Iframe with Permanent Open Redirection

The Script Used (Hosted on our server):

<script language=’javascript’ type=’text/javascript’>
try {
var rurl = ‘';;
} catch(exception) {
document.write(“This page has moved, <A HREF=’;&amp;jserror=1'>Click here</A> to go there.”);

Breaking the Code:

  1. The <html> and <body> tags define the HTML structure and content of the page.
  2. The <script> tag defines a block of JavaScript code that is executed by the web browser. The language attribute specifies that the code is written in the JavaScript language, and the type attribute specifies that the code is of type text/javascript.
  3. The try block contains a JavaScript function that attempts to execute the following code:

a. The variable rurl is set to the value ‘’.

b. The code replaces the current web page’s location with the URL stored in the rurl variable, effectively redirecting the user to the website at

4. If an exception is caught in the try block (i.e., if the code in the try block fails to execute), the catch block is executed instead. In this case, the document.write() function is used to display a message on the web page that says “This page has moved, Click here to go there.” The A HREF attribute of the hyperlink points to the URL;&amp;jserror=1, which is the destination website that the user is redirected to if the code in the try block fails.

Overall, this code was attempting to redirect the user to the website at If this redirection fails, the user is redirected to another website at;&amp;jserror=1.

How we found this vulnerability ?

  1. We created a post from account A and visited it from account B to make a comment
Comment Section

2. We used a markdown payload with mermaid feature:

```mermaid height=180,auto
Class08 ←> C2: Cool label<iframe/src=’https://ispsolutions.inn/'>

Injecting Payload - Mermaid
Loading the frame content on Discourse

NOTE-1: ispsolutions.inn was our domain on which the redirection script of hosted.

NOTE-2: It is not mandatory to have a mermaid feature enable, you can directly inject the iframe. In my case it was because of mermaid.

3. Then after 2 seconds of loading the iframe, the discourse website got redirected to domain

Permanent Redirection

Why this happened ?

This happened because of the function being used in the script. This function is used in websites to perform a page redirection by replacing the current URL in the browser’s address bar with a new URL.

The primary purpose of is to redirect the user to a different web page. By specifying a new URL as the function’s argument, the browser immediately navigates to that URL, effectively replacing the current page. This is a way to direct users to a different location on the web.

So when I loaded the website in an iframe the function got triggered and it redirected the page from an iframe to the original website.

Attack Flow


If any user injects this payload into any post’s reply or even creating the post, no other user will be able to read that post as he/she will be redirected to the attacker’s controlled website. Apart from it an attacker can use this vulnerability to redirect users to other malicious websites.

Calculated CVSS

Vector String - CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Score - 5.4 Medium


It is recommended to implement the below mentioned fixes

  1. User input should be filtered whenever it is received.
  2. When the data is send back from the server is should be encoded.
  3. Implement CSP with proper response headers like X-Frame-Options.
  4. Restrict harmful tags from being load.

Special thanks to Jinay Patel for helping me in exploiting this vulnerability.



Jerry Shah (Jerry)

|Penetration Tester| |Hack The Box| |Digital Forensics| |Malware Analysis|