BizPrint (print-google-cloud-print-gcp-woocommerce) before 4.10.0 contains a missing authorization vulnerability in its Debug\Core component that allows any authenticated user, including the lowest-privilege Subscriber role, to invoke the getPrinters and sendPrintRequest AJAX actions without a nonce or capability check. Attackers can send a crafted admin-ajax.php request with an arbitrary WooCommerce order_id to dispatch print jobs for other customers' orders and disclose printer configuration, exposing cross-customer PII and abusing printer resources.
The Russian APT group Star Blizzard (also known as Cold Relic) conducted a multi-stage cyber espionage campaign targeting US organizations. Initially, the group compromised a US organization in late 2025 using stolen super admin credentials and bypassed multi-factor authentication via push notification fatigue. They exfiltrated extensive data including cloud storage, employee lists, and emails. Subsequently, Star Blizzard impersonated an employee from the first victim to phish and breach a second US organization, leveraging stolen identities and MFA bypass techniques to maintain persistent access and conduct further data theft.
The WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups plugin for WordPress is vulnerable to Arbitrary Directory Deletion in all versions up to, and including, 4.19.0. This is due to insufficient path validation in the `cleanStagingDirectory` function, where the `deleteDir` parameter is only stripped of whitespace and double slashes by `sanitizePath()` without removing `..` traversal sequences or enforcing containment within the staging directory, leaving the sole pre-deletion guard as a simple string equality check against the WordPress home path. This makes it possible for authenticated attackers, with administrator-level access and above, to recursively delete arbitrary directories on the server — including `wp-content`, `wp-admin`, or directories outside the WordPress installation on shared hosting — resulting in denial of service or permanent data loss. An attacker must sequence a clone start, cancellation, and restart to drive the `delete_job` cache into the `directory` step before re-cancelling with a manipulated `deleteDir` value supplied via the `wp_ajax_wpstg_cancel_clone` endpoint.
Firekylin versions up to 2.18.1 have an authorization vulnerability allowing users with editor roles to access administrator-only secrets. This occurs because the admin API base guard permits all GET requests, enabling editors to retrieve sensitive data such as TOTP secrets, push credentials, cloud storage keys, and other users' app keys and secrets. This flaw could allow editors to publish posts with administrator privileges.
signalk-server versions from 2.28.0-beta.2 up to but not including 2.34.0 contain a server-side request forgery (SSRF) vulnerability via the app store icon fetcher. The server fetches absolute URLs declared in a plugin's signalk.appIcon field without proper restrictions, allowing an attacker to cause the server to make HTTP requests to internal or cloud metadata endpoints. Responses with image content types are stored and served back to the admin UI. This can be exploited by publishing a malicious plugin to the app store. A fix is available in version 2.34.0.
SignalK signalk-server versions from 2.28.0-beta.2 up to but not including 2.34.0 contain a server-side request forgery (SSRF) vulnerability in the App Store icon fetcher. This component trusts absolute URLs for signalk.appIcon, allowing attackers who publish npm packages with Signal K keywords to induce the server to make requests to internal or cloud metadata endpoints. The responses, if image-typed, are then served back via the admin UI. This vulnerability has a low severity score and was fixed in version 2.34.0.
BlueHammer (CVE-2026-33825) is a local privilege escalation chain targeting Windows Defender Antimalware Platform versions before 4.18.26030.3011. It requires initial code execution as a standard user and uses a series of legitimate Windows mechanisms to escalate privileges to NT AUTHORITY\SYSTEM. The exploit freezes the MsMpEng.exe process via CloudFilter manipulation and stages malicious update files. Laboratory tests demonstrated successful privilege escalation, recovery of domain-admin credentials from LSASS, and lateral movement using pass-the-hash techniques to compromise domain controllers. Exploitability depends on runtime factors such as pending signature updates, Defender state, filter drivers, VSS, and CloudFilter reachability. No known exploits are reported in the wild, and no patch information is provided.
## Summary
When cache interception is enabled, `@opennextjs/cloudflare` can interpret percent-encoded paths differently during middleware matching and cache lookup.
An encoded request may fail to match authorization middleware, then be decoded into the cache key of a protected route. The cached response may consequently be returned without invoking the middleware.
`enableCacheInterception` is disabled by default.
## Impact
A remote unauthenticated attacker may retrieve cached content from routes intended to be protected by middleware.
An application is affected when it:
- explicitly enables `enableCacheInterception`;
- relies on middleware for access control; and
- has a matching cached route.
## Details
Middleware matching previously used the encoded request pathname, while cache interception decoded the pathname before selecting a cache entry.
For example, consider an application with:
- middleware matcher `/admin/:path*`;
- middleware returning `401 Authentication required` for `/admin`;
- a statically generated, cached `/admin` route; and
- cache interception enabled:
```ts
export default defineCloudflareConfig({
incrementalCache: staticAssetsIncrementalCache,
enableCacheInterception: true,
});
```
An attacker can request:
```http
GET /%61dmin
```
The encoded pathname does not match `/admin/:path*`, so the authorization middleware is not invoked. Cache interception then decodes `%61dmin` to `admin` and may return the cached `/admin` response:
```http
HTTP/1.1 200 OK
x-opennext-cache: HIT
Protected content
```
Malformed paths exposed an additional inconsistency. For example:
```http
GET /%61dmin/%ZZ
```
The previous implementation decoded each segment independently. It decoded `%61dmin` to `admin` but retained the malformed `%ZZ` segment, allowing cache lookup to continue using a partially decoded pathname.
## Patches
The fix aligns encoded-path handling across middleware matching and cache lookup, and rejects malformed paths instead of partially decoding them. See the upstream fixes in [opennextjs-aws#1199](https://github.com/opennextjs/opennextjs-aws/pull/1199) and [opennextjs-aws#1200](https://github.com/opennextjs/opennextjs-aws/pull/1200).
Users should upgrade to `@opennextjs/cloudflare@1.20.2` or later.
## Workarounds
If upgrading is not immediately possible for an application:
1. Disable cache interception by removing `enableCacheInterception: true`.
2. Enforce authorization inside protected route handlers rather than relying exclusively on middleware.
3. Reject encoded paths for protected routes at a trusted proxy before they reach the Worker.
Adding individual encoded matcher variants is not a complete workaround because pathnames can have multiple equivalent encodings.
CVE-2026-76276 affects Splunk Enterprise versions prior to 10.4.3, 10.2.7, and 10.0.10. A low-privileged user without admin or power roles can access original source code of the Discover Splunk Observability Cloud app via Splunk Web due to embedded source maps in JavaScript bundles. This vulnerability does not affect version 9.4.x. The CVSS score is 4.3, indicating medium severity.
CVE-2026-76271 is a denial of service vulnerability in Splunk Enterprise versions 10.0.0 through 10.0.9, 10.2.0 through 10.2.6, and 10.4.0 through 10.4.2. It affects a REST API endpoint in the Discover Splunk Observability Cloud app, where an inefficient regular expression used for input validation can be exploited by a low-privileged user without admin or power roles. This causes excessive computational load, leading to denial of service. Versions 9.4.x are not affected.
Vvveb CMS versions prior to 1.0.8.6 contain a Server-Side Request Forgery (SSRF) vulnerability. The SSRF guard only resolves IPv4 addresses and does not inspect IPv6 addresses, allowing authenticated admin users to bypass private-range checks using IPv6 literals or domains with only AAAA records. This enables reading of internal-only services and cloud metadata, including IAM credentials. The issue is patched in version 1.0.8.6.
CVE-2026-55177 is a Server-Side Request Forgery (SSRF) vulnerability in dfpc-coe CloudTAK prior to version 13.10.0. Authenticated users with any token can exploit this flaw to make the CloudTAK server send arbitrary HTTP requests to internal network addresses without validation. This allows attackers to access sensitive internal services such as cloud instance metadata endpoints and loopback admin ports, potentially exposing temporary IAM credentials and other internal data. The vulnerability is fully patched in version 13.10.0.
CVE-2026-7171 is a stored Cross-Site Scripting (XSS) vulnerability in the TPVEnlanube Cloud Web application. It affects the 'Apellido 1' parameter in the endpoint '/administrator/index.php?page=admin.user_add&user_id=45&option=com_virtuemart'. An authenticated attacker could exploit this flaw to inject malicious scripts that execute in the browsers of other users. The vulnerability has a medium severity rating with a CVSS score of 4.8. No patch or remediation information is currently provided.
CVE-2026-7172 is a stored Cross-Site Scripting (XSS) vulnerability in the TPVEnlanube Cloud Web application. It affects the 'Nombre Completo' parameter in the '/administrator/index.php?option=com_virtuemart&page=admin.user_list' endpoint. An authenticated attacker could exploit this flaw to inject malicious scripts that execute in other users' browsers. The vulnerability has a medium severity with a CVSS 4.8 score. No affected versions or patch information are provided.
CVE-2026-7170 is a stored cross-site scripting (XSS) vulnerability in the TPVEnlanube Cloud Web application. It affects the 'vendor_store_name' parameter in the '/administrator/index.php?pshop_mode=admin&page=store.store_add&option=com_virtuemart&vendor_id=[ID]' endpoint. An authenticated attacker could exploit this flaw to inject malicious scripts that execute in users' browsers. The vulnerability has a medium severity rating with a CVSS 4.8 score. No patch or remediation information is currently provided.
Flowise versions up to 3.1.4 have a missing authorization control on the BullMQ admin dashboard when running in queue mode with the dashboard enabled and not in cloud mode. Any authenticated user, regardless of privilege level, can access the full Bull-Board UI and view sensitive data across all tenants. This includes chat inputs, credentials, custom function source code, and organizational identifiers. Additionally, users can perform write actions such as retrying, removing, promoting, and cleaning jobs across tenants. No patch is currently available for this vulnerability.
TDuck survey form through 6.0 lacks authorization checks on FormThemeController write endpoints for global form themes and categories. Authenticated non-admin users can add, modify, or delete themes and theme categories affecting forms owned by other users.
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's URL normalization does not recognize dot and dotdot path segments when they carry semicolon parameters. A request such as /user/..;foo=bar/admin is therefore not canonicalized to /admin even when path normalization is enabled. If an upstream interprets the segment according to RFC 3986 while Envoy applies routing or RBAC to the uncollapsed path, a remote client can cause path confusion and bypass path-based security policy. The relevant scope boundary is that the security consequence depends on a downstream/upstream path interpretation mismatch or a path-based Envoy decision. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's /stats?format=html admin endpoint uses StatsHtmlRender, which sanitizes string statistic values but emits statistic names without HTML encoding. A data-plane component such as grpc_stats with stats_for_all_methods enabled can incorporate attacker-controlled path segments into cached dynamic statistic names. When an operator views the HTML stats page, the stored name can execute script with the admin interface's origin and issue privileged same-origin requests. The relevant scope boundary is that the admin interface must be browser-accessible and an enabled component must persist attacker-influenced text in statistic names. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.