Lucene search
+L

82 matches found

Kitploit
Kitploit
•added 2026/09/26 1:43 p.m.•18 views

CVE-2023-52268

FreeScout End-User Portal Authentication Bypass Exploit CVE-2023-52268 Overview This exploit targets a vulnerability in the FreeScout End-User Portal Module versions below 1.0.65 that allows an attacker to bypass authentication through improper session token management. By generating and testing...

9.1CVSS6.2AI score0.00617EPSS
SaveExploits1
Cvelist
Cvelist
•added 2026/08/01 6:00 a.m.•45 views

CVE-2026-14197 Fluent Support < 2.3.1 - Agent+ Arbitrary Ticket Customer Reassignment via IDOR

The Fluent Support WordPress plugin before 2.3.1 does not perform a per-ticket access check before reassigning a ticket's customer, allowing a restricted support agent to change the assigned customer of any ticket in the system, including tickets outside their granted scope...

0.00255EPSS
SaveExploits0References1
attackerkb
attackerkb
•added 2026/08/01 6:00 a.m.•20 views

CVE-2026-14197

The Fluent Support WordPress plugin before 2.3.1 does not perform a per-ticket access check before reassigning a ticket's customer, allowing a restricted support agent to change the assigned customer of any ticket in the system, including tickets outside their granted scope...

5.5AI score0.00255EPSS
SaveExploits0References1
CVE
CVE
•added 2026/08/01 6:00 a.m.•65 views

CVE-2026-14197

The Fluent Support WordPress plugin (versions before 2.3.1 ) is vulnerable to an Insecure Direct Object Reference (IDOR) flaw. The software fails to perform a per-ticket access check when reassigning a ticket's customer. This allows a restricted support agent to bypass authorization and modify th...

3.8CVSS5.5AI score0.00255EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/08/01 6:00 a.m.•26 views

EUVD-2026-51722

The Fluent Support WordPress plugin before 2.3.1 does not perform a per-ticket access check before reassigning a ticket's customer, allowing a restricted support agent to change the assigned customer of any ticket in the system, including tickets outside their granted scope...

5.5AI score0.00255EPSS
SaveExploits0References1
Positive Technologies
Positive Technologies
•added 2026/08/01 12:00 a.m.•24 views

PT-2026-67038

The Fluent Support WordPress plugin before 2.3.1 does not perform a per-ticket access check before reassigning a ticket's customer, allowing a restricted support agent to change the assigned customer of any ticket in the system, including tickets outside their granted scope...

5.5AI score0.00255EPSS
SaveExploits0References1
NVD
NVD
•added 2026/07/31 7:16 a.m.•21 views

CVE-2026-15209

The JS Help Desk WordPress plugin before 3.1.5 does not verify that the requesting user owns the ticket being loaded: a low-privileged authenticated user can supply another user's ticket ID and read that ticket's contents, including the reporter's PII and message body...

6.5CVSS0.0034EPSS
SaveExploits0References1
Positive Technologies
Positive Technologies
•added 2026/07/31 12:00 a.m.•20 views

PT-2026-66715

The JS Help Desk WordPress plugin before 3.1.5 does not verify that the requesting user owns the ticket being loaded: a low-privileged authenticated user can supply another user's ticket ID and read that ticket's contents, including the reporter's PII and message body...

5.5AI score0.0034EPSS
SaveExploits0References2
GithubExploit
GithubExploit
•added 2026/07/28 1:33 p.m.•98 views

Exploit for Use of Hard-coded Credentials in Solarwinds Web_Help_Desk

CVE-2024-28987 - SolarWinds Web Help Desk Hardcoded Credential...

9.1CVSS7.5AI score0.93299EPSS
SaveExploits6
NVD
NVD
•added 2026/07/28 11:17 a.m.•20 views

CVE-2026-18029

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS0.00331EPSS
SaveExploits0References1
CVE
CVE
•added 2026/07/28 10:39 a.m.•41 views

CVE-2026-18029

The CVE-2026-18029 entry is tied to the pretix-girosolution payment integration. Affected component: payment status validation in GiroCheckout flow. Root cause: insufficient validation of payment status responses, enabling an attacker to reuse a successful status for one payment with a different ...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
Vulnrichment
Vulnrichment
•added 2026/07/28 10:39 a.m.•19 views

CVE-2026-18029 Insufficient validation of payment status in pretix-girosolution

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
Positive Technologies
Positive Technologies
•added 2026/07/28 12:00 a.m.•24 views

PT-2026-65439

Our payment integration with GiroCheckout did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References2
Cvelist
Cvelist
•added 2026/07/10 8:31 p.m.•48 views

CVE-2026-13039 Eventin 4.0.26 - 4.1.15 - Missing Authorization to Unauthenticated Payment Bypass via REST API

The Eventin – Event Calendar, Event Registration, Tickets & Booking AI Powered plugin for WordPress is vulnerable to authorization bypass due to a regression in versions from 4.0.26 up to and including 4.1.15. This is due to the plugin not properly verifying that a user is authorized to perform a...

5.3CVSS0.00353EPSS
SaveExploits0References2
NVD
NVD
•added 2026/06/25 3:16 p.m.•33 views

CVE-2026-57536

Our payment integration with Mollie did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS0.00331EPSS
SaveExploits0References1
NVD
NVD
•added 2026/06/25 3:16 p.m.•25 views

CVE-2026-13222

Our payment integration with Oppwa-based payment methods did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one...

6.3CVSS0.00331EPSS
SaveExploits0References1
NVD
NVD
•added 2026/06/25 3:16 p.m.•21 views

CVE-2026-13223

Our payment integration with Computop-based payment methods did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one...

6.3CVSS0.00331EPSS
SaveExploits0References1
OSV
OSV
•added 2026/06/25 2:08 p.m.•15 views

CVE-2026-57536 Insufficient validation of payment status in pretix-mollie

Our payment integration with Mollie did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS6AI score
SaveExploits0References5
Cvelist
Cvelist
•added 2026/06/25 2:08 p.m.•50 views

CVE-2026-57536 Insufficient validation of payment status in pretix-mollie

Our payment integration with Mollie did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS0.00331EPSS
SaveExploits0References1
Vulnrichment
Vulnrichment
•added 2026/06/25 2:08 p.m.•16 views

CVE-2026-57536 Insufficient validation of payment status in pretix-mollie

Our payment integration with Mollie did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment...

6.3CVSS5.9AI score0.00331EPSS
SaveExploits0References1
Rows per page
Query Builder