Some vulnerabilities have been reported in Drupal, which can be exploited by malicious users to conduct script insertion attacks and compromise a vulnerable system, and by malicious people to conduct cross-site scripting and cross-site request forgery attacks.

1) Input passed to an unspecified parameter 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) A vulnerability is caused by the fact that the private filesystem uses the MIME media type it receives from the web browser when handling uploads. This can be exploited for script insertion attacks.

Successful exploitation of this vulnerability requires valid user credentials with the right to upload files.

3) A vulnerability is caused due to missing restrictions on what file types that users are allowed to upload in the BlogAPI module. This can be exploited to e.g. execute arbitrary PHP code.

Successful exploitation of this vulnerability requires valid user credentials with the "administer content with blog api" permission.

4) A vulnerability is caused due to the application allowing users to perform certain actions via HTTP requests without performing any validity checks to verify the request. This can be exploited to add or delete user access rules, by enticing a logged-in user to visit a malicious web page.

The vulnerabilities are reported in all 5.x versions prior to 5.10 and all 6.x versions prior to 6.4.

Solution
Update to version 5.10 or 6.4.

Provided and/or discovered by
1) Bart Jansens, Drupal security team
2) The vendor credits Mark Burdett.
3) Gábor Hojtsy, Drupal security team and Mark Burdett
4) Barry Jaspan, Drupal security team

Changelog
Further details available to Secunia VIM customers

Original Advisory
DRUPAL-SA-2008-047:
http://drupal.org/node/295053

Deep Links
Links available to Secunia VIM customers