Connection-resource exhaustion in IBM Power Systems firmware levels FW1110.00 through FW1110.31, FW1120.00 through FW1120.01, and FW1060.00 through FW1060.81 lets a highly privileged attacker on an adjacent network segment drive a denial of service by consuming connections the service processor never releases, until legitimate management traffic can no longer be serviced. The assessed vector (CVSS 4.5, AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H) means exploitation requires pre-existing administrative access to the affected interface plus network adjacency to the management segment, which confines realistic risk to insiders or attackers who have already established a foothold on the management network; confidentiality and integrity are unaffected. No public exploit has been identified at time of analysis and there is no indication of active exploitation, making this a low-to-moderate priority availability issue rather than an urgent one.
Local users on IBM i 7.3, 7.4, 7.5, and 7.6 can modify the system BOOTP table because the operating system fails to enforce a proper authority check on that configuration function, a case of improper privilege management (CWE-269). Exploitation requires an interactive or authenticated local presence on the host with at least low-level privileges (CVSS vector AV:L/PR:L), so neither a remote nor a fully unauthenticated attacker can trigger it, and the resulting impact is capped at low confidentiality and low integrity with no availability effect (CVSS 4.4). No public exploit code has been identified at time of analysis and there is no evidence of active exploitation, though IBM has published a vendor fix; this is a low-to-moderate priority issue rather than a top-tier emergency, with exposure scaling with the number of local accounts permitted on the partition.
Improper access control in the @backstage/backend-defaults package of the Backstage developer portal framework (versions prior to 0.17.8, shipped in Backstage releases before v1.54.6) allows an authenticated user to invoke backend actions that an operator had explicitly excluded through backend.actions configuration. The excluded actions are filtered out when actions are listed, but the invocation path never re-applied those filters, so a caller who knows or guesses an action ID can still trigger it; per-action permissions and downstream authorization remain enforced, which caps the impact at a low-integrity exposure (CVSS 4.3, C:N/I:L/A:N). There is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV), and the issue only matters in deployments that actually configured action exclusions. Fixed in @backstage/backend-defaults 0.17.8.
An authorization bypass in Nango versions prior to 0.70.9 allows a same-team user with the development_full_access role to read production integration flow metadata and named flow configuration when RBAC is enabled (has_rbac=true). This occurs because two private flow-read routes-GET /api/v1/integrations/:providerConfigKey/flows and GET /api/v1/flow/:flowName-omit the can({ action: 'read', resource: 'flow', scopedBy: envScope }) guard, enabling access to env=prod despite production role boundaries. The flaw is fixed in version 0.70.9; no public exploit code or active exploitation is currently identified, and the CVSS score is 4.3 (low severity).
Metadata and file-existence disclosure in OpenList versions through 4.2.3 allows an authenticated low-privileged user with a restricted BasePath to bypass authorization and view search results for sibling directories when Bleve search indexing is enabled. The flaw stems from a non-separator-aware strings.HasPrefix check that mis-authorizes paths like /base2 as contained within /base, and the Bleve backend’s unfiltered Total count leaks match existence even when individual results are filtered. A public proof-of-concept exists, though exploitation requires the Bleve engine to be configured, a specific sibling-directory naming collision, and authentication; the CVSS score is 4.3 (low-to-medium severity).
Missing authorization checks in the WP User Manager plugin for WordPress (versions through 2.9.22) let an authenticated low-privileged user invoke plugin functionality that should be restricted to higher-privileged roles, resulting in unauthorized integrity changes rather than data disclosure or disruption. The flaw is rated CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), meaning remote exploitation is possible but requires a valid low-privileged account (PR:L) and only affects integrity (C:N/A:N); because the plugin provides front-end registration and profile management, such accounts are frequently self-obtainable on sites with open registration enabled, which materially raises practical reach even though fully anonymous attackers cannot exploit it. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, so this is best treated as a modest-priority, high-volume WordPress plugin hardening issue rather than an urgent emergency.
Missing authorization in the WP Desk Flexible Subscriptions WordPress plugin, affecting all versions through 1.8.4, lets an authenticated low-privilege user (for example a registered customer or subscriber, PR:L) invoke plugin functionality that lacks a proper capability check, altering data the account should not be able to change. Impact is limited to partial integrity loss - no confidentiality or availability effect and no scope change - giving it a moderate CVSS 3.1 base score of 4.3, and exploitation requires a valid session on the target WordPress/WooCommerce site. There is no evidence of active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis, so this is a moderate-risk, not a priority, issue.
Exposure of JavaScript source map files in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 lets remote attackers retrieve the original, unminified client-side source of the web application, exposing internal identifiers, endpoint references, comments and other development-time detail. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) no authentication or user interaction is required, and the impact is confined to a low-severity confidentiality loss - reconnaissance material rather than direct access, since integrity and availability are unaffected. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and EPSS data was not provided; the vendor itself scored the attack vector as adjacent (AV:A), which would further limit exposure to attackers on the same local or logical network segment. This is a low-priority finding that is nonetheless a confirmed, genuinely disclosed product weakness.
Convex Backend self-hosted deployments running images or local binaries older than the August 10, 2026 release can, in rare cases, allow a remote unauthenticated attacker to read deployment information if user interaction is achieved; Convex cloud deployments were patched automatically and are not affected. The maintainer intentionally withheld the affected component and trigger mechanism, no public exploit identified at time of analysis, and the independent assessment rates this as a genuinely low-priority issue despite the network attack vector because exploitation requires interaction and high attack complexity. The vendor CVSS is 4.3 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N), while the independent assessment uses AC:H; only confidentiality is affected, not integrity or availability.
Authenticated users of a WordPress site running the Paid Videochat Turnkey Site plugin (ppv-live-webcams) through version 7.5.12 can manipulate quantity/specified-value input parameters because the plugin fails to properly validate them (CWE-1284). Rated CVSS 3.1 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), the flaw is network-reachable but demands a logged-in account and yields only limited integrity impact, with no confidentiality or availability effect. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so this is a moderate-severity, low-priority hardening item rather than an urgent threat.
Insecure direct object reference in the Hotel Booking WordPress plugin (versions through 3.8) lets any authenticated user - a Subscriber-level account is sufficient - retrieve booking records that belong to other customers by supplying a booking identifier they do not own. Because the plugin performs no ownership check on the requested record, an attacker can harvest customer PII including names, email addresses, phone numbers, and postal addresses; the CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, score 4.3) confirms a network-reachable, low-privilege, read-only confidentiality impact with no integrity or availability effect. The issue is significantly easier to reach on sites that allow public user self-registration, which is common for hospitality bookings; no public exploit code was identified at time of analysis and there is no CISA KEV listing, so this is a genuine but moderate-priority authorization defect rather than an emergency.
Cross-site request forgery in OTRS 7.0.X, 8.0.X, 2023.X, 2024.X, 2025.X and 2026.X before 2026.7.X lets an unauthenticated remote attacker cause an authenticated administrator's browser to fire the DBUpdateLogCleanUp administrative action through a forged GET request, deleting the DBUpdate log entries present at the time the request is processed and degrading diagnostic and audit history. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, 4.3) exploitation requires an administrator with an active session to be lured into loading an attacker-controlled page, so the attacker cannot choose targets or confirm success, and no public exploit code was identified at time of analysis. Additional administrative, deployment/synchronization, and export or read-only endpoints were also found to lack ChallengeToken validation, but those paths cannot introduce arbitrary new configuration and export responses remain protected by the browser's same-origin policy, so no confidentiality impact has been demonstrated.
Cross-site request forgery in the Hotel Booking WordPress plugin (versions through 3.8) lets an attacker forge administrative requests that create, delete, or modify booking order records inside an administrator's authenticated browser session, yielding a limited integrity-only impact (CVSS 4.3, C:N/I:L/A:N). The attacker needs no account of their own (PR:N), but the attack only succeeds if a logged-in administrator is tricked into loading an attacker-controlled page or hidden auto-submitting form (UI:R), which is the primary limiting factor. No public exploit code has been identified at time of analysis, and confidentiality and availability are not affected - only the accuracy of booking order data is at risk.
Cross-site request forgery in FileRise versions prior to 3.14.0 lets an attacker who lures an already-authenticated user into issuing a forged POST create an empty file or a share link under that user's identity, because the /api/file/createFile.php and /api/file/createShareLink.php handlers omit the server-side X-CSRF-Token check that adjacent state-changing endpoints enforce. The attacker does not need credentials of their own (PR:N), but the victim must hold an active session and be induced to make the request (UI:R); assessed severity is low (CVSS 4.3, AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N), and impact is bounded to file creation and share-link creation with the victim's permissions, not arbitrary content upload or account takeover. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the default SameSite=Lax session cookie is the decisive practical limiter, since a standard scripted cross-site POST will not carry the session cookie.
Missing authorization in the VideoWhisper Broadcast Live Video WordPress plugin (all versions through 7.3.6) allows an authenticated low-privilege user to invoke plugin functionality they are not entitled to and alter site content or plugin settings without holding the required capability. The impact is integrity-only (CVSS 4.3, C:N/I:L/A:N), scope is unchanged, and no confidentiality loss or denial of service results. There is no public exploit identified at time of analysis, CISA KEV does not list this CVE, and the assessed exploitation conditions (a valid low-privileged account on a site with the plugin enabled) place real-world risk at low priority rather than urgent.
Local information disclosure in FreeRDP 3.0.0 through 3.31.x allows an unprivileged local attacker on a multi-user Unix host to read PKINIT private-key material that the client writes to a shared temporary directory with world-readable permissions during soft-smartcard logon. Exploitation requires the attacker to already hold a local account, the victim to perform a soft-smartcard PKINIT logon during the attacker's monitoring window, and the deployment to actually use soft-smartcard authentication; single-user hosts and installations not using this flow are unaffected. No public exploit identified at time of analysis, and the flaw is not known to be actively exploited; it yields only confidentiality impact, with no integrity or availability effects.
Locally positioned attackers who can control copy queue work in Progress ShareFile Storage Zones Controller 5.12.6 and earlier can exploit an unvalidated callback URL acknowledgement path combined with a race condition to make FileCopyService consume attacker-controlled metadata and content. The issue is assessed as low-to-moderate priority with limited integrity and availability impact (C:N/I:L/A:L), no confidentiality exposure, and high attack complexity; no public exploit code or CISA KEV active exploitation is identified in the provided data. Remediation should occur in normal maintenance cycles rather than emergency patching.
Username enumeration in Thelia 2.6.0 lets unauthenticated remote attackers determine which administrator accounts exist by observing that the administrative login and forgotten-password endpoints respond differently to invalid usernames versus incorrect passwords. Because those endpoints apply no rate limiting or anti-automation controls, enumeration can be carried out efficiently at scale, with the resulting account list serving as reconnaissance for later credential attacks. The issue only discloses account existence (low confidentiality impact) and does not grant access; no public exploit code or confirmed active exploitation was identified at time of analysis, and the reported CVSS base score of 3.7 reflects the low severity.
Race condition in the Pixelite Events Manager WordPress plugin (versions through 7.4.7) lets a remote, unauthenticated attacker target a narrow synchronization window in the plugin's handling of a shared resource, resulting in a limited integrity impact with no confidentiality or availability effect. Exploitation hinges on winning a concurrency race - tightly-timed overlapping requests must land inside the vulnerable window (CVSS AC:H), a probabilistic timing requirement that substantially reduces reliability and keeps overall severity low. No public exploit has been identified at time of analysis, and there is no confirmed active exploitation (no CISA KEV listing).
Symlink following in the nginx third-party module ngx_cache_purge before 3.0.4 allows a local attacker to cause deletion of files outside the configured proxy_cache_path: the module's purge walks (purge_all, wildcard purge, or a plain proxy_cache_purge PURGE request) trust nginx's ngx_walk_tree(), which classifies directory entries with stat() and therefore descends into planted symlinks. Exploitation is narrow - it requires that nginx and a served application such as WordPress run under the same OS user account and that the attacker already has that user's file-write or code-execution capability to plant the link - and no public exploit code or confirmed in-the-wild activity was identified at time of analysis, with the assessed CVSS of 3.6 (AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L) reflecting a genuinely low-priority, local-only, high-complexity issue. Version 3.0.4 blocks symlinks found inside the cache tree but does not close an applicable TOCTOU race condition, so the shared-user deployment remains the decisive risk factor.
Stored cross-site scripting in the HireZoot WordPress plugin before version 4.0.0 lets an authenticated user who holds the plugin's management capability (Administrator by default) store a script payload in a job specification setting that is later rendered without escaping in an admin-area settings page and executes in the browser of any administrator who opens that page. Because the payload runs inside the viewing administrator's session, any impact is bounded by that administrator's own privileges, and the flaw is only a meaningful privilege escalation where administrators lack the unfiltered_html capability - WordPress multisite installs or sites with DISALLOW_UNFILTERED_HTML defined - since on default single-site installations administrators can already inject unfiltered HTML. This is a low-priority, network-reachable issue (CVSS 3.5, PR:H, UI:R) and no public exploit was identified at time of analysis; the vendor has shipped a fix in version 4.0.0.
Improper input validation in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 lets a local attacker who already holds authenticated low-privilege access to the database host or instance disrupt the affected component, resulting in a limited availability impact. The issue is not remotely reachable and cannot be triggered by an unauthenticated user; our assessment rates it CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, a low-severity availability-only condition, and there is no public exploit identified at time of analysis. Overall this is a low-priority, low-real-risk issue despite being a named CVE, and vendor patching is available.
Authenticated users of Red Hat Quay 3 can retrieve auto-prune policy configurations belonging to repositories in other namespaces, exposing configuration details that should remain tenant-scoped. Exploitation requires a valid Quay account, control of a repository whose name collides with the target's repository name, and prior knowledge of the target policy's unique identifier - conditions reflected in the CVSS 3.1 base score of 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N). Impact is confined to information disclosure, with no modification of data or denial of service, and no public exploit has been identified at time of analysis.
Terminal-output injection in the Elixir Hex package manager (all versions from 0.0.1 up to, but not including, 2.5.2) allows a malicious package publisher or a hostile repository server to smuggle ANSI escape sequences and Unicode bidirectional overrides into what Mix prints, forging displayed URLs, package descriptions and suggested commands, hiding real output, or writing attacker-chosen text to the victim's clipboard via OSC 52. Exploitation is unauthenticated (CVSS:4.0 PR:N) but requires the victim to run one of the affected interactive Mix tasks - such as mix hex.info, mix hex.package search, mix hex.search, mix hex.user or mix hex.policy - against data the attacker controls, and it depends on the victim's terminal emulator interpreting the injected sequences; impact is confined to output forgery and clipboard manipulation, with no code execution, file access or privilege gain, and the assessed severity is low (CVSS 4.0 base 2.3). No public exploit code was identified at time of analysis and there is no indication of active exploitation; the vendor has released a fix in Hex 2.5.2.
FreeRDP clients before version 3.32.0 can be crashed by a malicious RDP server that sends a crafted sequence of video redirection messages, resulting in a NULL pointer dereference. The attack requires the victim to initiate an RDP connection to an attacker-controlled server with the client video redirection channel active, and it only causes a client denial of service without code execution or data exposure. No public exploit code has been identified at the time of analysis.
FreeRDP clients version 3.11.0 through 3.32.0 can be crashed by a malicious or compromised RDP server that sends a crafted USB redirection request. The vulnerability is a reachable assertion in the urb_isoch_transfer function, triggered by an OutputBufferSize value exceeding INT32_MAX, which leads to client termination. Exploitation requires the victim to connect to the malicious server with USB redirection enabled, and no public exploit code is identified; the issue is low severity (CVSS 2.3) with only denial-of-service impact.
Former collaborators on Open WebUI knowledge bases can keep downloading or deleting files they were previously granted access to, because the has_access_to_file authorization check evaluates a stale cached knowledge base reference after the collaborator has been removed. The flaw affects Open WebUI 0.6.0 through the release immediately preceding 0.11.4, and is only reachable by an authenticated user who previously held a read or write grant on a specific knowledge base and then lost it - a share-then-revoke lifecycle - so single-owner or never-shared knowledge bases are unaffected; impact is confined to file download and deletion inside Open WebUI, including files in the owner's private knowledge bases. Rated low severity (CVSS 4.0 base 2.3; independent assessment CVSS 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L), with no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV) - a genuinely low-priority issue despite the 'Authentication Bypass' tag.
An authorization logic flaw in the goose AI agent framework affects versions 1.28.0 through 1.43.x and lets tools annotated readOnlyHint: true run without user approval even after the session has been switched to Manual Approval mode. The bypass is stateful rather than a default-configuration remote attack: a session must previously have run in Smart Approval mode, which persists read-only tool annotations, and update_goose_mode subsequently fails to clear them, so PermissionInspector::inspect skips its approval prompt when a prompt-injected call invokes one of those annotated tools. Successful exploitation yields low confidentiality and integrity impact with no availability impact, requires user interaction (the victim must process injected content in an agent session that earlier used Smart Approval), and no public exploit code was identified at time of analysis; per the supplied CVSS vector this is a network-reachable, unauthenticated-vector issue but with high attack complexity and a required user-interaction component, so real-world risk is low.
LearnHouse versions before 1.4.0 contain a missing authorization flaw (CWE-862) in the playground duplication endpoint POST /api/v1/playgrounds/{uuid}/duplicate, which fails to re-apply the read-access and draft checks that the normal get_playground path enforces. An authenticated user who holds playground creation rights - for example an Instructor - and who already knows the exact UUID of someone else's RESTRICTED or unpublished playground can duplicate it, copy its html_content, and republish that content publicly. Exploitation is constrained: the attacker must be authenticated (not anonymous) and must possess a specific, non-trivial UUID, so this is a genuinely low-priority, low-impact disclosure issue rather than a broadly exploitable one; no public exploit code or confirmed active exploitation has been identified, and the fix is available in the 1.4.0 release.
CSV formula injection in Thelia (before 3.1.2 and 3.2.0 through 3.2.0, fixed in 3.2.1) lets unauthenticated visitors plant spreadsheet formulas in registration, checkout, and newsletter fields that are later exported verbatim by CSVSerializer and executed when an administrator opens the file in Excel, LibreOffice Calc, or Google Sheets. The attacker never touches the Thelia server: impact is limited to the exporting administrator's workstation, and exploitation depends on an admin both performing the export and opening the resulting file (CVSS 3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N; CVSS 4.0 base 2.3). No public exploit code and no confirmed active exploitation have been identified at time of analysis, and the low EPSS-style risk profile is consistent with the assessed vector - this is a genuinely low-priority issue that vendor patches already resolve.
Live heart-rate readings can be intercepted over Bluetooth Low Energy from Fire-Boltt BSW013 smartwatches running firmware through V0.0.8, because the Heart Rate Measurement characteristic (0x2A37) accepts subscriptions from unpaired devices with no bonding, authentication, or on-watch confirmation. An attacker within BLE radio range of a powered-on, advertising watch can collect the wearer's heart rate in real time without authenticating or interacting with the victim, and the vector (PR:N/UI:N) confirms no credentials or user action are required, though the exposure is confidentiality-only and ends when the watch leaves range or is powered off. Risk is genuinely low (CVSS 4.0 base 2.3; independent assessment 3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), and no public exploit code or confirmed active exploitation was identified at time of analysis; no vendor-released patch was identified in the provided data.
Cross-origin information disclosure in Network-AI (npm package network-ai) before 5.15.2 stems from an origin validation error in McpSseServer._handleRequest (lib/mcp-transport-sse.ts) that reflects a localhost Origin into the Access-Control-Allow-Origin response header regardless of which interface the server binds. An attacker-controlled page carrying a localhost Origin can therefore read unauthenticated endpoints such as /health cross-origin, but only when the operator has bound the MCP SSE server to a non-loopback address (a non-default configuration) and a victim visits that malicious page - no public exploit code identified at time of analysis. Impact is limited to low-sensitivity information disclosure (assessed CVSS:3.1 base 3.0, C:L/I:N/A:N), and the reported CVSS 4.0 base of 2.3 is consistent with this low-priority characterization.
Memory exhaustion in hex_core (a library vendored into Hex/mix and rebar3) lets an untrusted repository mirror or a malicious server answering hex_core API requests abort the client-side Erlang VM by returning a tiny, highly compressed response that expands into a very large term or signed envelope. The vulnerable code paths decompress and decode attacker-controlled bytes before the registry signature is verified, and the Erlang safe-binary decoder used for application/vnd.hex+erlang responses accepts compressed terms without bounding the decoded size. Exploitation requires the attacker to control the served data (malicious/compromised mirror, hostile API server, or TLS MITM) and the victim to actively run a fetch operation; this is an unauthenticated remote issue per the assessed vector (CVSS:4.0 PR:N, UI:A, AT:P), but it is a low-severity availability-only problem with no code execution or data exposure, and no public exploit identified at time of analysis.
Reflected cross-site scripting in Cairo-dock Glx-Dock through version 3.4.0 lets remote attackers execute arbitrary script in a victim's browser by crafting a URL that passes malicious input to the 'p' query parameter handled by ww_page.php. Exploitation requires no authentication but depends on a victim being socially engineered into opening the crafted link (UI:P), and the resulting impact is limited to low-integrity manipulation of that user's session with no server compromise or data-at-rest exposure. The vulnerability is rated CVSS 5.3 with a CVSS 4.0 exploit-maturity value of E:P, and publicly available exploit code exists; the vendor was contacted early but did not respond. Given the niche Linux desktop deployment of Glx-Dock and the mandatory user interaction, this is a moderate-to-low real-world priority despite being remotely reachable.
Unrestricted file upload in TinyFileManager 2.6 and earlier allows authenticated remote attackers to write files to arbitrary paths by manipulating the fullpath parameter passed to move_uploaded_file() in tinyfilemanager.php, potentially achieving remote code execution on the server. The vulnerability requires a valid session (PR:L in the CVSS vector) and no user interaction; publicly available exploit code exists, but there is no confirmation of active exploitation in the wild. No vendor-released patch is available because the vendor did not respond to disclosure.
Cross-site scripting in SourceCodester Drug Recommendation System 1.0 allows remote, unauthenticated attackers to inject script payloads into the Student Registration workflow at Auth/add_student.php via the txtname, txtpassword, txtemail, txtphone and txtprevious_school fields. Publicly available exploit code exists (CVSS 4.0 E:P, CVSS 3.1 base 5.3) and the injected script executes only when a victim - plausibly an administrator reviewing submitted registration records - renders the tainted output in a browser, so impact is bounded to that victim's browser session within the application. Exploitation is not confirmed actively exploited (not in CISA KEV), and no vendor-released patch was identified at time of analysis, making this a low-to-moderate priority issue despite the public exploit.
Resource exhaustion in the Hex package manager for Elixir (0.11.2 up to, but not including, 2.5.2) lets an untrusted, attacker-controlled package mirror consume unbounded memory or disk on the machine running mix deps.get, mix deps.update, mix hex.package fetch, or mix hex.docs fetch. Hex decompresses gzip response bodies and downloads/extracts package and docs tarballs before any signature, checksum, or 16 MiB/128 MiB size limits are applied, so the mirror's own payload size dictates consumption. Exploitation is narrow: it requires a non-default attacker-controlled mirror configured via HEX_MIRROR_URL, HEX_MIRROR, or the mirror_url option plus explicit user action to run a fetch, the default hex.pm CDN is not affected, and no public exploit has been identified at time of analysis (unauthenticated per CVSS PR:N, but user interaction is required and impact is availability-only, assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:R/C:N/I:N/A:L).
Stored cross-site scripting in the Netcore NR268 router (firmware 1.7.121109) lets an attacker on the same network segment supply a crafted DHCP Hostname value that the device's DHCP handler stores without sanitization and later reflects into the administrative 'dynamic IP' display page (dhcp_dynamicip_show.cgi), executing script in the administrator's browser when that page is opened. Publicly available exploit code exists - the disclosure includes a full public write-up and PoC - but there is no CISA KEV listing and no confirmed active exploitation. The practical risk is low: the payload only fires after an authenticated administrator visits the affected page (UI:P), the vector is LAN-side, and impact is limited to low confidentiality/integrity within the router's web UI context.
Stored cross-site scripting in SourceCodester Drug Recommendation System 1.0 lets unauthenticated remote attackers inject arbitrary script through the name or email argument handled by Admin/user_record.php, which then executes in the browser session of an administrator viewing the Admin Record Tables page. Publicly available exploit code exists, and no vendor-released patch has been identified, though CVSS 4.0 scoring of 5.3 with UI:P reflects that a privileged victim must passively render the tainted record before the payload fires. This is a genuinely low-priority issue despite being publicly disclosed, because impact is confined to script execution in the viewing user's browser (integrity-low) with no direct server compromise.
Hard-coded credentials in Meetecho Janus Gateway up to 1.4.2 can expose the Admin API through the bundled demo file html/demos/admin.js; the issue is remotely reachable and publicly available exploit code exists, but the independent assessment rates it low priority because exposure is limited to deployments that serve the demo content or leave the Admin API reachable. The CVSS 4.0 vector indicates low privileges (PR:L) with low confidentiality, integrity, and availability impact, and the provided references are VulDB entries rather than a confirmed vendor patch.
Path traversal in FreeRDP's WinPR clipboard file redirection (winpr/libwinpr/clipboard/synthetic_file.c) allows a malicious RDP server to slip '../' sequences into server-supplied cFileName fields of FileGroupDescriptorW clipboard data, so that the victim's next clipboard paste copies an arbitrary local file readable by the client user instead of the intended remote file. All FreeRDP versions before 3.32.0 are affected; exploitation requires the user to connect to a hostile or compromised RDP server and then paste a redirected clipboard file (reflected in the assessed vector as UI:R and AT:P), and unauthenticated remote attackers are sufficient per the CVSS PR:N vector. Impact is confidentiality-only (single local file disclosure, no code execution or integrity/availability loss), and no public exploit code or confirmed active exploitation was identified at time of analysis.
Server-side request forgery in houtini-ai voice-analyser-mcp through version 2.1.1 allows a low-privilege authenticated user to make the server issue arbitrary outbound HTTP requests by supplying a crafted sitemap_url to the collect_corpus tool. Because the crawler's fetch function in src/utils/crawler.ts forwards the user-controlled URL without adequate validation, an attacker who can reach and invoke that feature can pivot requests toward internal services, localhost ports, or cloud metadata endpoints, though the assessed impact is bounded to low confidentiality, integrity, and availability effects with no subsequent-system scope. Publicly available exploit code exists and the vendor was contacted but did not respond, and no vendor-released patch has been identified at time of analysis; this is a genuine but low-priority SSRF rather than an unauthenticated or high-severity flaw.
Server-side request forgery in houtini-ai seo-crawler-mcp through version 2.1.5 allows an authenticated caller of the MCP tool interface to coerce the Crawler component into issuing requests to arbitrary destinations through the run_seo_audit function in src/core/CrawlOrchestrator.ts. The vendor was contacted about the flaw but did not respond, so there is no upstream fix at time of analysis, and publicly available exploit code exists (disclosed via the Net-defense/public_exp reference), though there is no evidence of confirmed active exploitation (not in CISA KEV). The independent assessment rates this low priority: exploitation requires low-level privileges on the MCP server (PR:L per both the vendor CVSS 4.0 vector and the assessed CVSS 3.1 vector), needs no user interaction, and yields only low read-level impact, with real risk concentrated where the MCP server has network reach to sensitive internal endpoints such as cloud metadata or internal APIs and lacks URL/egress filtering.
Authenticated SQL injection in erzhongxmu JEEWMS through version 2026.09.27-W39 allows remote low-privileged users to execute arbitrary SQL via the 'searchstr' parameter in the PDA interface's WmToMoveGoodsController.list endpoint. Publicly available exploit code exists (CVSS 4.0 E:P), though no confirmed active exploitation (CISA KEV) has been reported. The vendor did not respond to disclosure, and no vendor-released patch has been identified, so risk is moderate and depends on limiting exposure of the PDA interface.
SQL injection in the Autocomplete Handler of erzhongxmu JEEWMS (versions up to 2026.09.27-W39) allows remote attackers who already hold a valid low-privilege account to manipulate the trem, searchField, or entityName arguments passed to CommonServiceImpl.getAutoList and execute arbitrary SQL against the backend database, exposing data reachable by that account. Publicly available exploit code exists, so the attack is practical for any user able to authenticate and reach the endpoint; the vector's E:P rating and the reporter's note that the exploit was made public confirm exploitability, though there is no CISA KEV listing indicating confirmed active exploitation. The vendor was contacted early but never responded, and no vendor-released patched version has been identified.
SQL injection in the JEEWMS warehouse management system (erzhongxmu JEEWMS through build 2026.09.27-W39) lets an authenticated low-privilege user execute arbitrary SQL by manipulating the 'searchstr' argument handled by WmInQmIController.list in the Inbound Quality Check PDA interface. The vulnerability is remotely reachable (CVSS:4.0 base 2.1; assessed CVSS:3.1 6.3, AV:N/AC:L/PR:L/UI:N with low confidentiality, integrity and availability impact), so the primary constraint on exploitation is that the attacker needs a valid low-privilege account - it is not exploitable by fully unauthenticated parties. Publicly available exploit code exists and the vendor was contacted but never responded, so no vendor patch is currently identified; the issue is not in CISA KEV and real-world priority is low given the authentication prerequisite and the niche deployment footprint of this product.
SQL injection in erzhongxmu JEEWMS (versions up to and including 2026.09.27-W39) lets an authenticated low-privileged user inject arbitrary SQL through the 'searchstr' argument of the WmSttInGoodsController.list endpoint, potentially reading, tampering with, or disrupting warehouse-management data. Publicly available exploit code exists, and the vendor was contacted early but did not respond, so no vendor-released patch has been identified; there is no confirmed active exploitation (CISA KEV). With an assessed CVSS:4.0 base score of 5.3 and low confidentiality, integrity, and availability impact, this is a moderate-priority issue whose main limiting factor is the authentication prerequisite - anonymous, unauthenticated users cannot reach the vulnerable code path.
DOM-based cross-site scripting in the Craft CMS control panel login and two-factor verification flow (Craft CMS 5.0.0 before 5.10.14) lets an unauthenticated attacker run JavaScript in the browser of a control-panel user who has TOTP 2FA enabled, executing with the victim's own permissions. The attacker must lure the victim into opening a crafted /admin/login?verify=1 URL whose returnUrl parameter carries a javascript: scheme, and the victim must do so during the narrow window between password submission and TOTP entry, so exploitation requires precise timing, social engineering and active user interaction (CVSS 4.0 base 2.1, reflecting AT:P and UI:A with no server-side impact). No public exploit code has been identified at time of analysis and the flaw cannot be triggered against accounts without 2FA; overall this is a genuinely low-priority issue where the multiple signals agree rather than conflict.
Launching an arbitrary activity with Samsung Flow's own privileges is possible for a local attacker on a device running Samsung Flow prior to version 4.9.22.4, because the app ships with an incorrect default permission setting that exposes the capability to other local code on the device. Only users of the affected Samsung Flow builds on devices that are actually paired/connected to a counterpart device are exposed, and the resulting impact is bounded to the connected system with low confidentiality and integrity effect (vendor CVSS 4.0 base 2.1; our assessment CVSS 3.1 AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N). There is no indication of active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, and the presence of the AT:P attack-requirement in the vendor vector means a specific pairing/connection state must exist before exploitation is even feasible.
Stored cross-site scripting (XSS) in the Netis WF2409E router (firmware 3.3.42541) allows an authenticated attacker with access to the web management interface to inject a malicious script into the Wireless Settings SSID parameter, which then executes in the browser of an administrator who loads that page. The exploit is publicly available, and while this raises exploit maturity (E:P), the issue is rated low priority because it requires valid credentials (PR:L) and depends on administrator interaction (UI:R or UI:P), with impact limited to script execution in the admin's browser context (integrity-low; no confidentiality or availability impact). No vendor patch has been released, as the vendor did not respond to the disclosure.