{"vulnerability": "CVE-2024-3931", "sightings": [{"uuid": "dba27774-3987-4b8d-9f76-614bf6cdd29f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-39317", "type": "seen", "source": "https://t.me/cvedetector/674", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-39317 - Wagtail is an open source content management syste\", \n  \"Content\": \"CVE ID : CVE-2024-39317 \nPublished : July 11, 2024, 4:15 p.m. | 39\u00a0minutes ago \nDescription : Wagtail is an open source content management system built on Django. A bug in Wagtail's `parse_query_string` would result in it taking a long time to process suitably crafted inputs. When used to parse sufficiently long strings of characters without a space, `parse_query_string` would take an unexpectedly large amount of time to process, resulting in a denial of service. In an initial Wagtail installation, the vulnerability can be exploited by any Wagtail admin user. It cannot be exploited by end users. If your Wagtail site has a custom search implementation which uses `parse_query_string`, it may be exploitable by other users (e.g. unauthenticated users). Patched versions have been released as Wagtail 5.2.6, 6.0.6 and 6.1.3. \nSeverity: 6.5 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"11 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-11T19:09:43.000000Z"}, {"uuid": "ad1a61be-a2f9-470b-90ac-95462849a029", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-39312", "type": "seen", "source": "Telegram/lB2tFuHZlESL5UYh_MvL0ZdCO9rG32bleGtwKzDfx5d-x5qR", "content": "", "creation_timestamp": "2025-03-06T02:16:32.000000Z"}, {"uuid": "2f2b4533-851a-454b-b168-446f111e2f24", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-39319", "type": "seen", "source": "https://t.me/cvedetector/6426", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-39319 - Aimeos ai-Controller Frontend Insecure Direct Object Reference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-39319 \nPublished : Sept. 26, 2024, 4:15 p.m. | 32\u00a0minutes ago \nDescription : aimeos/ai-controller-frontend is the Aimeos frontend controller package for e-commerce projects. Prior to versions 2024.4.2, 2023.10.9, 2022.10.8, 2021.10.8, and 2020.10.15, an insecure direct object reference allows an attacker to disable subscriptions and reviews of another customer. Versions 2024.4.2, 2023.10.9, 2022.10.8, 2021.10.8, and 2020.10.15 fix this issue. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-26T18:50:19.000000Z"}, {"uuid": "5d41fda5-ede6-43d6-a8cc-6099090e94c5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-39318", "type": "seen", "source": "https://t.me/cvedetector/2152", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-39318 - Ibexa XSS File Upload Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-39318 \nPublished : July 31, 2024, 4:15 p.m. | 42\u00a0minutes ago \nDescription : The Ibexa Admin UI Bundle contains all the necessary parts to run the Ibexa DXP Back Office interface. The file upload widget is vulnerable to XSS payloads in filenames. Access permission to upload files is required. As such, in most cases only authenticated editors and administrators will have the required permission. It is not persistent, i.e. the payload is only executed during the upload. In effect, an attacker will have to trick an editor/administrator into uploading a strangely named file. \nSeverity: 5.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"31 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-31T19:20:47.000000Z"}, {"uuid": "1f02b877-5b28-4a13-88ad-3eff2fa639ba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-3931", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/17828", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-3931\n\ud83d\udd25 CVSS Score: 5.1 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P)\n\ud83d\udd39 Description: A vulnerability was found in Totara LMS up to 18.7. It has been rated as problematic. Affected by this issue is some unknown functionality of the file admin/roles/check.php of the component User Selector. The manipulation of the argument ID Number leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 13.46, 14.38, 15.33, 16.27, 17.21 and 18.8 is able to address this issue. It is recommended to upgrade the affected component.\n\ud83d\udccf Published: 2024-04-18T00:00:04.983Z\n\ud83d\udccf Modified: 2025-06-10T05:14:33.471Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.261368\n2. https://vuldb.com/?ctiid.261368\n3. https://totara.community/mod/forum/discuss.php?d=27644", "creation_timestamp": "2025-06-10T05:29:47.000000Z"}, {"uuid": "0efa401c-4f79-436f-a649-f681ef9841c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-39311", "type": "seen", "source": "https://t.me/cvedetector/21451", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-39311 - Publify Cross-Site Scripting (XSS) Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-39311 \nPublished : March 28, 2025, 3:15 p.m. | 1\u00a0hour, 17\u00a0minutes ago \nDescription : Publify is a self hosted Web publishing platform on Rails. Prior to version 10.0.1 of Publify, corresponding to versions prior to 10.0.2 of the `publify_core` rubygem, publisher on a `publify` application is able to perform a cross-site scripting (XSS) attack on an administrator using the redirect functionality. The exploitation of this XSS vulnerability requires the administrator to click a malicious link. An attack could attempt to hide their payload by using HTML, or other encodings, as to not make it obvious to an administrator that this is a malicious link. A publisher may attempt to use this vulnerability to escalate their privileges and become an administrator. Version 10.0.1 of Publify and version 10.0.2 of the `publify_core` rubygem fix the issue. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-28T17:45:33.000000Z"}, {"uuid": "22985096-bfd0-4cf5-9127-bfbc3620210e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-39312", "type": "seen", "source": "https://t.me/cvedetector/206", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-39312 - Botan is a C++ cryptography library. X.509 certifi\", \n  \"Content\": \"CVE ID : CVE-2024-39312 \nPublished : July 8, 2024, 5:15 p.m. | 34\u00a0minutes ago \nDescription : Botan is a C++ cryptography library. X.509 certificates can identify elliptic curves using either an object identifier or using explicit encoding of the parameters. A bug in the parsing of name constraint extensions in X.509 certificates meant that if the extension included both permitted subtrees and excluded subtrees, only the permitted subtree would be checked. If a certificate included a name which was permitted by the permitted subtree but also excluded by excluded subtree, it would be accepted. Fixed in versions 3.5.0 and 2.19.5. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-08T19:56:00.000000Z"}]}