Defacement / Phishing vulnerability in hive-db.com

Defacement / Phishing

You can see from the screenshot below that I was able to replace the content of the target website with my own content.

This vulnerability could be exploited by malicious users for phishing campaigns as the link shared with the potential victims has a trusted domain in it!

The mantainer (one of the top 30 witnesses) has now been notified in multiple ways.

Stay tuned for updates! Will tell you a bit more about it after it gets fixed
😎 👍

UPDATE 1:

The vulnerability reported above has now been fixed by @jesta. The problem though is worse than I though and I've found another similar vulnerability that allows me to store code in the site and execute it when the user visits that page:

The issue has not been patched but the site is now less uselful since if you use any html tag in your post, when you try to inspect it in hive-db.com it will now just display "Content not available".

The maintainer said that at the moment he cannot fix it in a better way as he is not actively maintaining this old project (back in the Steemit days it was called https://steemdb.com).

When i have a chance I will test it a bit more for vulnerabilities but after an initial check it seems safe now.

_{My side project: @keys-defender}

- _{Keys protection_{(scan of transfers/posts/comments/others, auto-transfer to savings, auto-reset of keys)}}
- _{Phishing protection}
- _{Re-posting detection}
- _{Code injections detection}

_{My security disclosures (from most recent) on Hive:}
- _{XSS vulnerabilities in scribe.hivekings.com}
- _{XSS vulnerabilities in hiveblockexplorer.com}
- _{Malicious ads redirecting all Steemit iOS users to a phishing site}
- _{Reverse tabnabbing and clickjacking in steem.chat and steeemit registration page}