CVE Vulnerability Catalog

In n8n before version 2.28.0, an improper authorization vulnerability allows authenticated users to assign workflows to folders in other projects. Attackers can bypass project and folder authorization boundaries by supplying crafted request payloads during workflow creation, causing logical integrity violations in target project folder structures.

Grav before version 2.0.0 (up to 2.0.0-rc.9 and the 2.0 branch) contains a stored CSS injection vulnerability in the Markdown image resize() media action. Prior media hardening rejects direct ?style= payloads and unsafe attribute() fallbacks, but the resize() action in Excerpts::processMediaActions() writes caller-controlled values directly into the image's styleAttributes. A lower-privileged content editor who can edit page Markdown can store a crafted image URL with semicolon-delimited CSS declarations in the resize parameters, which are rendered into the final <img style=...> attribute when a higher-privileged reviewer/admin views the page or preview.

The Grav API plugin (getgrav/grav-plugin-api) version 1.0.0 contains an unrestricted file upload vulnerability in the avatar upload endpoint (/api/v1/users/user/avatar). The endpoint validates only the client-declared MIME type (getClientMediaType) beginning with 'image/' and does not inspect the actual file content or restrict the resulting extension, allowing an authenticated user to store arbitrary content — including PHP code, SVG with embedded JavaScript, and polyglot payloads — under user/accounts/avatars/ with predictable filenames. Direct HTTP access to the stored files is blocked by .htaccess (returns 403), but the files persist on disk and could lead to remote code execution or stored XSS in the presence of a path traversal flaw or server misconfiguration. Fixed in 1.0.1.

An authorization bypass vulnerability in n8n before 2.25.7 and 2.26.x before 2.26.2 allows authenticated users with read-only access to a shared workflow to retry its executions via the Public API, using the workflow:read scope instead of workflow:execute.

A vulnerability in n8n before versions 1.123.55, 2.25.7, and 2.26.2 involves incorrect authorization in three mutating evaluation test-run endpoints. These endpoints use the workflow:read scope instead of the appropriate workflow:execute scope for state-changing actions.

A vulnerability in n8n before versions 1.123.18 and 2.6.2 fails to verify HMAC-SHA256 signatures on Zendesk webhooks in the ZendeskTrigger node. Attackers who know the webhook URL can send unsigned POST requests to trigger workflows with arbitrary malicious data.

A cross-site scripting vulnerability exists in n8n before version 2.8.0 within the credential management flow. Authenticated users can inject malicious JavaScript URLs into the OAuth2 credential Authorization URL field. Attackers can craft malicious credentials and trick victims into clicking the OAuth authorization button, executing arbitrary scripts in the victim's browser with their privileges.

The vulnerability in Capgo before version 12.128.2 fails to strip EXIF metadata from images uploaded via the app information endpoint, exposing sensitive geolocation data. Attackers can upload images containing EXIF metadata to extract geographic location information and other embedded metadata.

A vulnerability in Capgo before version 12.128.2 stems from an authorization flaw in the transfer_app() function that fails to update the deploy_history.owner_org field when transferring applications between organizations. Attackers can exploit this omission to retain unauthorized access to deployment history records in the source organization or cause the destination organization to lose access to transferred application deployment records.

An information disclosure vulnerability in Capgo before version 12.128.2 exists in the Supabase PostgREST RPC function public.get_total_metrics(org_id), which is callable by the anon role using only the public sb_publishable_* key. An unauthenticated attacker can probe organization existence and leak sensitive usage metrics including MAU, bandwidth, and install counts by sending POST requests to /rest/v1/rpc/get_total_metrics with valid organization UUIDs.

An HTML injection vulnerability in Capgo before version 12.128.2 in the organization settings endpoint allows attackers to inject malicious HTML content. By crafting payloads in the organization name field, they can redirect users to untrusted websites, enabling phishing attacks and reputational damage.

Flowise before version 3.1.0 contains a path traversal vulnerability in the Faiss and SimpleStore vector store implementations. Authenticated users can supply an unsanitized basePath parameter, allowing vector store data to be written to arbitrary filesystem locations.

An authorization bypass vulnerability in Capgo before version 12.128.2 allows read-only org members to insert OTA manifest rows via the public.manifest INSERT policy. Attackers with read-only access can inject malicious manifest entries with arbitrary s3_path values, which are served to devices through the unauthenticated /updates endpoint, enabling OTA metadata poisoning and potential malicious asset delivery.

A policy bypass vulnerability in Capgo before version 12.128.2 allows attackers with app-scoped API keys to downgrade encrypted bundles to non-encrypted state by clearing session_key and key_id fields in the app_versions table via PostgREST.

A command injection vulnerability was found in OpenLLM 0.6.30 in the async_run_command function of src/openllm/common.py. A local attacker can manipulate the cmd argument to execute arbitrary system commands. The exploit is public and the project has not responded to the report.

A cross-site request forgery (CSRF) vulnerability has been found in Flask-MonitoringDashboard up to version 5.0.2. An unknown functionality allows remote exploitation. The exploit is publicly disclosed and the project has not responded to the issue report.

A vulnerability has been found in check-peer-dependencies up to version 4.3.4, allowing OS command injection via the shelljs.exec function in dist/packageUtils.js within the peerDependencies component. The attack can be initiated remotely.

A stored cross-site scripting (XSS) vulnerability has been found in Webbeyaz Web Design Mediküm Web due to improper input neutralization during web page generation. The issue affects versions up to 08072026, and the vendor has discontinued support for the product.

A reflected cross-site scripting (XSS) vulnerability has been found in Webbeyaz Web Design Mediküm Web due to improper input neutralization during page generation. The issue affects versions up to 08072026, and the vendor has discontinued support for the product.

The Nexter Blocks plugin for WordPress up to version 4.7.4 is vulnerable to Stored Cross-Site Scripting via the 'commentIcon' parameter due to insufficient input sanitization and output escaping. Authenticated attackers with contributor-level access or higher can inject arbitrary scripts that execute when a user visits an affected page.