On the way to 2nd Bounty XSS and Apache server .

Aneesha D
3 min readMar 1, 2022

Hello readers, in this post, we’ll look at XSS and Apache Server furthere on apache server I will post another article.

Cross Site Scripting (XSS)


Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted websites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser side script, to a different end user. Flaws that allow these attacks to succeed are quite widespread and occur anywhere a web application uses input from a user within the output it generates without validating or encoding it.

An attacker can use XSS to send a malicious script to an unsuspecting user. The end user’s browser has no way to know that the script should not be trusted, and will execute the script. Because it thinks the script came from a trusted source, the malicious script can access any cookies, session tokens, or other sensitive information retained by the browser and used with that site. These scripts can even rewrite the content of the HTML page. For more details on the different types of XSS flaws.

Let’s say the website’s address is https://example.net, and their production environment is https://example.com.




I visited to https://example.net and couldn’t find a way to log in or get to the dashboard, but there was a signup form for bughunter(title)/any user.

While I was signing up in the form I got a request going to the api.example.com and sent it to repeaterto check the Respose It was Apache server and I thought of finding the CVE for the same, and further about this I will post next time.

After exploring these, I found https://example.com and logged in with the identical credentials I had in the.net domain.

I saw it was an admin portal with a dashboard, customer email sending choices, and other features. I went through all of the tabs and pasted the XSS payload from github into all of the input fields, hoping to get something. So yet, I haven’t received anything.
Then there was a custom templete for email,


which I followed as well, but I didn’t get anything at first. Then t he XSS appeared when I clicked the title of the custom email template.

I submitted the report even though it was out of scope domain, and when the email was sent, I felt it may be self XSS or that it would be acceptable if the customer opened the email in the same domain.

After one day, I received a email from the team informing me that I was not permitted to test their production environment; hence, please check into the scope and out of scope, even if it is time consuming, otherwise you will spend a lot of time looking for bugs outside of scope.

Thanks very much and hope that you found this article helpful!