Facebook’s Parse OAuth2 Bug

In this post i’m going to show how i was able to hack into Parse accounts via OAuth vulnerability.
You can sign in into Parse by inserting your email and password or signing in with your Facebook account.



If we click on the “Log in with Facebook” button, a GET request is generated at this URL:



The parameters that we have to consider are:

  • response_type
  • client_id 
  • redirect_uri 
  • scope 

So i started to create a forged URL that redirects the victim to a malicious site which saves the Parse token in a file.To do this,i started playing with the redirect_uri parameter to see if it allows access to subdomains or subfolders,and this was the result.

Allow request: 

  • xxx.parse.com                                   (Allow redirect to subdomains)
  • xxx.parse.com/xxx/                            (Allow redirect to subfolders)


I noticed that the redirect_uri allow access to subdomains and subfolders, so i looked for open redirect vulnerability in Parse’s domain and subdomains but i coulnd’t find anything.

I realized that Parse’s subdomains files.parse.com allows me to upload an html file, so i uploaded an html file which has some html code which redirects me to a malicious URL.The output URL to see the content of the page was:

Final POC (Facebook already fix this issue)


This URL will redirect the user to the site which has a script that takes the token and will save it in a file.