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


Passionate about writing secure code?

http://secunia.com/company/jobs/open_positions/talented_programmer


Read this if your favourite tool is a disassembler

http://secunia.com/company/jobs/open_positions/reverse_engineer


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

TITLE:
Website Baker Multiple Vulnerabilities

SECUNIA ADVISORY ID:
SA39899

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

RELEASE DATE:
2010-07-01

DISCUSS ADVISORY:
http://secunia.com/advisories/39899/#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/39899/

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=39899

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 some vulnerabilities in Website
Baker, which can be exploited by malicious users to conduct script
insertion attacks, SQL injection attacks, disclose sensitive
information, and enumerate files on an affected system and by
malicious people to conduct cross-site scripting attacks.

1) Input passed to the "username" parameter in admin/login/index.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.

Successful exploitation requires that the victim is logged out.

2) Input passed via the "display_name" parameter to
admin/preferences/details.php is not properly sanitised before being
displayed to the user. This can be exploited to insert arbitrary HTML
and script code, which will be executed in a user's browser session in
context of an affected site when the malicious data is being viewed.

3) Input passed via the "title" parameter to
modules/form/save_field.php when adding or editing a form field of a
page is not properly sanitised before being displayed to the user.
This can be exploited to insert arbitrary HTML and script code, which
will be executed in a user's browser session in context of an affected
site when the malicious data is being viewed.

Successful exploitation of this vulnerability requires "Modify
Settings" permissions for "Pages".

4) Input passed to the "language", "date_format", and "time_format"
parameters in admin/preferences/details.php 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 "type", "parent", and "visibility" parameters
to admin/pages/add.php 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 "Add"
permissions for "Pages".

6) Input passed via the "parent" and "menu" parameters to
admin/pages/settings2.php (when "page_id" 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 "Modify
Settings" permissions for "Pages".

7) Input passed via the "module" parameter to
admin/pages/sections.php (when "page_id" 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 "Modify
Settings" permissions for "Pages".

8) The admin/modules/details.php script displays the "Module Details"
page or redirects to a different page depending on the existence of
the file passed via the "file" parameter. This can be exploited to
enumerate existing files on the local system via directory traversal
sequences.

Successful exploitation of this vulnerability requires "View"
permissions for "Modules".

9) The admin/templates/details.php script displays the "Template
Details" page or redirects to a different page depending on the
existence of the file passed via the "file" parameter. This can be
exploited to enumerate existing files on the local system via
directory traversal sequences.

Successful exploitation of this vulnerability requires "View"
permissions for "Templates".

10) Input passed to the "language" parameter in
admin/preferences/details.php is not properly verified before being
used to include files. This can be exploited to include arbitrary
files from local resources via directory traversal sequences and
URL-encoded NULL bytes.

11) Input passed to the "code" parameter in
admin/languages/details.php is not properly verified before being
used to include files. This can be exploited to include arbitrary
files from local resources via directory traversal sequences and
URL-encoded NULL bytes.

Successful exploitation of this vulnerability requires "View"
permissions for "Languages".

12) Input passed via the "template" parameter to
admin/pages/settings2.php when modifying page settings is not
properly verified before being used to include files. This can be
exploited to include arbitrary files from local resources via
directory traversal sequences and URL-encoded NULL bytes.

Successful exploitation of this vulnerability requires "Modify
Settings" permissions for "Pages".

13) Input passed via the "type" parameter to admin/pages/add.php is
not properly verified before being used to include files. This can be
exploited to include arbitrary files from local resources via
directory traversal sequences and URL-encoded NULL bytes.

Successful exploitation of this vulnerability requires "Add"
permissions for "Pages".

Successful exploitation of vulnerabilities #4, #5, #7, #10, and #11
requires that "magic_quotes_gpc" is disabled.

The vulnerabilities are confirmed in version 2.8.1 Revision 1287.
Other versions may also be affected.

SOLUTION:
Edit the source code to ensure that input is properly sanitised and
verified.

PROVIDED AND/OR DISCOVERED BY:
Secunia Research

ORIGINAL ADVISORY:
Secunia Research:
http://secunia.com/secunia_research/2010-89/
http://secunia.com/secunia_research/2010-90/
http://secunia.com/secunia_research/2010-91/
http://secunia.com/secunia_research/2010-92/
http://secunia.com/secunia_research/2010-93/

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.

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