17 matches found
GHSA-725G-W329-G7QR kora-lib: Token-2022 Transfer Fee Not Deducted During Payment Verification
Summary When a user pays transaction fees using a Token-2022 token with a TransferFeeConfig extension, Kora's verifytokenpayment credits the full raw transfer amount as the payment value. However, the on-chain SPL Token-2022 program withholds a portion of that amount as a transfer fee, so the...
kora-lib: Token-2022 Transfer Fee Not Deducted During Payment Verification
Summary When a user pays transaction fees using a Token-2022 token with a TransferFeeConfig extension, Kora's verifytokenpayment credits the full raw transfer amount as the payment value. However, the on-chain SPL Token-2022 program withholds a portion of that amount as a transfer fee, so the...
EUVD-2025-19922
Malicious code in bioql PyPI...
CVE-2025-6729
The PayMaster for WooCommerce plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 0.4.31 via the 'wpajaxpaymstatus' AJAX action This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to...
CVE-2025-6729
The PayMaster for WooCommerce plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 0.4.31 via the 'wpajaxpaymstatus' AJAX action This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to...
CVE-2025-6729
The PayMaster for WooCommerce plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 0.4.31 via the 'wpajaxpaymstatus' AJAX action This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to...
CVE-2025-6729 PayMaster for WooCommerce <= 0.4.31 - Authenticated (Subscriber+) Server-Side Request Forgery
The PayMaster for WooCommerce plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 0.4.31 via the 'wpajaxpaymstatus' AJAX action This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to...
CVE-2025-6729 PayMaster for WooCommerce <= 0.4.31 - Authenticated (Subscriber+) Server-Side Request Forgery
The PayMaster for WooCommerce plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 0.4.31 via the 'wpajaxpaymstatus' AJAX action This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to...
CVE-2025-6729
CVE-2025-6729 (PayMaster for WooCommerce) is an authenticated SSRF vulnerability in WordPress PayMaster for WooCommerce plugin, affecting all versions up to and including 0.4.31. An attacker with Subscriber-level access or higher can abuse the wp_ajax_paym_status AJAX action to make web requests ...
PT-2025-27849 · WordPress · Paymaster For Woocommerce
Name of the Vulnerable Software and Affected Versions: PayMaster for WooCommerce plugin for WordPress versions up to, and including, 0.4.31 Description: The issue allows authenticated attackers with Subscriber-level access and above to make web requests to arbitrary locations originating from the...
WordPress plugin PayMaster for WooCommerce 代码问题漏洞
WordPress and WordPress plugin are both products of the WordPress Foundation.WordPress is a set of blogging platforms developed using the PHP language. The platform supports setting up personal blog sites on servers with PHP and MySQL.WordPress plugin is an application plugin. A code issue...
WordPress PayMaster for WooCommerce plugin <= 0.4.31 - Authenticated (Subscriber+) Server-Side Request Forgery vulnerability
Authenticated Subscriber+ Server-Side Request Forgery vulnerability discovered by Poli in WordPress Plugin PayMaster for WooCommerce versions = 0.4.31...
Malicious code in paymaster-bundler-examples (npm)
--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware 976dfeb2cefe9c3b2fc6b0da31c62937a4bdbaabc387c7f16ce1a86e2b872e7c Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...
MAL-2025-2186 Malicious code in paymaster-bundler-examples (npm)
--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware 976dfeb2cefe9c3b2fc6b0da31c62937a4bdbaabc387c7f16ce1a86e2b872e7c Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...
The "totalRequiredBalance()" function in the TransactionHelper.sol library can compute address(uint160(_transaction.paymaster) as zero address even when _transaction.paymaster is non-zero
Lines of code Vulnerability details Impact A user may provide a non-zero entry for the "transaction.paymaster" field for a transaction to ensure they do not have to pay the gas fees. However, certain values of "transaction.paymaster" = 2^160 can result in addressuint160transaction.paymaster to be...
Operator can cause funds to be stolen by manipulating gas fee refund
Lines of code Vulnerability details Impact An operator can manipulate the refund of gas fee mechanism to steal from the bootloader balance. Inside refundCurrentL2Transaction function in the bootloader where the refund is happening for the refund recipient at L1097, the operator provides a value f...
Wrong decoding of paymaster data makes validatePaymasterUserOp always fail, DoS
Lines of code Vulnerability details Impact DoS of validatePaymasterUserOp makes UserOperation's with paymaster not executable Proof of Concept . decodePaymasterData on line 102 in VerifyingSingletonPaymaster.validatePaymasterUserOp returns wrong data and makes function always fail due to the...