The Fast Courier WordPress plugin through 5.2.3 does not restrict an unauthenticated REST route that writes order fulfillment data, allowing unauthenticated attackers to overwrite the courier status and customer-facing tracking details of any WooCommerce order by supplying its id.
Punk versions from 0.48 before 0.55 for Perl route Extended CONNECT requests to any GET route without an Origin check in ps_serve_one.
On HTTP/2 and HTTP/3 a WebSocket handshake arrives as an Extended CONNECT, which is matched as a GET and so reaches every GET route, API operation and mount. The Origin check runs only when a websocket route matches. On this transport the handler's status is the handshake response, and a 2xx accepts it.
A cross-origin page can open a WebSocket to any path and learn from its open or error event whether that path returns 2xx.
Plane is an open-source project management tool. Prior to 1.4.0, Plane exposes the workspace-scoped GET /api/assets/v2/workspaces/{workspace_slug}/download/{asset_id}/ endpoint for project-bound FileAsset objects without enforcing access to the asset's owning project. An authenticated user who belongs to the same workspace, is not a member of the victim's secret project, and knows the target asset UUID can receive a 302 redirect to a signed download URL. The intended project-scoped route for the same asset correctly returns 403. Confirmed affected project-bound asset types are ISSUE_ATTACHMENT, COMMENT_DESCRIPTION, PAGE_DESCRIPTION, and PROJECT_COVER. This bypass exposes private file content protected by the secret project boundary. This issue is fixed in 1.4.0.
CVE-2026-105144 is a path traversal vulnerability in the Drogon web framework affecting versions 1.9.13-1 and 10.0-beta.0 through 10.0-beta.3 on Windows. The flaw exists in the StaticFileRouter::route function, allowing remote attackers to manipulate file paths. Exploit code has been published, but there is no vendor response or patch available as of the disclosure date. The vulnerability has a medium severity rating with a CVSS 4.0 base score of 6.9.
Bouncy Castle for Java versions before 1.86 contain a vulnerability where truncated OpenPGP encrypted messages are accepted without error, leading to missing integrity checks on certain decryption paths. On the SEIPD version 1 path, this results in plaintext being delivered without any integrity verification, allowing altered ciphertext to produce accepted but modified plaintext. On the AEAD path, truncated chunks cause silent dropping of subsequent packets without error, potentially causing signed and encrypted messages to be read as unsigned. The low-level API remains unaffected if PGPEncryptedData.verify() is called directly. This issue also affects certain LTS and FIPS versions on the AEAD route. The vulnerability is a residual effect of a previous CVE and has been addressed in version 1.86 and later.
IDURAR ERP CRM versions up to 4.1.1 contain a stored cross-site scripting (XSS) vulnerability. Authenticated users can upload SVG files containing malicious JavaScript via profile update or settings upload endpoints. These scripts execute in the browsers of other users when the SVGs are served from the /public route. The vulnerability has a medium severity with a CVSS 4.0 score of 5.1.
Trigger.dev has a vulnerability where the deployment cancel operation is scoped only by project ID and not by environment ID. This allows an API key for a lower-trust environment (e.g., dev) to cancel deployments in higher-trust environments (e.g., production) within the same project. The deployment GET route correctly enforces environment scoping, but the cancel route does not, creating an authorization bypass. This affects both self-hosted and cloud deployments of Trigger.dev prior to version 4.5.6.
Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, the `next dev` development server exposes a Model Context Protocol endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the endpoint and read the project's disk location, source code snippets from error reports, route inventory, and development logs. Production deployments do not serve this endpoint. This issue is fixed in version 16.3.8.
Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, the next dev development server exposes a Model Context Protocol endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the endpoint and read the project's disk location, source code snippets from error reports, route inventory, and development logs. Production deployments do not serve this endpoint. This issue is fixed in version 16.3.8.
YesWiki versions prior to 4.6.7 have a server-side request forgery (SSRF) vulnerability. This flaw allows unauthenticated attackers to send signed Follow activities to a public actor inbox route, causing the server to make unauthorized internal requests. Attackers can use their own keyId to sign these requests while specifying internal actor URLs, potentially accessing internal hosts or cloud metadata services. The vulnerability has a high severity rating with a CVSS score of 7. No explicit patch information is provided in the input data.
YesWiki versions before 4.6.7 contain a server-side request forgery (SSRF) vulnerability in the validateKeyIdUrl() function. This flaw allows unauthenticated attackers to bypass SSRF protections by exploiting 6to4, NAT64, or IPv4-compatible IPv6 addresses. By sending a crafted Signature keyId to the public actor inbox route, attackers can potentially access cloud metadata services, loopback interfaces, or internal network hosts.
YesWiki versions before 4.6.7 have an authorization bypass vulnerability in the comments API editComment route. This flaw allows authenticated users with low privileges to overwrite arbitrary pages or comments by manipulating the pagetag field in a POST request. The vulnerability bypasses per-page write access controls, enabling unauthorized content replacement and reparenting of pages or comments.
Podgrab version 0 has a missing authentication vulnerability in its /ws WebSocket route, which is exposed on the root gin engine instead of being protected by BasicAuth. This allows unauthenticated clients to connect even when a password is configured. Attackers can hijack queue payloads intended for authenticated users, exposing episode metadata and server file paths, and potentially disrupting playback.
Improper Authentication vulnerability in Apache APISIX.
On a route using openid-connect plugin with remote introspection against an authorization server that serves multiple issuers, a token that introspects as active for one issuer may get accepted on a route restricted to another. This issue affects Apache APISIX: from 3.12.0 through 3.18.0.
Users are recommended to upgrade to version 3.19.0, which fixes the issue.
Use of Non-Canonical URL paths for authorization decisions vulnerability in Apache APISIX.
In some configurations where a permissive route overlaps a protected one, a crafted encoded path can reach an upstream endpoint that the matched route's policies were never meant to cover. A request that should have been rejected is served instead, giving unauthenticated access to a protected upstream endpoint. This issue affects Apache APISIX: from 2.14.1 through 3.18.0.
Users are recommended to upgrade to version 3.19.0, which fixes the issue.
Allocation of resources without limits or throttling vulnerability in batch-requests plugin in Apache APISIX.
An unauthenticated caller can drive a gateway worker into OOM via a route where the batch-requests plugin is used and the batch endpoint is publicly exposed. This issue affects Apache APISIX: from 1.3.0 through 3.18.0.
Users are recommended to upgrade to version 3.19.0, which fixes the issue.
Cross-Site request forgery (CSRF) vulnerability in feishu-auth and dingtalk-auth plugins in Apache APISIX.
An attacker who can get a user to click a crafted link may cause that user's browser session on a protected route to be established under the attacker's identity instead of their own. Any work the user then performs in that session, including uploads, form submissions, and account bindings, lands in the attacker's account. This issue affects Apache APISIX: from 3.17.0 through 3.18.0.
Users are recommended to upgrade to version 3.19.0, which fixes the issue.
Improper verification of cryptographic signature vulnerability in Apache APISIX.
Any unauthenticated attacker could impersonate any user on every route protected by the saml-auth plugin under default configuration. This issue affects Apache APISIX: from 3.17.0 through 3.18.0.
Users are recommended to upgrade to version 3.19.0, which fixes the issue.
Exposure of data element to wrong session vulnerability in Apache APISIX.
This issue affects Apache APISIX: from 2.3.0 before 3.7.0.
Under a supported authz-keycloak configuration, a request's authorization scope could persist into later requests on the same route, leading to unintended authorization expansion and inconsistent access-control decisions.
Users are recommended to upgrade to version 3.7.0 or higher, which fixes the issue.