----------------------------------------------------------------------


Secunia Research and vulnerability disclosures coordinated by Secunia:

http://secunia.com/research/


----------------------------------------------------------------------

TITLE:
RunCMS Multiple Vulnerabilities

SECUNIA ADVISORY ID:
SA43542

VERIFY ADVISORY:
Secunia.com
http://secunia.com/advisories/43542/
Customer Area (Credentials Required)
https://ca.secunia.com/?page=viewadvisory&vuln_id=43542

RELEASE DATE:
2011-03-31

DISCUSS ADVISORY:
http://secunia.com/advisories/43542/#comments

AVAILABLE ON SITE AND IN CUSTOMER AREA:
 * Last Update
 * Popularity
 * Comments
 * Criticality Level
 * Impact
 * Where
 * Solution Status
 * Operating System / Software
 * CVE Reference(s)

http://secunia.com/advisories/43542/

ONLY AVAILABLE IN CUSTOMER AREA:
 * Authentication Level
 * Report Reliability
 * Secunia PoC
 * Secunia Analysis
 * Systems Affected
 * Approve Distribution
 * Remediation Status
 * Secunia CVSS Score
 * CVSS

https://ca.secunia.com/?page=viewadvisory&vuln_id=43542

ONLY AVAILABLE WITH SECUNIA CSI AND SECUNIA PSI:
 * AUTOMATED SCANNING

http://secunia.com/vulnerability_scanning/personal/
http://secunia.com/vulnerability_scanning/corporate/wsus_sccm_3rd_third_party_patching/

DESCRIPTION:
Secunia Research has discovered multiple vulnerabilities in RunCMS,
which can be exploited by malicious users to conduct SQL injection
attacks and compromise a vulnerable system and by malicious people to
conduct cross-site scripting and request forgery attacks.

1) Input appended to the URL after modules/forum/topicmanager.php is
not properly sanitised before being returned to the user. This can be
exploited to execute arbitrary HTML and script code in a user's
browser session in context of an affected site.

2) The application allows users to perform certain actions via HTTP
requests without performing any validity checks to verify the
requests. This can be exploited to e.g. add arbitrary news articles
or conduct script insertion attacks by tricking a user into visiting
a malicious web site while being logged-in to the application.

3) Input passed via the "topic_id" parameter to
modules/forum/post.php (when "forum", "pid", and "is_reply" are set)
is not properly sanitised before being used in SQL queries. This can
be exploited to manipulate SQL queries by injecting arbitrary SQL
code.

Successful exploitation of this vulnerability requires that the
"Forum" module is enabled and requires "Can Reply" permissions.

4) Input passed via the "forum" parameter to modules/forum/search.php
(when "term" and "addtemrms" are set) is not properly sanitised before
being used in SQL queries. This can be exploited to manipulate SQL
queries by injecting arbitrary SQL code.

5) Input passed via the "forum" parameter to modules/forum/post.php
(when "message" and "post_id" are set) is not properly sanitised in
the "is_moderator()" function in modules/forum/functions.php before
being used in SQL queries. This can be exploited to manipulate SQL
queries by injecting arbitrary SQL code.

Successful exploitation requires permissions to post in a forum.

6) Input passed e.g. via the "FORumLastVisit" cookie parameter to
modules/forum/index.php is not properly sanitised in the
"getNewTopics()" function in modules/forum/class/class.forumtable.php
before being used in SQL queries. This can be exploited to manipulate
SQL queries by injecting arbitrary SQL code.

7) Input passed via the "sort" and "by" parameters to e.g.
modules/pm/index.php and modules/pm/pmsend.php is not properly
sanitised in the "getAllPM()" function in
modules/pm/class/pm.class.php before being used in SQL queries. This
can be exploited to manipulate SQL queries by injecting arbitrary SQL
code.

Successful exploitation of this vulnerability requires "Module
Access" rights for "Private Pm".

8) Input passed via the "bid" parameter to modules/banners/index.php
(when "op" is set to "click") is not properly sanitised before being
used in SQL queries. This can be exploited to manipulate SQL queries
by injecting arbitrary SQL code.

Successful exploitation of this vulnerability requires that the
"Banners" module is enabled and requires permissions to access the
module.

9) Input passed via the "bid" and "cid" parameters to
modules/banners/index.php (when "op" is set to "EmailStats" or
"Change") is not properly sanitised before being used in SQL queries.
This can be exploited to manipulate SQL queries by injecting arbitrary
SQL code.

Successful exploitation of this vulnerability requires that the
"Banners" module is enabled and requires permissions to access the
module.

10) Input passed via the "url" parameter to modules/banners/index.php
(when "op" is set to "Change" and "bid" and "cid" are set) is not
properly sanitised before being used in SQL queries. This can be
exploited to manipulate SQL queries by injecting arbitrary SQL code.

Successful exploitation of this vulnerability requires that the
"Banners" module is enabled, requires permissions to access the
module, and requires that "magic_quotes_gpc" is disabled.

11) Input passed via the "orderby" parameter to
modules/links/viewcat.php (when the "cid" parameter is set) is not
properly sanitised before being used in SQL queries. This can be
exploited to manipulate SQL queries by injecting arbitrary SQL code.

Successful exploitation of this vulnerability requires "Module
Access" rights for "Links" module.

12) Input passed e.g. via the "key" parameter to
modules/galleri/carte.php (when the "op" is set to "actv") is not
properly sanitised in the "countAllMail()" function in
modules/galleri/class/gall_mail.php before being used SQL queries.
This can be exploited to manipulate SQL queries by injecting
arbitrary SQL code.

Successful exploitation of this vulnerability requires "Module
Access" rights for the "Galleri" module.

13) Input passed via e.g. the "orderby" parameter to
modules/galleri/index.php (when "op" is set to "top_ten") is not
properly sanitised in the "getAllImg()" in
modules/galleri/class/gall_img.php before being used in SQL queries.
This can be exploited to manipulate SQL queries by injecting
arbitrary SQL code.

Successful exploitation requires that the "Galleri" module is enabled
and permissions to access the module.

14) The modules/galleri/uploaduser.php script improperly validates
uploaded files. This can be exploited to execute arbitrary PHP code
by uploading a PHP file with e.g. an appended ".gif" file extension.

Successful exploitation of this vulnerability requires upload
permissions for the "Galleri" module and that Apache is not
configured to handle the mime-type for media files with e.g. a "jpg"
or "gif" extension.

The vulnerabilities are confirmed in version 2.2.2. Other versions
may also be affected.

SOLUTION:
Edit the source code to ensure that input is properly sanitised. Do
not browse untrusted websites or follow untrusted links while
logged-in to the application. Restrict access to the
modues/galleri/galerie and modues/galleri/thumbnails directories
(e.g. via .htaccess).

PROVIDED AND/OR DISCOVERED BY:
Secunia Research.

ORIGINAL ADVISORY:
Secunia Research:
http://secunia.com/secunia_research/2011-27/
http://secunia.com/secunia_research/2011-28/
http://secunia.com/secunia_research/2011-29/
http://secunia.com/secunia_research/2011-30/

OTHER REFERENCES:
Further details available in Customer Area:
http://secunia.com/products/corporate/EVM/

DEEP LINKS:
Further details available in Customer Area:
http://secunia.com/products/corporate/EVM/

EXTENDED DESCRIPTION:
Further details available in Customer Area:
http://secunia.com/products/corporate/EVM/

EXTENDED SOLUTION:
Further details available in Customer Area:
http://secunia.com/products/corporate/EVM/

EXPLOIT:
Further details available in Customer Area:
http://secunia.com/products/corporate/EVM/

----------------------------------------------------------------------

About:
This Advisory was delivered by Secunia as a free service to help
private users keeping their systems up to date against the latest
vulnerabilities.

Subscribe:
http://secunia.com/advisories/secunia_security_advisories/

Definitions: (Criticality, Where etc.)
http://secunia.com/advisories/about_secunia_advisories/


Please Note:
Secunia recommends that you verify all advisories you receive by
clicking the link.
Secunia NEVER sends attached files with advisories.
Secunia does not advise people to install third party patches, only
use those supplied by the vendor.

----------------------------------------------------------------------