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

1) Drupal does not correctly use the Forms API and allows users to perform certain actions via HTTP requests without performing any validity checks to verify the request. This can be exploited e.g. to delete comments or content revisions and disable menu items by enticing a logged-in user to visit a malicious site.

The vulnerabilities are reported in Drupal 5.x prior to 5.2.

2) Certain server variables are 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 "administer content types" privileges.

The vulnerabilities are reported in Drupal 4.7.x prior to 4.7.7 and Drupal 5.x prior to Drupal 5.2

Solution
Update to version 4.7.7 and 5.2 or apply patches.

Provided and/or discovered by
The vendor credits:
1) Konstantin Käfer (menu issue) and the Drupal security team.
2) David Caylor (PHP_SELF issue) and Karthik (Content type naming issues).

Changelog
Further details available to Secunia VIM customers

Original Advisory
1) http://drupal.org/files/sa-2007-017/advisory.txt
2) http://drupal.org/files/sa-2007-018/advisory.txt

Alternate/detailed remediation
Further details available in Customer Area

Deep Links
Links available to Secunia VIM customers