|
Wordpress Cross-Site Scripting and Script Insertion Vulnerabilities
|
|
|
|
|
Secunia Advisory:
|
SA12683
|
|
|
Release Date:
|
2004-09-29
|
|
Last Update:
|
2005-02-22
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Cross Site Scripting
|
|
Where:
|
From remote
|
|
Solution Status:
|
Vendor Patch
|
|
| Software: | Wordpress 0.x
Wordpress 1.x
|
| | CVE reference: | CVE-2004-1559 (Secunia mirror)
|
|
|
Want to know the next time vulnerabilities are fixed in this product?
- Companies can be alerted via email and SMS! |
|
|
Description:
Thomas Waldegger has reported some vulnerabilities in Wordpress, which can be exploited by malicious people to conduct cross-site scripting and script insertion attacks.
1) Input passed to certain parameters in various scripts isn't properly verified before it is returned to the user. This can be exploited to execute arbitrary HTML or script code in a user's browser session in context of an affected site by tricking the user into visiting a malicious website or follow a specially crafted link.
Examples:
http://[victim]/wp-login.php?redirect_to=[code]
http://[victim]/wp-login.php?mode=bookmarklet&text=[code]
http://[victim]/wp-login.php?mode=bookmarklet&popupurl=[code]
http://[victim]/wp-login.php?mode=bookmarklet&popuptitle=[code]
http://[victim]/admin-header.php?redirect=1&redirect_url=%22;[code]//
http://[victim]/bookmarklet.php?popuptitle=[code]
http://[victim]/bookmarklet.php?popupurl=[code]]
http://[victim]/bookmarklet.php?content=[code]
http://[victim]/bookmarklet.php?post_title=[code]
http://[victim]/categories.php?action=edit&cat_ID=[code]
http://[victim]/edit.php?s=[code]
http://[victim]/edit-comments.php?s=[code]
http://[victim]/edit-comments.php?mode=[code]
2) Input passed when posting messages, adding new categories and changing profile values is not properly sanitised before being used. This can be exploited to inject arbitrary HTML and script code, which will be executed in a user's browser session in context of an affected site when the malicious user data is viewed.
Successful exploitation requires user to be an administrator or privileged user.
The vulnerabilities have been reported in version 1.2. Some vulnerabilities also exists in 1.2.2. Other versions may also be affected.
Solution:
Use another product.
Provided and/or discovered by:
Thomas Waldegger
Changelog:
2004-10-07: Updated "Solution" section.
2004-12-17: Version 1.2.1 didn't fix all vulnerabilities. Updated "Description" and "Solution" section.
2004-12-26: Version 1.2.2 didn't fix all vulnerabilities. Updated "Description" and "Solution" section.
2005-02-22: Added CVE reference.
Original Advisory:
http://wordpress.org/development/2004/10/wp-121/
|
|
|
|
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
|
|
|
10 Related Secunia Security Advisories
|
|
|
1. WordPress Cookies Security Bypass Weakness
|
|
2. WordPress User Account Enumeration Weakness
|
|
3. Wordpress "User-Agent" Header SQL Injection Vulnerability
|
|
4. WordPress Cross-Site Scripting Vulnerabilities
|
|
5. WordPress "cache_lastpostdate" PHP Code Insertion
|
|
6. Wordpress Multiple Vulnerabilities
|
|
7. WordPress "cat_ID" SQL Injection Vulnerability
|
|
8. WordPress Cross-Site Scripting and SQL Injection Vulnerabilities
|
|
9. Wordpress "wp-login.php" HTTP Response Splitting Vulnerability
|
|
10. Wordpress Multiple Vulnerabilities
|
|
|
Send Feedback to Secunia
|
|
If you have new information regarding this Secunia advisory or a product in our database, please send it to us using either our web form or email us at vuln@secunia.com.
Ideas, suggestions, and other feedback are most welcome.
|
|
|
|
