https://vulnerability.circl.lu/sightings/feed 2026-04-30T05:33:58.678292+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/0bf29fde-e606-44b2-b116-ebbc717e4b2b/export 2026-04-30T05:33:59.111436+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "0bf29fde-e606-44b2-b116-ebbc717e4b2b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21337", "type": "seen", "source": "https://t.me/cibsecurity/35808", "content": "\u203c CVE-2022-21337 \u203c\n\nVulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-01-19T14:32:02.000000Z"} 2022-01-19T14:32:02+00:00 https://vulnerability.circl.lu/sighting/33579ae6-5505-4c6a-b5d5-ea97abd83f94/export 2026-04-30T05:33:59.111351+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "33579ae6-5505-4c6a-b5d5-ea97abd83f94", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21338", "type": "seen", "source": "https://t.me/cibsecurity/35809", "content": "\u203c CVE-2022-21338 \u203c\n\nVulnerability in the Oracle Communications Convergence product of Oracle Communications Applications (component: General Framework). The supported version that is affected is 3.0.2.2.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Communications Convergence. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Communications Convergence accessible data as well as unauthorized read access to a subset of Oracle Communications Convergence accessible data. CVSS 3.1 Base Score 4.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-01-19T14:32:04.000000Z"} 2022-01-19T14:32:04+00:00 https://vulnerability.circl.lu/sighting/ea5ce228-9cc4-4c94-8162-b94404a6dfd4/export 2026-04-30T05:33:59.111263+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "ea5ce228-9cc4-4c94-8162-b94404a6dfd4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21332", "type": "seen", "source": "https://t.me/cibsecurity/35834", "content": "\u203c CVE-2022-21332 \u203c\n\nVulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-01-19T14:38:56.000000Z"} 2022-01-19T14:38:56+00:00 https://vulnerability.circl.lu/sighting/d09c62a9-dc60-46f7-a9f3-214a7c94b720/export 2026-04-30T05:33:59.111173+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "d09c62a9-dc60-46f7-a9f3-214a7c94b720", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21331", "type": "seen", "source": "https://t.me/cibsecurity/35849", "content": "\u203c CVE-2022-21331 \u203c\n\nVulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-01-19T14:41:49.000000Z"} 2022-01-19T14:41:49+00:00 https://vulnerability.circl.lu/sighting/4f55ef25-84ea-4384-8c01-ee4502ac42e1/export 2026-04-30T05:33:59.111072+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "4f55ef25-84ea-4384-8c01-ee4502ac42e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-2133", "type": "seen", "source": "https://t.me/cibsecurity/46399", "content": "\u203c CVE-2022-2133 \u203c\n\nThe OAuth Single Sign On WordPress plugin before 6.22.6 doesn't validate that OAuth access token requests are legitimate, which allows attackers to log onto the site with the only knowledge of a user's email address.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-07-17T14:27:59.000000Z"} 2022-07-17T14:27:59+00:00 https://vulnerability.circl.lu/sighting/b17be4ce-0e5c-4060-b95e-75da177762d8/export 2026-04-30T05:33:59.110927+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "b17be4ce-0e5c-4060-b95e-75da177762d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21331", "type": "published-proof-of-concept", "source": "https://t.me/BABATATASASA/5994", "content": "| PRION:CVE-2022-21605 3.3 https://vulners.com/prion/PRION:CVE-2022-21605 | PRION:CVE-2022-21604 3.3 https://vulners.com/prion/PRION:CVE-2022-21604 | PRION:CVE-2022-21599 3.3 https://vulners.com/prion/PRION:CVE-2022-21599 | PRION:CVE-2022-21594 3.3 https://vulners.com/prion/PRION:CVE-2022-21594 | PRION:CVE-2021-2307 3.3 https://vulners.com/prion/PRION:CVE-2021-2307\n| PRION:CVE-2023-21875 3.2 https://vulners.com/prion/PRION:CVE-2023-21875\n| PRION:CVE-2022-39403 3.0 https://vulners.com/prion/PRION:CVE-2022-39403\n| PRION:CVE-2022-21486 2.9 https://vulners.com/prion/PRION:CVE-2022-21486\n| PRION:CVE-2022-21485 2.9 https://vulners.com/prion/PRION:CVE-2022-21485 | PRION:CVE-2022-21484 2.9 https://vulners.com/prion/PRION:CVE-2022-21484\n| PRION:CVE-2022-21357 2.9 https://vulners.com/prion/PRION:CVE-2022-21357\n| PRION:CVE-2022-21355 2.9 https://vulners.com/prion/PRION:CVE-2022-21355 | PRION:CVE-2022-21333 2.9 https://vulners.com/prion/PRION:CVE-2022-21333 | PRION:CVE-2022-21331 2.9 https://vulners.com/prion/PRION:CVE-2022-21331\n| PRION:CVE-2022-21325 2.9 https://vulners.com/prion/PRION:CVE-2022-21325\n| PRION:CVE-2022-21324 2.9 https://vulners.com/prion/PRION:CVE-2022-21324\n| PRION:CVE-2022-21323 2.9 https://vulners.com/prion/PRION:CVE-2022-21323\n| PRION:CVE-2022-21321 2.9 https://vulners.com/prion/PRION:CVE-2022-21321 | PRION:CVE-2022-21319 2.9 https://vulners.com/prion/PRION:CVE-2022-21319\n| PRION:CVE-2022-21317 2.9 https://vulners.com/prion/PRION:CVE-2022-21317\n| PRION:CVE-2022-21313 2.9 https://vulners.com/prion/PRION:CVE-2022-21313 | PRION:CVE-2022-21312 2.9 https://vulners.com/prion/PRION:CVE-2022-21312 | PRION:CVE-2022-21311 2.9 https://vulners.com/prion/PRION:CVE-2022-21311\n| PRION:CVE-2019-2797 2.3 https://vulners.com/prion/PRION:CVE-2019-2797\n| PRION:CVE-2022-39402 2.1 https://vulners.com/prion/PRION:CVE-2022-39402\n| PRION:CVE-2022-21460 2.1 https://vulners.com/prion/PRION:CVE-2022-21460\n| PRION:CVE-2022-21451 2.1 https://vulners.com/prion/PRION:CVE-2022-21451 | PRION:CVE-2022-21444 2.1 https://vulners.com/prion/PRION:CVE-2022-21444\n| PRION:CVE-2021-35632 2.1 https://vulners.com/prion/PRION:CVE-2021-35632\n| PRION:CVE-2021-2042 2.1 https://vulners.com/prion/PRION:CVE-2021-2042 | PRION:CVE-2019-2969 2.1 https://vulners.com/prion/PRION:CVE-2019-2969 | PRION:CVE-2021-2232 1.9 https://vulners.com/prion/PRION:CVE-2021-2232\n| PRION:CVE-2019-2634 1.9 https://vulners.com/prion/PRION:CVE-2019-2634\n| PRION:CVE-2019-2535 1.9 https://vulners.com/prion/PRION:CVE-2019-2535\n| PRION:CVE-2018-3174 1.9 https://vulners.com/prion/PRION:CVE-2018-3174\n| PRION:CVE-2018-3084 1.9 https://vulners.com/prion/PRION:CVE-2018-3084\n| PRION:CVE-2023-22058 1.7 https://vulners.com/prion/PRION:CVE-2023-22058\n| PRION:CVE-2022-21625 1.7 https://vulners.com/prion/PRION:CVE-2022-21625\n| PRION:CVE-2022-21595 1.7 https://vulners.com/prion/PRION:CVE-2022-21595 | PRION:CVE-2019-2536 1.2 https://vulners.com/prion/PRION:CVE-2019-2536\n| PRION:CVE-2019-2513 1.2 https://vulners.com/prion/PRION:CVE-2019-2513\n|_ PRION:CVE-2022-21611 0.8 https://vulners.com/prion/PRION:CVE-2022-21611 8443/tcp closed https-alt conn-refused 30000/tcp closed ndmps conn-refused 30718/tcp closed unknown conn-refused 30951/tcp closed unknown conn-refused", "creation_timestamp": "2023-11-15T17:01:59.000000Z"} 2023-11-15T17:01:59+00:00 https://vulnerability.circl.lu/sighting/1cfef240-ea1d-43d6-a35d-bccc9f19faf3/export 2026-04-30T05:33:59.108353+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "1cfef240-ea1d-43d6-a35d-bccc9f19faf3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21333", "type": "published-proof-of-concept", "source": "https://t.me/BABATATASASA/5994", "content": "| PRION:CVE-2022-21605 3.3 https://vulners.com/prion/PRION:CVE-2022-21605 | PRION:CVE-2022-21604 3.3 https://vulners.com/prion/PRION:CVE-2022-21604 | PRION:CVE-2022-21599 3.3 https://vulners.com/prion/PRION:CVE-2022-21599 | PRION:CVE-2022-21594 3.3 https://vulners.com/prion/PRION:CVE-2022-21594 | PRION:CVE-2021-2307 3.3 https://vulners.com/prion/PRION:CVE-2021-2307\n| PRION:CVE-2023-21875 3.2 https://vulners.com/prion/PRION:CVE-2023-21875\n| PRION:CVE-2022-39403 3.0 https://vulners.com/prion/PRION:CVE-2022-39403\n| PRION:CVE-2022-21486 2.9 https://vulners.com/prion/PRION:CVE-2022-21486\n| PRION:CVE-2022-21485 2.9 https://vulners.com/prion/PRION:CVE-2022-21485 | PRION:CVE-2022-21484 2.9 https://vulners.com/prion/PRION:CVE-2022-21484\n| PRION:CVE-2022-21357 2.9 https://vulners.com/prion/PRION:CVE-2022-21357\n| PRION:CVE-2022-21355 2.9 https://vulners.com/prion/PRION:CVE-2022-21355 | PRION:CVE-2022-21333 2.9 https://vulners.com/prion/PRION:CVE-2022-21333 | PRION:CVE-2022-21331 2.9 https://vulners.com/prion/PRION:CVE-2022-21331\n| PRION:CVE-2022-21325 2.9 https://vulners.com/prion/PRION:CVE-2022-21325\n| PRION:CVE-2022-21324 2.9 https://vulners.com/prion/PRION:CVE-2022-21324\n| PRION:CVE-2022-21323 2.9 https://vulners.com/prion/PRION:CVE-2022-21323\n| PRION:CVE-2022-21321 2.9 https://vulners.com/prion/PRION:CVE-2022-21321 | PRION:CVE-2022-21319 2.9 https://vulners.com/prion/PRION:CVE-2022-21319\n| PRION:CVE-2022-21317 2.9 https://vulners.com/prion/PRION:CVE-2022-21317\n| PRION:CVE-2022-21313 2.9 https://vulners.com/prion/PRION:CVE-2022-21313 | PRION:CVE-2022-21312 2.9 https://vulners.com/prion/PRION:CVE-2022-21312 | PRION:CVE-2022-21311 2.9 https://vulners.com/prion/PRION:CVE-2022-21311\n| PRION:CVE-2019-2797 2.3 https://vulners.com/prion/PRION:CVE-2019-2797\n| PRION:CVE-2022-39402 2.1 https://vulners.com/prion/PRION:CVE-2022-39402\n| PRION:CVE-2022-21460 2.1 https://vulners.com/prion/PRION:CVE-2022-21460\n| PRION:CVE-2022-21451 2.1 https://vulners.com/prion/PRION:CVE-2022-21451 | PRION:CVE-2022-21444 2.1 https://vulners.com/prion/PRION:CVE-2022-21444\n| PRION:CVE-2021-35632 2.1 https://vulners.com/prion/PRION:CVE-2021-35632\n| PRION:CVE-2021-2042 2.1 https://vulners.com/prion/PRION:CVE-2021-2042 | PRION:CVE-2019-2969 2.1 https://vulners.com/prion/PRION:CVE-2019-2969 | PRION:CVE-2021-2232 1.9 https://vulners.com/prion/PRION:CVE-2021-2232\n| PRION:CVE-2019-2634 1.9 https://vulners.com/prion/PRION:CVE-2019-2634\n| PRION:CVE-2019-2535 1.9 https://vulners.com/prion/PRION:CVE-2019-2535\n| PRION:CVE-2018-3174 1.9 https://vulners.com/prion/PRION:CVE-2018-3174\n| PRION:CVE-2018-3084 1.9 https://vulners.com/prion/PRION:CVE-2018-3084\n| PRION:CVE-2023-22058 1.7 https://vulners.com/prion/PRION:CVE-2023-22058\n| PRION:CVE-2022-21625 1.7 https://vulners.com/prion/PRION:CVE-2022-21625\n| PRION:CVE-2022-21595 1.7 https://vulners.com/prion/PRION:CVE-2022-21595 | PRION:CVE-2019-2536 1.2 https://vulners.com/prion/PRION:CVE-2019-2536\n| PRION:CVE-2019-2513 1.2 https://vulners.com/prion/PRION:CVE-2019-2513\n|_ PRION:CVE-2022-21611 0.8 https://vulners.com/prion/PRION:CVE-2022-21611 8443/tcp closed https-alt conn-refused 30000/tcp closed ndmps conn-refused 30718/tcp closed unknown conn-refused 30951/tcp closed unknown conn-refused", "creation_timestamp": "2023-11-15T17:01:59.000000Z"} 2023-11-15T17:01:59+00:00