Threats

CVEs published in the last 120 days, plus everything on CISA’s known-exploited list. Scores, exploit likelihood and exploitation status in one place.

74,070 CVEs · 1,790 known exploited · CVE data updated 36 min ago · EPSS 3 hours ago

74,070 results · page 13 of 3704 EPSS = probability of exploitation in the next 30 days (FIRST)
Matching CVEs
Score CVE Affected EPSS Published
6.6 medium CVE-2026-131168 pretix A legacy code path allowed users to craft requests to a ticket shop that bypass some validation steps for the selected products. In consequence, this could lead to an attacker purchasing products that are in fact sold out. — 20 Nov 2026
8.9 high CVE-2026-131167 pretix pretix offloads certain processes to background tasks that are run by a different server to avoid HTTP workers being clogged with processes that take longer than a usual web request. The browser periodically polls the server to see if the task is already finished using a UUID-shaped task ID. Once the task is completed, pretix resumes to the next step of the operation based on the result of the task. The system does however not check if the result stems from the correct type of task. Therefore, an attacker can supply the UUID of a task of a different type and pretix will continue with the result from the wrong task. In most cases, this will just result in an error because the return types do not match up, but in some cases this can be abused to extract objects the attacker usually should not see. Specifically, a vector was discovered that allowed to abuse this for unauthorized access to other people's ticket purchases. The attacker can, however, not control which purchases they get access to. — 20 Nov 2026
6.0 medium CVE-2026-131166 pretix When configuring a device to use the security profile "pretixSCAN (kiosk mode, no order sync, no search)", the API search endpoint introduced in pretix 4.12 was not blocked correctly. This theoretically allows these devices to perform searches for orders even if that was not intended. If the device is in kiosk mode, the search button will still be hidden from users. — 20 Nov 2026
2.1 low CVE-2026-131165 pretix The fix for CVE-2026-127174 published in 2026.9.2 is incomplete: When expanding an export from "some events" to "all events", it is checked that the acting user is part of a team with permission to all events, but this check is not correctly bound to the organizer and could also be passed through permissions on a different organizer. — 20 Nov 2026
2.3 low CVE-2026-131164 pretix When a ticket holder opens the ticket page of a ticket that is an add-on (possible since 2026.9) the HTML content of the page contains the secret link to the parent product, creating a potential data leak. Under different specific conditions, when a ticket contains user-uploaded files in response to a question, the page can even contain the secret link to the entire order. — 20 Nov 2026
8.6 high CVE-2026-131163 pretix-adyen A stored XSS in pretix-adyen has been discovered where an attacker could configure his own ticket shop in a way that API calls are not made to Adyen, but an attacker-controlled server. Results of these API calls would then be embedded in a part of the shop without proper escaping, leading to full XSS including potential session takeover. — 20 Nov 2026
4.3 medium CVE-2026-129082 Omnisend Newsletters, Email Marketing, SMS and Popups by Omnisend Missing Authorization vulnerability in Omnisend Newsletters, Email Marketing, SMS and Popups by Omnisend omnisend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Newsletters, Email Marketing, SMS and Popups by Omnisend: from n/a through 1.9.1. — 20 Nov 2026
4.3 medium CVE-2026-127201 wpinsider-1 Simple Membership WP user Import The Simple Membership WP user Import plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.9.2 This is due to missing or incorrect nonce validation on the add function. This makes it possible for unauthenticated attackers to import arbitrary WordPress users into Simple Membership and modify their WordPress role via the plugin's membership-level-to-role mapping via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. — 20 Nov 2026
7.2 high CVE-2026-125094 Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization The Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.2.19 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the AMP plugin to be active in Transitional or Standard template mode, and comments must be open on the target post, which is the WordPress default. — 20 Nov 2026
5.4 medium CVE-2026-96295 Apache Texera Authenticated users can bypass normal controls on the reading and writing of workflow execution results. This allows any authenticated user to read or modify any other user's workflow execution results. This issue affects Apache Texera (incubating): from 1.1.0-incubating before 1.3.0-incubating. Users are recommended to upgrade to version 1.3.0-incubating, which fixes the issue. — 20 Nov 2026
4.8 medium CVE-2026-133667 flowintel flowintel contains multiple related flaws that allow an authenticated attacker to inject arbitrary HTML or script into pages viewed by other users. - Timeline rendering: the timeline library's autolinking feature rewrote already-sanitised case notes and imported MISP attribute values into generated HTML link elements. Crafted text containing quote characters could break out of the generated attribute context, altering the surrounding markup and enabling script execution in the victim's browser. - Search highlighting: the highlight injection logic used a regular expression to locate text between angle brackets and spliced <mark> elements into the resulting string. Because the pattern could match inside HTML attribute values, the rewrite could corrupt or inject content into attributes of already-sanitised markup, again leading to DOM-based cross-site scripting. - Content-Type confusion: three analyser selection endpoints returned session-stored JSON strings with a text/html content type. A browser receiving such a response will parse and render the body as HTML, so any HTML or script embedded in the stored value is executed in the victim's context. Preconditions: the attacker must be an authenticated user with the ability to create or import case content (notes, MISP attributes) containing specially crafted quote or angle-bracket sequences. The victim must subsequently open the affected case timeline, run a search, or request one of the selection endpoints. Impact: successful exploitation yields DOM-based cross-site scripting in the victim's browser session, potentially allowing disclosure of case data, session manipulation, or execution of arbitrary actions under the victim's identity. Affected versions: flowintel prior to 4.1.0. — 20 Nov 2026
7.1 high CVE-2026-133665 flowintel flowintel contains an information disclosure vulnerability that allows authenticated non-administrative users to access sensitive configuration data and logs intended for administrators only. The notification page and alert API responses exposed sensitive fields, including webhook URLs, signing secrets, IMAP credentials, and delivery logs, in the initial data or JSON responses. Although the user interface hid the configuration form from non-admin users, the underlying data remained accessible via the page source or API endpoints. This exposure included historical webhook URLs that may contain active bearer tokens. An attacker with a valid non-admin account could retrieve these credentials and logs, potentially leading to unauthorized access to notification services, impersonation of the application in webhook deliveries, or further lateral movement within the infrastructure. Affected versions: flowintel < 4.1.0 — 20 Nov 2026
8.6 high CVE-2026-133663 flowintel flowintel contains an Insecure Direct Object Reference (IDOR) vulnerability affecting multiple endpoints that manage child records of cases and tasks. An authenticated user with access to one case or task could read or modify records belonging to other cases by supplying identifiers of those records directly in the request. Affected operations include: - Reading task notes, subtasks, and URL tools by referencing their IDs without verifying they belong to the authorized task - Retrieving task assignees for a task belonging to a different case - Editing or deleting timeline events and timeline event links belonging to another case - Editing or removing case connectors belonging to another case - Invoking connector module operations (MISP, generic connectors, worker calls) by combining an authorized case with a connector link from a different case The root cause is that the application authorized the parent resource (case or task) in the URL but then fetched or operated on the child record independently without verifying the child's ownership relationship to the authorized parent. Security impact: an authenticated user can exfiltrate sensitive threat intelligence data from cases they do not have access to, and can modify or delete timeline entries, connector configurations, and other records in unauthorized cases, leading to data integrity loss and potential disruption of incident response workflows. Affected versions: flowintel prior to 4.1.0 — 20 Nov 2026
8.4 high CVE-2026-133662 flowintel flowintel contains multiple authorization bypass vulnerabilities in its Analyzer (MISP Modules) functionality, affecting both the web interface and the REST API. - Saving analyzer results to a case or task accepted caller-supplied case and task identifiers without verifying that the authenticated user is a member of the target case or holds the required restricted-task permissions. An authenticated user could write notes, create tasks, and attach MISP objects or attributes into another organization's case. - Stored analyzer results were retrievable by UUID by any authenticated user. Both the web endpoint and the API endpoint returned the full result payload without checking ownership, exposing another user's analysis output. - The save handler did not validate the structure of the request, did not reject conflicting destination selections, and did not halt processing when a task-note operation failed, allowing partial or unintended writes. Preconditions: the attacker must possess a valid authenticated session (or API token) in flowintel. No administrative role is required. Security impact: unauthorized cross-tenant data disclosure (analyzer results) and unauthorized cross-tenant data modification (notes, tasks, MISP objects/attributes in another organization's case). Affected versions: flowintel prior to 4.1.0. — 20 Nov 2026
5.3 medium CVE-2026-133661 flowintel FlowIntel contains multiple authorization and credential management vulnerabilities affecting connector instances, MISP helper tools, and case templates. - Connector instance metadata, connectivity checks, and case listings accepted instance IDs without verifying if the acting user had visibility or ownership rights, allowing unauthorized access to sensitive configuration and data. - Case template serialization and creation processes exposed connector instances attached to templates regardless of the user's permissions, potentially leaking credentials or instance details to users who should not have access. - Editing connector instances allowed changes to URLs or sharing scopes without requiring re-authentication of API keys, enabling the reuse of another user's credentials in a new context or the leakage of shared keys to unauthorized endpoints. - Outbound MISP connector keys were incorrectly accepted for authenticating incoming alerts, bypassing the intended separation between outbound integration credentials and inbound alert source authentication. These issues allow authenticated users to access unauthorized connector data, manipulate credential scopes, and potentially exploit credential confusion between different security contexts. Affected versions: < 4.1.0 — 20 Nov 2026
7.1 high CVE-2026-133660 flowintel FlowIntel contains an authorization bypass in its user directory and assignment endpoints that allows authenticated users to access data belonging to other organisations. When the LIMIT_USER_VIEW_TO_ORG setting is enabled to restrict directory visibility to the caller's organisation, several API endpoints (user lookup by ID, last name, Matrix ID, and role-based listings) did not consistently enforce the organisation boundary. An authenticated non-admin user could retrieve profiles of users in other organisations by supplying their identifiers. Additionally, OrgAdmin users could retrieve the task assignments of any user in the system, including tasks and case titles from private cases to which they had no access. The assignment endpoints did not verify that the requested user belonged to the caller's organisation or that the underlying cases were visible to the caller. Security impact: - Exposure of user identities (names, Matrix IDs, roles) across organisation boundaries - Disclosure of task assignments, case titles, and workflow details from private cases - Potential enumeration of other organisations' membership and case activity Affected versions: FlowIntel prior to 4.1.0 — 20 Nov 2026
8.6 high CVE-2026-133659 flowintel Flowintel contains multiple SSO identity and organisation trust boundary violations that collectively allow account takeover, privilege escalation, and unauthorized access to private case data. - Keycloak SSO accepted unverified email claims, and all SSO providers (Keycloak, Entra ID, SimpleSAML) could resolve a claimed email address to an existing account that was created via a different sign-in method, enabling cross-provider account collision and unauthorized access to another user's account and data. - Entra ID role mapping relied on group display names, which tenant members could duplicate by creating a group with the same name as a privileged group (e.g. FlowintelAdmin), resulting in unauthorized role escalation. - SSO provisioning reused organisations whose display names matched user-controlled profile names, granting the new SSO user access to that organisation's private cases without explicit administrator assignment. - Case sharing via the API resolved organisations by name using a first-match query, so ambiguous names could silently resolve to the wrong organisation. Preconditions: an attacker must have a valid SSO identity (Keycloak, Entra ID, or SimpleSAML) or be a member of the relevant Entra tenant. No local administrator access is required. Security impact: unauthorized access to private case data, privilege escalation to Editor or higher roles, and account takeover across authentication providers. Affected versions: Flowintel prior to 4.1.0. — 20 Nov 2026
6.3 medium CVE-2026-133658 flowintel Flowintel contains a privilege escalation vulnerability in its Matrix relay (bot) integration. When the relay forwarded API requests on behalf of a represented user, the authorization and permission checks evaluated the relay bot's elevated role while the request handlers acted as the lower-privileged represented user. This mismatch allowed users with restricted roles (e.g., Read Only) to perform write operations, directory lookups, calendar modifications, assignment changes, template creation, and import actions they were not authorized to perform. Additionally, relay authority was determined by matching editable user profile fields (name and email) rather than a protected, non-spoofable identifier. An ordinary user who modified their profile to match the expected bot name could be recognized as the trusted relay, enabling impersonation of the bot and potential access to its elevated privileges. Preconditions: - A valid Flowintel user account with a restricted role (e.g., Read Only) - Access to the Matrix relay integration or the ability to send API requests with the relay's API key and a MATRIX-ID header - For the impersonation vector: ability to edit one's own profile name fields Security impact: - Unauthorized write operations by users with read-only or otherwise restricted permissions - Potential impersonation of the trusted relay bot by ordinary users - Bypass of organization-level access controls and role-based restrictions - Unauthorized modification of cases, tasks, calendar events, templates, and user directory entries Affected versions: Flowintel prior to 4.1.0 — 20 Nov 2026
7.2 high CVE-2026-133652 flowintel Flowintel , contained a session management vulnerability in its browser authentication mechanism. The session identifier used a bare numeric user ID rather than a credential-bound token, resulting in several related weaknesses: - Remembered logins (remember-me cookies) remained valid after a user changed their password, allowing an attacker holding a previously issued cookie to retain access indefinitely. - Server-side session identifiers were not rotated upon login (local, SSO, or remembered), enabling session fixation. - Self-service email and password changes did not require verification of the current password, permitting an attacker with an active session to modify account credentials without knowledge of the existing password. - Administrator-initiated password resets did not revoke other browser sessions, invalidate remembered logins, or rotate the affected user's API key. An attacker who obtained a valid session or remember-me cookie (e.g., through XSS, network interception, or cookie theft) could maintain unauthorized access even after the legitimate user changed their password. Additionally, an attacker with any valid session could change the account's email address or password without knowing the current credentials, effectively taking over the account. Affected versions: Flowintel prior to 4.1.0. — 20 Nov 2026
6.1 medium CVE-2026-133651 flowintel FlowIntel contained a Cross-Site Request Forgery (CSRF) vulnerability affecting fourteen web routes that performed destructive or state-changing operations. The affected routes accepted HTTP GET requests in addition to (or instead of) POST, which bypassed the Flask-WTF CSRF token validation that is only enforced on non-GET requests. The vulnerable operations included: - Case deletion and case merging - Organisation removal from a case - Task deletion (case and template) - Case template and note template deletion - Connector, connector instance, and icon deletion - Custom tag deletion and status change - Taxonomy and galaxy status changes An attacker who could induce an authenticated user to follow a crafted link or load a page containing a cross-site navigation (e.g., an image tag or redirect) could trigger any of these destructive actions using the victim's session cookie, without the victim's explicit consent or awareness. No special privileges beyond a valid authenticated session with the appropriate role (editor or admin) were required on the victim's account. Security impact: unauthorized deletion or modification of cases, tasks, templates, connectors, icons, custom tags, taxonomies, and galaxies belonging to the victim or the organisation, resulting in loss of data integrity. Affected versions: FlowIntel prior to 4.1.0 — 20 Nov 2026