The PHP-Nuke EasyContent module is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data before using it in an SQL query. The risk is LOW. Expoiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
Mods please move if posted in wrong section, I wasnt sure where to ask this one.
There are several of us that use an open source program called yiimp, https://github.com/tpruvot/yiimp
several of our sites were attacked last night and I am reaching out to you guys to see if then vulnerability... (0 Replies)
Hi Guys,
I am using SOLARIS 10 and I want to install ZIP module for PHP.
I went to this link http://pecl.php.net/package/zip and I choose zip-1.12.3.tgz, the latest "stable" release, and then transferred it to my server.
Then I went to my path /usr/local/apache2/conf then untar the... (1 Reply)
Hi,
I have problem with parameter configuration.
My question is after the configuration, how to check if successfully change the value or not?
I saw someone has the same question, and followed his steps.
Original thread:... (3 Replies)
Ok..i've installed Apache 1.3.14, and it runs... BUT...I can't figure out how to get the php-4.0.4 module to run, and i've read through the install file and EVERYTYHING, aafter about 10 attempts I pissed myself off enough to goto sleep...Can anyone suggest a place to look for a lil bit more help?... (10 Replies)
PDO.PREPARE(3) 1 PDO.PREPARE(3)PDO ::prepare - Prepares a statement for execution and returns a statement object
SYNOPSIS
public PDOStatement PDO::prepare (string $statement, [array $driver_options = array()])
DESCRIPTION
Prepares an SQL statement to be executed by the PDOStatement.execute(3) method. The SQL statement can contain zero or more named (:name)
or question mark (?) parameter markers for which real values will be substituted when the statement is executed. You cannot use both named
and question mark parameter markers within the same SQL statement; pick one or the other parameter style. Use these parameters to bind any
user-input, do not include the user-input directly in the query.
You must include a unique parameter marker for each value you wish to pass in to the statement when you call PDOStatement.execute(3). You
cannot use a named parameter marker of the same name more than once in a prepared statement, unless emulation mode is on.
Note
Parameter markers can represent a complete data literal only. Neither part of literal, nor keyword, nor identifier, nor whatever
arbitrary query part can be bound using parameters. For example, you cannot bind multiple values to a single parameter in the IN()
clause of an SQL statement.
Calling PDO.prepare(3) and PDOStatement.execute(3) for statements that will be issued multiple times with different parameter values opti-
mizes the performance of your application by allowing the driver to negotiate client and/or server side caching of the query plan and meta
information, and helps to prevent SQL injection attacks by eliminating the need to manually quote the parameters.
PDO will emulate prepared statements/bound parameters for drivers that do not natively support them, and can also rewrite named or ques-
tion mark style parameter markers to something more appropriate, if the driver supports one style but not the other.
PARAMETERS
o $statement
- This must be a valid SQL statement for the target database server.
o $driver_options
- This array holds one or more key=>value pairs to set attribute values for the PDOStatement object that this method returns. You
would most commonly use this to set the PDO::ATTR_CURSOR value to PDO::CURSOR_SCROLL to request a scrollable cursor. Some drivers
have driver specific options that may be set at prepare-time.
RETURN VALUES
If the database server successfully prepares the statement, PDO.prepare(3) returns a PDOStatement object. If the database server cannot
successfully prepare the statement, PDO.prepare(3) returns FALSE or emits PDOException (depending on error handling).
Note
Emulated prepared statements does not communicate with the database server so PDO.prepare(3) does not check the statement.
EXAMPLES
Example #1
Prepare an SQL statement with named parameters
<?php
/* Execute a prepared statement by passing an array of values */
$sql = 'SELECT name, colour, calories
FROM fruit
WHERE calories < :calories AND colour = :colour';
$sth = $dbh->prepare($sql, array(PDO::ATTR_CURSOR => PDO::CURSOR_FWDONLY));
$sth->execute(array(':calories' => 150, ':colour' => 'red'));
$red = $sth->fetchAll();
$sth->execute(array(':calories' => 175, ':colour' => 'yellow'));
$yellow = $sth->fetchAll();
?>
Example #2
Prepare an SQL statement with question mark parameters
<?php
/* Execute a prepared statement by passing an array of values */
$sth = $dbh->prepare('SELECT name, colour, calories
FROM fruit
WHERE calories < ? AND colour = ?');
$sth->execute(array(150, 'red'));
$red = $sth->fetchAll();
$sth->execute(array(175, 'yellow'));
$yellow = $sth->fetchAll();
?>
SEE ALSO PDO.exec(3), PDO.query(3), PDOStatement.execute(3).
PHP Documentation Group PDO.PREPARE(3)