{"vulnerability": "CVE-2025-3806", "sightings": [{"uuid": "c21b3cb8-321f-4a1c-ac17-1a59fd1d95b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38066", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18715", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38066\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndm cache: prevent BUG_ON by blocking retries on failed device resumes\n\nA cache device failing to resume due to mapping errors should not be\nretried, as the failure leaves a partially initialized policy object.\nRepeating the resume operation risks triggering BUG_ON when reloading\ncache mappings into the incomplete policy object.\n\nReproduce steps:\n\n1. create a cache metadata consisting of 512 or more cache blocks,\n   with some mappings stored in the first array block of the mapping\n   array. Here we use cache_restore v1.0 to build the metadata.\n\ncat <> cmeta.xml\n\n  \n    \n  \n\nEOF\ndmsetup create cmeta --table \"0 8192 linear /dev/sdc 0\"\ncache_restore -i cmeta.xml -o /dev/mapper/cmeta --metadata-version=2\ndmsetup remove cmeta\n\n2. wipe the second array block of the mapping array to simulate\n   data degradations.\n\nmapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \\\n2>/dev/null | hexdump -e '1/8 \"%u\\n\"')\nablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \\\n2>/dev/null | hexdump -e '1/8 \"%u\\n\"')\ndd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock\n\n3. try bringing up the cache device. The resume is expected to fail\n   due to the broken array block.\n\ndmsetup create cmeta --table \"0 8192 linear /dev/sdc 0\"\ndmsetup create cdata --table \"0 65536 linear /dev/sdc 8192\"\ndmsetup create corig --table \"0 524288 linear /dev/sdc 262144\"\ndmsetup create cache --notable\ndmsetup load cache --table \"0 524288 cache /dev/mapper/cmeta \\\n/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\"\ndmsetup resume cache\n\n4. try resuming the cache again. An unexpected BUG_ON is triggered\n   while loading cache mappings.\n\ndmsetup resume cache\n\nKernel logs:\n\n(snip)\n------------[ cut here ]------------\nkernel BUG at drivers/md/dm-cache-policy-smq.c:752!\nOops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nCPU: 0 UID: 0 PID: 332 Comm: dmsetup Not tainted 6.13.4 #3\nRIP: 0010:smq_load_mapping+0x3e5/0x570\n\nFix by disallowing resume operations for devices that failed the\ninitial attempt.\n\ud83d\udccf Published: 2025-06-18T09:33:44.877Z\n\ud83d\udccf Modified: 2025-06-18T09:33:44.877Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/c614584c2a66b538f469089ac089457a34590c14\n2. https://git.kernel.org/stable/c/c5356a5e80442131e2714d0d26bb110590e4e568\n3. https://git.kernel.org/stable/c/025c8f477625eb39006ded650e7d027bcfb20e79\n4. https://git.kernel.org/stable/c/00586b78eeb7c626a14ca13453a1631f88a7cf36\n5. https://git.kernel.org/stable/c/3986ef4a9b6a0d9c28bc325d8713beba5e67586f\n6. https://git.kernel.org/stable/c/cc80a5cc520939d0a7d071cc4ae4b3c55ef171d0\n7. https://git.kernel.org/stable/c/f3128e3074e8af565cc6a66fe3384a56df87f803\n8. https://git.kernel.org/stable/c/5da692e2262b8f81993baa9592f57d12c2703dea", "creation_timestamp": "2025-06-18T10:40:17.000000Z"}, {"uuid": "29fdf752-1f50-473e-bd2c-3f1b58cb698f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38064", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18717", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38064\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nvirtio: break and reset virtio devices on device_shutdown()\n\nHongyu reported a hang on kexec in a VM. QEMU reported invalid memory\naccesses during the hang.\n\n Invalid read at addr 0x102877002, size 2, region '(null)', reason: rejected\n Invalid write at addr 0x102877A44, size 2, region '(null)', reason: rejected\n ...\n\nIt was traced down to virtio-console. Kexec works fine if virtio-console\nis not in use.\n\nThe issue is that virtio-console continues to write to the MMIO even after\nunderlying virtio-pci device is reset.\n\nAdditionally, Eric noticed that IOMMUs are reset before devices, if\ndevices are not reset on shutdown they continue to poke at guest memory\nand get errors from the IOMMU. Some devices get wedged then.\n\nThe problem can be solved by breaking all virtio devices on virtio\nbus shutdown, then resetting them.\n\ud83d\udccf Published: 2025-06-18T09:33:42.931Z\n\ud83d\udccf Modified: 2025-06-18T09:33:42.931Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/aee42f3d57bfa37b2716df4584edeecf63b9df4c\n2. https://git.kernel.org/stable/c/8bd2fa086a04886798b505f28db4002525895203", "creation_timestamp": "2025-06-18T10:40:19.000000Z"}, {"uuid": "20d5d000-b84a-4647-9103-4ea3b8cea4b3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38065", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18716", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38065\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\norangefs: Do not truncate file size\n\n'len' is used to store the result of i_size_read(), so making 'len'\na size_t results in truncation to 4GiB on 32-bit systems.\n\ud83d\udccf Published: 2025-06-18T09:33:44.048Z\n\ud83d\udccf Modified: 2025-06-18T09:33:44.048Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ceaf195ed285b77791e29016ee6344b3ded609b3\n2. https://git.kernel.org/stable/c/341e3a5984cf5761f3dab16029d7e9fb1641d5ff\n3. https://git.kernel.org/stable/c/5111227d7f1f57f6804666b3abf780a23f44fc1d\n4. https://git.kernel.org/stable/c/15602508ad2f923e228b9521960b4addcd27d9c4\n5. https://git.kernel.org/stable/c/121f0335d91e46369bf55b5da4167d82b099a166\n6. https://git.kernel.org/stable/c/cd918ec24168fe08c6aafc077dd3b6d88364c5cf\n7. https://git.kernel.org/stable/c/2323b806221e6268a4e17711bc72e2fc87c191a3\n8. https://git.kernel.org/stable/c/062e8093592fb866b8e016641a8b27feb6ac509d", "creation_timestamp": "2025-06-18T10:40:18.000000Z"}, {"uuid": "3ce42c9f-6c3b-4d32-9991-3c72ce52f0de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38067", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/18714", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38067\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nrseq: Fix segfault on registration when rseq_cs is non-zero\n\nThe rseq_cs field is documented as being set to 0 by user-space prior to\nregistration, however this is not currently enforced by the kernel. This\ncan result in a segfault on return to user-space if the value stored in\nthe rseq_cs field doesn't point to a valid struct rseq_cs.\n\nThe correct solution to this would be to fail the rseq registration when\nthe rseq_cs field is non-zero. However, some older versions of glibc\nwill reuse the rseq area of previous threads without clearing the\nrseq_cs field and will also terminate the process if the rseq\nregistration fails in a secondary thread. This wasn't caught in testing\nbecause in this case the leftover rseq_cs does point to a valid struct\nrseq_cs.\n\nWhat we can do is clear the rseq_cs field on registration when it's\nnon-zero which will prevent segfaults on registration and won't break\nthe glibc versions that reuse rseq areas on thread creation.\n\ud83d\udccf Published: 2025-06-18T09:33:45.518Z\n\ud83d\udccf Modified: 2025-06-18T09:33:45.518Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/2df285dab00fa03a3ef939b6cb0d0d0aeb0791db\n2. https://git.kernel.org/stable/c/fd881d0a085fc54354414aed990ccf05f282ba53", "creation_timestamp": "2025-06-18T10:40:17.000000Z"}, {"uuid": "4b0e4674-7e3a-40cb-a4a4-e80682ac3336", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38068", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18713", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38068\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: lzo - Fix compression buffer overrun\n\nUnlike the decompression code, the compression code in LZO never\nchecked for output overruns.  It instead assumes that the caller\nalways provides enough buffer space, disregarding the buffer length\nprovided by the caller.\n\nAdd a safe compression interface that checks for the end of buffer\nbefore each write.  Use the safe interface in crypto/lzo.\n\ud83d\udccf Published: 2025-06-18T09:33:46.125Z\n\ud83d\udccf Modified: 2025-06-18T09:33:46.125Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4b173bb2c4665c23f8fcf5241c7b06dfa6b5b111\n2. https://git.kernel.org/stable/c/a98bd864e16f91c70b2469adf013d713d04d1d13\n3. https://git.kernel.org/stable/c/0acdc4d6e679ba31d01e3e7e2e4124b76d6d8e2a\n4. https://git.kernel.org/stable/c/7caad075acb634a74911830d6386c50ea12566cd\n5. https://git.kernel.org/stable/c/167373d77c70c2b558aae3e327b115249bb2652c\n6. https://git.kernel.org/stable/c/cc47f07234f72cbd8e2c973cdbf2a6730660a463", "creation_timestamp": "2025-06-18T10:40:16.000000Z"}, {"uuid": "c063478d-5af5-4e38-ab47-42d129f70d88", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38069", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18712", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38069\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nPCI: endpoint: pci-epf-test: Fix double free that causes kernel to oops\n\nFix a kernel oops found while testing the stm32_pcie Endpoint driver\nwith handling of PERST# deassertion:\n\nDuring EP initialization, pci_epf_test_alloc_space() allocates all BARs,\nwhich are further freed if epc_set_bar() fails (for instance, due to no\nfree inbound window).\n\nHowever, when pci_epc_set_bar() fails, the error path:\n\n  pci_epc_set_bar() ->\n    pci_epf_free_space()\n\ndoes not clear the previous assignment to epf_test->reg[bar].\n\nThen, if the host reboots, the PERST# deassertion restarts the BAR\nallocation sequence with the same allocation failure (no free inbound\nwindow), creating a double free situation since epf_test->reg[bar] was\ndeallocated and is still non-NULL.\n\nThus, make sure that pci_epf_alloc_space() and pci_epf_free_space()\ninvocations are symmetric, and as such, set epf_test->reg[bar] to NULL\nwhen memory is freed.\n\n[kwilczynski: commit log]\n\ud83d\udccf Published: 2025-06-18T09:33:46.711Z\n\ud83d\udccf Modified: 2025-06-18T09:33:46.711Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/fe2329eff5bee461ebcafadb6ca1df0cbf5945fd\n2. https://git.kernel.org/stable/c/8b83893d1f6c6061a7d58169ecdf9d5ee9f306ee\n3. https://git.kernel.org/stable/c/934e9d137d937706004c325fa1474f9e3f1ba10a", "creation_timestamp": "2025-06-18T10:40:11.000000Z"}, {"uuid": "c52e7f19-f64f-4f1a-817a-7fab96a0aa3d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38068", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lruwpn5s252m", "content": "", "creation_timestamp": "2025-06-18T11:45:43.094026Z"}, {"uuid": "3f7d7ab1-4fdc-4cf5-9d77-9bf1277a63bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38065", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lruys2yfny25", "content": "", "creation_timestamp": "2025-06-18T12:22:52.281061Z"}, {"uuid": "cce69107-d234-4377-a987-8fc9c5e4c751", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3806", "type": "seen", "source": "https://t.me/cvedetector/23390", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-3806 - Dazhouda Lcms Cross Site Scripting Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-3806 \nPublished : April 19, 2025, 5:15 p.m. | 1\u00a0hour, 45\u00a0minutes ago \nDescription : A vulnerability, which was classified as problematic, has been found in dazhouda lecms up to 3.0.3. Affected by this issue is some unknown functionality of the file /admin of the component Edit Profile Handler. The manipulation leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. \nSeverity: 2.4 | LOW \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-19T21:50:03.000000Z"}, {"uuid": "43dc02c4-19ad-4644-a00a-7c92b8fc77d1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38066", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lruvqhsao32k", "content": "", "creation_timestamp": "2025-06-18T11:28:17.701811Z"}, {"uuid": "682b32c2-4f19-4b06-ad75-7d26e5def8f5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38069", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lruxgljwwi2m", "content": "", "creation_timestamp": "2025-06-18T11:58:33.380197Z"}, {"uuid": "384770be-ff3d-468f-bff8-61351c85c2ba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3806", "type": "seen", "source": "MISP/abd2a650-703d-4a2f-9f73-3051c1672e27", "content": "", "creation_timestamp": "2025-08-09T13:26:56.000000Z"}, {"uuid": "0a756aba-db5b-41b6-bf46-debbddfd0976", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38060", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "7e1bb5c4-00a6-4b2a-80a6-8539e2ca1e44", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38062", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "6ba9c390-fa93-4354-a84f-c75f5cd16ddb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38063", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "fbe74de2-9013-4335-8ef6-d8c53da861e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38064", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "87a07d10-911e-44f0-8196-d5e02cab5f76", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38069", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "796c9775-325d-4e48-8bf2-8a7f854d4f66", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38067", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "6eecfa01-aa6f-4faf-a26e-aa6b3f9e6d13", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38062", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "5cc2fc72-23ec-4298-b09b-1fc804438be3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38069", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "96444304-3c53-4efc-b509-889224e4de0d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38067", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lruz2zh3uc23", "content": "", "creation_timestamp": "2025-06-18T12:27:52.649050Z"}, {"uuid": "23cb08fb-5b23-4366-ab4f-637bda11646d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3806", "type": "seen", "source": "MISP/abd2a650-703d-4a2f-9f73-3051c1672e27", "content": "", "creation_timestamp": "2025-08-11T18:47:38.000000Z"}, {"uuid": "6c256597-19e3-47d5-aa63-a0188d057a00", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38068", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "077d7142-4346-4196-8745-a9d404056363", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38063", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "a4915d03-0c86-4720-a35f-5cff69b4f92b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38064", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "159fa6a2-0700-4af5-83c6-5fb95d24e940", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3806", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12587", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3806\n\ud83d\udd25 CVSS Score: 4.8 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability, which was classified as problematic, has been found in dazhouda lecms up to 3.0.3. Affected by this issue is some unknown functionality of the file /admin of the component Edit Profile Handler. The manipulation leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-19T16:31:04.599Z\n\ud83d\udccf Modified: 2025-04-19T16:31:04.599Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305660\n2. https://vuldb.com/?ctiid.305660\n3. https://vuldb.com/?submit.554977\n4. https://github.com/dtwin88/cve-md/blob/main/lecms%20V3.0.3/lecms.md", "creation_timestamp": "2025-04-19T17:02:26.000000Z"}]}