Unauthenticated vote-integrity bypass in the Contest Gallery WordPress plugin before 34.0.1 allows remote attackers to cast multiple votes for the same contest entry, inflating its tally without compromising site data or availability. The plugin relies on a client-supplied request header and an unbound client-generated token rather than a server-verified visitor identity, so any visitor can replay or forge vote submissions. Publicly available exploit code exists, but there is no CISA KEV confirmation of active exploitation; CVSS 5.3 reflects integrity-only impact (I:L).
Unauthenticated visitors can view the content of maintenance-exempt pages on WordPress sites running CMP - Coming Soon & Maintenance plugin before 4.1.21 when the operator has enabled maintenance mode and manually whitelisted pages by URL pattern. The disclosure is limited to those explicitly whitelisted pages and requires that non-default configuration; publicly available exploit code exists.
Unauthenticated information disclosure in the SureCart WordPress plugin before 4.9.5 allows anonymous visitors to pull merchant-private catalog metadata - pricing, commission, stock levels, SKU and tax internals, including unpublished products - by abusing the include parameters of the plugin's public single-upsell-funnel REST endpoint. The endpoint neither restricts which related objects a caller may request nor strips private fields from the returned objects, so any reachable storefront exposing at least one upsell funnel is affected without authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3). Publicly available exploit code exists according to the WPScan reference, and the vendor has released a patch in version 4.9.5; impact is bounded to catalog disclosure, with no customer records, credentials, write access, or code execution exposed.
Unauthenticated information disclosure in the WordPress Booking Package plugin before 1.7.31 exposes calendar-account configuration data, including administrator notification email addresses, to any remote attacker who can reach the site. The plugin returns these sensitive settings from a response handler without performing authorization checks, and the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms no credentials, interaction, or special configuration are needed. Publicly available exploit code exists and a vendor patch is available, but the impact is limited to confidentiality of configuration values with no write access or code execution, keeping overall risk moderate rather than critical.
Missing authorization in the SmartyParcel WordPress plugin before 1.23.4 allows unauthenticated remote attackers to download shipping labels belonging to arbitrary orders, exposing customer names, addresses and phone numbers. The flaw is a classic insecure direct object reference (CWE-639) affecting any site running the plugin with generated labels in place; publicly available exploit code exists, and CISA KEV status does not apply, so active exploitation in the wild is not confirmed. With a CVSS base score of 5.3 (confidentiality-only impact), EPSS-style urgency should be moderate, but the privacy and regulatory implications of leaked shipping data make timely patching worthwhile.
Booking Package WordPress plugin before 1.7.31 allows unauthenticated remote attackers to reset its premium subscription state, disabling paid features on affected sites. The issue is a missing authorization and validity check in the subscription-reset code path, requiring no credentials or user interaction, and is limited to integrity impact on the plugin’s premium status. Publicly available exploit code exists, and the vendor has released version 1.7.31 to address the flaw; risk is bounded to sites actively using the paid tier.
Unauthenticated attackers can mark bookings as paid and confirmed in the Ettrick Escape Room Booking WordPress plugin before 1.3.1 because the plugin does not verify payment status with the payment provider before changing booking state. This is a medium-severity (CVSS 5.3) missing-authorization/business-logic flaw (CWE-862) affecting sites that use the plugin's booking and payment-confirmation workflow; publicly available exploit code exists, but no CISA KEV active exploitation is recorded. Successful abuse is limited to integrity impact-fraudulent paid/confirmed bookings and possible revenue loss-without code execution, data disclosure, or site takeover.
Unauthenticated payment-state forgery in the Payment Gateway for Idram WordPress plugin before 2.1.6 lets remote attackers mark arbitrary orders as paid - or force them into a failed state - by submitting forged payment notifications. The root cause is that the merchant credentials used to compute the notification checksum are empty by default, so no meaningful signature check occurs on unconfigured installations; an attacker only needs the callback URL and a target order identifier. Publicly available exploit code exists and WPScan documented the issue, with a CVSS of 5.3 reflecting integrity-only impact (C:N/I:L/A:N) bounded to WooCommerce-style order payment status rather than data disclosure or site takeover; EPSS and KEV data were not provided, and the independent assessment rates this a moderate, not top-tier, priority.
Unauthenticated lead export in the Click n Chat (Chat Widget Integration) WordPress plugin, versions 1.0.4 up to but not including 1.1.3, allows any remote visitor to download the full set of captured contact records - names, email addresses and phone numbers - with no authentication, no user interaction and no non-default configuration required. Publicly available exploit code exists, and the issue was reported by WPScan as an information disclosure flaw (CWE-200). A vendor patch is available in version 1.1.3, which closes the missing authorization check on the lead-export handler.
Unauthenticated order manipulation in the Wava Payment Plugin for WordPress (0.3.1 through 0.3.9) allows remote attackers to forge payment-provider notifications and change WooCommerce order states, including marking unpaid orders paid and completed and cancelling other customers' orders. Versions through 0.3.7 also return billing details such as names, addresses, emails, and phone numbers to the same unauthenticated caller. Publicly available exploit code exists, and the vendor has released 0.3.10 to address the missing authorization and authenticity checks.
Broken access control in the TI WooCommerce Wishlist WordPress plugin before 2.13.0 lets unauthenticated remote attackers read the metadata and item contents of private wishlists by querying the plugin's REST API directly, bypassing the owner-only checks enforced on the front-end. No account, privilege, or user interaction is needed - only a vulnerable installation and a way to reference the target wishlist identifiers - and exposure is limited to wishlist metadata and contents rather than broader site or credential data. Publicly available exploit code exists for this CWE-284 flaw (CVSS 5.3, unauthenticated), though it is not confirmed as actively exploited in the wild.
Unauthenticated attackers can mark a pending WooCommerce order as paid by replaying a payment identifier captured from any single genuine SUMIT transaction, because the SUMIT Payment Gateway plugin before 4.0.0 fails to bind the provider payment to the target order and does not compare the payment amount to the order total. The flaw is CWE-863 incorrect authorization and is rated CVSS 5.3 (Medium) with a network vector requiring no privileges or user interaction. Publicly available exploit code exists; no CISA KEV active-exploitation confirmation was provided.
Unauthenticated attackers can retrieve other customers' order details - billing location, purchased products, and totals - from WordPress sites running Kliken: Ads + Pixel for Meta before 1.2.3 by enumerating predictable order IDs. The flaw is an authorization bypass (CWE-639) rated CVSS 5.3 with only confidentiality impact, and publicly available exploit code exists. A vendor patch is available in version 1.2.3.
Simple Shopping Cart WordPress plugin before 5.3.3 allows unauthenticated attackers to have their orders marked as paid by submitting a PayPal payment notification for a transaction sent to a PayPal account they control, because the default configuration does not verify that the receiving account belongs to the site owner. Publicly available exploit code exists for this issue, while active exploitation is not confirmed in the provided data. The flaw is rated CVSS 5.3 and affects integrity only, with no confidentiality or availability impact.
Unauthenticated payment-notification forgery in the Payment Gateway for Telcell WordPress plugin (versions before 2.0.5) allows remote attackers to mark arbitrary WooCommerce orders as paid, because the secret used to sign incoming callbacks is empty by default and therefore trivially reproducible. The same callback handler can also flip an attacker-chosen order to failed when an invalid signature is supplied, giving a second abuse path. Publicly available exploit code exists; there is no CISA KEV entry, and the impact is bounded to integrity of order/payment state (CVSS 5.3, I:L only), with risk concentrated on stores that leave the gateway at default settings.
Price tampering in the LatePoint WordPress booking plugin before 5.7.5 lets a remote unauthenticated visitor manipulate the client-supplied value that sets the booking charge, so the amount due can be resolved to zero and the visitor walks away with a confirmed appointment and a recorded order without paying. Any WordPress site running a pre-5.7.5 LatePoint installation that sells chargeable appointments through the plugin's own checkout flow is exposed; no account, special role, or non-default configuration is needed, only the ability to submit a booking (CVSS 3.1: AV:N/AC:L/PR:N/UI:N, 5.3, limited to integrity impact). Publicly available exploit code exists, and the issue is documented in the WPScan vulnerability database; the practical exposure is a direct revenue-loss and booking-fraud vector rather than a data breach. No CISA KEV entry was provided, so active exploitation is not confirmed.
Broken authorization in the Uncanny Toolkit for LearnDash WordPress plugin before 3.8.2 lets a subsite administrator on a multisite network flip arbitrary network users outside their own site to an 'unverified' state, locking those accounts out of the site. The flaw only manifests on WordPress multisite installs - default single-site deployments are not affected - and requires the attacker to already hold elevated subsite-admin privileges, so realistic exposure is confined to insider or compromised-admin privilege abuse rather than remote anonymous attack. Publicly available exploit code exists and a vendor fix (3.8.2) is released; there is no confidentiality exposure or code execution, only a targeted denial of login service.
Broken access control in WPZOOM Portfolio Lite before 1.4.34 allows authenticated users with the WordPress Contributor role or higher to convert other users' posts and pages into portfolio items, altering order and removing the content from its original listings and URLs. The flaw requires only a low-privilege account and no victim interaction, so it is most impactful on multi-author sites or those with open contributor registration; publicly available exploit code exists. The vendor has released version 1.4.34 to address the missing authorization check.
Missing authorization in the AI Engine WordPress plugin before 3.8.6 allows an authenticated user holding the Editor role or higher to rewrite the title and excerpt of arbitrary objects on the site - including navigation menus, block templates, global styles and WooCommerce coupons that the caller has no capability to edit. The defect is a missing per-object capability check (CWE-862) on the title/excerpt update path and is present in default plugin behavior, requiring no special configuration to reach. Impact is bounded to those two fields rather than full content control, and publicly available exploit code exists, though no confirmed active exploitation (CISA KEV) has been reported; this is a genuine but moderate-priority issue rather than a critical one, and the vendor has fixed it in 3.8.6.
Node.js startup snapshots can carry a stale crypto random cache into restored processes, so processes restored from a snapshot may emit repeated or predictable random values (CVE-2026-106074, CWE-330). Only applications that build or run using the snapshot feature - --build-snapshot / --snapshot-blob workflows or single-executable applications - are in scope, and the affected builds are Node.js 26.12.0, 24.22.0 and 22.23.3; impact is capped at low confidentiality and low integrity with no availability effect. No confirmed active exploitation (not in CISA KEV) has been reported, and while a public PoC reference exists, it is not verified as working exploit code.
Insecure cancellation-token generation in the Booking Package WordPress plugin before 1.7.31 allows unauthenticated attackers to reconstruct any booking's cancellation token from publicly exposed values, disclosing that booking's personal data and, when visitor cancellation is enabled, canceling the booking. Publicly available exploit code exists, and the CVSS 3.1 score is 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N), indicating moderate risk: disclosure works on default installs, while cancellation depends on the visitor-cancellation setting. No CISA KEV active-exploitation signal is present in the supplied data.
Authenticated subscribers on WordPress sites running the Productive Commerce plugin before 1.1.49 can activate any plugin already installed on the site, because one of its AJAX actions omits a capability check and the nonce meant to guard it is exposed on every admin-area page. The flaw is a moderate, integrity-only authorization issue (CVSS 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) that requires a logged-in account and cannot be used to upload new plugins. Publicly available exploit code exists, and the vendor has released version 1.1.49 to address it.
Missing authorization checks in the SmartyParcel WordPress plugin before version 1.23.4 let any authenticated user - including a default subscriber - delete shipping label and tracking records belonging to arbitrary orders across the entire store. Because the vulnerable code path performs no capability or ownership validation, an attacker only needs a valid low-privilege account, which is trivially self-provisioned on stores that leave WordPress user registration open. Publicly available exploit code exists, and the impact is confined to integrity loss (records deleted, no data disclosure or site takeover), consistent with the CVSS 4.3 score (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N); no confirmed active exploitation (CISA KEV) has been reported.
Cross-site request forgery in the Download Manager WordPress plugin lets remote attackers trick a logged-in administrator into changing the plugin's privacy and storage settings, including the credential that protects its unauthenticated maintenance endpoint. The flaw affects versions before 3.3.71 and 4.0.0 through 7.5.9, requires administrator interaction with a crafted link (UI:R), and publicly available exploit code exists. With CVSS 4.3, impact is limited to integrity of plugin settings, but an attacker who sets the maintenance-endpoint credential can expose that otherwise-unauthenticated interface.
Unauthenticated username enumeration in Trudesk through 1.2.11 allows remote attackers to submit crafted regular-expression patterns to POST /api/v1/login and infer valid accounts from distinguishable 'Invalid User' versus 'Invalid Password' responses. The issue is a regex/NoSQL injection in the login lookup (CWE-943) with low confidentiality impact; no public exploit identified at time of analysis and no CISA KEV confirmation. The CVSS 4.0 score is 6.9, and the independent assessment rates it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
Heap out-of-bounds read in FreeRDP clients on Windows before 3.32.1 allows a malicious or compromised RD Gateway to leak client heap memory or crash the client through crafted pre-authentication consent or service messages. The defect is in client_cli_present_gateway_message, where a byte count is misused as a wide-character printf precision, causing roughly twice the intended buffer to be read. No public exploit code has been identified at time of analysis, and exploitation requires the client to connect through an attacker-controlled gateway, for example via lure or network redirection.
Server-side request forgery in SvelteKit before 3.0.0 allows unauthenticated remote attackers to abuse the framework's server-side self-fetch fallback as a redirect-following proxy, reaching internal services by influencing Host or forwarded headers. Exploitation requires that the application uses self-fetch fallbacks and that the attacker can control Host or X-Forwarded-Host/-Proto values, which is realistic behind a misconfigured or trusting reverse proxy; the resulting impact depends on which internal services are network-reachable. No public exploit identified at time of analysis, and the vendor-released fix is SvelteKit 3.0.0.
Unauthenticated data injection in Trigger.dev before 4.5.5 allows remote attackers to write arbitrary content into a run's realtime stream by POSTing to /realtime/v1/streams/:runId/:streamId. The handler has no auth wrapper and the run lookup is not scoped to a runtime environment, so a known or guessed predictable friendlyId (e.g. run_1234abcd) can reach production streams, though impact is bounded to integrity of stream data with no read access, code execution, or availability loss. No public exploit code identified at time of analysis.
Memory exhaustion in adm-zip 0.6.0 and earlier allows unauthenticated remote attackers to bypass the library's decompression-bomb guard on the asynchronous getDataAsync() path, causing the full decompressed payload to be allocated regardless of an entry's declared uncompressed size. This is a genuine but bounded availability issue: only Node.js applications that read ZIP entries asynchronously and rely on the declared size as their bomb protection are exposed, there is no confidentiality or integrity impact, and meaningful denial of service typically requires repeated or large crafted submissions. Publicly available exploit code exists in the form of a working proof-of-concept published with the GitHub advisory, and the flaw is fixed in adm-zip 0.6.1.
Apache Traffic Server can be stalled by a crafted chunked HTTP transfer whose trailers ATS has been configured to strip: the proxy discards the trailer bytes but still waits for them, so the transaction hangs until the connection timeout expires. Versions 10.0.0 through 10.1.4 and 10.2.0 are exposed in their default configuration because proxy.config.http.drop_chunked_trailers is enabled by default in the 10.x line, while 8.1.11 and 9.2.5 through 9.2.15 are affected only where an operator has explicitly turned that setting on. Rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N, availability-only Low), this is a modest denial-of-service issue that degrades individual proxied connections rather than the whole service; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited.
Information disclosure in pdfmake 0.3.8 through 0.3.11 lets attackers read local files that the setLocalAccessPolicy() restriction is supposed to block, by placing an SVG image whose href points at a local path. The flaw is reachable by unauthenticated remote attackers (CVSS v4 PR:N) but only matters when a host application builds PDFs from attacker-influenced document definitions and relies on that policy to sandbox file access; impact is limited to confidentiality. No public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor patch ships in 0.3.12.
Heap out-of-bounds read in the FreeRDP Android client before 3.32.1 allows a malicious or compromised RDP server to read past allocated surface buffers by supplying unvalidated mappedWidth and mappedHeight values in an RDPGFX_MAP_SURFACE_TO_WINDOW_PDU. Only Android client builds of FreeRDP that negotiate the graphics pipeline (RDPGFX) channel are affected, and because the attack direction is server-to-client, a victim must first be induced to connect to the hostile endpoint - there is no way for an attacker to reach arbitrary hosts directly. Successful exploitation yields limited heap memory disclosure and possible client crashes, with no code execution or write primitive described; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and the CVSS:4.0 score of 6.9 is driven by low confidentiality impact combined with network reachability.
Missing authorization checks in the legacy AJAX handlers of Chamilo LMS 2.0.0 pre-releases (2.0.0-alpha.1 through RC.2) let unauthenticated remote attackers enumerate learner accounts and pull other users' certificate PDFs by calling actions such as get_users_by_group_course, user_by_all_roles and export_all_certificates. Impact is confined to confidentiality (user names and certificate documents); there is no write, modification or availability effect, and stable 1.x production installations are not in the affected range. The independent assessment rates this as a genuine but moderate-severity information-disclosure issue (CVSS v4.0 score of 6.9, assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/C:L), and no public exploit code or CISA KEV entry was identified at time of analysis.
Request body inspection bypass in Coraza WAF versions 3.0.4 through 3.8.0 allows unauthenticated remote attackers to evade custom body rules by sending a valid URL-encoded form body with a Content-Type parameter such as 'application/x-www-form-urlencoded; charset=UTF-8', leaving ARGS_POST and REQUEST_BODY empty while the backend still parses the payload. This is a moderate-priority WAF evasion issue rather than a server compromise; deployments that rely on custom ARGS_POST or REQUEST_BODY rules are exposed, while an unmodified current OWASP CRS with rule 901340 forces fallback inspection and neutralizes the bypass. No public exploit identified at time of analysis; vendor-released patch: 3.8.1.
Any authenticated Trudesk user can read tickets belonging to groups they are not a member of - subject, issue body, comments, ticket owner and assignee - by simply iterating sequential ticket IDs against GET /api/v1/tickets/:uid, and every release through 1.2.11 is affected. The apiTickets.single handler omits the group-membership check entirely, making this a textbook IDOR (CWE-639) instead of an injection or memory-safety bug, so attacker impact is limited to read-only disclosure with no modification or code execution. Risk is medium (CVSS 5.3; our assessment CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N): the only prerequisite is a valid account at any privilege level, no public exploit code or confirmed active exploitation has been identified at time of analysis, and instances that permit self-registration or host many low-privilege accounts should be treated as the highest exposure.
HTTP request smuggling in Apache Traffic Server (8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0) lets unauthenticated remote attackers send HEAD requests carrying Content-Length or Transfer-Encoding headers to desynchronize HTTP message framing between ATS and an upstream or downstream agent. The scope-changed CVSS 3.1 score of 9.3 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N) reflects high integrity impact - cache poisoning, request/response queue confusion, and possible access-control bypass - with limited confidentiality exposure; no public exploit code was identified at time of analysis. Vendor-released fixes are available in 9.2.16, 10.1.5, and 10.2.1.
JSON body inspection bypass in Coraza 3.0.0 through 3.8.1 lets unauthenticated remote attackers hide SQL-injection payloads from OWASP CRS rules while the backend still receives and processes them. The flaw is in Coraza's JSON body processor, which flattens nested objects into dot-separated ARGS_POST names without escaping dots that appear literally in property names, so a decoy sibling key such as "account.role" overwrites the flattened entry for the nested "account.role" value inside Coraza's map while standard backend JSON parsers keep both properties intact. Real-world impact is conditional: the bypass only matters where the protected application has an injectable downstream sink, though the vendor advisory demonstrates the evasion working against CRS v4.25 rule 949110; no public exploit code was identified and there is no KEV/active-exploitation signal, and independent assessment rates the direct risk as integrity-only (CVSS 3.1 5.3, C:N/I:L/A:N) rather than as code execution.
Unauthenticated gradebook certificate tampering affects Chamilo LMS 2.0.0 pre-release builds (alpha.1 through RC.2), where the GradebookController set_default_certificate endpoint lacks authorization checks and lets any remote user supply an arbitrary course id and document id to alter certificate configuration. The independent assessment rates this moderate severity (CVSS 3.1: 6.9, AV:N/AC:L/PR:N/UI:N with integrity-only, low impact), and exploitation is constrained to unpatched pre-release deployments that are network-reachable. No public exploit code or confirmed active exploitation is identified in the available data, and the vendor has released a fix in 2.0.0-RC.3.
adm-zip versions before 0.6.1 can apply attacker-controlled setuid, setgid, or sticky bits when extracting archives with the non-default keepOriginalPermission option enabled. This is a conditional local privilege-escalation risk: the archive must be extracted in a privileged context such as root and the resulting executable must later be run, so exploitation depends on that specific workflow. No public exploit identified at time of analysis, and the vendor-released patch is adm-zip 0.6.1.
Information disclosure in TP-Link Deco BE63 v2.0 lets an attacker who already holds administrative privileges on the device, and can reach it from an adjacent LAN or Wi-Fi segment, query the cloud-client daemon and recover the linked TP-Link ID account password in plaintext. That credential could then be used to access the associated TP-Link cloud account and perform actions as the affected user. The vendor has released a firmware update, and no public exploit was identified at time of analysis; the independent assessment rates this as a constrained medium-severity risk because exploitation requires admin access and adjacent-network positioning.
Trigger.dev CLI versions before 4.5.9 can disclose resolved environment secret values when deployment is run with debug logging, because the debug output serializes the build-worker options object with unredacted envVars; this exposes database connection strings and service credentials to anyone who can read the resulting terminal transcript, CI debug log, captured tool output, or support bundle. The assessed impact is confidentiality-only (CWE-532, CVSS:3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), and exploitation is constrained by the need for debug-level logging and access to retained output; normal non-debug environment listings redact values. Trigger.dev 4.5.9 contains the vendor fix, and no public exploit code is identified at time of analysis.
Insecure temporary file handling in Cisco Expressway Series allows a local, low-privileged attacker to tamper with data and disrupt services when another user or process interacts with an attacker-influenced temporary file (CVSS 6.6; AV:L/PR:L/UI:R, C:N/I:H/A:H). The flaw is tracked as CWE-377 and affects the Cisco Telepresence Video Communication Server (VCS) Expressway product line; the available CPE data does not identify a specific version range. No public exploit code or confirmed active exploitation was identified in the provided intelligence at time of analysis.
Crafted relationship-inclusion parameters on Laravel JSON:API resource endpoints can be turned into destructive database operations, letting a low-privileged user wipe data from related tables through what should be a read-only request. Applications running laravel/framework versions 12.45.0 through 12.67.x, or 13.x before 13.27.0, that expose client-controlled 'include' query parameters via the JsonApiResource / ResolvesJsonApiElements feature are affected; the vendor fixed the flaw in 12.68.0 and 13.27.0. Because a single request can irreversibly empty tables, the integrity and availability impact outweighs the modest attack complexity, though exploitation is conditional on JSON:API resources actually being adopted and on the endpoint honoring user-supplied includes - no public exploit code or confirmed active exploitation was identified at time of analysis.
Denial of service in Splunk Enterprise allows a low-privileged authenticated user to render the entire instance unavailable, requiring a manual restart to restore service. The flaw is a missing resource-consumption limit in the REST API endpoint for lookup table files, which fails to bound response field selections (CWE-770). Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 are affected; exploitation requires only a valid Splunk account (PR:L) that need not hold the admin or power roles, and no public exploit code or active exploitation has been identified at time of analysis. Impact is strictly availability - no data confidentiality or integrity loss - making this a genuine but moderate-priority issue that escalates in environments with broad API access.
Broken access control in Nuxt (3.11.0 through 3.21.4 and 4.4.4) lets unauthenticated remote attackers retrieve pages that routeRules and appMiddleware are meant to gate, by requesting a percent-encoded form of a protected path that contains a dynamic or catch-all parameter. Route-rule keys are compared against the raw request path, while Vue Router decodes the parameter during route resolution, so the gating rule never matches and the page plus its SSR data payload is returned to the requester; the same mismatch also breaks redirect, appLayout, ssr, prerender and cache/isr/swr-derived payload rules in the app manifest. CVSS 3.1 is 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) - moderate, limited confidentiality and integrity impact - and no public exploit code or confirmed active exploitation was identified at time of analysis; exposure is limited to applications that actually gate dynamic/catch-all routes via route-level rules.
Denial-of-service in Pillow's multi-frame image handling: the MAX_IMAGE_PIXELS decompression-bomb guard can be bypassed for MPO, DCX, and MIC containers when an application calls seek() to navigate to frames or pages beyond the first, allowing a small attacker-supplied file to trigger unbounded memory and CPU consumption. Only applications that open these specific multi-frame formats and seek past the first frame are affected; single-frame opens and first-frame-only pipelines are not. The flaw is rated CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L (availability-only, no confidentiality or integrity impact), affects Pillow releases prior to 13.0.0, and no public exploit code was identified at time of analysis.
Integer underflow in Pillow's legacy PILfont text-width calculation (CVE-2026-96641, GHSA-4rm8-3hmm-39fg) can be triggered when an application loads and measures text with a manipulated .pil bitmap font, producing a low-impact availability condition; the Pillow project rates it Medium and fixed it in release 13.0.0. The assessed CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, indicating a local attack vector, no privileges required, no user interaction, and impact limited to availability with no confidentiality or integrity effect. No public exploit was identified at time of analysis, and no CISA KEV entry is indicated in the available data.
Splunk SOAR deployments below 8.7.0 allow any authenticated user whose role omits the view-apps permission to export and download an installed app archive, exposing proprietary source code and any sensitive data or secrets embedded in that package. The flaw is a missing authorization check in the app export path, rated CVSS 6.5 with confidentiality-only impact. No public exploit code or CISA KEV entry was identified at time of analysis, and exploitation requires a valid low-privileged account on the SOAR instance.
Splunk Secure Gateway exposes mobile alert notification data belonging to other users to any authenticated low-privileged account that lacks the admin Splunk role or sc_admin Secure Gateway role. The flaw is missing user-level authorization on read requests to certain Secure Gateway App Key Value Store (KV Store) REST API collections, and it affects Splunk Enterprise releases below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 plus Secure Gateway releases below 3.10.12, 3.9.26, and 3.8.73. No public exploit has been identified at time of analysis, and the vendor-assigned CVSS 3.1 score is 6.5 with a confidentiality-only impact.
Reflected and stored cross-site scripting can occur in Astro Framework versions prior to 7.3.2 when an application passes attacker-controlled data as a dynamic child of a <script> or <style> element rendered through the astro:jsx renderer, including MDX components. Exploitation is conditional on that developer-introduced pattern-compiler-generated literal script/style content and other JSX expression contexts are not affected-and requires the victim to load the crafted page (UI:R). No public exploit code was identified at time of analysis; the NVD score is 6.5, while our independent assessment treats impact as limited (S:C/C:L/I:L/A:N) because the vulnerable pattern is not a default configuration.