{"vulnerability": "CVE-2019-2513", "sightings": [{"uuid": "14fb8414-47d2-491c-984b-6f278b907a38", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-25137", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2581", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2019-25137\n\ud83d\udd39 Description: Umbraco CMS 4.11.8 through 7.15.10, and 7.12.4, allows Remote Code Execution by authenticated administrators via msxsl:script in an xsltSelection to developer/Xslt/xsltVisualize.aspx.\n\ud83d\udccf Published: 2023-05-18T00:00:00\n\ud83d\udccf Modified: 2025-01-22T16:43:41.293Z\n\ud83d\udd17 References:\n1. https://www.exploit-db.com/exploits/46153\n2. https://github.com/noraj/Umbraco-RCE\n3. https://0xdf.gitlab.io/2020/09/05/htb-remote.html\n4. https://github.com/Ickarah/CVE-2019-25137-Version-Research", "creation_timestamp": "2025-01-22T17:01:53.000000Z"}, {"uuid": "e4a8f111-4142-4bfd-83b2-49dd10d34aeb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-25137", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/37879", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01 \n\n\u66f4\u65b0\u4e86\uff1aRCE\n\u63cf\u8ff0\uff1aCVE-2019-25137 is an Umbraco RCE vulnerability, the script within this repo is slightly altered\nURL\uff1ahttps://github.com/dact91/CVE-2019-25137-RCE\n\n\u6807\u7b7e\uff1a#RCE", "creation_timestamp": "2025-05-23T19:51:37.000000Z"}, {"uuid": "3c3cac15-361b-4793-842f-914d36239256", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2019-2513", "type": "published-proof-of-concept", "source": "https://t.me/BABATATASASA/5994", "content": "|       PRION:CVE-2022-21605    3.3     https://vulners.com/prion/PRION:CVE-2022-21605              |       PRION:CVE-2022-21604    3.3     https://vulners.com/prion/PRION:CVE-2022-21604              |       PRION:CVE-2022-21599    3.3     https://vulners.com/prion/PRION:CVE-2022-21599              |       PRION:CVE-2022-21594    3.3     https://vulners.com/prion/PRION:CVE-2022-21594              |       PRION:CVE-2021-2307     3.3     https://vulners.com/prion/PRION:CVE-2021-2307\n|       PRION:CVE-2023-21875    3.2     https://vulners.com/prion/PRION:CVE-2023-21875\n|       PRION:CVE-2022-39403    3.0     https://vulners.com/prion/PRION:CVE-2022-39403\n|       PRION:CVE-2022-21486    2.9     https://vulners.com/prion/PRION:CVE-2022-21486\n|       PRION:CVE-2022-21485    2.9     https://vulners.com/prion/PRION:CVE-2022-21485              |       PRION:CVE-2022-21484    2.9     https://vulners.com/prion/PRION:CVE-2022-21484\n|       PRION:CVE-2022-21357    2.9     https://vulners.com/prion/PRION:CVE-2022-21357\n|       PRION:CVE-2022-21355    2.9     https://vulners.com/prion/PRION:CVE-2022-21355              |       PRION:CVE-2022-21333    2.9     https://vulners.com/prion/PRION:CVE-2022-21333              |       PRION:CVE-2022-21331    2.9     https://vulners.com/prion/PRION:CVE-2022-21331\n|       PRION:CVE-2022-21325    2.9     https://vulners.com/prion/PRION:CVE-2022-21325\n|       PRION:CVE-2022-21324    2.9     https://vulners.com/prion/PRION:CVE-2022-21324\n|       PRION:CVE-2022-21323    2.9     https://vulners.com/prion/PRION:CVE-2022-21323\n|       PRION:CVE-2022-21321    2.9     https://vulners.com/prion/PRION:CVE-2022-21321              |       PRION:CVE-2022-21319    2.9     https://vulners.com/prion/PRION:CVE-2022-21319\n|       PRION:CVE-2022-21317    2.9     https://vulners.com/prion/PRION:CVE-2022-21317\n|       PRION:CVE-2022-21313    2.9     https://vulners.com/prion/PRION:CVE-2022-21313              |       PRION:CVE-2022-21312    2.9     https://vulners.com/prion/PRION:CVE-2022-21312              |       PRION:CVE-2022-21311    2.9     https://vulners.com/prion/PRION:CVE-2022-21311\n|       PRION:CVE-2019-2797     2.3     https://vulners.com/prion/PRION:CVE-2019-2797\n|       PRION:CVE-2022-39402    2.1     https://vulners.com/prion/PRION:CVE-2022-39402\n|       PRION:CVE-2022-21460    2.1     https://vulners.com/prion/PRION:CVE-2022-21460\n|       PRION:CVE-2022-21451    2.1     https://vulners.com/prion/PRION:CVE-2022-21451              |       PRION:CVE-2022-21444    2.1     https://vulners.com/prion/PRION:CVE-2022-21444\n|       PRION:CVE-2021-35632    2.1     https://vulners.com/prion/PRION:CVE-2021-35632\n|       PRION:CVE-2021-2042     2.1     https://vulners.com/prion/PRION:CVE-2021-2042               |       PRION:CVE-2019-2969     2.1     https://vulners.com/prion/PRION:CVE-2019-2969               |       PRION:CVE-2021-2232     1.9     https://vulners.com/prion/PRION:CVE-2021-2232\n|       PRION:CVE-2019-2634     1.9     https://vulners.com/prion/PRION:CVE-2019-2634\n|       PRION:CVE-2019-2535     1.9     https://vulners.com/prion/PRION:CVE-2019-2535\n|       PRION:CVE-2018-3174     1.9     https://vulners.com/prion/PRION:CVE-2018-3174\n|       PRION:CVE-2018-3084     1.9     https://vulners.com/prion/PRION:CVE-2018-3084\n|       PRION:CVE-2023-22058    1.7     https://vulners.com/prion/PRION:CVE-2023-22058\n|       PRION:CVE-2022-21625    1.7     https://vulners.com/prion/PRION:CVE-2022-21625\n|       PRION:CVE-2022-21595    1.7     https://vulners.com/prion/PRION:CVE-2022-21595              |       PRION:CVE-2019-2536     1.2     https://vulners.com/prion/PRION:CVE-2019-2536\n|       PRION:CVE-2019-2513     1.2     https://vulners.com/prion/PRION:CVE-2019-2513\n|_      PRION:CVE-2022-21611    0.8     https://vulners.com/prion/PRION:CVE-2022-21611              8443/tcp  closed https-alt       conn-refused     30000/tcp closed ndmps           conn-refused     30718/tcp closed unknown         conn-refused     30951/tcp closed unknown         conn-refused", "creation_timestamp": "2023-11-15T17:01:59.000000Z"}]}