DATABASE RESOURCES PRICING ABOUT US

{"id": "VULNERABLE:691", "vendorId": null, "type": "vulnerlab", "bulletinFamily": "exploit", "title": "Better WP Security v3.4.3 Wordpress - Web Vulnerabilities", "description": "", "published": "2012-08-20T00:00:00", "modified": "2012-08-20T00:00:00", "cvss": {"score": 0.0, "vector": "NONE"}, "cvss2": {}, "cvss3": {}, "href": "https://www.vulnerability-lab.com/get_content.php?id=691", "reporter": "Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@vulnerability-lab.com)", "references": [], "cvelist": [], "immutableFields": [], "lastseen": "2021-12-20T07:39:12", "viewCount": 2, "enchantments": {"dependencies": {}, "score": {"value": -0.1, "vector": "NONE"}, "backreferences": {}, "exploitation": null, "vulnersScore": -0.1}, "sourceData": "Document Title:\r\n===============\r\nBetter WP Security v3.4.3 Wordpress - Web Vulnerabilities\r\n\r\n\r\nReferences (Source):\r\n====================\r\nhttp://www.vulnerability-lab.com/get_content.php?id=691\r\n\r\n\r\nRelease Date:\r\n=============\r\n2012-08-20\r\n\r\n\r\nVulnerability Laboratory ID (VL-ID):\r\n====================================\r\n691\r\n\r\n\r\nCommon Vulnerability Scoring System:\r\n====================================\r\n3.5\r\n\r\n\r\nProduct & Service Introduction:\r\n===============================\r\nplugin thereby ensuring that as many security holes as possible are patched without having to worry about \r\nconflicting features or the possibility of missing anything on your site. With one-click activation for most \r\nfeatures as well as advanced features for experienced users Better WP Security can help protect any site.\r\n\r\n(Copy of the Vendor Homepage: http://wordpress.org/extend/plugins/better-wp-security/ )\r\n\r\n\r\nAbstract Advisory Information:\r\n==============================\r\nThe Vulnerability Laboratory Research Team discovered multiple persistent web vulnerabilities in the Better WP security v3.4.3 Wordpress Application Addon.\r\n\r\n\r\nVulnerability Disclosure Timeline:\r\n==================================\r\n2012-08-21:\tPublic Disclosure\r\n\r\n\r\nDiscovery Status:\r\n=================\r\nPublished\r\n\r\n\r\nExploitation Technique:\r\n=======================\r\nRemote\r\n\r\n\r\nSeverity Level:\r\n===============\r\nLow\r\n\r\n\r\nTechnical Details & Description:\r\n================================\r\nMultiple persistent input validation vulnerabilities are detected in the Better WP security v3.4.3 Wordpress Application Addon.\r\nThe vulnerability allows remote attackers to hijack website customer, moderator or admin sessions with medium or high required user inter \r\naction. The bugs are located on server side in the Limit Login Attempts, Exception Handling Error & Intrusion Detection module with the \r\nbound vulnerable email address & error parameter. Successful exploitation can result in wordpress application account steal, client side \r\nphishing & client-side content request manipulation. Exploitation requires medium or high user inter action & without privileged \r\nweb application user account.\r\n\r\nVulnerable Module(s):\r\n\t\t\t\t[+] Better WP Security - Limit Login Attempts & Intrusion Detection\r\n\t\t\t\t[+] Exception Handling Error\r\n\r\nVulnerable Parameter(s):\r\n\t\t\t\t[+] Email Address\r\n\t\t\t\t[+] Error\r\n\r\n\r\nProof of Concept (PoC):\r\n=======================\r\nThe persistent vulnerability can be exploited by remote attackers with low required user inter action & low privileged \r\napplication user account. For demonstration or reproduce ...\r\n\r\nInject the following example string to the application input (persistent) or parameter (client side)\r\nString: >\"<iframe src=http://www.vulnerability-lab.com></iframe>\r\n\r\n\r\nReview: Listings\r\n\r\n<tr valign=\"top\">\r\n<th scope=\"row\" class=\"settinglabel\">\r\n<label for=\"\" \"ll_emailaddress\"=\"\">Email Address</label>\r\n</th>\r\n<td class=\"settingfield\">\r\n<input id=\"ll_emailaddress\" name=\"ll_emailaddress\" value=\"\\\" type=\"text\">\r\n<[PERSISTENT INJECTED SCRIPT CODE!]\")' <=\"\" admin@vulnerability-lab.com\"=\"\">\r\n\r\n\r\nReview: Exception Handling\r\n\r\n<div class=\"error\" style=\"text-align: center;\"><p style=\"color: red; font-size: 14px; font-weight: \r\nbold;\">Attention !</p><p>\r\nPlease add this site now to your <a target=\"_blank\" href=\"http://managewp.com/wp-admin\">ManageWP.com</a> account. \r\nOr deactivate the Worker plugin to avoid <a target=\"_blank\" href=\"http://managewp.com/user-guide/security\">security issues</a>.\t \t\r\n</p></div><div id=\"message\" class=\"error\"><p>Login time period needs to be aan integer greater than 0.</p></div>\r\n<div id=\"message\" class=\"error\"><p>\\\"><[PERSISTENT INJECTED SCRIPT CODE!]\")' <=\"\" is=\"\" \r\nnot=\"\" a=\"\" valid=\"\" ip.<=\"\" p=\"\"></div>\r\n\r\n\r\nSolution - Fix & Patch:\r\n=======================\r\nThe vulnerabilities can be patched by parsing the email address & error exception handling parameters and output listing.\r\n\r\n\r\nSecurity Risk:\r\n==============\r\nThe security risk of the persistent input validation vulnerabilities are estimated as medium.\r\n\r\n\r\nCredits & Authors:\r\n==================\r\nVulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@vulnerability-lab.com)\r\n\r\n\r\nDisclaimer & Information:\r\n=========================\r\nThe information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties, \r\neither expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-\r\nLab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business \r\nprofits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some \r\nstates do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation \r\nmay not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases \r\nor trade with fraud/stolen material.\r\n\r\nDomains: www.vulnerability-lab.com \t- www.vuln-lab.com\t\t\t - www.vulnerability-lab.com/register\r\nContact: admin@vulnerability-lab.com \t- support@vulnerability-lab.com \t - research@vulnerability-lab.com\r\nSection: video.vulnerability-lab.com \t- forum.vulnerability-lab.com \t\t - news.vulnerability-lab.com\r\nSocial:\t twitter.com/#!/vuln_lab \t\t- facebook.com/VulnerabilityLab \t - youtube.com/user/vulnerability0lab\r\nFeeds:\t vulnerability-lab.com/rss/rss.php\t- vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php\r\n\r\nAny modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. \r\nPermission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other \r\nmedia, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, sourcecode, videos and \r\nother information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), \r\nmodify, use or edit our material contact (admin@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission.\r\n\r\n \t\t\t\t \tCopyright \u00a9 2012 | Vulnerability Laboratory\r\n\r\n\r\n\r\n", "category": "Web Application Vulnerabilities", "_state": {"dependencies": 1646378720, "score": 1659853389, "epss": 1679174273}, "_internal": {"score_hash": "7352d9029facf6a23464986d632c30b2"}}

{}