https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Mon, 04 May 2026 23:30:10 +0000 https://vulnerability.circl.lu/sighting/ff9999d1-787b-46f4-bddf-80a3533e8cc9/export {"uuid": "ff9999d1-787b-46f4-bddf-80a3533e8cc9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56140", "type": "seen", "source": "https://t.me/cvedetector/13252", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56140 - Astro Cross-Site Request Forgery Bypass Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-56140 \nPublished : Dec. 18, 2024, 9:15 p.m. | 35\u00a0minutes ago \nDescription : Astro is a web framework for content-driven websites. In affected versions a bug in Astro\u2019s CSRF-protection middleware allows requests to bypass CSRF checks. When the `security.checkOrigin` configuration option is set to `true`, Astro middleware will perform a CSRF check. However, a vulnerability exists that can bypass this security. A semicolon-delimited parameter is allowed after the type in `Content-Type`. Web browsers will treat a `Content-Type` such as `application/x-www-form-urlencoded; abc` as a `simple request` and will not perform preflight validation. In this case, CSRF is not blocked as expected. Additionally, the `Content-Type` header is not required for a request. This issue has been addressed in version 4.16.17 and all users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 5.9 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"18 Dec 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-18T22:54:11.000000Z"} {"uuid": "ff9999d1-787b-46f4-bddf-80a3533e8cc9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56140", "type": "seen", "source": "https://t.me/cvedetector/13252", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56140 - Astro Cross-Site Request Forgery Bypass Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-56140 \nPublished : Dec. 18, 2024, 9:15 p.m. | 35\u00a0minutes ago \nDescription : Astro is a web framework for content-driven websites. In affected versions a bug in Astro\u2019s CSRF-protection middleware allows requests to bypass CSRF checks. When the `security.checkOrigin` configuration option is set to `true`, Astro middleware will perform a CSRF check. However, a vulnerability exists that can bypass this security. A semicolon-delimited parameter is allowed after the type in `Content-Type`. Web browsers will treat a `Content-Type` such as `application/x-www-form-urlencoded; abc` as a `simple request` and will not perform preflight validation. In this case, CSRF is not blocked as expected. Additionally, the `Content-Type` header is not required for a request. This issue has been addressed in version 4.16.17 and all users are advised to upgrade. There are no known workarounds for this vulnerability. \nSeverity: 5.9 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"18 Dec 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-18T22:54:11.000000Z"} https://vulnerability.circl.lu/sighting/ff9999d1-787b-46f4-bddf-80a3533e8cc9/export Wed, 18 Dec 2024 22:54:11 +0000