A reflected Cross-Site Scripting vulnerability has been encountered in the Magic Fields 1 WordPress plugin. This issue allows an attacker to perform a wide variety of actions, such as stealing Administrators' session tokens, or performing arbitrary actions on their behalf.
For feedback or questions about this advisory mail us at sumofpwn at securify.nl
This issue has been found during the Summer of Pwnage hacker event, running from July 1-29. A community summer event in which a large group of security bughunters (worldwide) collaborate in a month of security research on Open Source Software (WordPress this time). For fun. The event is hosted by Securify in Amsterdam.
This issue was successfully tested on Magic Fields 1 version 1.7.1.
Magic Fields is a WordPress plugin that allows for easy creation of custom fields in various post types in a WordPress post. A reflected Cross-Site Scripting vulnerability was found in Magic Fields that allows an attacker to perform a wide variety of actions, such as stealing administrators' session tokens, or performing arbitrary actions on their behalf. To exploit this issue an attacker needs to lure a user with administrator privileges to a page controlled by the attacker or trick him into clicking a malicious link.
Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted websites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser script, to a different end user. Flaws that allow these attacks to succeed are quite widespread and occur when a web application uses input from a user without validating or encoding it. Reflected XSS occurs when user input is immediately returned by a web application in an error message, search result, or any other response that includes some or all of the input provided by the user as part of the request.
The plugin has several instances where XSS is possible due to lacking output encoding and user input sanitization:
1. The custom-write-panel-id field does not validate <script> tags and does not perform output encoding. Proof of concept code that demonstrates this issue is listed in the proof of concept section.
2. The value of the custom-group-id parameter in the RCCWP_CreateCustomFieldPage.php file is insufficiently validated:
53: echo $_GET['custom-group-id'];3. The value of the custom-field-css parameter in the RCCWP_CreateCustomFieldPage.php file is insufficiently validated:
53: echo $_POST['custom-field-css'];
Proof of concept code that demonstrates the Cross-Site Scripting in the custom-write-panel-id field is listed below: