zCMS [PHP, OOP, Phoenix, Secure]

Status
Not open for further replies.
I can't see to delete the navs 'Buy VIP' and 'Forum' they're not in site_navi, so some help would be nice? ;3
 
I agree with Azaidi, zCMS ISNT as good as its cracked up to be. There are soooo many exploits still unpatched, had this on my hotel when I used VPS and it got hacked in the first 10minutes of opening.
We had to go patch each exploit ourselves, even the simple ones that shouldn't of been left open by it's "coder"

"exoh"
 
I agree with Azaidi, zCMS ISNT as good as its cracked up to be. There are soooo many exploits still unpatched, had this on my hotel when I used VPS and it got hacked in the first 10minutes of opening.
We had to go patch each exploit ourselves, even the simple ones that shouldn't of been left open by it's "coder"

"exoh"

Yeah, no, shutup. You have no idea what you are talking about.

The "exploit" that I supposedly left in there is an unfiltered $_GET param that is actually left unfiltered in the stock copy of uber. So where's your theory now.

Exploit is in article.php btw. Enjoy. This is why Supa will stay private for a while before release - idiots like you.
 
Yeah, no, shutup. You have no idea what you are talking about.

The "exploit" that I supposedly left in there is an unfiltered $_GET param that is actually left unfiltered in the stock copy of uber. So where's your theory now.

Exploit is in article.php btw. Enjoy. This is why Supa will stay private for a while before release - idiots like you.

You can't blame em if the CMS has exploits in there.
 
I understand the frustration - people are mad because a param was left unfiltered. However, a simple $_GET param is easily resolvable.

There shouldn't be further argument regarding this.
If your understanding of PHP is at least basic, then you should be able to resolve the issue.
 
mysql_real_escape_string(stripslashes(trim( $_GET **** )))

Wow that's really hard :O

Woa. Woa. Woa. Woa.
Stop there.

Do you even know what Realescape, Stripslashes, and Trim does?

You will only need Stripslashes & Trim, or you could do this
Functions Bro, Functions

PHP:
/**
 * Cleans the inputted String
 * Will protects against Basic SQL injections
 * @param $_GET / $_POST
 * @return Stripped Variable
 */
function cleanvar($s_string){
	
$sStr = Stripslashes($s_string);

$sTtr = Trim($sStr);

return $sTtr;
}


cleanvar($_GET[ADMINPASSWORDINPLAINTEXTISSOSAFE]);
 
Woa. Woa. Woa. Woa.
Stop there.

Do you even know what Realescape, Stripslashes, and Trim does?

You will only need Stripslashes & Trim, or you could do this
Functions Bro, Functions

PHP:
/**
 * Cleans the inputted String
 * Will protects against Basic SQL injections
 * @param $_GET / $_POST
 * @return Stripped Variable
 */
function cleanvar($s_string){
    
$sStr = Stripslashes($s_string);

$sTtr = Trim($sStr);

return $sTtr;
}


cleanvar($_GET[ADMINPASSWORDINPLAINTEXTISSOSAFE]);


You do realize that if anything is going in, or coming out of a database you want to use mysql_real_escape_string right?

When you're trimming a string, you're basically removing whitespaces from both sides, which imo, could cause a lot of database confusion if someone posts a space before an e-mail or something. Stripslashes just removes backslashes.. Therefore the function you're using really isn't cleaning the string from any/all vulnerabilities that it may contain. That's where mysql_real_escape_string comes in handy. It removes specicial characters that could manipulate your SQL database.

So function or not, his code was still correct over yours... that is if your main intention was stripping the string completely clean. Goes to show that functions doesn't always make your code 'right'. It just makes it more organized, and dynamic... while also requiring less work down the line. Before moving onto functions you should at least understand the complete basics.

Not trying to offend you or anything either. =P
 
You do realize that if anything is going in, or coming out of a database you want to use mysql_real_escape_string right?

When you're trimming a string, you're basically removing whitespaces from both sides, which imo, could cause a lot of database confusion if someone posts a space before an e-mail or something. Stripslashes just removes backslashes.. Therefore the function you're using really isn't cleaning the string from any/all vulnerabilities that it may contain. That's where mysql_real_escape_string comes in handy. It removes specicial characters that could manipulate your SQL database.

So function or not, his code was still correct over yours... that is if your main intention was stripping the string completely clean. Goes to show that functions doesn't always make your code 'right'. It just makes it more organized, and dynamic... while also requiring less work down the line. Before moving onto functions you should at least understand the complete basics.

Not trying to offend you or anything either. =P

You also need to be connected to a db to use mysql_real_escape_string but if you use MySQLi..


PHP:
$db = new MySQLi("connection infos");
$string = "''''lol''''";
echo $db->real_escape_string($string);

^^
 
It was just an example typed on my mobile, I know how to make a function of it. + What G33k did can be shortened a lot:

function cleanvar($s_string){
return stripslashes(trim($s_string));
}
I know I left the mysql_real_escape string out but I'm just shortening his php code :P
 
Code is not about being short.
If i could, i could paste all code from conradUK into 1 PHP FILE

BUT THAT WOULD BE A CLUSTERFUCK
 
i got this error :O

Notice: Undefined index: HTTP_CF_CONNECTING_IP in C:\xampp\htdocs\global.php on line 21

Warning: mysql_result() [function.mysql-result]: Unable to jump to row 0 on MySQL result index 12 in C:\xampp\htdocs\inc\class.core.php on line 19
 
Status
Not open for further replies.
Back