π¨ CVE-2025-71354
picklescan before 0.0.29 fails to detect malicious pickle files that exploit idlelib.debugobj.ObjectTreeItem.SetText function in reduce methods. Attackers can craft pickle files with embedded code that bypasses picklescan detection and executes arbitrary commands when pickle.load() is called.
π@cveNotify
picklescan before 0.0.29 fails to detect malicious pickle files that exploit idlelib.debugobj.ObjectTreeItem.SetText function in reduce methods. Attackers can craft pickle files with embedded code that bypasses picklescan detection and executes arbitrary commands when pickle.load() is called.
π@cveNotify
GitHub
Missing detection when calling built-in python idlelib.debugobj.ObjectTreeItem
### Summary
Using idlelib.debugobj.ObjectTreeItem.SetText, which is a built-in python library function to execute remote pickle file.
### Details
The attack payload executes in the followi...
Using idlelib.debugobj.ObjectTreeItem.SetText, which is a built-in python library function to execute remote pickle file.
### Details
The attack payload executes in the followi...
π¨ CVE-2025-71361
picklescan before 0.0.29 fails to detect malicious idlelib.calltip.Calltip.fetch_tip calls in pickle files, allowing remote code execution. Attackers can embed undetected payloads in pickle files that execute arbitrary code when loaded via pickle.load().
π@cveNotify
picklescan before 0.0.29 fails to detect malicious idlelib.calltip.Calltip.fetch_tip calls in pickle files, allowing remote code execution. Attackers can embed undetected payloads in pickle files that execute arbitrary code when loaded via pickle.load().
π@cveNotify
GitHub
Missing detection when calling built-in python idlelib.calltip.Calltip
### Summary
Using idlelib.calltip.Calltip.fetch_tip, which is a built-in python library function to execute remote pickle file.
### Details
The attack payload executes in the following ste...
Using idlelib.calltip.Calltip.fetch_tip, which is a built-in python library function to execute remote pickle file.
### Details
The attack payload executes in the following ste...
π¨ CVE-2026-12242
The AdRotate Banner Manager plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 5.17.7 via the 'banner' attribute of the adrotate shortcode. This is due to insufficient input validation and sanitization of the banner shortcode attribute before concatenation into a PHP code string wrapped in W3 Total Cache mfunc or Borlabs Cache fragment markers. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute arbitrary PHP code on the server. This vulnerability requires W3 Total Cache or Borlabs Cache support to be enabled in AdRotate settings.
π@cveNotify
The AdRotate Banner Manager plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 5.17.7 via the 'banner' attribute of the adrotate shortcode. This is due to insufficient input validation and sanitization of the banner shortcode attribute before concatenation into a PHP code string wrapped in W3 Total Cache mfunc or Borlabs Cache fragment markers. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute arbitrary PHP code on the server. This vulnerability requires W3 Total Cache or Borlabs Cache support to be enabled in AdRotate settings.
π@cveNotify
π¨ CVE-2026-13140
Stored Cross-Site Scripting in the exposed AWS API key store of Thinkst Applied Research Canarytokens.
Anonymous exploitation requires knowledge of a random identifier.
This issue affects Canarytokens: from Docker tag sha-4116b92cb before sha-f5aa5c4e, from Git commit 4116b92cb before f5aa5c4e.
π@cveNotify
Stored Cross-Site Scripting in the exposed AWS API key store of Thinkst Applied Research Canarytokens.
Anonymous exploitation requires knowledge of a random identifier.
This issue affects Canarytokens: from Docker tag sha-4116b92cb before sha-f5aa5c4e, from Git commit 4116b92cb before f5aa5c4e.
π@cveNotify
GitHub
Stored Cross-Site Scripting in Canarytokens
### Summary
Stored Cross-Site Scripting in the exposed AWS API key store of Thinkst Applied Research Canarytokens.
Anonymous exploitation requires knowledge of an unguessable identifier.
#...
Stored Cross-Site Scripting in the exposed AWS API key store of Thinkst Applied Research Canarytokens.
Anonymous exploitation requires knowledge of an unguessable identifier.
#...
π¨ CVE-2026-13163
Open redirect vulnerability (CWE-601) in the _safe_redirect function of the click-tracking endpoint (/c/<token>/) in Mailerup <1.0.0 on all platforms allows remote unauthenticated attackers to redirect victims to arbitrary external sites and conduct phishing attacks via a crafted u query parameter, because the URL scheme is validated (blocking javascript: and data:) but the destination host is not restricted to an allowlist, and a signing.BadSignature exception is silently caught so a valid signed token is not required.
π@cveNotify
Open redirect vulnerability (CWE-601) in the _safe_redirect function of the click-tracking endpoint (/c/<token>/) in Mailerup <1.0.0 on all platforms allows remote unauthenticated attackers to redirect victims to arbitrary external sites and conduct phishing attacks via a crafted u query parameter, because the URL scheme is validated (blocking javascript: and data:) but the destination host is not restricted to an allowlist, and a signing.BadSignature exception is silently caught so a valid signed token is not required.
π@cveNotify
GitHub
fix(seguridad): cerrar registro anΓ³nimo, fuga de API keys e inyecciones Β· Maalfer/mailerup@99eb6d4
Control de acceso:
- Eliminar RegisterView/RegisterSerializer y la ruta pΓΊblica /api/auth/register/.
Las cuentas solo las crea el admin (/api/auth/users/, IsAdminUser) o
createsuperuser. Cierra...
- Eliminar RegisterView/RegisterSerializer y la ruta pΓΊblica /api/auth/register/.
Las cuentas solo las crea el admin (/api/auth/users/, IsAdminUser) o
createsuperuser. Cierra...
π¨ CVE-2026-56223
Capgo before 12.128.2 contains a cross-domain SSO account takeover vulnerability in the provision-user endpoint that allows attackers to merge arbitrary victim accounts based on email match without validating SSO provider domain authorization. An attacker with enterprise org admin access and a malicious IdP can forge SAML assertions containing victim email addresses to trigger account merge and gain full access to victim accounts, organizations, and data.
π@cveNotify
Capgo before 12.128.2 contains a cross-domain SSO account takeover vulnerability in the provision-user endpoint that allows attackers to merge arbitrary victim accounts based on email match without validating SSO provider domain authorization. An attacker with enterprise org admin access and a malicious IdP can forge SAML assertions containing victim email addresses to trigger account merge and gain full access to victim accounts, organizations, and data.
π@cveNotify
GitHub
Cross-Domain SSO Email Assertion Allows Account Takeover via Identity Merge in provision-user
## Summary
The SSO user provisioning merge path in `provision-user.ts` transfers SSO identities and deletes duplicate accounts based solely on email address match without verifying that the auth...
The SSO user provisioning merge path in `provision-user.ts` transfers SSO identities and deletes duplicate accounts based solely on email address match without verifying that the auth...
π¨ CVE-2026-56231
Capgo before 12.128.2 contains a broken object level authorization (BOLA) vulnerability in the POST /build/start/:jobId and POST /build/cancel/:jobId endpoints. The handlers authorize the request based only on the attacker-controlled app_id supplied in the request body and never verify that the jobId in the URL belongs to that app_id (or the same tenant/org) before issuing privileged builder commands with the server-held builder API key. An authenticated user with the app.build_native permission for any app they control can start or cancel arbitrary builder jobs belonging to other tenants by supplying a victim jobId, resulting in cross-tenant build sabotage (denial of service), unauthorized compute actions, and potential billing impact.
π@cveNotify
Capgo before 12.128.2 contains a broken object level authorization (BOLA) vulnerability in the POST /build/start/:jobId and POST /build/cancel/:jobId endpoints. The handlers authorize the request based only on the attacker-controlled app_id supplied in the request body and never verify that the jobId in the URL belongs to that app_id (or the same tenant/org) before issuing privileged builder commands with the server-held builder API key. An authenticated user with the app.build_native permission for any app they control can start or cancel arbitrary builder jobs belonging to other tenants by supplying a victim jobId, resulting in cross-tenant build sabotage (denial of service), unauthorized compute actions, and potential billing impact.
π@cveNotify
GitHub
Cross-tenant build job control (cancel/start) via jobId parameter enables build sabotage (BOLA)
### Summary
An authenticated user who has app.build_native permission for any app they control can invoke start and cancel actions against an arbitrary builder job by providing a victim jobId in t...
An authenticated user who has app.build_native permission for any app they control can invoke start and cancel actions against an arbitrary builder job by providing a victim jobId in t...
π¨ CVE-2026-56232
Capgo before 12.128.2 fails to enforce limited_to_orgs and limited_to_apps constraints on subkeys provided via x-limited-key-id header in middlewareKey function. Attackers can bypass subkey scope restrictions by referencing their own subkeys, causing all downstream route handlers to use the unrestricted parent key instead of the scoped subkey.
π@cveNotify
Capgo before 12.128.2 fails to enforce limited_to_orgs and limited_to_apps constraints on subkeys provided via x-limited-key-id header in middlewareKey function. Attackers can bypass subkey scope restrictions by referencing their own subkeys, causing all downstream route handlers to use the unrestricted parent key instead of the scoped subkey.
π@cveNotify
GitHub
MiddlewareKey x-limited-key-id subkey scope bypass: limited_to_orgs and limited_to_apps constraints are completely ignored (+ missingβ¦
### Summary
`middlewareKey()` in `hono_middleware.ts` accepts `x-limited-key-id` subkeys but never enforces their `limited_to_orgs` or `limited_to_apps` scope constraints. The subkey is loaded a...
`middlewareKey()` in `hono_middleware.ts` accepts `x-limited-key-id` subkeys but never enforces their `limited_to_orgs` or `limited_to_apps` scope constraints. The subkey is loaded a...
π¨ CVE-2026-56244
Capgo before 12.128.2 allows non-admin API keys to read webhook signing secrets via Supabase REST due to insufficient row-level security policies on the webhooks table. Attackers can retrieve the webhook secret and forge valid X-Capgo-Signature headers to send authenticated webhook events to configured receivers, breaking webhook authenticity and integrity.
π@cveNotify
Capgo before 12.128.2 allows non-admin API keys to read webhook signing secrets via Supabase REST due to insufficient row-level security policies on the webhooks table. Attackers can retrieve the webhook secret and forge valid X-Capgo-Signature headers to send authenticated webhook events to configured receivers, breaking webhook authenticity and integrity.
π@cveNotify
GitHub
Non-admin API keys can read webhook signing secrets (webhooks.secret) via Supabase REST, enabling forged Capgo webhooks
### Summary
A read-only / non-admin Capgo API key can query Supabase REST (/rest/v1/webhooks) and retrieve the webhook signing secret (whsec_*). With this secret, an attacker can generate valid X-...
A read-only / non-admin Capgo API key can query Supabase REST (/rest/v1/webhooks) and retrieve the webhook signing secret (whsec_*). With this secret, an attacker can generate valid X-...
π¨ CVE-2026-56245
Supabase Capgo before 12.128.2 contains an authorization bypass vulnerability in the SECURITY DEFINER record_build_time RPC function that allows unauthenticated attackers to insert arbitrary build-time records. Attackers can exploit this by calling POST /rest/v1/rpc/record_build_time with a public API key to poison billing and quota data for any organization, enabling resource exhaustion and cross-tenant billing manipulation.
π@cveNotify
Supabase Capgo before 12.128.2 contains an authorization bypass vulnerability in the SECURITY DEFINER record_build_time RPC function that allows unauthenticated attackers to insert arbitrary build-time records. Attackers can exploit this by calling POST /rest/v1/rpc/record_build_time with a public API key to poison billing and quota data for any organization, enabling resource exhaustion and cross-tenant billing manipulation.
π@cveNotify
GitHub
Unauthenticated SECURITY DEFINER RPC record_build_time allows cross-tenant build-time accounting poisoning (billing/quota impact)
### Summary
An unauthenticated attacker using only the public Supabase sb_publishable_* key can call POST /rest/v1/rpc/record_build_time (granted to anon) to insert/update rows in public.build_log...
An unauthenticated attacker using only the public Supabase sb_publishable_* key can call POST /rest/v1/rpc/record_build_time (granted to anon) to insert/update rows in public.build_log...
π¨ CVE-2026-56256
Capgo before 12.128.2 enforces mandatory two-factor authentication only at the UI level. Sensitive Organization (ORG) management API endpoints (e.g., editing organization details, inviting users) do not validate 2FA completion on the backend. An authenticated Admin user who has not enabled 2FA can replay or modify a previously captured ORG API request to perform privileged organization actions, bypassing the globally enforced 2FA requirement.
π@cveNotify
Capgo before 12.128.2 enforces mandatory two-factor authentication only at the UI level. Sensitive Organization (ORG) management API endpoints (e.g., editing organization details, inviting users) do not validate 2FA completion on the backend. An authenticated Admin user who has not enabled 2FA can replay or modify a previously captured ORG API request to perform privileged organization actions, bypassing the globally enforced 2FA requirement.
π@cveNotify
GitHub
π‘οΈ Vulnerability Report: 2FA Enforcement Bypass β Admin Can Edit Organization & Invite Users Without Enabling 2FA
π‘οΈ Vulnerability Report: 2FA Enforcement Bypass β Admin Can Edit Organization & Invite Users Without Enabling 2FA
Reported by: Vikash Gupta
Severity: High
Category: Authentication Bypass /...
Reported by: Vikash Gupta
Severity: High
Category: Authentication Bypass /...
π¨ CVE-2026-56257
Capgo before 12.128.2 allows direct patching of public.apps.owner_org through PostgREST, bypassing the transfer_app() workflow and creating split-brain ownership. Attackers can directly update apps.owner_org while leaving app_versions.owner_org unchanged, enabling old-org keys to retain access to version data while new-org keys control the app record.
π@cveNotify
Capgo before 12.128.2 allows direct patching of public.apps.owner_org through PostgREST, bypassing the transfer_app() workflow and creating split-brain ownership. Attackers can directly update apps.owner_org while leaving app_versions.owner_org unchanged, enabling old-org keys to retain access to version data while new-org keys control the app record.
π@cveNotify
GitHub
Direct PostgREST update of public.apps.owner_org bypasses transfer_app() and leaves app_versions.owner_org with the previous organization
### Summary
A caller who can directly update `public.apps.owner_org` through PostgREST can bypass the intended `transfer_app()` workflow and create a split-brain ownership state for the same app...
A caller who can directly update `public.apps.owner_org` through PostgREST can bypass the intended `transfer_app()` workflow and create a split-brain ownership state for the same app...
π¨ CVE-2026-56262
Crawl4AI before 0.8.7 contains an authentication bypass vulnerability in the monitor router endpoints that allows unauthenticated attackers to access destructive operations. Remote attackers can invoke the /monitor/actions/cleanup endpoint and manipulate monitoring state without authentication, causing service disruption.
π@cveNotify
Crawl4AI before 0.8.7 contains an authentication bypass vulnerability in the monitor router endpoints that allows unauthenticated attackers to access destructive operations. Remote attackers can invoke the /monitor/actions/cleanup endpoint and manipulate monitoring state without authentication, causing service disruption.
π@cveNotify
GitHub
GitHub - unclecode/crawl4ai: ππ€ Crawl4AI: Open-source LLM Friendly Web Crawler & Scraper. Don't be shy, join here: https://disβ¦
ππ€ Crawl4AI: Open-source LLM Friendly Web Crawler & Scraper. Don't be shy, join here: https://discord.gg/jP8KfhDhyN - unclecode/crawl4ai
π¨ CVE-2026-56269
Flowise before 3.1.0 (npm package flowise, versions 3.0.13 and earlier) uses a weak hardcoded default value 'Secre$t' for the TOKEN_HASH_SECRET environment variable in packages/server/src/enterprise/utils/tempTokenUtils.ts when the variable is not configured. This secret derives the AES-256-CBC key used to encrypt user IDs and workspace IDs in the 'meta' field of JWT tokens. An attacker who knows the default secret can decrypt this metadata to extract internal user and workspace identifiers, and re-encrypt manipulated values such as altered user or workspace IDs. Because the JWT signature is validated separately, decrypting or tampering with this metadata does not by itself grant access, but the disclosure of internal identifiers and possible metadata manipulation could aid privilege escalation or unauthorized data access.
π@cveNotify
Flowise before 3.1.0 (npm package flowise, versions 3.0.13 and earlier) uses a weak hardcoded default value 'Secre$t' for the TOKEN_HASH_SECRET environment variable in packages/server/src/enterprise/utils/tempTokenUtils.ts when the variable is not configured. This secret derives the AES-256-CBC key used to encrypt user IDs and workspace IDs in the 'meta' field of JWT tokens. An attacker who knows the default secret can decrypt this metadata to extract internal user and workspace identifiers, and re-encrypt manipulated values such as altered user or workspace IDs. Because the JWT signature is validated separately, decrypting or tampering with this metadata does not by itself grant access, but the disclosure of internal identifiers and possible metadata manipulation could aid privilege escalation or unauthorized data access.
π@cveNotify
GitHub
Weak Default Token Hash Secret
**Detection Method:** Kolega.dev Deep Code Scan
| Attribute | Value |
|---|---|
| Severity | Critical |
| CWE | CWE-798 (Use of Hard-coded Credentials) |
| Location | packages/server/src/ent...
| Attribute | Value |
|---|---|
| Severity | Critical |
| CWE | CWE-798 (Use of Hard-coded Credentials) |
| Location | packages/server/src/ent...
π¨ CVE-2026-56270
Flowise before 3.1.0 (versions 3.0.13 and earlier) contains a missing authentication vulnerability in the /api/v1/loginmethod endpoint that allows unauthenticated users to retrieve an organization's complete SSO configuration, including OAuth client secrets in cleartext, by providing an organizationId parameter. Remote attackers can send a GET request to harvest sensitive API credentials for Google, Microsoft/Azure, GitHub, and Auth0 integrations. This affects FlowiseAI Cloud and self-hosted instances where the endpoint is exposed.
π@cveNotify
Flowise before 3.1.0 (versions 3.0.13 and earlier) contains a missing authentication vulnerability in the /api/v1/loginmethod endpoint that allows unauthenticated users to retrieve an organization's complete SSO configuration, including OAuth client secrets in cleartext, by providing an organizationId parameter. Remote attackers can send a GET request to harvest sensitive API credentials for Google, Microsoft/Azure, GitHub, and Auth0 integrations. This affects FlowiseAI Cloud and self-hosted instances where the endpoint is exposed.
π@cveNotify
GitHub
Unauthenticated Information Disclosure of OAuth Secrets (Cleartext) via GET Request
### Summary
I have discovered a critical Missing Authentication vulnerability on the /api/v1/loginmethod endpoint. The API allows unauthenticated users (guests) to retrieve the full SSO configurat...
I have discovered a critical Missing Authentication vulnerability on the /api/v1/loginmethod endpoint. The API allows unauthenticated users (guests) to retrieve the full SSO configurat...
π¨ CVE-2026-56272
Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 iterations instead of the OWASP-recommended minimum of 10 rounds. Attackers can crack password hashes approximately 30 times faster with modern GPU hardware, potentially compromising all user accounts in a database breach scenario.
π@cveNotify
Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 iterations instead of the OWASP-recommended minimum of 10 rounds. Attackers can crack password hashes approximately 30 times faster with modern GPU hardware, potentially compromising all user accounts in a database breach scenario.
π@cveNotify
GitHub
Insufficient Password Salt Rounds
**Detection Method:** Kolega.dev Deep Code Scan
| Attribute | Value |
|---|---|
| Severity | Medium |
| CWE | CWE-916 (Use of Password Hash With Insufficient Computational Effort) |
| Locati...
| Attribute | Value |
|---|---|
| Severity | Medium |
| CWE | CWE-916 (Use of Password Hash With Insufficient Computational Effort) |
| Locati...
π¨ CVE-2026-56302
Capgo before 12.128.2 contains an unsecured images bucket lacking any row level security controls, allowing unauthenticated attackers to read, insert, and delete stored app icons. Remote attackers can exploit this misconfiguration to delete all icons and leak sensitive app IDs and user IDs.
π@cveNotify
Capgo before 12.128.2 contains an unsecured images bucket lacking any row level security controls, allowing unauthenticated attackers to read, insert, and delete stored app icons. Remote attackers can exploit this misconfiguration to delete all icons and leak sensitive app IDs and user IDs.
π@cveNotify
GitHub
Unsecured supabase images bucket
### Summary
The `images` bucket is used to store app icons. Currently it is not secured with ANY RLS. This allows anyone to delete, insert, select from said bucket
### Details
Here is the expl...
The `images` bucket is used to store app icons. Currently it is not secured with ANY RLS. This allows anyone to delete, insert, select from said bucket
### Details
Here is the expl...
π¨ CVE-2026-56310
Cap-go before 12.128.2 contains an authorization bypass vulnerability in the GET /organization/members endpoint that allows org-limited API keys to bypass limited_to_orgs restrictions. Attackers with org-limited API keys can read membership data including uid, email, image_url, role, and is_tmp from organizations outside their assigned scope.
π@cveNotify
Cap-go before 12.128.2 contains an authorization bypass vulnerability in the GET /organization/members endpoint that allows org-limited API keys to bypass limited_to_orgs restrictions. Attackers with org-limited API keys can read membership data including uid, email, image_url, role, and is_tmp from organizations outside their assigned scope.
π@cveNotify
GitHub
Org-limited API keys can bypass limited_to_orgs and read other organizationsβ member data via GET /organization/members
### Summary
An API key explicitly restricted to a single organization via `limited_to_orgs` can still read membership data for a different organization through `GET /organization/members`.
Th...
An API key explicitly restricted to a single organization via `limited_to_orgs` can still read membership data for a different organization through `GET /organization/members`.
Th...
π¨ CVE-2026-56337
Capgo before 12.128.2 contains an information disclosure vulnerability in the public.exist_app_v2 RPC function that allows unauthenticated attackers to enumerate app_ids by calling POST /rest/v1/rpc/exist_app_v2 with arbitrary appid parameters. Remote attackers can exploit this SECURITY DEFINER function to determine whether specific app_ids exist in the public.apps table, enabling cross-tenant app enumeration and privacy violations.
π@cveNotify
Capgo before 12.128.2 contains an information disclosure vulnerability in the public.exist_app_v2 RPC function that allows unauthenticated attackers to enumerate app_ids by calling POST /rest/v1/rpc/exist_app_v2 with arbitrary appid parameters. Remote attackers can exploit this SECURITY DEFINER function to determine whether specific app_ids exist in the public.apps table, enabling cross-tenant app enumeration and privacy violations.
π@cveNotify
GitHub
Unauthenticated Supabase RPC exist_app_v2(appid) (SECURITY DEFINER) bypasses RLS and reveals whether an app_id exists
### Summary
An anon client can call POST /rest/v1/rpc/exist_app_v2 and learn whether an arbitrary app_id exists in public.apps, enabling cross-tenant app enumeration/existence oracle.
### Detai...
An anon client can call POST /rest/v1/rpc/exist_app_v2 and learn whether an arbitrary app_id exists in public.apps, enabling cross-tenant app enumeration/existence oracle.
### Detai...
π¨ CVE-2026-56338
Capgo before 12.128.2 contains a denial of service vulnerability in the /auth/v1/otp endpoint that prevents email verification for two-factor authentication due to captcha validation failures. Authenticated users cannot complete 2FA enrollment as the backend consistently returns HTTP 500 errors with captcha verification process failed messages, blocking access to security controls.
π@cveNotify
Capgo before 12.128.2 contains a denial of service vulnerability in the /auth/v1/otp endpoint that prevents email verification for two-factor authentication due to captcha validation failures. Authenticated users cannot complete 2FA enrollment as the backend consistently returns HTTP 500 errors with captcha verification process failed messages, blocking access to security controls.
π@cveNotify
GitHub
2FA email verification fails due to captcha validation error (/auth/v1/otp returns 500)
### Summary
Email verification required for enabling 2FA consistently fails due to a server-side captcha validation error. When users click βSend verification codeβ, the backend returns an HTTP 50...
Email verification required for enabling 2FA consistently fails due to a server-side captcha validation error. When users click βSend verification codeβ, the backend returns an HTTP 50...
π¨ CVE-2026-56351
n8n before version 2.4.0 contains a sql injection vulnerability in MySQL, PostgreSQL, and Microsoft SQL nodes that allows authenticated users to inject arbitrary SQL through unescaped identifier values in node configuration parameters. Attackers with workflow creation permissions can supply specially crafted table or column names to execute unauthorized database commands and compromise data integrity.
π@cveNotify
n8n before version 2.4.0 contains a sql injection vulnerability in MySQL, PostgreSQL, and Microsoft SQL nodes that allows authenticated users to inject arbitrary SQL through unescaped identifier values in node configuration parameters. Attackers with workflow creation permissions can supply specially crafted table or column names to execute unauthorized database commands and compromise data integrity.
π@cveNotify
GitHub
SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes
## Impact
An authenticated user with permission to create or modify workflows and access to a database credential could unknowingly create a workflow that was vulnerable to SQL injection, even whi...
An authenticated user with permission to create or modify workflows and access to a database credential could unknowingly create a workflow that was vulnerable to SQL injection, even whi...