{"vulnerability": "CVE-2025-30218", "sightings": [{"uuid": "e1473bc3-4918-4f60-932d-667e98572c8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-30218", "type": "seen", "source": "https://t.me/cvedetector/21921", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-30218 - Next.js Cross-Origin Request Exposure\", \n  \"Content\": \"CVE ID : CVE-2025-30218 \nPublished : April 2, 2025, 10:15 p.m. | 20\u00a0minutes ago \nDescription : Next.js is a React framework for building full-stack web applications. To mitigate CVE-2025-29927, Next.js validated the x-middleware-subrequest-id which persisted across multiple incoming requests. However, this subrequest ID is sent to all requests, even if the destination is not the same host as the Next.js application. Initiating a fetch request to a third-party within Middleware will send the x-middleware-subrequest-id to that third party. This vulnerability is fixed in 12.3.6, 13.5.10, 14.2.26, and 15.2.4. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T01:01:29.000000Z"}, {"uuid": "9ecf7f68-adac-4006-b633-a6845e9e8b40", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-30218", "type": "seen", "source": "https://bsky.app/profile/feedbot.unronritaro.net/post/3lltyj64efo2d", "content": "", "creation_timestamp": "2025-04-02T18:14:04.701829Z"}, {"uuid": "365d7d2c-a39f-4e7b-a5f4-50755e581f4b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-30218", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114270672120502866", "content": "", "creation_timestamp": "2025-04-02T22:14:42.954633Z"}, {"uuid": "0f7ec2e4-1345-4717-9f5b-2fd94df1bac0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-30218", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114270672120502866", "content": "", "creation_timestamp": "2025-04-02T22:14:42.963084Z"}, {"uuid": "e65287cd-d110-4c2c-a453-3f9016f6f4f8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-30218", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lluikvzlgw2h", "content": "", "creation_timestamp": "2025-04-02T23:01:31.697097Z"}, {"uuid": "020a58e3-e5f8-444d-b263-c0fe4140b666", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-30218", "type": "seen", "source": "https://bsky.app/profile/azu.bsky.social/post/3llutwttpqh2u", "content": "", "creation_timestamp": "2025-04-03T02:24:54.084272Z"}, {"uuid": "4be1865c-37fe-420d-9588-6ebfb2418337", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2025-30218", "type": "seen", "source": "https://bsky.app/profile/rss.y-u-e.workers.dev/post/3llvjzhfedw2s", "content": "", "creation_timestamp": "2025-04-03T09:00:04.984194Z"}, {"uuid": "4f6eef14-9d59-4478-a4d1-b707b496f46b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-30218", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10140", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-30218\n\ud83d\udd25 CVSS Score: 1.7 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U)\n\ud83d\udd39 Description: Next.js is a React framework for building full-stack web applications. To mitigate CVE-2025-29927, Next.js validated the x-middleware-subrequest-id which persisted across multiple incoming requests. However, this subrequest ID is sent to all requests, even if the destination is not the same host as the Next.js application. Initiating a fetch request to a third-party within Middleware will send the x-middleware-subrequest-id to that third party. This vulnerability is fixed in 12.3.6, 13.5.10, 14.2.26, and 15.2.4.\n\ud83d\udccf Published: 2025-04-02T21:23:14.660Z\n\ud83d\udccf Modified: 2025-04-02T21:23:14.660Z\n\ud83d\udd17 References:\n1. https://github.com/vercel/next.js/security/advisories/GHSA-223j-4rm8-mrmf\n2. https://vercel.com/changelog/cve-2025-30218-5DREmEH765PoeAsrNNQj3O", "creation_timestamp": "2025-04-02T21:34:07.000000Z"}]}