OS command injection in Sunwood-ai-labs github-kanban-mcp-server through version 0.4.0 lets an attacker who can influence the state or labels arguments of the handleListIssues tool inject shell metacharacters that reach an operating-system command (CWE-78). The flaw is network-reachable and unauthenticated per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R), but it requires the operator or driving agent to invoke the issue-listing operation before the injected input executes, so it is not a fully autonomous remote trigger. Exploitation has not been confirmed in the wild and no public exploit code was identified at time of analysis; the vendor released version 0.4.1 plus commit 253d93bbdf7ee9fe42bd8fdf15feea93ae59cbae as the fix.
Cross-site scripting (CWE-80) in the WpEvently WordPress plugin from Magepeople Inc. affects all versions through 5.7.9 and lets an attacker place script-related HTML that executes in a victim's browser once the injected content is rendered. The supplied vector scores 5.3 with PR:N, but real-world exploitation still hinges on a victim loading the affected page (our assessment uses UI:R rather than UI:N), so impact is bounded to visitor-side script execution such as content or session manipulation rather than server compromise; the vulnerable parameter and whether the payload is stored or reflected are not described in the sources. Only a Patchstack database entry is available, no public exploit code has been identified at time of analysis, and the issue is prioritized as this-month rather than immediate action.
A pre-authentication out-of-bounds read in the SNMP component of Arm Keil MDK-Middleware 8.0.0 through 8.3.0 lets a remote, unauthenticated attacker reach SNMP parsing code before any credential check and read past the bounds of an internal buffer, with the assessed impact limited to availability (CVSS 5.3, AV:N/AC:L/PR:N/UI:N/C:N/I:N/A:L). Only devices whose firmware is built on the affected middleware with the SNMP component compiled in, enabled and network-reachable (typically SNMP on UDP 161) are exposed; devices that do not ship or expose this stack are not exploitable. Exploitation has not been observed (CISA SSVC Exploitation: none) and no public exploit was identified at time of analysis, so this is a medium-severity denial-of-service-class issue rather than an emergency, though the automatable nature of the flaw warrants patching within the vendor's normal cycle.
Sandbox isolation in DeepSeek Harness 0.1.0-rc.0 through 0.1.0-rc.5 can be manipulated through the createContext function of the cordis-host-runner extension (packages/extensions/cordis-host-runner/src/sandbox.ts), giving remote, unauthenticated attackers limited confidentiality, integrity and availability impact - but only where a user of the affected deployment takes an interaction step, as reflected in the UI:P metric. Impact is capped at LOW on all three pillars with no scope change, so the realistic outcome is a weakened sandbox boundary rather than host takeover. No CISA KEV entry and no public exploit code were identified at time of analysis, no vendor patch or fixed version is listed, and the vendor was contacted about the disclosure without responding; VulDB-derived triage places the issue in the 'this_month' priority band.
Missing authentication on several boneIO Black API endpoints lets any unauthenticated caller who can reach the device on the local network read system logs, the firmware version, the device serial number, the configured MQTT username, configuration file listings and the interactive API documentation. The exposure is confined to information disclosure - there is no integrity or availability impact - but the harvested details are directly useful for reconnaissance and for planning follow-on attacks against the device or the MQTT broker it talks to. All versions prior to 1.6.0 are affected; 1.6.0 requires an authenticated role on every API route, disables the interactive API documentation and withholds the serial number from anonymous callers. No public exploit code was identified at time of analysis and there is no CISA KEV entry, so the practical risk is bounded by the adjacent-network requirement.
Information disclosure in Kameleo through version 5.3.1 lets an unauthenticated remote attacker read data exposed by the /general/user-info endpoint of the Local API component, provided the victim is induced to perform an interaction that causes the request to be issued (CVSS 4.0 base 5.3; assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:R, C:L only). Only low-confidentiality data is at risk - there is no integrity or availability impact - and the Local API must be active and reachable along the attacker's request path, which typically means a browser-mediated or cross-origin trigger against a normally localhost-bound service. No public exploit code was identified at time of analysis, and the vendor did not respond to the disclosure, so no vendor-released patch has been identified.
Information disclosure in the Local API of Kameleo (versions up to and including 5.0.1.26) lets a remote, unauthenticated attacker read data exposed by the /profiles endpoint, with the assessed CVSS 3.1 score of 5.3 reflecting confidentiality-only impact (C:L) and a required victim-side action (UI:R). Exploitation is opportunistic rather than mass-scale: Kameleo must be running with its Local API reachable along the attacker's request path, and the exact mechanism by which /profiles leaks data is not described in the available sources. The vendor addressed the issue in release 5.2.0, whose security note states that proxy passwords are now redacted in API responses; no confirmed active exploitation (CISA KEV) or verified public exploit code was identified at time of analysis, and the vulnerability is triaged as a plan-and-patch item rather than an emergency.
Information disclosure in Kameleo up to and including 5.3.1 allows remote attackers to read cookie data held by the client engine by manipulating the 'guid' argument passed to CookieController.ListCookies in client-engine-application/w.cs. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) indicates no privileges are needed and the attack is network-reachable, but exploitation depends on passive user interaction, and impact is confined to low confidentiality with no integrity or availability effect. No vendor patch or fixed version is identified - the vendor was contacted and did not respond - and there is no CISA KEV entry or confirmed public exploit code; the references include an external Google Drive link whose contents are not characterized in the available data.
Reflected cross-site scripting in RosarioSIS before 12.9.2 allows an unauthenticated attacker to break out of the double-quoted form action attribute on the Food_Service MenuReports page by supplying crafted menu_id (or modname) values through Modules.php, injecting an onmouseover handler that can steal session and CSRF tokens and let the attacker act as the administrator. Exploitation is gated by a hard prerequisite: a logged-in administrator must open the attacker's crafted link and interact with the injected element for the payload to execute in their session, which is why the CVSS 4.0 base score is 5.3 despite PR:N (user interaction is passive). The vendor addressed the flaw in version 12.9.2 (commit 08c871d wraps the reflected values in URLEscape()); no public exploit identified at time of analysis, and priority is triaged as this_month rather than emergency.
Frappe Builder before 1.36.1 lets any authenticated user bypass its SSRF guard by supplying a public URL that redirects, or DNS-rebinds, to internal or link-local addresses. The convert_to_webp endpoint lacks a permission decorator, so any authenticated Builder user can reach cloud metadata services, scan internal ports, or hang requests because no timeout is set; import_remote_assets and import_remote_fonts require Builder Page write permission. This is a moderate, non-emergency issue, and no public exploit was identified at time of analysis.
Missing authorization in Frappe Builder's builder.ai.api.improve_prompt endpoint lets any logged-in non-Guest session - including a Website User with no Builder access whatsoever - run LLM completions on the AI provider key the site owner configured for Builder, spending the owner's paid credits and returning the model output to the caller. Versions 1.33.0 through 1.35.x are affected; 1.36.0 removes the endpoint entirely. Exploitation still requires that an AI provider key (OpenRouter per the report) is actually stored in Builder's AI settings, and the impact is limited to resource consumption - no site data read or write, no system compromise. No public exploit code or CISA KEV entry was identified at time of analysis, and the vulnerability is scheduled for routine (this-month) handling rather than emergency response.
Missing authorization (CWE-862) in the WordPress plugin Contact Form by Supsystic, affecting all versions through 1.10.7, lets a remote attacker reach functionality that should have been gated by an access-control check without authenticating. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, 5.3) confines the impact to low integrity - an attacker may be able to make some unauthorized modification, but cannot disclose data or disrupt availability through this flaw. The precise plugin feature or action that lacks the authorization check is not described in the available sources, and no public exploit has been identified at time of analysis; priority is rated this_month.
Missing authorization (CWE-862) in the WPExperts APIExperts Square for WooCommerce plugin, affecting all versions up to and including 4.7.5, allows unauthenticated remote attackers to reach functionality that should sit behind an access-control check, with a partial integrity-only impact and no effect on confidentiality or availability (CVSS 5.3). The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates the flaw is reachable over the network against default configurations with no credentials and no user interaction, although the concrete protected function or data exposed is not described in the available sources. There is no KEV entry and no public exploit identified at time of analysis, and the practical exposure is bounded by the plugin's limited deployment footprint and the medium-severity, integrity-only rating.
Unauthenticated remote attackers can make limited unauthorized data modifications in Magepeople's Booking and Rental Manager for WooCommerce through version 2.8.2 because an access-control check is missing. The CVSS 5.3 rating reflects network reachability with no privileges or user interaction, but only low integrity impact and no confidentiality or availability impact. No public exploit code or CISA KEV entry was identified at time of analysis.
Authorization bypass in the Royal Elementor Addons WordPress plugin through 1.7.1069 lets remote attackers request data belonging to other users or objects by supplying an attacker-chosen identifier to a plugin endpoint. The assessed impact is limited to low confidentiality disclosure (C:L, I:N, A:N), with no data modification or denial of service, and no public exploit was identified at time of analysis. The CVSS 3.1 score is 5.3; the vector indicates PR:N, though the exact vulnerable endpoint and trigger are not described in the available sources.
Missing authorization (CWE-862) in the VillaTheme 'Bopo - WooCommerce Product Bundle Builder' WordPress plugin, affecting versions up to and including 1.2.3, lets remote attackers reach an incorrectly protected plugin function without any credentials - the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N scores 5.3, with integrity-only impact (C:N/I:L/A:N). Because no privilege check is enforced on the affected code path, an unauthenticated visitor can perform an action that should require elevated permissions, though the sources do not specify which action or endpoint. No public exploit has been identified at time of analysis and the flaw is not in CISA KEV; Patchstack's report places it in the 'this month' remediation tier rather than an emergency tier, reflecting the narrow plugin footprint and the limited integrity-only consequence.
WP Discussion Board, a WordPress plugin, fails to enforce an authorization check on one of its functions in versions up to and including 2.6.0, letting remote visitors reach data or actions that should have been restricted by access-control configuration. The assessed vector (CVSS 5.3, AV:N/AC:L/PR:N/UI:N) means the flaw is exploitable over the network without credentials or user interaction against a default-exposed WordPress site, but the impact is bounded to low confidentiality exposure (C:L, I:N, A:N) rather than data modification or code execution. No public exploit code is identified at time of analysis, there is no CISA KEV listing, and the priority label is 'this_month'; the exact vulnerable endpoint, parameter or plugin configuration that triggers the missing check is not described in the available sources.
Heap-based buffer overflow in the OLE2 parser of GNOME libgsf (function ole_info_read_metabat in gsf/gsf-infile-msole.c) affects versions up to 1.14.60 and allows remote attackers to corrupt heap memory when a victim opens, previews, or otherwise processes a crafted OLE2 compound document with an application that relies on the library. The required user interaction (UI:P) prevents a fully unattended trigger, and the assessed impact is limited to low confidentiality, integrity and availability effects rather than confirmed code execution. No public exploit identified at time of analysis; an upstream fix commit has been published, and the issue fits a routine monthly patch cycle rather than an emergency response.
Improper initialization in the WiFi Configuration component of the Yoosee GM8135S Camera (firmware 21.00.01.36) lets an attacker positioned on the same local or WiFi network manipulate the wpa_supplicantX.conf file, with the impact assessed as limited to integrity (no confidentiality or availability loss). Exploitation is rated as high complexity and difficult by both the CVSS vectors and the vendor, no authentication or user interaction is required, and the mechanism that actually triggers the improper initialization is not described in the available sources. A public writeup reference exists (not verified as working exploit code), the EPSS-style signal and vuln.today decision label are both low ('monitor'), and this is a low-priority issue on every available signal; the vendor was contacted but did not respond, and no fixed version is listed.
Reflected cross-site scripting (CWE-79) in the video library web application of the Castile-La Mancha Regional Parliament allows remote, unauthenticated attackers to execute arbitrary JavaScript in a victim's browser when the victim interacts with attacker-crafted content or a crafted URL (CVSS 4.0 base 5.1, Medium). The application embeds user-supplied content into the page without sanitising it before rendering, so the payload executes in the security context of the site; because the flaw is reflected there is no stored payload and each victim must be individually lured, which is the main limiting factor. Impact is bounded to Low confidentiality and integrity within the browser session of users of this single, narrowly deployed application. No public exploit has been identified at time of analysis and there is no CISA KEV entry; the priority label assigned by vuln.today is this_month.
Reflected cross-site scripting in the Zuinq Studio IsMyGym gym management software reservation endpoint lets remote attackers inject arbitrary JavaScript through the 'ret' parameter, which is echoed back in the HTTP response without sanitization. Rated 5.1 under CVSS 4.0 (assessed CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), the flaw requires the victim to actively open a crafted link, after which the script executes in that user's browser session with the privileges of that session. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the affected version range is not enumerated - the CPE is a wildcard covering all IsMyGym releases; INCIBE published the originating advisory.
Stored cross-site scripting in the web interface of WolfVision Cynap collaboration devices allows an attacker who can influence a stored, externally supplied value to execute script in the browser of another user who later views the page rendering that value. The flaw affects the Cynap Videobar (before 1.72e), the Cynap Pro, Cynap Core Pro, Cynap Receiver, Cynap Pure, Cynap Pure Mini and Cynap Pure Pro family (before 1.78a), and Cynap Pure (Next Gen) and Cynap Bridge (before 2.00d), with Cynap, Cynap Core and Cynap Pure SDM also listed by the EUVD record. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) the attacker needs some level of authenticated access to write the value and the victim must be induced to load the affected page, so this is stored XSS rather than unauthenticated remote code execution; no public exploit has been identified at time of analysis and EPSS is low at 0.25% (17th percentile).
Cross-site scripting in DOMPurify versions up to and including 3.4.16 lets an attacker slip a javascript: URL past the sanitizer's SMIL guard when the integrating application parses content with PARSER_MEDIA_TYPE set to 'application/xhtml+xml' and allowlists the SVG animate (or set) element together with the camelCase attributeName attribute. In that mode the guard that strips attributeName="href" never fires, so a sanitized SVG keeps an <animate> that rewrites its parent link's href, and a victim who clicks that link executes the injected script. Exploitation requires this non-default configuration plus user interaction, which is why the vendor classifies it as a hardening bug rather than a default-config bypass; EPSS is low at 0.22% (12th percentile), there is no CISA KEV listing, and a public proof-of-concept shipped with the advisory demonstrates the behavior in Chrome, with the vendor releasing 3.4.17 as the fix.
DOMPurify 3.4.4 through 3.4.16 can be made to preserve attacker-chosen template expressions in the text content of an attached shadow root when SAFE_FOR_TEMPLATES is enabled together with a DOM-returning mode (RETURN_DOM, RETURN_DOM_FRAGMENT or IN_PLACE); because a disallowed separator element can sit between two individually harmless text fragments, the fragments become adjacent once that element is removed and reconstitute a complete `${...}`, `{{...}}` or `<%...%>` expression. The exposure is not a default-configuration flaw: the application must sanitize a DOM node that already carries a shadow root and must subsequently feed that shadow root's textContent or innerHTML into a template evaluator, so real impact depends entirely on the downstream engine's evaluation context. Severity is mid-tier and conditional - EPSS is 0.18% (7th percentile), there is no CISA KEV entry, and the vendor has released a fix in 3.4.17; a public PoC reference (a demonstration snippet in the GitHub advisory) exists but is not verified as working exploit code.
DOM-based XSS in DOMPurify (all versions before 3.4.17) survives sanitization when an application runs IN_PLACE mode with a hook that removes a parent, ancestor, or not-yet-visited sibling: the detached subtree is never walked or neutralized, so an already-loading <img onerror> fires after sanitize() returns. Exploitation is conditional on that specific non-default configuration - remote, unauthenticated, but requiring user interaction and attacker markup containing a deferred handler - and the vendor has released 3.4.17 with a fix (PR 1672 / commit a77a3e7). Risk signals are modest and this is not an emergency: EPSS is 0.16% (6th percentile), there is no CISA KEV entry, and priority is 'this_month'; the vendor advisory itself includes a public proof-of-concept that demonstrates the handler firing in Chromium.
ECDSA JWS signature malleability in erlang-jose (potatosalad:jose) 1.0.0 through 1.11.12 lets anyone holding a single legitimately issued ES256/ES256K/ES384/ES512 token produce multiple distinct signature byte strings that all verify against the same key, because verify/4 never checks the RFC 7518 §3.4 fixed signature length. It cannot forge new payloads or impersonate a signer - the underlying (r, s) pair is unchanged - but it defeats controls that assume a token or signature is unique, such as token-revocation-by-hash, replay/idempotency caches and deduplication keyed on raw signature bytes; applications that enforce uniqueness via a claim such as jti are not meaningfully affected. Exploitation requires an already-valid token as input (assessed vector AV:N/PR:L), a demonstration PoC reference ships with the vendor advisory but it is not verified as working exploit code against third-party deployments, EPSS is 0.09% (1st percentile), there is no CISA KEV listing, and the vendor released a fix in 1.11.13.
Cross-site request forgery in boneIO Black controllers lets a malicious webpage drive state-changing API calls - rebooting the device, toggling relay circuits, moving gates and blinds, or shutting it down - against any reachable unit. All versions before 1.6.0 are affected, and because authentication is disabled by default (CVE-2026-77053), any user on the same internal network who visits an attacker-controlled page can trigger those actions; where authentication is enabled, the missing CSRF tokens and Origin/Referer checks still allow forged requests to ride an existing session. Exploitation is unauthenticated (PR:N) but requires the victim to open the malicious page (UI:A), no public exploit has been identified at time of analysis, and the vendor fixed the issue in 1.6.0.
Out-of-bounds read in NXP's MCUXpresso SDK USB middleware (mcuxsdk-middleware-usb) before 2.13.0 allows a malicious USB host to disclose device memory by sending RNDIS SET messages for OID_GEN_CURRENT_PACKET_FILTER or OID_802_3_MULTICAST_LIST with an out-of-range informationBufferOffset. The CDC RNDIS device-class handler USB_DeviceCdcRndisSetCommand() validated informationBufferLength but trusted the host-supplied offset, so the read can run beyond the fixed command buffer. Exploitation requires physical USB access to an affected MCU that exposes the RNDIS function to an untrusted host; no public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Stored cross-site scripting in the Webasyst Framework Photos app (through 4.4.0) allows an authenticated backend user with album edit rights to save a crafted 'url' value that executes JavaScript in an administrator's backend session when the album settings dialog is opened. The issue is rated 5.1 (medium) and requires victim interaction; it is not remotely exploitable without a backend account and album-edit permission. No CISA KEV entry was identified and no public exploit identified at time of analysis, and the available data does not list a fixed version.
Server-side request forgery in Kameleo's proxy-validation feature affects versions up to and including 5.0.1.26 and lets an authenticated low-privilege user who interacts with the proxy tester manipulate the host and port arguments of InternalController.TestProxy so the client-engine application issues requests to destinations of the attacker's choosing. The assessed impact is limited (CVSS 5.1; low confidentiality, integrity, and availability impact), and exploitation requires access to the Kameleo client-engine API plus passive user interaction. No public exploit code has been identified at time of analysis and there is no CISA KEV entry; upgrading to 5.2.0 removes the vulnerable route.
NocoDB through 2026.08.0 has a medium-severity race condition in its password-reset flow, implemented in packages/nocodb/src/services/users/users.service.ts, with low impact on confidentiality, integrity, and availability. Exploitation is remote but requires a low-privileged authenticated account and interaction with the reset flow; the exact trigger sequence is not described in the available sources. No public exploit was identified at time of analysis, no fixed version is listed, and the vendor deleted the referenced GitHub issue without explanation.
A race condition was addressed with additional validation. This issue is fixed in macOS Golden Gate 27.2, macOS Sequoia 15.8.2, macOS Tahoe 26.7.2. An attacker may tamper with code-signed applications to execute arbitrary code in the application's context.
Out-of-bounds write in ExLlamaV2 0.3.0 through 0.3.2 can corrupt process memory when a crafted GPTQ-quantized model supplies manipulated g_idx index data that is processed by QMatrix::make_sequential in the CUDA extension. The issue is local-only and requires the victim to load an attacker-controlled model; impact is limited to integrity and availability with no confidentiality loss, and no public exploit was identified at time of analysis (EPSS 0.15%, low real-world priority).
A heap out-of-bounds read in libfvde's FileVault 2 encrypted metadata parser (metadata type 0x001a) can crash the application that opens an attacker-supplied volume, with impact limited to availability of the parsing process rather than data disclosure or code execution. The defect affects libfvde builds through the 20260923 snapshot and is reached when embedded XML plist data in an encrypted metadata block is not NUL-terminated, so libfvde_volume_open() executes an unbounded strlen that walks past the allocated heap block. The published CVSS 4.0 score is 4.8 (an assessed CVSS 3.1 vector of AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L matches the evidence), EPSS is 0.13% at the 3rd percentile, the issue is not listed in CISA KEV and is not confirmed actively exploited, and although a third-party technical write-up is referenced, no verified working exploit code is confirmed; realistic exposure is confined to forensic/DFIR tools and automated triage pipelines that ingest untrusted disk images.
Heap out-of-bounds read in gbsplay's VGM loader (vgm_open() in gbs.c) allows a crafted .vgm file to walk the command-stream parser past the end of its heap buffer and crash the player. All builds through 0.0.103 are affected; the trigger is a VGM stream containing wait opcodes without the 0x66 end-of-data terminator, which leaves the parse loop running to and beyond the buffer boundary. The vector is local and requires the victim to open or play the malicious file (CVSS:3.1/AV:L/AC:L/PR:N/UI:R), and impact is confined to availability - no code execution or confirmed disclosure. EPSS is 0.13% (3rd percentile), there is no KEV entry or confirmed active exploitation, no verified working exploit code is publicly available (a public technical write-up exists but is not verified as working exploit code), and a bounds-checking upstream fix commit is referenced.
Heap out-of-bounds read in libdwarf through 2.3.3's .debug_addr parsing path: dwarf_debug_addr_table() validates the unit length without including the table's starting offset, so an object file whose .debug_addr section declares a non-zero table offset slips past the size check and a later dwarf_debug_addr_by_index() call reads past the heap buffer. Only libdwarf-based consumers that actually parse an attacker-supplied object file are affected (local attack vector, user interaction required), and the outcome is bounded to disclosure of adjacent heap bytes or a crash. No confirmed active exploitation (not in CISA KEV) and EPSS is only 0.13% (3rd percentile); a public write-up and PoC reference exist but are not verified as working exploit code, and an upstream fix commit is available.
Heap out-of-bounds read in gbsplay 0.0.103 and earlier lets anyone who opens a crafted GBR file sized between 0x21 and 0x162 bytes read past the end of a heap buffer while gbr_open() in gbs.c scans the ROM title field, crashing the player or leaking a small amount of adjacent heap memory. The flaw is reachable in the default configuration with no special option enabled, but it requires the victim to load the attacker-supplied file locally, so it is a low-priority local issue with no code execution or integrity impact (CVSS 4.0 base 4.8; independent assessment CVSS 3.1 AV:L/AC:L/PR:N/UI:R, C:L/A:L; EPSS 0.13%, 2nd percentile). Vulnerability is not in CISA KEV and SSVC records exploitation as none; a public technical writeup describing the flaw exists, and an upstream fix commit is available.
Heap out-of-bounds write and read in HTSlib through 1.24 is triggered when a crafted .gzi BGZF index stores an entry count of 0xFFFFFFFF, which truncates the 32-bit noffs/moffs fields in bgzf_index_load_hfile() to zero and collapses the index allocation to malloc(0); subsequent writes past that buffer and an offs[-1] read in bgzf_useek() corrupt heap memory or crash HTSlib-based tools such as samtools and bcftools. The vector is local: the victim must load an attacker-supplied .gzi index file and then perform a seek, with assessed impact limited to Low integrity and Low availability - no confidentiality impact and no confirmed code execution. EPSS is 0.12% (2nd percentile), there is no CISA KEV listing, and a public technical write-up describing the truncation exists; it is not verified as working exploit code.
Kameleo through 5.0.1.26 can disclose profile information to a local, low-privileged user through the Profile Controller's ListProfiles function (CWE-200). The supplied CVSS 4.0 vector scores 4.8 (medium) with confidentiality-only impact; the vendor fixed it in 5.2.0, and the supplied intelligence does not confirm CISA KEV exploitation or working public exploit code.
vLLM's OpenAI-compatible server before 0.32.0 registers Starlette CORSMiddleware with allowed_origins defaulting to ["*"], so a malicious web page loaded by a victim can issue cross-origin requests to a vLLM server the browser can reach and read the responses. When no --api-key or VLLM_API_KEY is configured - the default - endpoints such as GET /v1/models and POST /v1/chat/completions are reachable, letting the page enumerate models, drive chat completions, burn GPU time, and read model output through the victim's browser; if a key is set, the guarded prefixes require that the caller already hold a usable token. Cookie-based CSRF does not apply because allow_credentials is False by default, and exploitation needs user interaction plus a browser-reachable server, which is why this scores only 3.4 and is tracked as monitor priority; no public exploit code was identified at time of analysis.
Script injection in seroval's JavaScript-output serializers lets a RegExp whose source contains '<' terminate an HTML <script> element and execute attacker script in the rendered page, affecting releases before 1.0.0 and from 1.5.5 up to but not including 1.6.10. The flaw only materializes in applications that build regular-expression syntax from untrusted input, serialize that RegExp through serialize, serializeAsync, crossSerialize, crossSerializeAsync, crossSerializeStream, Serializer or compileJSON, and embed the output inside a script element as server-side rendering commonly does; a victim must then load that page (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N, 4.7). EPSS is low (0.19%, 8th percentile), the issue is not in CISA KEV, and no public exploit has been identified at time of analysis, though the vendor has released 1.6.10 with the fix.
BRAIN2 installations up to and including version 3.09 can write the cleartext password of the Windows service account that runs the BRAIN2 MainService into a setup log file, but only when Microsoft SQL Server access is configured with Integrated Security and the service account is specified during the installation wizard. The log lands in the temporary directory of the administrator who ran the installer, which the vendor states is normally restricted to administrative users, so an attacker needs local access and effective administrative rights to reach the credential. CVSS 3.1 scores this 4.4 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N); no public exploit code has been identified at time of analysis and the issue is not in CISA KEV.
Image handling on unpatched Apple macOS releases can be driven into a buffer overflow that terminates the processing process, giving a denial-of-service outcome with no confidentiality or integrity impact. The flaw is addressed by improved bounds checking in macOS Golden Gate 27.2, macOS Sequoia 15.8.2 and macOS Tahoe 26.7.2, so only systems below those builds are exposed; exploitation requires the victim to process an attacker-supplied maliciously crafted image (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L, 4.3). No public exploit identified at time of analysis, SSVC records no known exploitation and EPSS is 0.48% (41st percentile), making this a this-month, low-urgency patch item rather than an emergency.
Missing authorization in the VillaTheme Customer Coupons for WooCommerce plugin, affecting versions through 1.3.14, allows an authenticated low-privilege user such as a registered customer to perform a sensitive coupon-related action without the required permission check. The flaw is rated CVSS 4.3 (Medium) with limited integrity impact only-no confidentiality or availability impact-and no public exploit has been identified at time of analysis. The trigger endpoint and exact action are not described in the available sources; exploitation requires a WordPress site running WooCommerce and the vulnerable plugin plus a valid low-privilege account.
Zephyr's Bluetooth host (subsys/bluetooth/host, versions 2.3.0 through 4.4.2) can be driven to permanently strand connection reservations: when CONFIG_BT_EXT_ADV_MAX_ADV_SET > 1 and an application runs a directed and an undirected connectable extended advertising set on the same identity, an adjacent, unauthenticated attacker who freely chooses an initiator address mapping to the directed set's target causes the wrong bt_conn to be consumed, leaving the undirected set's reservation unreleasable. Each occurrence burns one CONFIG_BT_MAX_CONN slot until bt_disable() or reboot, and repeated attempts against applications that restart the directed set after each disconnect exhaust the pool so connectable advertising fails with -ENOMEM; the directed set also keeps advertising without a reservation, so genuine connections on it are dropped. Impact is availability only (no memory corruption or information disclosure), the vulnerable configuration is non-default on both Kconfig options, and no public exploit code was identified at time of analysis and the issue is not in CISA KEV.
Missing authorization in APIExperts Square for WooCommerce through 4.7.5 lets an authenticated low-privilege user (PR:L) perform limited unauthorized changes, with CVSS 4.3 and integrity-only impact. The flaw is in the WordPress plugin slug woosquare and is classified CWE-862; no public exploit code is identified at time of analysis. No fixed version is specified in the available advisory data, so sites should monitor the vendor/Patchstack record for an update.
Cross-site request forgery in the WordPress plugin Media Library Assistant through version 3.42 lets an attacker induce a logged-in site user to submit a forged request in that user's existing session, producing low-integrity changes with no confidentiality or availability impact. This is a moderate-severity, low-priority issue rather than an urgent one: the attacker needs no account or privileges of their own but cannot succeed without a victim authenticated to WordPress who is tricked into visiting attacker-controlled content. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Missing authorization in the VillaTheme DEPART WordPress plugin (depart-deposit-and-part-payment-for-woo) through version 1.0.10 allows an authenticated low-privilege user to perform an action that should require higher permissions, resulting in limited integrity impact on the affected WooCommerce store. The flaw is rated CVSS 4.3 (CWE-862) with network reachability and no user interaction required, and it only affects sites where the plugin is installed and active. No public exploit identified at time of analysis, and the risk signals (EPSS/KEV absent, patch-level priority 'this_month') point to a moderate, non-urgent issue rather than an emergency.
Missing authorization in the Meow Apps AI Engine plugin for WordPress (versions from n/a through 3.8.6) lets an authenticated low-privilege user - for example a subscriber on a site that allows self-registration - perform actions that should require higher capabilities, with impact limited to integrity modification. The flaw is remotely reachable and low-complexity (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, 4.3) but requires an existing account, and there is no confidentiality or availability effect. No public exploit code has been identified at time of analysis; the issue is tracked for remediation this month rather than as an emergency.
The Payment Gateway WordPress plugin through 2.2.0 does not ensure a shared secret is configured before using it to authenticate the bank's payment-notification callback, allowing unauthenticated attackers to forge a valid notification and mark any WooCommerce order as paid on installs where the secret has not been set, and the same callback lets them move any pending order to a failed state whether or not the secret is configured.