{"vulnerability": "CVE-2026-2991", "sightings": [{"uuid": "195627c4-7bc4-40a8-a529-01d135a086f4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-2991", "type": "seen", "source": "https://bsky.app/profile/thehackerwire.bsky.social/post/3mhdz6jqerg2u", "content": "", "creation_timestamp": "2026-03-18T17:28:51.279937Z"}, {"uuid": "3b33da86-29be-4cc4-b516-204566ffb8b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-2991", "type": "published-proof-of-concept", "source": "Telegram/7Ka92ZktN6KhnkFfP_8rgWwSyfUtl8VaXBMYWOC8bY9QwTk", "content": "", "creation_timestamp": "2026-04-04T03:00:05.000000Z"}, {"uuid": "b4066ad2-e9e9-47ce-892d-d9b458ac4144", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-2991", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/78673", "content": "\ud83d\udea8 GitHub \u76d1\u63a7\u6d88\u606f\u63d0\u9192\n\n\ud83d\udea8 \u53d1\u73b0\u5173\u952e\u8bcd\uff1a #CVE-2026\n\n\ud83d\udce6 \u9879\u76ee\u540d\u79f0\uff1a CVE-2026-2991\n\ud83d\udc64 \u9879\u76ee\u4f5c\u8005\uff1a Jumpthereness578\n\ud83d\udee0 \u5f00\u53d1\u8bed\u8a00\uff1a PHP\n\u2b50 Star\u6570\u91cf\uff1a 0  |  \ud83c\udf74 Fork\u6570\u91cf\uff1a 0\n\ud83d\udcc5 \u66f4\u65b0\u65f6\u95f4\uff1a 2026-04-03 23:44:48\n\n\ud83d\udcdd \u9879\u76ee\u63cf\u8ff0\uff1a\nExplore a PoC for CVE-2026-2991, an auth bypass in KiviCare 4.1.2 and earlier via the patient social-login REST endpoint\n\n\ud83d\udd17 \u70b9\u51fb\u8bbf\u95ee\u9879\u76ee\u5730\u5740", "creation_timestamp": "2026-04-04T00:00:26.000000Z"}, {"uuid": "01b110c9-1e1b-484d-b812-b712077a1cbf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-2991", "type": "seen", "source": "https://t.me/cve0day/344", "content": "CVE-2026-2991\n\nThe KiviCare \u2013 Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 4.1.2. This is due to the patientSocialLogin() function not verifying the social provider access token before authenticating a user. This makes it possible for unauthenticated attackers to log in as any patient registered on the system by providing only their email address and an arbitrary value for the access token, bypassing all credential verification. The attacker gains access to sensitive medical records, appointments, prescriptions, and billing information (PII/PHI breach). Additionally, authentication cookies are set before the role check, meaning the auth cookies for non-patient users (including administrators) are also set in the HTTP response headers, even though a 403 response is returned.\n\nGitHub Link:\nhttps://github.com/Jumpthereness578/CVE-2026-2991", "creation_timestamp": "2026-08-28T00:00:39.402633Z"}, {"uuid": "77fb1a3a-29e2-427d-b85f-a5704a8dbd1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-2991", "type": "seen", "source": "https://t.me/cve0day/344", "content": "CVE-2026-2991\n\nThe KiviCare \u2013 Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 4.1.2. This is due to the patientSocialLogin() function not verifying the social provider access token before authenticating a user. This makes it possible for unauthenticated attackers to log in as any patient registered on the system by providing only their email address and an arbitrary value for the access token, bypassing all credential verification. The attacker gains access to sensitive medical records, appointments, prescriptions, and billing information (PII/PHI breach). Additionally, authentication cookies are set before the role check, meaning the auth cookies for non-patient users (including administrators) are also set in the HTTP response headers, even though a 403 response is returned.\n\nGitHub Link:\nhttps://github.com/Jumpthereness578/CVE-2026-2991", "creation_timestamp": "2026-08-27T15:00:10.908174Z"}, {"uuid": "aec0de4d-6edb-4db1-85e3-25a9940da858", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-2991", "type": "published-proof-of-concept", "source": "https://t.me/cve0day/344", "content": "CVE-2026-2991\n\nThe KiviCare \u2013 Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 4.1.2. This is due to the patientSocialLogin() function not verifying the social provider access token before authenticating a user. This makes it possible for unauthenticated attackers to log in as any patient registered on the system by providing only their email address and an arbitrary value for the access token, bypassing all credential verification. The attacker gains access to sensitive medical records, appointments, prescriptions, and billing information (PII/PHI breach). Additionally, authentication cookies are set before the role check, meaning the auth cookies for non-patient users (including administrators) are also set in the HTTP response headers, even though a 403 response is returned.\n\nGitHub Link:\nhttps://github.com/Jumpthereness578/CVE-2026-2991", "creation_timestamp": "2026-08-29T00:00:31.604410Z"}]}