WWBN AVideo is an open source video platform. In 29.0 and earlier, plugin/AuthorizeNet/processPayment.json.php credits the logged-in user's wallet based only on the attacker-controlled amount POST parameter. The endpoint contains a TODO for real Authorize.Net charging, hardcodes $paymentSuccess = true, and then calls YPTWallet::addBalance() without validating
any Authorize.Net transaction, webhook signature, hosted payment token, nonce, or server-side payment record. This allows any logged-in user to add arbitrary funds to their own AVideo wallet when the AuthorizeNet and YPTWallet plugins are enabled.
The Contact Form 7 – PayPal & Stripe Add-on plugin for WordPress is vulnerable to Payment Bypass via Insufficient Verification of Data Authenticity in all versions up to, and including, 2.4.9. Although `cf7pp_paypal_ipn_handler()` correctly validates IPN authenticity by posting back to PayPal with `cmd=_notify-validate`, it fails to compare the IPN payload's `mc_gross` (payment amount), `mc_currency`, or `receiver_email` fields against the corresponding stored order values before passing the attacker-controlled `invoice` field directly to `cf7pp_complete_payment()`, which marks the order completed after only an integer cast with no amount verification. This makes it possible for unauthenticated attackers to mark arbitrary high-value pending orders as fully paid by making a minimal real PayPal payment and crafting an IPN whose `invoice` parameter references the targeted order, effectively completing purchases without tendering the required payment amount.
Microsoft UFO open-source framework for intelligent automation across devices and platforms. In 3.0.1-4-ge2626659, Microsoft UFO's constellation client tracks pending task responses by session_id only and does not verify that a TASK_END message came from the device that originally received the task. When the constellation sends a task to a target device, it records a pending Future under a session key. The pending task record stores the expected device ID, but the completion path ignores that binding. If another authenticated peer device sends a forged TASK_END with the same session_id, the constellation accepts the response and completes the victim device's pending Future with attacker-controlled result data. This is an authenticated cross-device task-result injection issue.
CVE-2026-41164 is a medium severity vulnerability in nuts-foundation's nuts-node prior to versions 6.2.3 and 5.4.31. The v1 access token introspection endpoint incorrectly accepts any JWT signed by a key on the node without properly validating the JWT type, issuer-to-key binding, or required claims. This flaw allows a Verifiable Presentation (VP) JWT to be replayed as an access token and receive an active introspection response. The issue is fixed in versions 6.2.3 and 5.
CVE-2026-47202 is a critical improper authentication vulnerability in Kavita versions prior to 0.9.0.2. It allows a remote unauthenticated attacker to request a JSON Web Token (JWT) for any user, including administrators, if the attacker knows the username. This flaw stems from improper token validation. The vulnerability has a high CVSS 4.0 score of 9.3, indicating severe impact. A fix is available in version 0.
TypeBot versions 3.16.0 and earlier have an improper authentication vulnerability in the WhatsApp Cloud API webhook endpoint. The endpoint does not verify the x-hub-signature-256 HMAC signature that Meta includes in webhook deliveries. Because the webhook URL exposes workspaceId and credentialsId in the path, which are logged and visible in multiple places, an unauthenticated attacker can send spoofed webhook messages. This can trigger bot flows, consume API resources, and interact with external services using the workspace owner's credentials. The issue is fixed in version 3.17.0.
Insufficient Verification of Data Authenticity in the feedback function of Mesalvo MEONA (MEONA Client and MEONA Server). The MEONA Client transmits the recipient address of a feedback report to the MEONA Server, and the server sends the report to the transmitted address instead of the address configured on the server. The feedback function is available only in the MEONA administration area, which requires one of the administrative roles ADMINISTRATOR, SUPERADMINISTRATOR or TYPIST (catalogue editing), or the PHARMACIST role holding the PHARMACY_ADMINISTRATOR right, assigned explicitly by the operating hospital's administrators. Such a user who modifies the client request can cause the MEONA Server to send a message with content of the user's choosing, from the sender address configured on the server, to a recipient of the user's choosing, within the limits permitted by the operator's mail relay. The message can be used for social engineering because it appears to originate from an internal hospital system.
Exploitation requires a MEONA account with one of the administrative roles named above and access to the operating hospital's internal network; MEONA is operated exclusively within closed hospital networks without exposure to the public Internet, and where a hospital permits remote access to that network at all, it is only through the hospital's own remote-access infrastructure (e.g. VPN) under the hospital's control. The message contains only the recipient, subject and text entered by the user; no data of other users or patients is disclosed. Mesalvo is not aware of any exploitation outside the reported security test.
This issue affects MEONA Client and MEONA Server in versions 2024.10, 2025.04 (before 2025.04.24) and 2026.03 (before 2026.03.02). MEONA 2025.04.24 and 2026.03.02 (planned Q4 2026) enforce the configured recipient address on the server. Operators can restrict at their mail relay which recipients the MEONA sender address may reach.
AutoGPT versions 0.6.34 through 0.6.51 contain a deserialization vulnerability where Redis cache data is deserialized using pickle.loads without integrity or authenticity checks. This allows an attacker who can poison a shared Redis cache key to execute arbitrary commands in the backend container, impacting confidentiality, integrity, and availability. The issue is fixed in version 0.6.52.
Mullvad VPN is a VPN client app for desktop and mobile. When using macOS with versions 2026.1 and below, Mullvad VPN may allow local privilege escalation during installation or upgrade. The installer package executes binaries from /Applications/Mullvad VPN.app without verifying if the bundle is attacker-controlled or that the path is the legitimate Mullvad application. A user in the admin group can pre-place a crafted application bundle at that location and may be able to achieve code execution as root. Since the issue only affected the installer, there is no immediate need for users to update if they are already running an older version. This issue has been fixed in version 2026.2-beta1.
CVE-2026-44523 affects the open-source note-taking application Note Mark prior to version 0.19.4. The vulnerability arises because the application does not enforce a minimum length or entropy requirement on the JWT_SECRET configuration value, allowing very weak secrets, including those as short as one byte. This inadequate encryption strength can compromise confidentiality and integrity of JWT tokens. The issue is fixed in version 0.19.4. The vulnerability has a critical CVSS score of 10. No known exploits are reported in the wild.
CVE-2026-44592 is a critical vulnerability in wavelens gradient version 1.1.0, a nix-based continuous integration system. When the configuration variable GRADIENT_DISCOVERABLE is set to true (the default), an unauthenticated attacker who can access the /proto endpoint can register as a worker by submitting a new worker UUID without any credentials. This grants the attacker a session with PeerAuth::Open privileges, allowing visibility into jobs from all organizations and the ability to push arbitrary store paths into the system's nar_storage and cached_path tables. This vulnerability is fixed in version 1.1.1. No official patch link or vendor advisory is provided in the data, and the remediation level is not specified.
Spring Cloud AWS versions from 3.0.0 up to 4.0.1 did not verify the signature of incoming SNS messages on HTTP/HTTPS endpoints using specific notification mapping annotations. This allowed an unauthenticated attacker who knows the endpoint URL to send crafted HTTP POST requests mimicking SNS Notification or SubscriptionConfirmation messages. The vulnerability is fixed in version 4.0.2.
CubeCart versions 6.6.x through 6.7.1 have an improper input validation vulnerability where the software builds the CC_STORE_URL constant directly from the Host request header without validation. This value is used verbatim in transactional email links, including password reset links. An unauthenticated attacker can exploit this by sending a password recovery request with a malicious Host header, causing the victim to receive a password reset link pointing to an attacker-controlled domain. If the victim clicks the link, the attacker can gain full account takeover or store takeover if an admin account is targeted. This vulnerability is fixed in CubeCart version 6.7.
apko allows users to build and publish OCI container images built from apk packages. Prior to version 1.2.7, apko verifies the signature on APKINDEX.tar.gz but never compares individually downloaded .apk packages against the checksum recorded in the signed index. The checksum is parsed and available via ChecksumString(), and the downloaded package control hash is computed, but the two values are never compared in getPackageImpl(). Mismatched packages are silently accepted. An attacker who can substitute download responses (compromised mirror, HTTP repository, poisoned CDN cache) can install arbitrary packages into built images. This issue has been patched in version 1.2.7.
New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to version 0.12.10, a vulnerability exists in the Stripe webhook handler that allows an unauthenticated attacker to forge webhook events and credit arbitrary quota to their account without making any payment. This issue has been patched in version 0.12.10.
Roadiz is a polymorphic content management system based on a node system. Prior to versions 2.3.43, 2.5.45, 2.6.31, and 2.7.18, the roadiz/openid package generates an OIDC nonce in OAuth2LinkGenerator::generate() and includes it in the authorization request sent to the identity provider, but never stores it and never validates it on the callback. The OpenIdJwtConfigurationFactory validation chain does not include a nonce constraint, and OpenIdAuthenticator::authenticate() never checks the nonce claim in the returned ID token against a stored value. This issue has been patched in versions 2.3.43, 2.5.45, 2.6.31, and 2.7.18.
VINCE versions 3.0.38 and earlier do not properly verify the From address authenticity due to encoding confusion and use the from address for automated actions such as Ticket creation or Ticket updates.
Vaultwarden versions 1.35.4 and earlier contain a vulnerability in the WebAuthn authentication flow where persistent credential metadata flags are updated based on unverified authenticator data before signature validation. An attacker who knows a user's password but cannot produce a valid WebAuthn signature can modify these backup flags, causing a persistent denial of service for WebAuthn two-factor authentication on that user's credential. The issue is fixed in version 1.35.5.
CVE-2026-43534 is a critical input validation vulnerability in OpenClaw versions before 2026.4.10. It allows attackers to enqueue external hook metadata as trusted system events by supplying malicious hook names, thereby escalating untrusted input into a higher-trust agent context.
The Five Star Restaurant Reservations plugin for WordPress is vulnerable to a payment bypass via PHP type juggling in versions up to, and including, 2.7.16 This is due to the valid_payment() function using a PHP loose comparison (==) between the attacker-controlled payment_id POST parameter and the booking's stripe_payment_intent_id property. When an unauthenticated attacker submits a request to the nopriv AJAX handler rtb_stripe_pmt_succeed before the Stripe payment intent has been created for a booking (i.e., before the JavaScript-triggered create_stripe_pmtIntnt() call has stored an intent ID in post meta), the stripe_payment_intent_id property on the booking object remains null. The comparison sanitize_text_field('') == null evaluates to TRUE in PHP loose comparison, causing the payment verification check to pass with zero actual payment. This makes it possible for unauthenticated attackers to mark any existing payment_pending booking as paid without completing a Stripe payment by submitting an empty payment_id parameter.