{"vulnerability": "CVE-2025-4144", "sightings": [{"uuid": "1f3aa2bf-a095-4575-9188-8c88b2d65fe5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-41444", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lr6odmolj52q", "content": "", "creation_timestamp": "2025-06-09T15:17:15.799809Z"}, {"uuid": "c814ad10-faeb-4728-9f15-3eb3d6605357", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-41442", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-191-08", "content": "", "creation_timestamp": "2025-07-10T10:00:00.000000Z"}, {"uuid": "4474bf64-51ae-413c-bb5c-baac72f48c73", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-41444", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114653436896870669", "content": "", "creation_timestamp": "2025-06-09T12:36:49.569695Z"}, {"uuid": "91dc9715-4e03-48c8-8aec-620f238d254c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-4144", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lo37f4ryof2e", "content": "", "creation_timestamp": "2025-05-01T01:56:07.881393Z"}, {"uuid": "99235e44-aa3a-4f85-9e79-2e368bb2c212", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-41441", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17531", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-41441\n\ud83d\udd25 CVSS Score: 3.7 (cvssV3_0, Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\ud83d\udd39 Description: Mailform Pro CGI prior to 4.3.4 generates error messages containing sensitive information, which may allow a remote unauthenticated attacker to obtain coupon codes. This vulnerability only affects products that use the coupon feature.\n\ud83d\udccf Published: 2025-05-26T06:27:12.284Z\n\ud83d\udccf Modified: 2025-05-26T06:27:12.284Z\n\ud83d\udd17 References:\n1. https://www.synck.com/blogs/news/newsroom/detail_1745302910.html\n2. https://jvn.jp/en/jp/JVN39546799/", "creation_timestamp": "2025-05-26T06:47:04.000000Z"}, {"uuid": "21f4bbe2-c622-4ecb-8983-c86d21ce1881", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-4144", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14209", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-4144\n\ud83d\udd25 CVSS Score: 5.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/U:Amber)\n\ud83d\udd39 Description: PKCE was implemented in the OAuth implementation in workers-oauth-provider that is part of  MCP framework https://github.com/cloudflare/workers-mcp . However, it\u00a0was found that an attacker could cause the check to be skipped.\n\n\nFixed in:\n\n \n\n https://github.com/cloudflare/workers-oauth-provider/pull/27 https://github.com/cloudflare/workers-oauth-provider/pull/27 \n\n\nImpact: \n\nPKCE is a defense-in-depth mechanism against certain kinds of attacks and was an optional extension in OAuth 2.0 which became required in the OAuth 2.1 draft. (Note that the MCP specification requires OAuth 2.1.).\u00a0This bug completely bypasses PKCE protection.\n\ud83d\udccf Published: 2025-05-01T00:50:27.543Z\n\ud83d\udccf Modified: 2025-05-01T00:50:27.543Z\n\ud83d\udd17 References:\n1. https://github.com/cloudflare/workers-oauth-provider/pull/27", "creation_timestamp": "2025-05-01T01:13:32.000000Z"}, {"uuid": "6ee3faeb-b947-4184-b9ac-e065f22adc04", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-41444", "type": "seen", "source": "Telegram/bTJ9s_6Dm5c98HBw_nHhlVxkUI4b7kIVaieHQvre00jyC9A", "content": "", "creation_timestamp": "2025-06-09T12:01:36.000000Z"}, {"uuid": "8831897a-5955-45f8-a716-64de6f224afe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-4144", "type": "seen", "source": "https://t.me/cvedetector/24175", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-4144 - Cloudflare Workers-Oauth-Provider PKCE Bypass\", \n  \"Content\": \"CVE ID : CVE-2025-4144 \nPublished : May 1, 2025, 1:15 a.m. | 52\u00a0minutes ago \nDescription : PKCE was implemented in the OAuth implementation in workers-oauth-provider that is part of  MCP framework  . However, it\u00a0was found that an attacker could cause the check to be skipped.  \n  \n  \nFixed in:  \n  \n   \n  \n     \n  \n  \nImpact:   \n  \nPKCE is a defense-in-depth mechanism against certain kinds of attacks and was an optional extension in OAuth 2.0 which became required in the OAuth 2.1 draft. (Note that the MCP specification requires OAuth 2.1.).\u00a0This bug completely bypasses PKCE protection. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T04:48:02.000000Z"}]}