39c7c53159
4 changes to exploits/shellcodes Windows WMI - Recieve Notification Exploit (Metasploit) Google Chrome V8 - Object Allocation Size Integer Overflow WordPress Plugin WF Cookie Consent 1.1.3 - Cross-Site Scripting IceWarp Mail Server < 11.1.1 - Directory Traversal
47 lines
No EOL
1.9 KiB
Text
47 lines
No EOL
1.9 KiB
Text
# Exploit Title: WF Cookie Consent - Authenticated Persistent Cross-Site Scripting
|
|
# Date: 23/04/2018
|
|
# Exploit Author: B0UG
|
|
# Vendor Homepage: http://www.wunderfarm.com/
|
|
# Software Link: https://en-gb.wordpress.org/plugins/wf-cookie-consent/
|
|
# Version: Tested on version 1.1.3 (older versions may also be affected)
|
|
# Tested on: WordPress
|
|
# Category : Webapps
|
|
# CVE: CVE-2018-10371
|
|
|
|
I. VULNERABILITY
|
|
-------------------------
|
|
Authenticated Persistent Cross-Site Scripting
|
|
|
|
II. BACKGROUND
|
|
-------------------------
|
|
WF Cookie Consent is a WordPress plugin which has been designed to display cookie consent notifications on a WordPress website.
|
|
|
|
III. DESCRIPTION
|
|
-------------------------
|
|
A authenticated persistent cross-site scripting vulnerability has been identified in the web interface of the plugin that allows the execution of arbitrary HTML/script code to be executed in a victim's web browser.
|
|
|
|
IV. PROOF OF CONCEPT
|
|
-------------------------
|
|
1) Access WordPress control panel.
|
|
2) Navigate to the 'Pages'.
|
|
3) Add a new page and insert the script you wish to inject into the page title.
|
|
4) Now navigate to 'Settings' and select 'WF Cookie Consent'.
|
|
5) Your injected script will now be executed.
|
|
|
|
V. IMPACT
|
|
-------------------------
|
|
An attacker can execute malicious code in a victim's browser to perform various activities such as stealing cookies, session tokens, credentials and personal data amongst others.
|
|
|
|
VI. SYSTEMS AFFECTED
|
|
-------------------------
|
|
WordPress websites running "WF Cookie Consent" plugin version 1.1.3 (older versions may also be affected).
|
|
|
|
VII. REMEDIATION
|
|
-------------------------
|
|
Implement a web application such as Wordfence or uninstall the plugin.
|
|
|
|
VIII. DISCLOSURE TIMELINE
|
|
-------------------------
|
|
April 23, 2018 1: Vulnerability identified.
|
|
April 23, 2018 2: Informed developer of the vulnerability.
|
|
May 2, 2018 3: No reply from the developer. |