CVE-2026-131169 is a vulnerability where copying a scheduled export causes the export to run with the permissions of the original export's owner. This allows users to create exports containing data they normally cannot access, but only within events they already have permission to view.
A stored cross-site scripting (XSS) vulnerability exists in Brainstorm Force Spectra ultimate-addons-for-gutenberg versions up to 2.20.6. This vulnerability arises from improper neutralization of input during web page generation, allowing attackers with low privileges to inject malicious scripts that can be executed in the context of other users. The flaw impacts confidentiality, integrity, and availability of the affected system. The vulnerability has a CVSS 3.1 base score of 6.5, indicating a medium severity level.
A vulnerability in a payment integration with Stripe allowed improper validation of payment status responses. An attacker with knowledge of a valid charge ID could reuse a successful payment status from one payment to claim multiple tickets for different payments. The issue mainly affects payments created through Stripe's deprecated "source" API, which pretix stopped using in 2024.1 for most methods and completely by 2024.9.
A missing authorization vulnerability exists in weDevs Dokan dokan-lite up to version 5.3.4. This flaw allows exploitation of incorrectly configured access control security levels, potentially enabling unauthorized actions that impact integrity without affecting confidentiality or availability.
A Missing Authorization vulnerability exists in Magepeople inc.'s Taxi Booking Manager for WooCommerce plugin, affecting versions up to 2.2.10. This flaw allows exploitation of incorrectly configured access control security levels, potentially enabling unauthorized actions. The vulnerability has a medium severity rating with a CVSS score of 4.3.
A stored cross-site scripting (XSS) vulnerability exists in the Gutenberg Blocks by Kadence Blocks plugin up to version 3.9.1.1. This vulnerability allows improper neutralization of input during web page generation, potentially enabling attackers with low privileges to execute malicious scripts in the context of affected users. The vulnerability has a medium severity with a CVSS score of 6.5.
A legacy code path in a ticket shop application allowed attackers to craft requests that bypass validation steps for selected products. This flaw could enable attackers to purchase products that are actually sold out. The vulnerability has a high severity score of 8.7. No affected versions or patch information are provided.
A Missing Authorization vulnerability exists in Omnisend Newsletters, Email Marketing, SMS and Popups by Omnisend affecting versions up to 1.9.1. This flaw allows exploitation of incorrectly configured access control security levels, potentially enabling unauthorized actions. The vulnerability has a medium severity with a CVSS score of 4.3.
A stored cross-site scripting (XSS) vulnerability exists in pretix-adyen where an attacker can configure a ticket shop to redirect API calls to a malicious server. The responses from this server are embedded in the shop without proper escaping, enabling full XSS attacks including potential session hijacking.
A vulnerability exists in a ticketing system since version 2026.9 where the HTML content of a ticket page for add-on tickets exposes a secret link to the parent product, potentially leaking sensitive data. Additionally, under certain conditions involving user-uploaded files in ticket responses, the page may reveal a secret link to the entire order.
pretix uses background tasks identified by UUIDs to handle long-running processes separately from HTTP workers. A vulnerability exists where the system does not verify that the result corresponds to the correct task type, allowing an attacker to supply a UUID from a different task type. This can lead to unauthorized access to other users' ticket purchase information, although the attacker cannot control which purchases are accessed. Most attempts result in errors due to type mismatches. The vulnerability has a high severity score of 8.9.
A vulnerability exists in pretix when configuring a device with the security profile "pretixSCAN (kiosk mode, no order sync, no search)". The API search endpoint introduced in pretix 4.12 is not properly blocked, allowing devices to perform order searches despite the intended restrictions. However, in kiosk mode, the search button remains hidden from users, limiting direct user access to this functionality.
CVE-2026-131165 is a medium severity vulnerability involving an incomplete fix for a prior issue (CVE-2026-127174). The flaw occurs when expanding an export from "some events" to "all events". The system checks if the acting user belongs to a team with permission to all events, but this permission check is not properly bound to the specific organizer. As a result, permissions from a different organizer could incorrectly grant access.
The Optimole WordPress plugin (up to version 4.2.19) contains a stored cross-site scripting (XSS) vulnerability via the 'comment' parameter. This flaw allows unauthenticated attackers to inject malicious scripts that execute when users view the affected pages. Exploitation requires the AMP plugin to be active in Transitional or Standard template mode and that comments are open on the targeted post, which is the default WordPress setting.
FlowIntel prior to version 4.1.0 contains an authorization bypass vulnerability in its user directory and assignment API endpoints. This flaw allows authenticated users to access user profiles and task assignments belonging to other organizations, even when directory visibility is restricted. OrgAdmin users can also view task assignments and case titles from private cases outside their organization. The vulnerability leads to exposure of user identities, task details, and potential enumeration of other organizations' membership and case activity.
FlowIntel versions prior to 4.1.0 contain multiple authorization and credential management vulnerabilities. These flaws allow authenticated users to access connector instance metadata, case listings, and templates without proper permission checks, potentially exposing sensitive configuration and credentials. Editing connector instances can reuse API keys without re-authentication, risking credential leakage. Additionally, outbound MISP connector keys can be misused to authenticate incoming alerts, breaking intended credential separation.
flowintel prior to version 4.1.0 contains multiple related DOM-based cross-site scripting (XSS) vulnerabilities. These flaws allow an authenticated attacker with permissions to create or import case content to inject arbitrary HTML or script into pages viewed by other users. The vulnerabilities arise from improper sanitization and handling of user-supplied content in timeline rendering, search highlighting, and content-type handling in certain endpoints. Successful exploitation can lead to script execution in victims' browsers, potentially exposing case data or allowing unauthorized actions under the victim's identity.
flowintel versions prior to 4.1.0 have an information disclosure vulnerability that allows authenticated non-administrative users to access sensitive configuration data and logs intended only for administrators. Sensitive fields exposed include webhook URLs, signing secrets, IMAP credentials, and delivery logs. Although the UI hides these configurations from non-admin users, the data remains accessible via page source or API responses, including historical webhook URLs that may contain active bearer tokens. This could enable unauthorized access to notification services and potential lateral movement within the infrastructure.
Flowintel prior to version 4.1.0 contains multiple security flaws in its Single Sign-On (SSO) implementation that allow attackers with valid SSO identities to take over accounts, escalate privileges, and access private case data without authorization. These issues arise from unverified email claims in Keycloak, ambiguous role mapping in Entra ID, reuse of organization names matching user profile names, and ambiguous organization resolution in API case sharing. Exploitation requires only a valid SSO identity or membership in the relevant Entra tenant, with no local admin access needed.
flowintel prior to version 4.1.0 contains an Insecure Direct Object Reference (IDOR) vulnerability affecting multiple endpoints that manage child records of cases and tasks. Authenticated users with access to one case or task can read or modify records belonging to other cases by supplying identifiers of those records directly in requests. This leads to unauthorized data access and modification, impacting data confidentiality and integrity.