Multiple critical security vulnerabilities have been identified and fixed in the nginx 1.24 module for Red Hat Enterprise Linux 8. These include use-after-free conditions in various components such as the HTTP/2 worker process, resolver, and mail proxy server, a flow control window overflow in HTTP/2, and a denial of service vulnerability via crafted TLS connections. The update addresses these issues to prevent potential exploitation.
Insertion of Sensitive Information Into Sent Data vulnerability in Nickboss WordPress File Upload wp-file-upload allows Retrieve Embedded Sensitive Data.This issue affects WordPress File Upload: from n/a through 5.2.4.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in weDevs Happy Addons for Elementor happy-elementor-addons allows Stored XSS.This issue affects Happy Addons for Elementor: from n/a through 3.51.3.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPKoi WordPress Themes WPKoi Templates for Elementor wpkoi-templates-for-elementor allows Stored XSS.This issue affects WPKoi Templates for Elementor: from n/a through 3.7.5.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LeapWorx Premium Addons for Elementor premium-addons-for-elementor allows Stored XSS.This issue affects Premium Addons for Elementor: from n/a through 4.11.119.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Brainstorm Force Spectra ultimate-addons-for-gutenberg allows Stored XSS.This issue affects Spectra: from n/a through 2.20.5.
Authorization bypass in the publication of XOneManager 3.8.3.0 updates. During testing, the server accepted initial requests from an authenticated project member with read-only access without verifying publication permissions. If the workflow is completed, updates with modified content could be distributed to managed devices.
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.
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
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
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.
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
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
Authorization omission in the 'admusers' operation of the POST request to '/xmanagercore/api/services/' in XOneManager 3.8.3.0. The API fails to verify the required role for querying the directory. An authenticated member of the project can obtain the list of platform accounts—including administrative accounts—along with details such as email addresses, roles, and associated companies.
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.