nuclei-templates/http/cves/2019/CVE-2019-15858.yaml

id: CVE-2019-15858

info:
  name: WordPress Woody Ad Snippets <2.2.5 - Cross-Site Scripting/Remote Code Execution
  author: dwisiswant0,fmunozs,patralos
  severity: high
  description: |
    WordPress Woody Ad Snippets prior to 2.2.5 is susceptible to cross-site scripting and remote code execution via admin/includes/class.import.snippet.php, which allows unauthenticated options import as demonstrated by storing a cross-site scripting payload for remote code execution.
  remediation: |
    Update to the latest version of the Woody Ad Snippets plugin (2.2.5) or apply the vendor-provided patch to mitigate the vulnerability.
  reference:
    - https://github.com/GeneralEG/CVE-2019-15858
    - https://blog.nintechnet.com/multiple-vulnerabilities-in-wordpress-woody-ad-snippets-plugin-lead-to-remote-code-execution/
    - https://wpvulndb.com/vulnerabilities/9490
    - https://nvd.nist.gov/vuln/detail/CVE-2019-15858
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
    cvss-score: 8.8
    cve-id: CVE-2019-15858
    cwe-id: CWE-306
    epss-score: 0.02782
    epss-percentile: 0.8928
    cpe: cpe:2.3:a:webcraftic:woody_ad_snippets:*:*:*:*:*:wordpress:*:*
  metadata:
    max-request: 1
    vendor: webcraftic
    product: woody_ad_snippets
    framework: wordpress
  tags: cve,cve2019,wordpress,wp-plugin,xss,wp

http:
  - method: GET
    path:
      - "{{BaseURL}}/wp-content/plugins/insert-php/readme.txt"

    matchers-condition: and
    matchers:
      - type: word
        part: body
        negative: true
        words:
          - "2.2.5"

      - type: word
        part: body
        words:
          - "Changelog"

      - type: word
        part: body
        words:
          - "Woody ad snippets"

      - type: status
        status:
          - 200
misc changes 2021-01-02 04:59:06 +00:00			`id: CVE-2019-15858`
Reintroduce CVE-2019-15858.yaml check Old version had a lot of FP as it did not check if the returned page was acutally the correct readme. So I added a check for the name of the plugin and another one to ensure there is a changelog. This shoud remove almost all false positives. 2020-12-15 01:53:39 +00:00
			`info:`
Enhancement: cves/2019/CVE-2019-15858.yaml by mp 2022-06-14 15:10:31 +00:00			`name: WordPress Woody Ad Snippets <2.2.5 - Cross-Site Scripting/Remote Code Execution`
Updated author names 2021-06-09 12:20:56 +00:00			`author: dwisiswant0,fmunozs,patralos`
Reintroduce CVE-2019-15858.yaml check Old version had a lot of FP as it did not check if the returned page was acutally the correct readme. So I added a check for the name of the plugin and another one to ensure there is a changelog. This shoud remove almost all false positives. 2020-12-15 01:53:39 +00:00			`severity: high`
			`description: \|`
Enhancement: cves/2019/CVE-2019-15858.yaml by mp 2022-06-14 15:10:31 +00:00			`WordPress Woody Ad Snippets prior to 2.2.5 is susceptible to cross-site scripting and remote code execution via admin/includes/class.import.snippet.php, which allows unauthenticated options import as demonstrated by storing a cross-site scripting payload for remote code execution.`
updated 2019 CVEs 2023-09-06 12:53:28 +00:00			`remediation: \|`
			`Update to the latest version of the Woody Ad Snippets plugin (2.2.5) or apply the vendor-provided patch to mitigate the vulnerability.`
refactor: Description field uniformization * info field reorder * reference values refactored to list * added new lines after the id and before the protocols * removed extra new lines * split really long descriptions to multiple lines (part 1) * other minor fixes 2022-04-22 10:38:41 +00:00			`reference:`
			`- https://github.com/GeneralEG/CVE-2019-15858`
additional reference to cves templates (#4395) * additional reference to cves templates * Update CVE-2006-1681.yaml * Update CVE-2009-3318.yaml * Update CVE-2009-4223.yaml * Update CVE-2010-0942.yaml * Update CVE-2010-0944.yaml * Update CVE-2010-0972.yaml * Update CVE-2010-1304.yaml * Update CVE-2010-1308.yaml * Update CVE-2010-1313.yaml * Update CVE-2010-1461.yaml * Update CVE-2010-1470.yaml * Update CVE-2010-1471.yaml * Update CVE-2010-1472.yaml * Update CVE-2010-1474.yaml * removed duplicate references * misc fix Co-authored-by: Prince Chaddha <prince@projectdiscovery.io> Co-authored-by: Prince Chaddha <cyberbossprince@gmail.com> 2022-05-17 09:18:12 +00:00			`- https://blog.nintechnet.com/multiple-vulnerabilities-in-wordpress-woody-ad-snippets-plugin-lead-to-remote-code-execution/`
			`- https://wpvulndb.com/vulnerabilities/9490`
Enhancement: cves/2019/CVE-2019-15858.yaml by mp 2022-06-14 15:10:31 +00:00			`- https://nvd.nist.gov/vuln/detail/CVE-2019-15858`
Added cve annotations + severity adjustments 2021-09-10 11:26:40 +00:00			`classification:`
			`cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`
refactor: Description field uniformization * info field reorder * reference values refactored to list * added new lines after the id and before the protocols * removed extra new lines * split really long descriptions to multiple lines (part 1) * other minor fixes 2022-04-22 10:38:41 +00:00			`cvss-score: 8.8`
Added cve annotations + severity adjustments 2021-09-10 11:26:40 +00:00			`cve-id: CVE-2019-15858`
			`cwe-id: CWE-306`
CVE Enrichment :tada: 2023-07-11 19:49:27 +00:00			`epss-score: 0.02782`
Added EPSS Percentile 2023-08-31 11:46:18 +00:00			`epss-percentile: 0.8928`
updated 2019 CVEs 2023-09-06 12:53:28 +00:00			`cpe: cpe:2.3:a:webcraftic:woody_ad_snippets::::::wordpress::*`
Added max request counter of each template 2023-04-28 08:11:21 +00:00			`metadata:`
			`max-request: 1`
CVE Enrichment :tada: 2023-07-11 19:49:27 +00:00			`vendor: webcraftic`
			`product: woody_ad_snippets`
updated 2019 CVEs 2023-09-06 12:53:28 +00:00			`framework: wordpress`
CVE Enrichment :tada: 2023-07-11 19:49:27 +00:00			`tags: cve,cve2019,wordpress,wp-plugin,xss,wp`
Reintroduce CVE-2019-15858.yaml check Old version had a lot of FP as it did not check if the returned page was acutally the correct readme. So I added a check for the name of the plugin and another one to ensure there is a changelog. This shoud remove almost all false positives. 2020-12-15 01:53:39 +00:00
Refactoring the directory structure based on protocols (#7137) * moving http templates * updated cves.json * moved network CVEs * updated scripts * updated workflows * updated requests to http * replaced network to tcp --------- Co-authored-by: sandeep <8293321+ehsandeep@users.noreply.github.com> 2023-04-27 04:28:59 +00:00			`http:`
Reintroduce CVE-2019-15858.yaml check Old version had a lot of FP as it did not check if the returned page was acutally the correct readme. So I added a check for the name of the plugin and another one to ensure there is a changelog. This shoud remove almost all false positives. 2020-12-15 01:53:39 +00:00			`- method: GET`
			`path:`
			`- "{{BaseURL}}/wp-content/plugins/insert-php/readme.txt"`

			`matchers-condition: and`
			`matchers:`
			`- type: word`
Update CVE-2019-15858.yaml 2022-06-20 17:29:35 +00:00			`part: body`
CVE Enrichment :tada: 2023-07-11 19:49:27 +00:00			`negative: true`
Reintroduce CVE-2019-15858.yaml check Old version had a lot of FP as it did not check if the returned page was acutally the correct readme. So I added a check for the name of the plugin and another one to ensure there is a changelog. This shoud remove almost all false positives. 2020-12-15 01:53:39 +00:00			`words:`
			`- "2.2.5"`

			`- type: word`
Update CVE-2019-15858.yaml 2022-06-20 17:29:35 +00:00			`part: body`
Reintroduce CVE-2019-15858.yaml check Old version had a lot of FP as it did not check if the returned page was acutally the correct readme. So I added a check for the name of the plugin and another one to ensure there is a changelog. This shoud remove almost all false positives. 2020-12-15 01:53:39 +00:00			`words:`
			`- "Changelog"`

			`- type: word`
Update CVE-2019-15858.yaml 2022-06-20 17:29:35 +00:00			`part: body`
Reintroduce CVE-2019-15858.yaml check Old version had a lot of FP as it did not check if the returned page was acutally the correct readme. So I added a check for the name of the plugin and another one to ensure there is a changelog. This shoud remove almost all false positives. 2020-12-15 01:53:39 +00:00			`words:`
			`- "Woody ad snippets"`
Enhancement: cves/2019/CVE-2019-15858.yaml by mp 2022-06-14 15:10:31 +00:00
Update CVE-2019-15858.yaml 2022-06-20 17:29:35 +00:00			`- type: status`
			`status:`
			`- 200`