Lucene search
+L

166 matches found

CVE
CVE
•added 2026/11/08 6:00 a.m.•29 views

CVE-2026-104639

The Razorpay for WooCommerce WordPress plugin (versions before 4.8.9 ) is vulnerable to an SQL injection attack. The root cause is the failure to properly sanitize and escape values derived from incoming webhook requests before they are processed in a SQL query. This vulnerability allows administ...

4.1CVSS6.1AI score0.00186EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/11/08 6:00 a.m.•18 views

EUVD-2026-119473

The Razorpay for WooCommerce WordPress plugin before 4.8.9 does not sanitize and escape a value derived from an incoming webhook request before using it in a SQL query, allowing users able to obtain the webhook secret administrators to perform SQL injection attacks...

4.1CVSS6.1AI score0.00186EPSS
SaveExploits0References1
Positive Technologies
Positive Technologies
•added 2026/11/08 12:00 a.m.•8 views

PT-2026-139904

The Razorpay for WooCommerce WordPress plugin before 4.8.9 does not sanitize and escape a value derived from an incoming webhook request before using it in a SQL query, allowing users able to obtain the webhook secret administrators to perform SQL injection attacks...

4.1CVSS6.1AI score0.00186EPSS
SaveExploits0References2
NVD
NVD
•added 2026/11/03 3:17 p.m.•11 views

CVE-2026-121449

Dockhand from 1.0.47 before 1.0.54 exposes plaintext stack secrets because deployStack attaches resolved secret values to its result as resolvedSecrets, which Git-stack routes return unfiltered. Holders of a stack's webhook secret or users with stacks:start permission can trigger the Git stack...

7.1CVSS0.00404EPSS
SaveExploits0References3
EUVD
EUVD
•added 2026/11/03 2:28 p.m.•20 views

EUVD-2026-115871

Dockhand from 1.0.47 before 1.0.54 exposes plaintext stack secrets because deployStack attaches resolved secret values to its result as resolvedSecrets, which Git-stack routes return unfiltered. Holders of a stack's webhook secret or users with stacks:start permission can trigger the Git stack...

7.1CVSS5.9AI score0.00404EPSS
SaveExploits0References3
NVD
NVD
•added 2026/11/03 9:17 a.m.•12 views

CVE-2026-103327

The CryptoCloud WordPress plugin from 3.0.0 through 3.0.1 does not verify the authenticity of the payment notifications received by its gateway callback, as the integrity check is skipped while the webhook secret is left at its empty default, allowing unauthenticated attackers to mark arbitrary...

5.3CVSS0.00114EPSS
SaveExploits0References1
EUVD
EUVD
•added 2026/11/03 8:20 a.m.•15 views

EUVD-2026-115720

The CryptoCloud WordPress plugin from 3.0.0 through 3.0.1 does not verify the authenticity of the payment notifications received by its gateway callback, as the integrity check is skipped while the webhook secret is left at its empty default, allowing unauthenticated attackers to mark arbitrary...

5.3CVSS6.1AI score0.00114EPSS
SaveExploits0References1
CVE
CVE
•added 2026/11/03 8:20 a.m.•16 views

CVE-2026-103327

The CryptoCloud WordPress plugin (versions 3.0.0 through 3.0.1 ) contains a vulnerability where it fails to verify the authenticity of payment notifications received via its gateway callback. The root cause is that the integrity check is skipped while the webhook secret remains at its empty defau...

5.3CVSS6.1AI score0.00114EPSS
SaveExploits0References1
Cvelist
Cvelist
•added 2026/11/03 8:20 a.m.•32 views

CVE-2026-103327 CryptoCloud - Crypto Payment Gateway 3.0.0 - 3.0.1 - Unauthenticated Arbitrary Order Payment Forgery via Empty-Default Webhook Secret

The CryptoCloud WordPress plugin from 3.0.0 through 3.0.1 does not verify the authenticity of the payment notifications received by its gateway callback, as the integrity check is skipped while the webhook secret is left at its empty default, allowing unauthenticated attackers to mark arbitrary...

5.3CVSS0.00114EPSS
SaveExploits0References1
Positive Technologies
Positive Technologies
•added 2026/11/03 12:00 a.m.•16 views

PT-2026-136038

The CryptoCloud WordPress plugin from 3.0.0 through 3.0.1 does not verify the authenticity of the payment notifications received by its gateway callback, as the integrity check is skipped while the webhook secret is left at its empty default, allowing unauthenticated attackers to mark arbitrary...

5.3CVSS6.1AI score0.00114EPSS
SaveExploits0References3
Cvelist
Cvelist
•added 2026/10/16 6:00 a.m.•52 views

CVE-2026-92427 Coinsnap Bitcoin Crowdfunding <= 1.2.0 - Unauthenticated Payment Record Forgery via Webhook Secret Disclosure

The Coinsnap Bitcoin Crowdfunding WordPress plugin through 1.2.0 does not restrict access to the secret used to authenticate its payment gateway webhook, disclosing it to unauthenticated users and rendering the webhook's signature check ineffective. This allows unauthenticated attackers to forge...

0.00194EPSS
SaveExploits0References1
CVE
CVE
•added 2026/10/16 6:00 a.m.•32 views

CVE-2026-92427

The Coinsnap Bitcoin Crowdfunding WordPress plugin (versions through 1.2.0 ) is vulnerable to an unauthenticated payment record forgery. The root cause is a failure to restrict access to the secret used for authenticating the payment gateway webhook, which is disclosed to unauthenticated users. T...

5.3CVSS6.1AI score0.00194EPSS
SaveExploits0References1
Vulnrichment
Vulnrichment
•added 2026/10/16 6:00 a.m.•18 views

CVE-2026-92427 Coinsnap Bitcoin Crowdfunding <= 1.2.0 - Unauthenticated Payment Record Forgery via Webhook Secret Disclosure

The Coinsnap Bitcoin Crowdfunding WordPress plugin through 1.2.0 does not restrict access to the secret used to authenticate its payment gateway webhook, disclosing it to unauthenticated users and rendering the webhook's signature check ineffective. This allows unauthenticated attackers to forge...

6.1AI score0.00194EPSS
SaveExploits0References1
Github Security Blog
Github Security Blog
•added 2026/09/10 9:06 p.m.•49 views

n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open

Impact The GitHub Trigger generated a signing secret when it registered a webhook and verified X-Hub-Signature-256 on each delivery. When GitHub answered the create request with a 422 because a webhook for the URL already existed, the node adopted the remote hook but kept only its id and events,...

6.3CVSS5.8AI score0.00259EPSS
SaveExploits0References6Affected Software1
EUVD
EUVD
•added 2026/09/10 9:06 p.m.•23 views

EUVD-2026-74276

n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open...

6.3CVSS5.8AI score0.00259EPSS
SaveExploits0References5
Patchstack
Patchstack
•added 2026/09/10 9:06 p.m.•20 views

NPM: n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open

NPM: n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open vulnerability discovered by ? in WordPress Npm n8n versions 1.123.76...

6.3CVSS5.9AI score0.00259EPSS
SaveExploits0References6Affected Software1
osv_ghsa
osv_ghsa
•added 2026/09/10 9:06 p.m.•29 views

GHSA-5M98-CGCR-XX3Q n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open

Impact The GitHub Trigger generated a signing secret when it registered a webhook and verified X-Hub-Signature-256 on each delivery. When GitHub answered the create request with a 422 because a webhook for the URL already existed, the node adopted the remote hook but kept only its id and events,...

6.3CVSS5.8AI score0.00259EPSS
SaveExploits0References6
NVD
NVD
•added 2026/09/08 10:19 p.m.•20 views

CVE-2026-86080

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the GitHub Trigger generated a webhook secret but discarded it when GitHub returned HTTP 422 and the node reused an existing webhook. Workflow static data then retained webhookId without webhookSecret, and...

6.3CVSS0.00259EPSS
SaveExploits0References4
Cvelist
Cvelist
•added 2026/09/08 9:25 p.m.•50 views

CVE-2026-86080 n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the GitHub Trigger generated a webhook secret but discarded it when GitHub returned HTTP 422 and the node reused an existing webhook. Workflow static data then retained webhookId without webhookSecret, and...

6.3CVSS0.00259EPSS
SaveExploits0References4
osv_cve
osv_cve
•added 2026/09/08 9:25 p.m.•23 views

CVE-2026-86080 n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the GitHub Trigger generated a webhook secret but discarded it when GitHub returned HTTP 422 and the node reused an existing webhook. Workflow static data then retained webhookId without webhookSecret, and...

6.3CVSS5.8AI score0.00259EPSS
SaveExploits0References6
Rows per page
Query Builder