RCE
Monthly
Arbitrary file write - escalating to remote code execution on hosts that execute PHP from upload directories - affects the WordPress plugin Photo Gallery, Sliders, Proofing and Themes in all versions before 4.5.0. The flaw sits in the archive-extraction routine: a variable is reused as a loop counter, so the filename-extension check always passes and a user who has been granted the plugin's gallery-management capability by an administrator can place an attacker-controlled file (including a .php payload) into a web-accessible gallery directory; the CVSS vector (PR:H, UI:N) confirms this is an authenticated, elevated-privilege path rather than a subscriber or anonymous one. Publicly available exploit code exists, so exploitation is realistic for any site where a non-administrator holds the gallery-management role, and full code execution depends on the host actually serving PHP out of the upload path - on hardened hosts the impact is limited to arbitrary file write.
Remote code execution in Mistral Vibe before 2.25.5 allows an attacker to run arbitrary shell commands with the privileges of the user running the tool, because worktree creation executes a repository's own git hooks - notably the post-checkout hook and the fsmonitor command - before any workspace trust validation takes place. The attack requires the victim to deliberately open, clone, or check out an attacker-controlled repository (user interaction is mandatory, and the request itself is unauthenticated per the CVSS PR:N vector), and code execution is bounded by the permissions of the Vibe user, with no privilege escalation or server-side attack surface. There is no public exploit identified at time of analysis and the flaw is not confirmed as actively exploited; a vendor-released patch in 2.25.5 addresses the ordering bug.
Code execution in OpenPanel's js-runtime component lets an authenticated user who holds project write access escape the JavaScript webhook template sandbox and run arbitrary code inside the worker process. The template validator fails to block computed (bracket-notation) member access that traverses a constructor chain to the Function constructor, so merely creating or editing a webhook template is sufficient - no user interaction is required (UI:N). No public exploit code has been identified at time of analysis, and no CISA KEV or EPSS signal was supplied, but our independent assessment rates this a genuine high-priority issue, with CVSS 3.1 AV:N/PR:L/UI:N/S:C/C:H/I:H/A:H (scope change to the host system and full confidentiality, integrity and availability impact).
Authenticated users with subscriber-level access or higher can execute arbitrary WordPress shortcodes through the ProfilePress plugin (slug wp-user-avatar) in all versions up to and including 4.17.2, because user-controlled values reach do_shortcode() without validation. Exploitation requires a low-privilege account, which is trivially obtained on sites that enable the plugin's self-service registration feature, and no user interaction is needed; however, the practical impact is variable and often limited, since substantial confidentiality or integrity loss only materializes when other privileged or data-exposing shortcodes are registered on the same site. The vendor's upstream severity rating is 8.1, while independent assessment rates the realistic vector as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N (limited C/I, no availability impact); no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Remote code execution in The Welcomizer WordPress plugin versions up to and including 2.8.1 lets authenticated users with Subscriber-level access or higher execute arbitrary PHP on the server by abusing the twiz_ajax_callback AJAX action's savesection handler. The handler checks a nonce but omits a current_user_can() capability check, and eval() processes attacker-supplied PHP from the twiz_custom_logic POST parameter when output is set to twiz_logic_output; the nonce is exposed to any authenticated user via twiz-ajax.js.php, so it does not prevent exploitation. Wordfence reports this with CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), and no public exploit identified at time of analysis.
Arbitrary PHP function invocation in the Save as PDF Plugin by PDFCrowd for WordPress (all versions up to and including 4.6.1) allows any authenticated user with Contributor-level access or higher to have the server AES-encrypt an attacker-chosen pdf_created_callback value into a valid button blob, which is later passed to PHP as a callable when any unauthenticated visitor POSTs that blob to the wp_ajax_nopriv_save_as_pdf_pdfcrowd AJAX endpoint. Published CVSS 3.1 is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); our assessment retains the High rating but bounds the impact to C:H/I:L/A:L because the invoked callback receives only the plugin's options array as its single, fixed argument, making disclosure of the site's stored PDFCrowd API key and username the most reliable outcome rather than fully attacker-controlled code execution. Contributors are required only to mint the blob - the trigger replay is unauthenticated - and no public exploit identified at time of analysis, with no confirmed actively exploited (CISA KEV) status.
Shortcode injection in the WP Recipe Maker plugin for WordPress (all versions up to and including 10.8.1) lets an attacker plant arbitrary registered shortcode tokens inside the content of an approved wprm-comment-rating comment, which the plugin later feeds through do_shortcode() during recipe metadata generation and reflects into the JSON-LD reviewBody field served on every recipe page render. Because execution occurs before the plugin's strip_shortcodes()/wp_strip_all_tags() cleanup runs on the resulting string, output from sensitive shortcodes (attachment captions, private post fields, other data exposed by installed shortcodes) can be disclosed to any visitor loading the affected page. The CVSS vector records PR:N, so the injection itself is unauthenticated, but practical exploitation is gated by the site's comment-approval threshold and by whether installed shortcodes actually expose sensitive content; the vendor score of 9.1 is assessed as inflated relative to an AC:H/I:L reality, and no public exploit code has been identified at time of analysis.
Unauthenticated attackers can execute arbitrary WordPress shortcodes through the Forminator Forms plugin (all versions up to and including 1.57.2) because a value reaching do_shortcode in the quizzes front-action handler is not properly validated. A site is only reachable through this path if Forminator is installed and active and a form or quiz routes through the vulnerable front-action, and the real-world damage is bounded by which shortcodes other installed plugins register - benign shortcodes mean limited impact, while data- or state-changing shortcodes raise it substantially. No public exploit code or confirmed in-the-wild activity (CISA KEV) was identified at time of analysis; note that the vendor-assigned CVSS 9.1 overstates the assessed impact, which our analysis places at CVSS 6.5 (C:L/I:L) for fully remote, unauthenticated, low-complexity exploitation.
Unauthenticated arbitrary file upload in the Gravity Forms WordPress plugin through version 3.1.0.4 can lead to remote code execution on any site whose publicly reachable form contains a File Upload field with its Visibility set to 'Hidden', because hidden upload fields skip the extension-validation step and a rejected file's intact upload state is subsequently persisted by upload_file() without re-validation. Per the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), no credentials or user interaction are required (PR:N/UI:N) and the attack is fully remote (AV:N), but the non-default hidden File Upload field is a mandatory precondition; a secondary practical limiter is that code execution depends on the server actually executing the uploaded file type in the upload directory. No public exploit code and no CISA KEV entry were identified at time of analysis, yet the combination of unauthenticated access, arbitrary file write and PHP-execution potential makes this a high-priority fix for any installation that meets the precondition.
Remote code execution in WP Photo Album Plus affects all versions through the wppa_image_magick path, allowing authenticated attackers with subscriber-level access and above to run server-side code when the site uses ImageMagick processing. The issue is argument injection into an ImageMagick command executed via PHP exec(), enabled by insufficient sanitization of the multipart upload filename and reliance on escapeshellcmd() instead of proper argument quoting. Exploitation requires ImageMagick to be available and the plugin to route uploads through ImageMagick rather than GD, and no public exploit was identified at time of analysis; CVSS 3.1 base score is 7.5 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H).
Out-of-bounds heap write in FluidSynth's command handler lets an attacker supply an out-of-range channel argument to the pitch_bend_range command, which is written through the selected synth channel without bounds checking. The worst-case exposure is unauthenticated remote code execution or denial of service (CVSS 3.1 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) when FluidSynth runs as a TCP command server via new_fluid_server() or 'fluidsynth -s'; absent that network mode, the flaw is only locally reachable through malicious commands fed to the interactive shell on standard input, and applications that embed the library without the shell, command handler, or TCP server are unaffected. The vendor has released a fix in FluidSynth 2.5.6 (spanning affected releases from 1.1.2); no public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV).
PHP object injection in Cotonti 1.0.0 allows authenticated users with comment-write permissions to pass attacker-controlled base64-encoded data through the cb (comeback) parameter of the comments plugin EditAction, which is then unserialized without an allowed_classes restriction. This can lead to arbitrary PHP object instantiation and, only if a viable POP gadget chain exists among loaded classes, escalation to file write or remote code execution. No public exploit code or active exploitation has been identified at time of analysis; the vendor has published a fix in PR #1897, and the vendor CVSS 4.0 score is 7.7, while the independent CVSS 3.1 assessment is AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
Arbitrary code execution is possible on IBM Guardium Data Protection 12.2 when a remote attacker who already holds high-privilege credentials abuses a file-handling feature that fails to constrain a user-supplied pathname to its intended restricted directory (CWE-22). The requirement for HIGH privileges (PR:H) on the management interface is the primary limiting factor, restricting realistic exploitation to trusted administrative accounts on an appliance that is normally deployed on internal or segmented networks, though no user interaction is required (UI:N). The vendor has published a fix advisory, and no public exploit identified at time of analysis (no CISA KEV listing and no published proof-of-concept in the supplied intelligence).
Arbitrary file upload in WP Cloud Plugins (Use-your-Drive, Out-of-the-Box/Dropbox, Share-one-Drive/OneDrive-SharePoint, and Lets-Box/Box) versions 2.0 through 3.8.3 lets attackers with subscriber-level access write executable files to the WordPress uploads directory, enabling remote code execution (CVSS 8.8). The vulnerable download_file_to_uploads function is reachable through an import AJAX action that is also registered via wp_ajax_nopriv_ and lacks a capability check in can_import(), so the effective authentication prerequisite may be lower than the CVSS PR:L rating suggests, though exploitation still requires one of the four plugins installed and active and depends on the host allowing PHP execution inside wp-content/uploads. No public exploit code identified at time of analysis and the issue is not listed in CISA KEV.
Unauthenticated insecure deserialization in the Change Audit System (CAS) listener of IBM Guardium Data Protection 12.2 allows a network attacker who can reach TCP port 16017 to submit crafted serialized messages that are insecurely deserialized and used for attacker-controlled reflective method dispatch, potentially resulting in unintended code execution on the Guardium appliance with high confidentiality, integrity, and availability impact. The vendor-reported base score is 9.8 (AV:N/AC:L/PR:N/UI:N); our independent assessment keeps the unauthenticated, no-user-interaction profile but applies AC:H, because the practical gating factor is whether an attacker has a network path to the non-standard CAS port rather than any product configuration toggle. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV); IBM has published a vendor patch advisory, and this should be treated as a genuinely high-priority issue for any deployment where port 16017 is reachable from untrusted networks, while remaining lower-risk in segmented or hardened environments where the listener is internal-only.
Unauthenticated remote code execution in IBM Guardium Data Protection 12.2 lets a network attacker who can reach the appliance interface that processes serialized input run arbitrary code in the context of the affected service, yielding full loss of confidentiality, integrity and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). The root cause is insecure deserialization of untrusted data (CWE-502), and because the assessed vector carries PR:N and UI:N, no credentials or user interaction are needed, so real-world exposure is determined almost entirely by network reachability to the Guardium management/collector segment rather than by the public internet. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV; IBM has published a vendor patch, which keeps this a top-tier remediation priority rather than an actively exploited emergency.
Heap-based buffer overflow in the IBM MQ C client shipped with IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 lets a remote attacker who controls the queue manager's responses crash the client process or potentially execute arbitrary code in its context (CVSS 3.1 base 8.1). The flaw is triggered when the client requests AMS (Advanced Message Security) policy data and the client fails to properly validate the returned queue manager response; exploitation is unauthenticated from the client side (PR:N) but requires the attacker to operate a malicious or compromised queue manager or to man-in-the-middle the client-to-queue-manager channel, which is why the vector carries AC:H. No public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor patch is available.
An integer overflow in IBM MQ's MQINQ (inquire object attributes) request processing lets an authenticated remote user crash the queue manager and, per the vendor, potentially execute arbitrary code, giving the issue a CVSS 3.1 base score of 8.8 with high confidentiality, integrity and availability impact. Exploitation is network-based against the queue manager listener (default 1414/tcp), requires valid MQ credentials or connection authority (PR:L) and no user interaction; the vendor describes reliable code execution as a potential rather than confirmed outcome, so denial of service is the more assured impact. No public exploit identified at time of analysis, and a vendor fix is available per the IBM advisory.
IBM MQ for HPE NonStop versions 8.1.0 through 8.1.0.40 contain a heap-based buffer overflow (CWE-122) that is triggered during queue manager startup when improperly validated cluster migration data is processed. The flaw is exploitable only by an authenticated attacker who can supply crafted migration data to a queue manager participating in MQ clustering, and the dependable outcome is a denial of service (queue manager startup failure or crash), with arbitrary code execution considered only potentially achievable. Independent assessment rates the realistic impact lower than the vendor's 7.5 score (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H), and there is confirmed no public exploit code and no CISA KEV listing - no public exploit identified at time of analysis. A vendor patch is available via IBM support page node 7287705.
Code injection in Mongoid allows unauthenticated attackers who can influence a query argument to execute arbitrary JavaScript in the MongoDB server via a string-typed query criterion, leading to disclosure of stored field values, unintended document selection for writes, and reduced database performance. The vulnerability affects Mongoid versions 8.0.0 through 8.0.12, 8.1.0 through 8.1.12, 9.0.0 through 9.0.11, and 9.1.0, but exploitation requires the application to pass externally influenced string criteria to the query builder and the MongoDB deployment to permit server-side JavaScript evaluation. No public exploit identified at time of analysis.
Arbitrary Python code execution in LMDeploy 0.12.1 through 0.12.2 lets an attacker who publishes a malicious model on HuggingFace Hub run code on any machine that loads it, because the model's `quantization_config.quant_dtype` string is interpolated into `eval(f'torch.{quant_dtype}')` at lmdeploy/pytorch/config.py:620 without any validation. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) reflects that exploitation is remote and unauthenticated but requires the victim to actively load the attacker-supplied model, confirmed by our independent assessment that UI:R is the limiting factor and that the `_update_torch_dtype` whitelist at line 53 only guards `torch_dtype`, not `quant_dtype`. Publicly available proof-of-concept code exists in the vendor advisory (repo-level proof using a mocked HF config that yields `uid=0(root)`), but there is no confirmed actively exploited (CISA KEV) status, and no EPSS score was supplied; a fixed release, 0.12.3, is available.
Unauthenticated remote code execution in LMDeploy 0.9.2 through 0.15.x lets any attacker who can reach a DistServe/PD-disaggregation deployment's POST /distserve/p2p_connect endpoint run arbitrary code with the privileges of the LMDeploy serving process. The endpoint accepts an attacker-supplied ZeroMQ peer address; the engine connects to it and deserializes the reply with PyZMQ's recv_pyobj(), which is backed by Python pickle and therefore executes code during object reconstruction, before any type or schema check can run. Rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-502); exploitation is unauthenticated only in the default configuration where the operator has not enabled API-key authentication, and no public exploit code has been identified at time of analysis. A vendor patch is available in LMDeploy 0.16.0, which replaces the pickle-based ZeroMQ protocol with JSON plus Pydantic validation.
Physical-access arbitrary code execution on Carecam HMT.CM2507 IP cameras, where firmware automatically runs a predetermined script from attached removable media without verifying its authenticity or integrity. An attacker who can reach the camera's SD/USB interface and insert crafted media can execute code in the device's security context, achieving high confidentiality, integrity and availability impact; the assessed CVSS 3.1 vector (AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects that no credentials or user interaction are needed once physical access is obtained, and that this is the primary limiting factor since there is no network-facing path to the flaw. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV - exploitation requires an attacker with hands-on access to the hardware.
Heap-based memory corruption in the IBM MQ for HPE NonStop queue manager lets an attacker who already holds a valid, low-privileged authenticated channel connection (PR:L) crash or potentially take over the broker by sending a message carrying a malformed distribution list structure, yielding the full confidentiality, integrity and availability impact reflected in the CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is a heap buffer overflow (CWE-122) arising from improper validation of the multi-recipient list records embedded in an MQ message, so exploitation is network-reachable and requires no user interaction, but it is not reachable pre-authentication or against a default queue manager configuration. IBM has published a vendor patch and no public exploit code or evidence of active exploitation was identified at time of analysis.
Integer overflow (CWE-190) in IBM MQ distribution list processing lets an authenticated user with PUT authority to a distribution list send a crafted MQPUT message that corrupts memory handling, reliably crashing the queue manager and potentially enabling arbitrary code execution. The flaw is network reachable with low complexity and no user interaction (CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8 High), but requires a valid MQ session plus put/queue authority on a reachable queue manager, so it is not exploitable by unauthenticated attackers. No public exploit code or confirmed active exploitation has been identified at time of analysis; an RCE outcome is not confirmed and the reliably achievable impact against affected versions is denial of service, while IBM has published a vendor fix.
IBM MQ queue managers that process XA (X/Open distributed) transactions are vulnerable to a memory-corruption buffer overflow triggered when a malformed XA transaction identifier (XID) is parsed, allowing an authenticated attacker with network access to crash the queue manager and potentially execute arbitrary code in its context. Exploitation requires valid credentials and the ability to drive XA transaction operations over an MQ channel (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, vendor score 8.8), so the reliably achievable outcome is denial of service while code execution remains a potential, not guaranteed, consequence. There is no public exploit identified at time of analysis and no confirmed active exploitation, but a vendor patch is available and the low attack complexity combined with the complete loss of confidentiality, integrity and availability impact makes prompt remediation important.
Heap buffer underflow in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated remote attacker to crash or destabilize the queue manager, and potentially to execute arbitrary code, by submitting a crafted multi-segment message that is reassembled during processing. The dependable outcome is denial of service: reliable code execution is not confirmed, and exploitation requires valid low-privilege credentials (PR:L) plus access to a channel or queue that accepts submitted messages. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; urgency is real but constrained because only the specialized HPE NonStop build is affected, not general IBM MQ distributions.
IBM MQ queue managers running affected releases can be crashed - and, per IBM, potentially have arbitrary code executed on them - by an authenticated participant in an MQ cluster that sends cluster command messages with malformed length fields. The flaw affects MQ 9.1.0.0 through 9.1.0.37 LTS, 9.2.0.0 through 9.2.0.43 LTS, 9.3.0.0 through 9.3.0.41 LTS and 9.3.0.0 through 9.3.5.1 CD, 9.4.0.0 through 9.4.0.25 LTS and 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0; it is network-reachable (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8 HIGH) but requires a valid cluster identity, and IBM frames code execution only as a possibility while denial of service is the more certain outcome. No public exploit code exists and no public exploit was identified at time of analysis - CISA SSVC records Exploitation: none and Automatable: no - while EPSS estimates exploitation likelihood at roughly 0.36% (29th percentile), so priority should be driven by exposure of clustered queue managers rather than by observed attack activity.
Remote code execution in IBM MQ Java and JMS client libraries allows an authenticated attacker with access to a message queue or topic to bypass the deserialization allow-list filter in exception handling and execute arbitrary code on client applications. The flaw is network-reachable but requires low-privileged authentication (PR:L) and is limited to a specific exception-handling path (AC:H), with impact confined to the client process rather than the MQ server. No public exploit code was identified at time of analysis.
A pre-authentication heap buffer overflow in IBM MQ Appliance protocol message processing lets a remote, unauthenticated attacker crash the appliance (denial of service) or potentially execute arbitrary code in the context of the MQ appliance firmware. Only network reachability to the appliance's protocol message listener is required - no credentials, session, or user interaction - and the vendor rates this 10.0 with a scope change, while our independent assessment keeps the same base metrics but scores scope as unchanged (S:U) because the overflow occurs in the MQ process itself rather than crossing a security boundary. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV), but the combination of a CVSS 10.0, zero-click pre-auth reachability, and confirmed code-execution potential makes this a genuine top-priority vulnerability rather than a high-CVSS-but-low-real-risk case; an IBM vendor advisory with a patch is available.
Malformed compressed data delivered over an IBM MQ channel that has compression enabled can trigger an out-of-bounds heap write, allowing a remote attacker to crash the queue manager and, potentially, execute arbitrary code in the MQ process. The issue affects IBM MQ 9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS / up to 9.3.5.1 CD, 9.4.0.0-9.4.0.25 LTS / up to 9.4.5.1 CD, and 10.0.0.0, with the CVSS base of 9.8 reflecting a network-reachable, unauthenticated worst case, though our assessed vector raises attack complexity to High (AC:H) because the channel must be explicitly configured with compression and reachable by the attacker. Denial of service is the readily achievable outcome, while reliable code execution requires defeating the process's memory protections; no public exploit code has been identified at time of analysis, SSVC rates exploitation as none, and EPSS is low at 0.37% (31st percentile).
Unauthenticated remote code execution affects the Interchange e-commerce platform (the interchange/interchange project) through its admin 'quick question' page, where attacker-supplied yes/no parameters flow into a reparsed [calc] template block and injected Perl is evaluated server-side. The flaw is reachable without authentication in default installations, as confirmed by the upstream fix adding a previously absent [if-mm super] superuser gate, and SSVC rates it Automatable with total technical impact; however, injected code executes inside Interchange's Safe compartment, so unrestricted, full-impact code execution additionally requires the non-default AllowGlobal directive to be enabled on the catalog being accessed. The vendor rates this 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) while our independent assessment rates it AC:H given the sandbox constraint; no public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor patch/advisory is available.
Stack-based buffer overflow in the web management server of PLANET IGS-5225-8P2T4S industrial managed switches allows a remote authenticated administrator to crash the device or, with carefully crafted input, potentially execute arbitrary code on the underlying operating system. Affected devices run V1 firmware before 1.2412b260707 or V2 firmware before 2.2412b260519, and exploitation requires valid administrative credentials plus network reachability to the switch's management interface; the high attack complexity means many payloads will only produce a denial of service rather than code execution. No public exploit has been identified at time of analysis, and PLANET has released fixed firmware for both branches.
Stack-based buffer overflow in the web management server of PLANET IGS-5225-8P2T4S industrial managed switches lets an authenticated remote attacker (PR:L) crash the device for a denial of service or, with greater effort, execute arbitrary code on the underlying operating system. Affected are V1 firmware before 1.2412b260707 and V2 firmware before 2.2412b260519; exploitation requires network reachability to the switch web interface, valid credentials, and high attack complexity (AC:H) to achieve reliable code execution, so a straightforward crash/DoS is the more accessible outcome. There is no confirmed active exploitation (CISA KEV) and no public exploit identified at time of analysis; vendor firmware fixes are available.
Privileged users of PLANET IGS-5225-8P2T4S industrial managed switches running V1 firmware before 1.2412b260707 or V2 firmware before 2.2412b260519 can activate undocumented debug functionality that ships enabled in the embedded software, reaching an OS command execution path that grants root-level access to the device. Exploitation requires high-privilege administrative/management access and local access to the device management plane (CVSS:4.0 AV:L/PR:H), so the realistic threat is a malicious insider or an attacker who has already obtained management credentials rather than an unauthenticated remote compromise. No public exploit code and no confirmed active exploitation were identified at time of analysis, and vendor-released patched firmware is available.
Authenticated code injection in XWiki Rendering (the xwiki-rendering-xml module, versions before 14.10.2) lets any user who can edit their own user profile - or any other document - close the surrounding HTML macro and inject Groovy or Python script macros that execute with programming rights, granting remote code execution and unrestricted read/write access to all wiki contents. Exploitation requires only a low-privilege, authenticated account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, severity 9.9) and needs no victim interaction beyond the affected page being rendered; the attacker reaches the flaw through rendered output that is embedded in an HTML macro without escaping, with exploitable sinks including the user profile (since XWiki syntax 2.0, demonstrably exploitable from XWiki 3.3 Milestone 1) and the extension point org.xwiki.platform.search.ui.docdoesnotexist (added in XWiki 8.3 Milestone 1). No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, though the vendor advisory documents a detailed reproduction payload and the scope change (S:C) combined with high confidentiality, integrity and availability impact makes this a genuine high-priority issue; vendors have released the fix in XWiki 14.10.2 and 15.0 RC1.
Local privilege escalation in Sublime Text for Windows - Sublime Text 4 through Build 4192 and Sublime Text 3 through Build 3207 - lets an authenticated local attacker who already holds an unprivileged account plant a malicious DLL in the user-writable update staging directory under %LOCALAPPDATA%, mark it read-only to defeat the installer's cleanup pass, and have the elevated installer copy the payload into the protected installation directory, where it executes in the context of any higher-privileged user who later launches the editor. The attack is local-only and conditional: it requires a prior foothold on the host, depends on the update staging mechanism being reached, and fires only when an elevated user subsequently opens the application (passive user interaction). Risk is real but situational rather than a mass-exploitation threat, and publicly available exploit code exists in the form of a published gist, so EPSS-style prioritization should focus on multi-user Windows endpoints where a standard user and an administrator both use the same Sublime Text install. No vendor-released patch is identified in the available data at time of analysis.
Remote code execution in ClipBucket v5 (all releases before 5.5.3-#182) allows an authenticated low-privileged user to upload a PHP file that is stored and later executed by PHP-FPM, yielding full server compromise. The photo upload endpoint validates only the file's MIME type/magic bytes but never rewrites the extension, so a payload beginning with valid image magic bytes retains its .php extension on disk (CWE-434, CVSS 4.0 base 8.7 / independently assessed CVSS 3.1 as AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:H). Exploitation requires only a standard account - readily self-registered on default deployments with open registration - plus a web-executable upload directory served by PHP-FPM; there is no unauthenticated path and no public exploit code identified at time of analysis, and the issue is not confirmed actively exploited (not in CISA KEV).
Sandbox escape in vm2 3.12.0 and earlier allows unauthenticated remote attackers who can supply JavaScript to an application embedding vm2's VM or NodeVM to break out of the sandbox and execute arbitrary code on the host, provided the embedder exposes at least one host API returning a host-realm (native) Promise whose rejection value is host-pivotable - the advisory cites a host process object as the example. The flaw is an incomplete rejection-sanitization failure in lib/bridge.js: the sandbox-side Symbol.species and .then neutralization is installed only on the sandbox intrinsic Promise.prototype, so it never applies to host Promises, letting sandboxed code overwrite p.constructor[Symbol.species] and call p.then() without an onRejected handler, after which V8's internal Thrower re-throws the raw host rejection value into an attacker-controlled resolve/reject closure, bypassing handleException and hostPromiseSanitizeReject and yielding an unsanitized, fully functional bridge proxy of the host object. No public exploit identified at time of analysis, but the CVSS 4.0 base score is 10.0 and the issue is fixed in 3.12.1.
Sandbox escape in vm2 through 3.12.0 lets unauthenticated remote attackers execute arbitrary code on the host when the embedding application exposes at least one non-strict (sloppy-mode) host function to the sandbox. By calling such a function with a nullish receiver (`fn()`, `fn.call()`, `Reflect.apply(fn, undefined, [])`, etc.), sandboxed script causes V8 to substitute the host realm’s global object for `this`, which vm2 then wraps and returns as a live proxy of the host global; the attacker can then reach `process` and run commands such as `process.getBuiltinModule('child_process').execSync`. Vendor-released patch: upgrade to 3.12.1; no public exploit identified at time of analysis, but the required pre-condition is common because ordinary JavaScript functions are non-strict by default, and vm2 is deprecated, so unmaintained deployments remain exposed-independent assessment rates this a top-tier priority.
Authenticated, low-privileged users with access to the Cohesity NetBackup Flex OS management shell can inject crafted argument input into a privileged administrative command and achieve arbitrary code execution as root, gaining unrestricted control of the Flex appliance host and every container it runs. The issue is network-reachable with low attack complexity and requires no user interaction, so the only real prerequisite is a valid low-privileged shell account; scoring 9.4 under CVSS 4.0 (assessed 9.1 under CVSS 3.1), it rates as a genuine high-priority vulnerability. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so exploitation is currently limited to attackers who already hold credentials.
Remote code execution in the AF Companion WordPress plugin before version 2.2.0 lets an authenticated user who holds the plugin's low-privileged 'store-management' role upload arbitrary files, including PHP, through an import feature that performs no file-type validation. Because the uploaded PHP is executable by the web server, an attacker with that mid-tier account - a WooCommerce shop-manager-tier role rather than a full administrator - can place and run code on the host with no user interaction and no non-default configuration required. Publicly available exploit code exists for this issue, and the vendor has released version 2.2.0 to fix it; the practical limiting factor is the authenticated mid-tier role, so sites that never delegate store-management accounts to untrusted parties face materially lower risk.
Unauthenticated remote code execution affects HGiga's OAKlouds Custom Page module in the 2.0, 3.0 and 4.0 lines at builds below 26, where an attacker who can reach the Custom Page endpoint can submit malicious serialized content and have it deserialized into arbitrary code running with the web service's privileges. The CVSS 4.0 score of 9.3 reflects the worst case for an unauthenticated network attacker (PR:N, UI:N, AT:N, high confidentiality, integrity and availability impact on the vulnerable system), and the practical limiter is exposure - whether the affected instance is reachable from untrusted networks - rather than any technical precondition. No public exploit code has been identified at time of analysis and the flaw is not currently listed as confirmed actively exploited (CISA KEV), but the low attack complexity, unauthenticated access and full-system impact make this a genuinely high-priority issue for any organization running the affected builds, and a vendor fix is available.
Path traversal in Vvveb CMS 1.0.0 through 1.0.8.4 lets an authenticated user holding the default Editor role's editor/* permission write attacker-controlled PHP content into arbitrary writable files outside the active theme directory, escalating to remote code execution when the traversal target is web-accessible. Exploitation is authenticated (CVSS PR:L) but low-privilege, since the stock Editor role shipped in affected versions grants editor/* by default; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV. The vulnerability is fixed in version 1.0.8.5, which sanitizes the attacker-controlled filename and drops editor/* from the default Editor role.
Authenticated SQL injection in SQLBot before 1.9.0 allows a user with a valid account to achieve operating-system command execution inside the SQLBot container. The attacker submits a crafted sheet["tableName"] value to POST /api/v1/datasource/, SQLBot stores it unsanitized, and the value is later interpolated into datasource cleanup SQL executed by PostgreSQL when that datasource is deleted via DELETE /api/v1/datasource/{id}; a second-order injection that can reach PostgreSQL COPY TO PROGRAM and run arbitrary commands with the privileges of the postgres process. Exploitation is gated by valid credentials, a two-request state dependency (raising attack complexity, AC:H/AT:P), and the postgres role's ability to invoke COPY TO PROGRAM; there is no public exploit identified at time of analysis, and only deployments running releases prior to 1.9.0 are affected.
Authenticated remote code execution in SQLBot (dataease/SQLBot) versions prior to 1.9.0 lets an attacker with datasource-management privileges plant an arbitrary Python module inside the application's Alembic migration directory by abusing attacker-controlled multipart filenames on the POST /api/v1/datasource/parseExcel endpoint, a technique that masquerades as a CWE-22 path-traversal issue but yields module-level code execution on the next SQLBot startup or migration run. Exploitation is not immediate: the upload is written to disk before spreadsheet parsing and validation complete, so the endpoint can return a parse error while the planted file survives, and code execution is deferred until Alembic imports the module (independent assessment scores CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Vendor-released patch: 1.9.0; no public exploit identified at time of analysis, though the upstream advisory and fix commits are public.
Use-after-free code execution in PDFium, Chrome's bundled PDF rendering engine, allows a remote attacker who lures a victim into opening a crafted HTML page to run arbitrary code inside Chrome's renderer sandbox on any build prior to 153.0.8010.52. The bug is network-reachable and low-complexity with no authentication required, but it does require user interaction (the victim must navigate to the attacker-supplied page), and because the CVSS scope is unchanged (S:U) the compromise is contained within the renderer - full system takeover would require chaining a separate sandbox-escape flaw. Google has released a fixed build and there is no public exploit identified at time of analysis, though the CVSS 8.8 score and memory-corruption tag make timely patching advisable.
Heap buffer overflow in PDFium, the PDF rendering engine built into Google Chrome, allows a remote attacker to potentially execute arbitrary code inside the Chrome renderer sandbox on Windows systems running versions prior to 153.0.8010.52. Exploitation requires the victim to open an attacker-supplied crafted PDF (UI:R), so the attack is delivered via social engineering rather than direct network exploitation; no credentials are needed (PR:N) and default Chrome installations render PDFs without any special configuration. The vendor rates this High severity with a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), and although a vendor patch is available, no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV). Because code execution is confined to the renderer sandbox, full host compromise would additionally require a separate sandbox-escape vulnerability not covered by this advisory.
Type confusion in the V8 JavaScript engine of Google Chrome prior to 153.0.8010.52 allows remote, unauthenticated attackers to execute arbitrary code inside the renderer sandbox when a victim is socially engineered into loading a crafted HTML page (CVSS 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is not automatic: it requires user interaction, and because the resulting code execution is confined to the renderer sandbox, turning it into host-level compromise would require chaining a separate sandbox-escape vulnerability. There is no public exploit code identified at time of analysis and the flaw is not listed in CISA KEV, but a vendor patch (Chrome 153.0.8010.52) is available and this is a patch-now item for a ubiquitous product.
Local sandbox escape in Google Chrome on Windows (versions prior to 153.0.8010.52) lets an attacker who can already execute a program on the target host run arbitrary code outside the browser sandbox by abusing incorrect reference resolution in Chrome's Tracing component (CWE-706). The vendor rates it High with a CVSS of 8.1 (AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H), meaning exploitation is local-only, requires no user interaction, but is gated by high attack complexity - consistent with a race or timing-dependent condition that is not reliably repeatable. No public exploit code has been identified at time of analysis, and because a local foothold is a prerequisite, this is realistically a chained sandbox-escape stage rather than a standalone initial-access vulnerability.
Use-after-free in the Dawn (WebGPU) component of Google Chrome on Android before 153.0.8010.52 allows a remote, unauthenticated attacker to potentially execute arbitrary code outside the browser sandbox when a victim renders a crafted HTML page. Exploitation requires the user to load attacker-controlled content (CVSS 9.6, AV:N/AC:L/PR:N/UI:R), and Google rates the bug Chromium security severity Critical; the only affected configuration is Chrome on Android below the fixed 153.0.8010.52 build, and devices already updated are not exposed. There is no CISA KEV listing and no public exploit identified at time of analysis, so the practical risk is driven by the size of the unpatched Android install base rather than by observed attacks.
Use-after-free in Google Chrome's Extensions component allows a remote attacker to execute arbitrary code outside the browser sandbox on any desktop build prior to 153.0.8010.52, provided the victim loads a crafted, attacker-controlled extension. The flaw carries a 9.6 CVSS score (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), meaning no prior authentication to the target is needed, but the attacker must still persuade the user to install or load a malicious extension, which is the real-world limiting factor; the sandbox-scope change (S:C) reflects code execution escaping Chrome's renderer/extensions sandbox. A vendor patch shipping in 153.0.8010.52 is available, and no public exploit code or confirmed active exploitation has been identified at time of analysis. Because Chrome auto-updates aggressively, the exposed population shrinks quickly once the fixed build propagates.
Remote code execution outside the browser sandbox in Google Chrome on Android prior to 153.0.8010.52 is possible when a victim opens a crafted HTML page containing malicious WebGL content that triggers a stack-based buffer overflow. Unauthenticated remote attackers can achieve code execution in the context of the GPU/renderer process with high impact to confidentiality, integrity, and availability, though exploitation requires user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6, Chromium security severity Critical). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; Google has released a fixed build (153.0.8010.52) and the flaw is tracked as EUVD-2026-82476 and VulDB 407131.
Symlink-based archive extraction in Grafana OSS and Grafana Enterprise lets a malicious plugin archive write arbitrary files - including an executable backend binary - outside the plugin installation directory, and that binary then runs with the Grafana server process's privileges, yielding remote code execution. Exploitation is gated on a Grafana operator installing a plugin from an attacker-influenced archive (via the plugin catalog, grafana-cli, GF_INSTALL_PLUGINS, or preinstall configuration), which is the UI:R component of the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H vector; there is no unattended remote trigger against a running server. A key aggravating factor is that plugin archives are extracted before their signature is verified, so enforcing signed plugins does not mitigate this issue, and Grafana Enterprise carries the identical extraction code. No public exploit code has been identified at time of analysis, and the vulnerability is not in CISA KEV; independent assessment rates this a genuine high-priority issue rather than a high-CVSS-but-low-real-risk paper cut.
Memory corruption in OpenSlide's Ventana BIF parser (versions 3.4.1 through 4.0.1) allows a crafted whole-slide image to write attacker-chosen values to attacker-chosen memory offsets, crashing the process that opens the slide or potentially achieving arbitrary code execution. Any application, viewer, or server-side tiling/conversion service that uses the affected library to ingest untrusted Ventana .bif files is exposed, since the defect is not configuration-dependent and affects all supported platforms; exploitation requires a user or process to open the malicious file, and reliable code execution (as opposed to a crash) further depends on controlling heap layout. No public exploit code or confirmed active exploitation was identified at time of analysis, but the underlying write-what-where primitive makes this a high-severity risk for digital-pathology pipelines that accept third-party or uploaded slides.
Unauthenticated remote code execution in Chamilo LMS 2.0.0 and earlier lets any network-reachable attacker run arbitrary code on the server through the CStudio editor plugin's import-project big-upload endpoint, which shipped without an authentication check and without sanitizing attacker-supplied filenames. Graded CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H) with no special prerequisites beyond the CStudio upload flow being deployed and reachable, this is assessed as a genuine top-tier priority for any exposed instance; no public exploit code was identified at time of analysis and no CISA KEV listing applies, though the vendor-released patch in 2.0.1 fully closes the issue.
Arbitrary code execution is possible inside the NetBox Device Type Library's pytest validation harness because the test suite deserializes pull-request-controlled pickle cache files via pickle.load. An unauthenticated contributor can flip USE_LOCAL_KNOWN_SLUGS in tests/test_configuration.py and commit a crafted tests/known-modules.pickle or tests/known-racks.pickle in the same pull request, so the payload fires whenever the tests are run: automatically by the GitHub Actions validation workflow on the PR, or by a maintainer executing pytest locally against the untrusted branch (the user-interaction requirement in the CVSS vector). Affected deployments are the repository's CI pipeline and any maintainer workstation running the suite, not NetBox servers that merely import the library's device definitions; no public exploit code has been identified at time of analysis, and GitHub Actions exposure is bounded by the read-only token granted to pull_request workflows, while a privileged local test run carries full confidentiality, integrity and availability impact.
Loading a crafted legacy X10 'static short' XBM image with SAIL versions prior to 1.0.0 triggers a forward heap buffer overflow in sail_codec_load_frame_v8_xbm() that lets a file-controlled write corrupt process state, reliably crash the consuming application, and potentially achieve code execution depending on the host's memory layout and mitigations. The flaw is reachable through sail_load_from_file, sail_load_from_memory, and sail_start_loading_*, but only when the destination image has an odd row stride (ceil(width/8) odd) and only on the X10 short path - the X11 'static char' path is explicitly unaffected. Exploitation is local and file-based (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8) and requires the victim to open the malicious image; no public exploit code or confirmed active exploitation was identified at time of analysis, and the impact scales with image height.
Heap-based buffer overflow in the SAIL image library's PSD decoder affects versions 0.9.10 and earlier, letting a crafted PSD file corrupt heap memory, reliably crash the host process, and potentially achieve code execution. Any application that passes attacker-controlled PSD data to sail_load_from_file() or sail_load_from_memory() is exposed; the CVSS vector carries PR:N (unauthenticated against the library), but practical exploitation still requires a victim to open or process a malicious image (UI:R), so the vendor's 9.8/UI:N rating overstates real-world risk. No public exploit code or confirmed active exploitation was identified at time of analysis, and the flaw is fixed in SAIL 1.0.0.
Heap-based buffer overflow in the SAIL cross-platform image library version 0.9.10 and earlier allows an attacker who supplies a crafted color-mapped, run-length-encoded TGA file (image_type == 9) to write attacker-controlled bytes past the end of a heap pixel buffer, causing heap corruption, a reliable crash, or potential code execution. The flaw is an incomplete fix for CVE-2026-40494: the earlier pixel-count clamp limits how many pixels are written but never constrains the per-pixel write width, which is derived from an attacker-controlled header bpp value of 9 through 32 (2-4 bytes) while the destination buffer is allocated as one-byte-per-pixel SAIL_PIXEL_FORMAT_BPP8_INDEXED. Although the CVSS vector is AV:N/PR:N, exploitation requires the victim's application to load the malicious image through sail_load_from_file() or sail_load_from_memory(), so a user-interaction condition is inherent; no public exploit code was identified at time of analysis, and the issue is fixed in SAIL 1.0.0. Note that the vendor-published CVSS of 9.8 (UI:N) overstates exploitability relative to the independent assessment of CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
Unauthenticated remote code execution affects Wavelog amateur radio logging software versions 1.8 through 2.4.1 because the installer endpoints /install/ajax.php and /install/includes/interface_assets/triggers.php remain reachable after setup and pass unsanitized input into configuration-writing routines. An attacker who can reach the exposed /install/ path can inject attacker-controlled PHP into configuration files, resulting in code execution on the server, with no authentication or user interaction required (CVSS vector PR:N/UI:N). The issue is fixed in version 2.4.2, and no public exploit identified at time of analysis.
Arbitrary code execution in the CI pipeline of the NetBox devicetype-library repository lets an unauthenticated contributor run attacker-controlled Python on GitHub Actions runners by submitting a pull request that adds a shadowing module (for example tests/git.py to hijack the harness's 'from git import ...') or a tests/conftest.py that pytest auto-imports during collection. The flaw exists because the repository lacks tests/__init__.py and invokes pytest without --import-mode=importlib, so pytest's default prepend import mode places tests/ and the repository root at the front of sys.path, causing PR-supplied files to take precedence over installed packages such as GitPython. Per the assessed vector (AV:N/AC:L/PR:N/UI:R), exploitation is unauthenticated but gated by user interaction: PR-supplied code only executes when a maintainer approves or runs the fork-PR workflow, and by default fork-PR workflows receive a read-only GITHUB_TOKEN with no repository secrets, so token or secret theft is fully realized only where that approval gate is disabled, on workflows with write tokens, or when a maintainer runs the harness locally; no public exploit code was identified at time of analysis, and this is a CI/supply-chain code-execution issue affecting the repository's build pipeline rather than any deployed NetBox instance.
Local privilege escalation to root in NetworkManager-l2tp: a local user who holds NetworkManager VPN-connection-creation permission (typically granted through polkit on a desktop or shared Linux host) can smuggle an arbitrary pppd 'plugin' directive into the root-owned pppd options file by setting the L2TP connection's mru or mtu property to a valid integer followed by trailing non-numeric text, for example '1400 plugin /tmp/evil.so'. Because the plugin directive is consumed by the privileged pppd process when the crafted VPN connection is activated, pppd loads an attacker-controlled shared object and executes code as root. No public exploit code has been identified at time of analysis, there is no confirmed active exploitation, and the flaw is strictly local with no remote or network-facing exposure; the practical bar is the PR:L gate, since an ordinary unprivileged account cannot trigger it unless it has been given VPN management rights.
Authentication bypass in the FaustWP WordPress plugin before 1.8.11 lets an authenticated low-privilege user (PR:L - for example a Subscriber) tamper with a valid authorization-code envelope and obtain an Administrator access token, enabling full WordPress REST API access, administrator-account creation, plugin installation, and ultimately arbitrary code execution (CVSS 8.8, CWE-345). Because the token HMAC does not cover the 16-byte AES-CBC initialization vector, XOR-ing a few bits into the IV deterministically rewrites the first decrypted block so that a Subscriber's "ac|2|<exp>" authorization code becomes "at|1|<exp>" - an admin access token - while the HMAC still validates. Exploitation is network-reachable and needs only a logged-in account able to call GET /generate plus the plugin's headless auth flow being active; no admin privileges and no victim interaction are required. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, though the published patch diff and regression tests make the technique trivially reproducible.
Hard-coded pacman signing key in lxc-ci's Arch Linux image build lets a mirror-position attacker forge trusted packages and execute code as root on affected guests. Images built from images/archlinux.yaml and published before 2026-05-28 embed the same pacman local-signing private key in /etc/pacman.d/gnupg, and every container or VM created from those images inherits it (CWE-321); because the key can be recovered from any published image, the assessed vector (AV:N/AC:H/PR:N/UI:R) positions an unauthenticated remote attacker who operates or intercepts an HTTP package mirror to sign tampered packages that clients accept during a root install or update. Exploitation is gated by three conditions - a pre-2026-05-28 image, attacker mirror/on-path control, and a victim-initiated root package operation - so it is a genuine supply-chain trust failure rather than a fully automatable one; no public exploit identified at time of analysis.
Stack-based buffer overflow in MCC Universal Library for Linux (uldaq) 1.2.1 and earlier lets a local attacker corrupt memory inside any process that loads the library, yielding arbitrary code execution or information disclosure at that process's privilege level. Exploitation requires crafted input to reach the vulnerable parsing routine - realistically an attacker-controlled or spoofed MCC USB data-acquisition device attached to the host, or attacker-supplied data processed by an application linked against uldaq - and needs no credentials and no user interaction (CVSS 4.0 8.6; assessed CVSS 3.1 8.4-equivalent vector AV:L/AC:L/PR:N/UI:N). No public exploit identified at time of analysis, and although impact is high, the local-only attack vector makes this a genuinely high-impact but access-constrained flaw.
Heap-based buffer overflow in rabbitmq-c, the C-language AMQP client library, affects all versions prior to 0.16.0 and is triggered when a malicious or compromised AMQP broker sends an undersized connection.tune frame_max value during the amqp_login() handshake. Because amqp_tune_connection() reallocates the outbound frame buffer using the attacker-supplied value without enforcing AMQP_FRAME_MIN_SIZE, the immediately serialized connection.tune-ok frame overflows the undersized heap allocation, producing memory corruption and likely denial of service, with code execution considered theoretically possible but not demonstrated. Exploitation requires the victim client to initiate a connection to attacker-controlled infrastructure (CVSS 7.1, AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H), or an on-path attacker to inject the malicious tune frame into plaintext, non-TLS AMQP traffic; no public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor-released patch in version 0.16.0 is available.
Unauthenticated remote code execution affects SolarWinds Access Rights Manager 2026.2 and all earlier versions, where a hardcoded static cryptographic key (CWE-321) shipped in default installations allows an attacker to execute arbitrary code with full confidentiality, integrity, and availability impact. Per the vendor CVSS vector (AV:A/AC:L/PR:N/UI:N), no credentials and no user interaction are required, but the attacker must be positioned on an adjacent or same-segment network rather than reaching the service across arbitrary internet paths - a point that conflicts with the advisory's 'remote' wording and should be confirmed with SolarWinds. No public exploit code was identified at time of analysis and the CVE is not listed in CISA KEV, so there is no confirmed active exploitation, though the combination of unauthenticated access, low complexity, and full CIA impact makes this a high-priority fix for any exposed deployment.
Remote code execution in MISP prior to 2.5.47 allows an authenticated attacker who can submit the platform's events/contact form to run arbitrary PHP as the MISP web user. By setting the contact form's 'person' field to a reserved CakePHP console switch such as '-app' and the adjacent 'message' field to a phar:// URI, the attacker redirects the background-job worker's application root into an attacker-controlled archive whose Config/core.php is then included - a deterministic, single-shot exploit requiring authenticated access to the submission endpoint (CVSS 3.1 AV:N/AC:L/PR:L/UI:N, rated 8.7 under CVSS 4.0) and no timing or race condition. Exploitation status per available intelligence: no public exploit identified at time of analysis, EPSS is low at 0.50% (42nd percentile), and CISA SSVC records Exploitation: none, though the flaw is fully fixed only by upgrading to 2.5.47 and the impact of success is full server-side compromise of the web process.
HortusFox-Web releases prior to 6.1 expose the Import/Export data-portability feature to arbitrary file write, letting an authenticated administrator execute OS commands as the web server user by slipping a PHP file into the web-accessible public directory. The flaw carries a CVSS 4.0 score of 8.6 (assessed as CVSS 3.1 AV:N/AC:L/PR:H/UI:N/C:H/I:H/A:H, high confidentiality, integrity and availability impact) and is gated behind administrator privileges plus the operator running an import of attacker-supplied data, so it is not remotely exploitable by an unauthenticated user on a default install. Vendor patching is available via the 6.1 release and the upstream commit 1c7108f; no public exploit code or confirmed active exploitation was identified at time of analysis.
Argument injection in Appwrite before 2.0.0 allows an authenticated user holding the functions.write or sites.write permission to turn a crafted providerRootDirectory value into arbitrary GNU tar command-line arguments, escalating to remote code execution as the builds worker process user via payloads such as --checkpoint-action=exec. The flaw is not admin-only: the assessed CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, vendor score 8.7 under CVSS 4.0) reflects that a low-privileged, authenticated account with deployment-write rights over a reachable Appwrite instance is sufficient, with no user interaction and no non-default configuration required. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; a vendor-released fix is available in Appwrite 2.0.0, making this a genuine high-priority issue rather than a CVSS-inflated one.
Code execution can be achieved through an uncontrolled search path in Dell Server Update Utility (SUU) and its bundled Driver Packs for Windows and Linux at all versions prior to 26.07.01, which load libraries from locations an attacker may be able to control (CWE-427). Exploitation is local and not remotely reachable: per the CVSS vector (AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H) an attacker must already hold low-privileged local access, must be able to plant a malicious library in a directory the utility searches, and must wait for a higher-privileged user or administrator to subsequently run SUU so the planted code loads with that user's privileges. No public exploit code was identified and the flaw is not confirmed as actively exploited (not in CISA KEV); Dell has released a fixed version, 26.07.01, via advisory DSA-2026-422.
Unauthenticated PHP object injection in b2evolution CMS 6.7.8 through 7.2.5 lets remote attackers POST crafted serialized payloads to htsrv/call_plugin.php that bypass the incomplete CVE-2016-8901 validation fix and reach unserialize(), instantiating arbitrary PHP objects with attacker-chosen properties. The vendor rates this 9.2 (CVSS 4.0 AV:N/AC:L/AT:P/PR:N/UI:N with VC/VI/VA:H, so unauthenticated network reach into a PHP unserialize() sink), while the independent assessment scores it high (CVSS 3.1 AV:N/AC:H/PR:N/UI:N, C/I/A:H) because full code execution additionally requires a suitable POP gadget chain to exist in the deployed version or its active plugins; absent such a chain, impact is limited to arbitrary object instantiation and magic-method side effects. No public exploit code has been identified at time of analysis, and the affected branch is end-of-life, making unpatched legacy installs the realistic target.
Sandbox escape in the vm2 Node.js sandboxing library before 3.11.7 lets an attacker who supplies a malicious script file to the vm2 command-line tool execute arbitrary code in the host Node.js process, gaining access to host modules such as fs and child_process. The vulnerable entry point is the CLI utility specifically, not the library's programmatic VM/NodeVM API: an attacker-crafted script uses require(__filename) to re-execute itself in the host realm and slip past the sandbox membrane. Exploitation is local rather than network-facing (CVSS 4.0 AV:L/UI:P, PR:N), requiring a victim or automated job to invoke the vm2 CLI against the attacker-controlled file; the vendor rating is 9.3 (critical), but the local vector and required user interaction make real-world exposure materially narrower than the network-facing vm2 escapes, and there is no public exploit identified at time of analysis.
Sandbox escape in vm2 3.9.6 through 3.11.6 lets attacker-supplied JavaScript running inside a NodeVM break out and execute arbitrary code in the host Node.js process when three conditions line up: the host runs Node.js 24 or newer, the embedder has explicitly allowlisted the node:test builtin, and the sandboxed code is under attacker control. The bypass exists because vm2's family-based DANGEROUS_BUILTINS check does not recognise Node.js 24's scheme-only 'node:test' key, so the module is placed in the generic host-passthrough loader, and a single 'node:' prefix strip in requireImpl() means require('node:node:test') resolves to that stored key; forwarded node:test.run() calls reach the host implementation, which spawns a separate Node process and honours attacker-supplied execArgv values such as --eval=<JavaScript>. Vendor severity is 9.4 (CVSS 4.0) and our independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, a genuine full sandbox escape to host code execution whose real-world reachability is constrained by the hard Node.js 24+ and non-default node:test allowlist prerequisites; no public exploit identified at time of analysis. Fixed in vm2 3.11.7.
Sandbox escape leading to remote code execution affects the vm2 Node.js sandbox library before version 3.11.7 when the embedding application enables require.external without an explicit require.root that excludes node_modules. Under that configuration, attacker-supplied JavaScript running inside the sandbox can require vm2's own package, construct an unrestricted NodeVM instance, and then execute arbitrary host OS commands through child_process, yielding a complete escape from the sandbox to the underlying operating system. Exploitation requires two operator-chosen, non-default preconditions (running untrusted code in vm2 AND the permissive require configuration), so deployments that leave require.external disabled or pin require.root away from node_modules are not exposed; no public exploit code was identified at time of analysis, and the vendor-released fix is version 3.11.7.
Sandbox escape in the vm2 npm library versions 3.10.2 through 3.11.6, when running on Node.js 26, allows attacker-supplied JavaScript to break out of the sandbox and reach the host Function constructor and process object, resulting in arbitrary code execution. The escape is unauthenticated and requires no special vm2 configuration - no require.external, builtin allowlists, or unsafe options - but it is gated on the Node.js 26 / V8 14.6 runtime, so the same vm2 versions on other Node.js major versions are not affected by this finding. No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical prerequisite is that a deployment accepts and executes untrusted code inside vm2, which is the library's core threat model.
Sandbox escape and arbitrary native code execution in vm2 3.11.3 through 3.11.6 occurs when a NodeVM sandbox is configured to allow the host crypto builtin: sandboxed JavaScript can reach crypto.setEngine() and hand it a filesystem path pointing at an attacker-supplied shared library (for example one shipped inside an untrusted plugin package already unpacked to disk), which OpenSSL passes to the operating system's dynamic loader and whose constructor then executes in the host process. Exploitation needs the crypto builtin alone - fs, process, module, child_process, worker_threads, vm and inspector access are all unnecessary - and there is no public exploit code or confirmed active exploitation (no CISA KEV listing) at time of analysis, though the reporter-assigned score of 9.4 reflects the severity if those prerequisites are met. Real-world urgency is gated by deployment-specific factors: the crypto builtin must be explicitly exposed to the sandbox and the host must already contain an attacker-writable native library, so a patched release or a tightened builtin allow-list fully removes the attack surface.
Native code execution outside the sandbox affects vm2 versions 3.11.3 through 3.11.6 when the host node:sqlite builtin is exposed to a NodeVM sandbox - either explicitly or through the wildcard builtin: ['*'] - which is not a default configuration. Sandboxed plugin code can create an in-memory DatabaseSync with extension loading turned on, resolve an attacker-supplied native library via a __dirname-derived path, and call loadExtension(), causing SQLite to load that library into the Node.js host process and execute its native entry point with host privileges; the vm.readonly() wrapper prevents property assignment but leaves host-authority callables reachable, and a 'node:node:sqlite' double-prefix quirk in the resolver/prefix-stripping logic lets the sandbox reach the configured builtin. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV) - the vendor released vm2 3.11.7 to fix it. Real-world priority is strongly gated by configuration: exploitation requires all of permitting node:sqlite in the sandbox, enabling SQLite extension loading, and having an attacker-controlled .so/.dll on disk within the plugin package.
Sandbox escape leading to remote code execution in vm2 3.11.6 lets untrusted code inside the sandbox reach a live proxy to a host-realm object and run commands with the host process privileges, for example through e.detail.mainModule.require('child_process').execSync(...). The flaw is an incomplete fix for GHSA-m283-3h24-438v: registering a rejection handler via Function.prototype.call or .apply indirection (p.then.call(p, undefined, cb)) bypasses the identity check at lib/bridge.js:1624, so the raw host Error and its non-primitive own properties are handed to sandbox code. Exploitation is conditional: the embedder must bridge an async host Promise into the sandbox and that Promise must reject with an Error carrying a non-primitive own property that references a host object (for example err.detail = process); direct p.then(undefined, cb), .bind and Reflect.apply forms are correctly sanitised. Upgrade to vm2 3.11.7 closes the bypass; no public exploit identified at time of analysis.
Sandbox escape and remote code execution in vm2 versions 3.11.4 through 3.11.6 allow JavaScript executed inside a NodeVM to break out and run arbitrary commands with the privileges of the host Node.js process. The flaw is reachable only in a specific, non-default configuration where the NodeVM is created with a truthy `nesting` value and an array-shaped `require` option (for example `new NodeVM({nesting: true, require: []})`); in that case the array satisfies a guard intended to reject nesting without an explicit require configuration, and the resulting resolver falls back to a nesting override that permits the sandboxed code to require the host `vm2` module and construct an inner NodeVM with an attacker-chosen builtin allowlist such as `child_process`. Exploitation requires no authentication or user interaction (CVSS 4.0 vector reports PR:N/UI:N) beyond the ability to supply code the sandbox runs, which is vm2's intended threat model; there is no public exploit code or CISA KEV confirmation of active exploitation at time of analysis, but the impact is complete confidentiality, integrity, and availability loss on the host, and the vendor CVSS 4.0 score of 9.5 is consistent with that assessed impact.
Sandbox escape in vm2 before 3.11.8 allows unauthenticated remote attackers to achieve full remote code execution and host process information disclosure by crafting a host-wrapped AggregateError that is revisited within a single exception-handler traversal, bypassing handleException's cycle detection and exposing unsanitized host proxies in the errors array. The flaw is an incomplete fix for Error.cause sanitization, and exploitation requires the host application to execute attacker-controlled JavaScript inside a vulnerable vm2 instance, which is vm2's normal use case, though the malformed-error and traversal condition is non-trivial (CVSS AC:H/AT:P). No public exploit identified at time of analysis; environments that do not run untrusted code in vm2, or that have migrated off the deprecated vm2, are not exposed.
Path traversal in HUBzero CMS through 2.2.32 lets authenticated project members write files to arbitrary paths outside the project repository, potentially achieving code execution when the written file lands in a web-servable, executable location. The flaw lives in the com_projects file-upload API (filefsv1_0.php upload/download tasks and filesv1_0.php chunkedUploadTask) and the projects/files plugin, where the 'subdir' and chunked-upload 'flowIdentifier' parameters flow unsanitized into move_uploaded_file/copy and base64-derived temp-directory paths. Exploitation is remote and needs no user interaction but requires a low-privileged project-member account (CVSS v4.0 PR:L); vendor fix commits are published, yet no public exploit code has been identified at time of analysis and the issue is not known to be actively exploited.
Unauthenticated remote code execution in Migratico Lite, a WordPress site-migration plugin, affects all versions up to and including 2.6.8 and lets a remote attacker who can reach an affected site inject and execute arbitrary code with the privileges of the web server. The vendor-disclosed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H = 10.0, reported by Patchstack) requires no authentication and no user interaction, so any WordPress installation running an affected plugin version is potentially exposed; our independent assessment keeps the same network/authentication profile but scores scope as unchanged (S:U), giving an effective base score of 9.8. Exploitation is tempered by practical limits: Migratico Lite is a niche migration plugin with a modest install base, and the sparse public advisory does not disclose the vulnerable endpoint or parameter, so no public exploit code has been identified at time of analysis and weaponization currently depends on an attacker locating the injection sink themselves. There is no CISA KEV entry for this CVE.
Remote code execution as root on FatPipe MPVPN, WARP, and IPVPN appliances running the end-of-life 10.1.2r60p100 firmware is possible when an attacker can reach the management interface and submit a crafted authentication request that overflows a fixed-size stack buffer in /usr/sbin/auth_user_pass. The vendor score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects unauthenticated, no-interaction exploitation with high confidentiality, integrity, and availability impact, but real-world exposure is gated: the management interface is disabled by default and must be affirmatively enabled by the customer, and WAN access control lists are recommended to restrict reachability to trusted administrative networks. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; because 10.1.2r60p100 is end-of-life, no patched firmware version has been identified, so exposure persists until the appliance is decommissioned or tightly network-isolated.
Stack-based buffer overflow in Dell OpenManage Server Administrator (OMSA) versions prior to 11.1.0.3 allows an attacker who already holds high privileges on the OMSA service to achieve remote code execution over the network. Exploitation is constrained by the CVSS PR:H prerequisite-only compromised administrative accounts, malicious insiders, or chaining from another privilege-granting flaw can trigger it-but no user interaction is required and attack complexity is low. No public exploit code or CISA KEV active exploitation is identified in the available intelligence.
Remote code execution in Dell OpenManage Server Administrator (OMSA) managed-node installations prior to 11.1.0.3: a heap-based buffer overflow (CWE-122) that an attacker holding administrator-level privileges on the OMSA service can trigger over the network without user interaction, gaining code execution on the managed host with full confidentiality, integrity, and availability impact. The flaw scores 7.2 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and affects Windows, RHEL 8.10, RHEL 9.4, SLES 15, and Ubuntu 22.04 managed nodes. No public exploit code and no confirmed active exploitation were identified at time of analysis; the high-privilege prerequisite keeps this a privileged-user-to-code-execution escalation rather than a pre-authentication internet-facing exploit, with risk rising where OMSA is exposed to untrusted networks or chained after an authentication bypass such as CVE-2026-81475 in the same DSA-2026-403 bundle.
Unauthenticated remote code execution in the wpShopGermany IT-RECHT KANZLEI WordPress plugin affects every release from 1.6 up to but not including 2.4. The plugin builds its API authentication token from data the requester supplies and creates that token as a side effect of the routine that is supposed to validate it, so an attacker can compute a valid token without any credentials and use the access it grants to write arbitrary files on the server, which in a PHP/WordPress context converts directly into code execution. No authentication or user interaction is required - only network reachability to the plugin's token-authenticated API endpoint - and publicly available exploit code exists (the finding was published by WPScan). Our independent assessment rates the realistic vector as AC:L/PR:N/UI:N/S:U with high confidentiality, integrity and availability impact, a step more severe than the vendor's 9.0 AC:H/S:C rating; the practical brake on this issue is deployment scope, since this is a niche legal-compliance plugin rather than a mass-market component.
Unauthenticated arbitrary file upload in the Multi Uploader for Gravity Forms WordPress plugin (all versions up to and including 1.1.9) lets attackers write executable files to the affected site's server through the move_file() chunked-upload handler, which applies insufficient file-type validation, making remote code execution possible. Exploitation requires the plugin to be installed and active alongside the commercial Gravity Forms plugin and a publicly reachable form that exposes a multi-uploader field; the CVSS vector (PR:N/UI:N) confirms no authentication or victim interaction is needed, though RCE additionally depends on the uploaded file landing in a web-executable location. Risk is rated high-priority (CVSS 9.8), with the practical exposure narrowed by the plugin's niche deployment and its Gravity Forms dependency; no public exploit code and no CISA KEV active-exploitation entry were identified at time of analysis.
Unauthenticated arbitrary file upload in the Paid Downloads WordPress plugin (all versions up to and including 3.15) lets remote attackers bypass authorization and file-type checks in the admin_request_handler function to place attacker-controlled files on the server, which can lead to remote code execution. The flaw is reachable without credentials because is_admin() returns true for requests to /wp-admin/admin-post.php, and the handler performs neither a capability check nor an extension/content validation; per assessment, the AC:H rating reflects that reliable code execution depends on server configuration - Apache deployments with AllowOverride enabled may have retrieval of the uploaded file blocked by a plugin-placed .htaccess, confining dependable RCE to nginx, LiteSpeed, or Apache with AllowOverride None, while the upload and authorization bypass itself succeeds on any stack. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, but the unauthenticated upload primitive combined with a CVSS 8.1 score makes this a high-priority, patch-dependent risk for any site running the plugin.
Arbitrary file write - escalating to remote code execution on hosts that execute PHP from upload directories - affects the WordPress plugin Photo Gallery, Sliders, Proofing and Themes in all versions before 4.5.0. The flaw sits in the archive-extraction routine: a variable is reused as a loop counter, so the filename-extension check always passes and a user who has been granted the plugin's gallery-management capability by an administrator can place an attacker-controlled file (including a .php payload) into a web-accessible gallery directory; the CVSS vector (PR:H, UI:N) confirms this is an authenticated, elevated-privilege path rather than a subscriber or anonymous one. Publicly available exploit code exists, so exploitation is realistic for any site where a non-administrator holds the gallery-management role, and full code execution depends on the host actually serving PHP out of the upload path - on hardened hosts the impact is limited to arbitrary file write.
Remote code execution in Mistral Vibe before 2.25.5 allows an attacker to run arbitrary shell commands with the privileges of the user running the tool, because worktree creation executes a repository's own git hooks - notably the post-checkout hook and the fsmonitor command - before any workspace trust validation takes place. The attack requires the victim to deliberately open, clone, or check out an attacker-controlled repository (user interaction is mandatory, and the request itself is unauthenticated per the CVSS PR:N vector), and code execution is bounded by the permissions of the Vibe user, with no privilege escalation or server-side attack surface. There is no public exploit identified at time of analysis and the flaw is not confirmed as actively exploited; a vendor-released patch in 2.25.5 addresses the ordering bug.
Code execution in OpenPanel's js-runtime component lets an authenticated user who holds project write access escape the JavaScript webhook template sandbox and run arbitrary code inside the worker process. The template validator fails to block computed (bracket-notation) member access that traverses a constructor chain to the Function constructor, so merely creating or editing a webhook template is sufficient - no user interaction is required (UI:N). No public exploit code has been identified at time of analysis, and no CISA KEV or EPSS signal was supplied, but our independent assessment rates this a genuine high-priority issue, with CVSS 3.1 AV:N/PR:L/UI:N/S:C/C:H/I:H/A:H (scope change to the host system and full confidentiality, integrity and availability impact).
Authenticated users with subscriber-level access or higher can execute arbitrary WordPress shortcodes through the ProfilePress plugin (slug wp-user-avatar) in all versions up to and including 4.17.2, because user-controlled values reach do_shortcode() without validation. Exploitation requires a low-privilege account, which is trivially obtained on sites that enable the plugin's self-service registration feature, and no user interaction is needed; however, the practical impact is variable and often limited, since substantial confidentiality or integrity loss only materializes when other privileged or data-exposing shortcodes are registered on the same site. The vendor's upstream severity rating is 8.1, while independent assessment rates the realistic vector as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N (limited C/I, no availability impact); no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Remote code execution in The Welcomizer WordPress plugin versions up to and including 2.8.1 lets authenticated users with Subscriber-level access or higher execute arbitrary PHP on the server by abusing the twiz_ajax_callback AJAX action's savesection handler. The handler checks a nonce but omits a current_user_can() capability check, and eval() processes attacker-supplied PHP from the twiz_custom_logic POST parameter when output is set to twiz_logic_output; the nonce is exposed to any authenticated user via twiz-ajax.js.php, so it does not prevent exploitation. Wordfence reports this with CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), and no public exploit identified at time of analysis.
Arbitrary PHP function invocation in the Save as PDF Plugin by PDFCrowd for WordPress (all versions up to and including 4.6.1) allows any authenticated user with Contributor-level access or higher to have the server AES-encrypt an attacker-chosen pdf_created_callback value into a valid button blob, which is later passed to PHP as a callable when any unauthenticated visitor POSTs that blob to the wp_ajax_nopriv_save_as_pdf_pdfcrowd AJAX endpoint. Published CVSS 3.1 is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); our assessment retains the High rating but bounds the impact to C:H/I:L/A:L because the invoked callback receives only the plugin's options array as its single, fixed argument, making disclosure of the site's stored PDFCrowd API key and username the most reliable outcome rather than fully attacker-controlled code execution. Contributors are required only to mint the blob - the trigger replay is unauthenticated - and no public exploit identified at time of analysis, with no confirmed actively exploited (CISA KEV) status.
Shortcode injection in the WP Recipe Maker plugin for WordPress (all versions up to and including 10.8.1) lets an attacker plant arbitrary registered shortcode tokens inside the content of an approved wprm-comment-rating comment, which the plugin later feeds through do_shortcode() during recipe metadata generation and reflects into the JSON-LD reviewBody field served on every recipe page render. Because execution occurs before the plugin's strip_shortcodes()/wp_strip_all_tags() cleanup runs on the resulting string, output from sensitive shortcodes (attachment captions, private post fields, other data exposed by installed shortcodes) can be disclosed to any visitor loading the affected page. The CVSS vector records PR:N, so the injection itself is unauthenticated, but practical exploitation is gated by the site's comment-approval threshold and by whether installed shortcodes actually expose sensitive content; the vendor score of 9.1 is assessed as inflated relative to an AC:H/I:L reality, and no public exploit code has been identified at time of analysis.
Unauthenticated attackers can execute arbitrary WordPress shortcodes through the Forminator Forms plugin (all versions up to and including 1.57.2) because a value reaching do_shortcode in the quizzes front-action handler is not properly validated. A site is only reachable through this path if Forminator is installed and active and a form or quiz routes through the vulnerable front-action, and the real-world damage is bounded by which shortcodes other installed plugins register - benign shortcodes mean limited impact, while data- or state-changing shortcodes raise it substantially. No public exploit code or confirmed in-the-wild activity (CISA KEV) was identified at time of analysis; note that the vendor-assigned CVSS 9.1 overstates the assessed impact, which our analysis places at CVSS 6.5 (C:L/I:L) for fully remote, unauthenticated, low-complexity exploitation.
Unauthenticated arbitrary file upload in the Gravity Forms WordPress plugin through version 3.1.0.4 can lead to remote code execution on any site whose publicly reachable form contains a File Upload field with its Visibility set to 'Hidden', because hidden upload fields skip the extension-validation step and a rejected file's intact upload state is subsequently persisted by upload_file() without re-validation. Per the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), no credentials or user interaction are required (PR:N/UI:N) and the attack is fully remote (AV:N), but the non-default hidden File Upload field is a mandatory precondition; a secondary practical limiter is that code execution depends on the server actually executing the uploaded file type in the upload directory. No public exploit code and no CISA KEV entry were identified at time of analysis, yet the combination of unauthenticated access, arbitrary file write and PHP-execution potential makes this a high-priority fix for any installation that meets the precondition.
Remote code execution in WP Photo Album Plus affects all versions through the wppa_image_magick path, allowing authenticated attackers with subscriber-level access and above to run server-side code when the site uses ImageMagick processing. The issue is argument injection into an ImageMagick command executed via PHP exec(), enabled by insufficient sanitization of the multipart upload filename and reliance on escapeshellcmd() instead of proper argument quoting. Exploitation requires ImageMagick to be available and the plugin to route uploads through ImageMagick rather than GD, and no public exploit was identified at time of analysis; CVSS 3.1 base score is 7.5 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H).
Out-of-bounds heap write in FluidSynth's command handler lets an attacker supply an out-of-range channel argument to the pitch_bend_range command, which is written through the selected synth channel without bounds checking. The worst-case exposure is unauthenticated remote code execution or denial of service (CVSS 3.1 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) when FluidSynth runs as a TCP command server via new_fluid_server() or 'fluidsynth -s'; absent that network mode, the flaw is only locally reachable through malicious commands fed to the interactive shell on standard input, and applications that embed the library without the shell, command handler, or TCP server are unaffected. The vendor has released a fix in FluidSynth 2.5.6 (spanning affected releases from 1.1.2); no public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV).
PHP object injection in Cotonti 1.0.0 allows authenticated users with comment-write permissions to pass attacker-controlled base64-encoded data through the cb (comeback) parameter of the comments plugin EditAction, which is then unserialized without an allowed_classes restriction. This can lead to arbitrary PHP object instantiation and, only if a viable POP gadget chain exists among loaded classes, escalation to file write or remote code execution. No public exploit code or active exploitation has been identified at time of analysis; the vendor has published a fix in PR #1897, and the vendor CVSS 4.0 score is 7.7, while the independent CVSS 3.1 assessment is AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
Arbitrary code execution is possible on IBM Guardium Data Protection 12.2 when a remote attacker who already holds high-privilege credentials abuses a file-handling feature that fails to constrain a user-supplied pathname to its intended restricted directory (CWE-22). The requirement for HIGH privileges (PR:H) on the management interface is the primary limiting factor, restricting realistic exploitation to trusted administrative accounts on an appliance that is normally deployed on internal or segmented networks, though no user interaction is required (UI:N). The vendor has published a fix advisory, and no public exploit identified at time of analysis (no CISA KEV listing and no published proof-of-concept in the supplied intelligence).
Arbitrary file upload in WP Cloud Plugins (Use-your-Drive, Out-of-the-Box/Dropbox, Share-one-Drive/OneDrive-SharePoint, and Lets-Box/Box) versions 2.0 through 3.8.3 lets attackers with subscriber-level access write executable files to the WordPress uploads directory, enabling remote code execution (CVSS 8.8). The vulnerable download_file_to_uploads function is reachable through an import AJAX action that is also registered via wp_ajax_nopriv_ and lacks a capability check in can_import(), so the effective authentication prerequisite may be lower than the CVSS PR:L rating suggests, though exploitation still requires one of the four plugins installed and active and depends on the host allowing PHP execution inside wp-content/uploads. No public exploit code identified at time of analysis and the issue is not listed in CISA KEV.
Unauthenticated insecure deserialization in the Change Audit System (CAS) listener of IBM Guardium Data Protection 12.2 allows a network attacker who can reach TCP port 16017 to submit crafted serialized messages that are insecurely deserialized and used for attacker-controlled reflective method dispatch, potentially resulting in unintended code execution on the Guardium appliance with high confidentiality, integrity, and availability impact. The vendor-reported base score is 9.8 (AV:N/AC:L/PR:N/UI:N); our independent assessment keeps the unauthenticated, no-user-interaction profile but applies AC:H, because the practical gating factor is whether an attacker has a network path to the non-standard CAS port rather than any product configuration toggle. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV); IBM has published a vendor patch advisory, and this should be treated as a genuinely high-priority issue for any deployment where port 16017 is reachable from untrusted networks, while remaining lower-risk in segmented or hardened environments where the listener is internal-only.
Unauthenticated remote code execution in IBM Guardium Data Protection 12.2 lets a network attacker who can reach the appliance interface that processes serialized input run arbitrary code in the context of the affected service, yielding full loss of confidentiality, integrity and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). The root cause is insecure deserialization of untrusted data (CWE-502), and because the assessed vector carries PR:N and UI:N, no credentials or user interaction are needed, so real-world exposure is determined almost entirely by network reachability to the Guardium management/collector segment rather than by the public internet. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV; IBM has published a vendor patch, which keeps this a top-tier remediation priority rather than an actively exploited emergency.
Heap-based buffer overflow in the IBM MQ C client shipped with IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 lets a remote attacker who controls the queue manager's responses crash the client process or potentially execute arbitrary code in its context (CVSS 3.1 base 8.1). The flaw is triggered when the client requests AMS (Advanced Message Security) policy data and the client fails to properly validate the returned queue manager response; exploitation is unauthenticated from the client side (PR:N) but requires the attacker to operate a malicious or compromised queue manager or to man-in-the-middle the client-to-queue-manager channel, which is why the vector carries AC:H. No public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor patch is available.
An integer overflow in IBM MQ's MQINQ (inquire object attributes) request processing lets an authenticated remote user crash the queue manager and, per the vendor, potentially execute arbitrary code, giving the issue a CVSS 3.1 base score of 8.8 with high confidentiality, integrity and availability impact. Exploitation is network-based against the queue manager listener (default 1414/tcp), requires valid MQ credentials or connection authority (PR:L) and no user interaction; the vendor describes reliable code execution as a potential rather than confirmed outcome, so denial of service is the more assured impact. No public exploit identified at time of analysis, and a vendor fix is available per the IBM advisory.
IBM MQ for HPE NonStop versions 8.1.0 through 8.1.0.40 contain a heap-based buffer overflow (CWE-122) that is triggered during queue manager startup when improperly validated cluster migration data is processed. The flaw is exploitable only by an authenticated attacker who can supply crafted migration data to a queue manager participating in MQ clustering, and the dependable outcome is a denial of service (queue manager startup failure or crash), with arbitrary code execution considered only potentially achievable. Independent assessment rates the realistic impact lower than the vendor's 7.5 score (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H), and there is confirmed no public exploit code and no CISA KEV listing - no public exploit identified at time of analysis. A vendor patch is available via IBM support page node 7287705.
Code injection in Mongoid allows unauthenticated attackers who can influence a query argument to execute arbitrary JavaScript in the MongoDB server via a string-typed query criterion, leading to disclosure of stored field values, unintended document selection for writes, and reduced database performance. The vulnerability affects Mongoid versions 8.0.0 through 8.0.12, 8.1.0 through 8.1.12, 9.0.0 through 9.0.11, and 9.1.0, but exploitation requires the application to pass externally influenced string criteria to the query builder and the MongoDB deployment to permit server-side JavaScript evaluation. No public exploit identified at time of analysis.
Arbitrary Python code execution in LMDeploy 0.12.1 through 0.12.2 lets an attacker who publishes a malicious model on HuggingFace Hub run code on any machine that loads it, because the model's `quantization_config.quant_dtype` string is interpolated into `eval(f'torch.{quant_dtype}')` at lmdeploy/pytorch/config.py:620 without any validation. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) reflects that exploitation is remote and unauthenticated but requires the victim to actively load the attacker-supplied model, confirmed by our independent assessment that UI:R is the limiting factor and that the `_update_torch_dtype` whitelist at line 53 only guards `torch_dtype`, not `quant_dtype`. Publicly available proof-of-concept code exists in the vendor advisory (repo-level proof using a mocked HF config that yields `uid=0(root)`), but there is no confirmed actively exploited (CISA KEV) status, and no EPSS score was supplied; a fixed release, 0.12.3, is available.
Unauthenticated remote code execution in LMDeploy 0.9.2 through 0.15.x lets any attacker who can reach a DistServe/PD-disaggregation deployment's POST /distserve/p2p_connect endpoint run arbitrary code with the privileges of the LMDeploy serving process. The endpoint accepts an attacker-supplied ZeroMQ peer address; the engine connects to it and deserializes the reply with PyZMQ's recv_pyobj(), which is backed by Python pickle and therefore executes code during object reconstruction, before any type or schema check can run. Rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-502); exploitation is unauthenticated only in the default configuration where the operator has not enabled API-key authentication, and no public exploit code has been identified at time of analysis. A vendor patch is available in LMDeploy 0.16.0, which replaces the pickle-based ZeroMQ protocol with JSON plus Pydantic validation.
Physical-access arbitrary code execution on Carecam HMT.CM2507 IP cameras, where firmware automatically runs a predetermined script from attached removable media without verifying its authenticity or integrity. An attacker who can reach the camera's SD/USB interface and insert crafted media can execute code in the device's security context, achieving high confidentiality, integrity and availability impact; the assessed CVSS 3.1 vector (AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects that no credentials or user interaction are needed once physical access is obtained, and that this is the primary limiting factor since there is no network-facing path to the flaw. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV - exploitation requires an attacker with hands-on access to the hardware.
Heap-based memory corruption in the IBM MQ for HPE NonStop queue manager lets an attacker who already holds a valid, low-privileged authenticated channel connection (PR:L) crash or potentially take over the broker by sending a message carrying a malformed distribution list structure, yielding the full confidentiality, integrity and availability impact reflected in the CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is a heap buffer overflow (CWE-122) arising from improper validation of the multi-recipient list records embedded in an MQ message, so exploitation is network-reachable and requires no user interaction, but it is not reachable pre-authentication or against a default queue manager configuration. IBM has published a vendor patch and no public exploit code or evidence of active exploitation was identified at time of analysis.
Integer overflow (CWE-190) in IBM MQ distribution list processing lets an authenticated user with PUT authority to a distribution list send a crafted MQPUT message that corrupts memory handling, reliably crashing the queue manager and potentially enabling arbitrary code execution. The flaw is network reachable with low complexity and no user interaction (CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8 High), but requires a valid MQ session plus put/queue authority on a reachable queue manager, so it is not exploitable by unauthenticated attackers. No public exploit code or confirmed active exploitation has been identified at time of analysis; an RCE outcome is not confirmed and the reliably achievable impact against affected versions is denial of service, while IBM has published a vendor fix.
IBM MQ queue managers that process XA (X/Open distributed) transactions are vulnerable to a memory-corruption buffer overflow triggered when a malformed XA transaction identifier (XID) is parsed, allowing an authenticated attacker with network access to crash the queue manager and potentially execute arbitrary code in its context. Exploitation requires valid credentials and the ability to drive XA transaction operations over an MQ channel (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, vendor score 8.8), so the reliably achievable outcome is denial of service while code execution remains a potential, not guaranteed, consequence. There is no public exploit identified at time of analysis and no confirmed active exploitation, but a vendor patch is available and the low attack complexity combined with the complete loss of confidentiality, integrity and availability impact makes prompt remediation important.
Heap buffer underflow in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated remote attacker to crash or destabilize the queue manager, and potentially to execute arbitrary code, by submitting a crafted multi-segment message that is reassembled during processing. The dependable outcome is denial of service: reliable code execution is not confirmed, and exploitation requires valid low-privilege credentials (PR:L) plus access to a channel or queue that accepts submitted messages. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; urgency is real but constrained because only the specialized HPE NonStop build is affected, not general IBM MQ distributions.
IBM MQ queue managers running affected releases can be crashed - and, per IBM, potentially have arbitrary code executed on them - by an authenticated participant in an MQ cluster that sends cluster command messages with malformed length fields. The flaw affects MQ 9.1.0.0 through 9.1.0.37 LTS, 9.2.0.0 through 9.2.0.43 LTS, 9.3.0.0 through 9.3.0.41 LTS and 9.3.0.0 through 9.3.5.1 CD, 9.4.0.0 through 9.4.0.25 LTS and 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0; it is network-reachable (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8 HIGH) but requires a valid cluster identity, and IBM frames code execution only as a possibility while denial of service is the more certain outcome. No public exploit code exists and no public exploit was identified at time of analysis - CISA SSVC records Exploitation: none and Automatable: no - while EPSS estimates exploitation likelihood at roughly 0.36% (29th percentile), so priority should be driven by exposure of clustered queue managers rather than by observed attack activity.
Remote code execution in IBM MQ Java and JMS client libraries allows an authenticated attacker with access to a message queue or topic to bypass the deserialization allow-list filter in exception handling and execute arbitrary code on client applications. The flaw is network-reachable but requires low-privileged authentication (PR:L) and is limited to a specific exception-handling path (AC:H), with impact confined to the client process rather than the MQ server. No public exploit code was identified at time of analysis.
A pre-authentication heap buffer overflow in IBM MQ Appliance protocol message processing lets a remote, unauthenticated attacker crash the appliance (denial of service) or potentially execute arbitrary code in the context of the MQ appliance firmware. Only network reachability to the appliance's protocol message listener is required - no credentials, session, or user interaction - and the vendor rates this 10.0 with a scope change, while our independent assessment keeps the same base metrics but scores scope as unchanged (S:U) because the overflow occurs in the MQ process itself rather than crossing a security boundary. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV), but the combination of a CVSS 10.0, zero-click pre-auth reachability, and confirmed code-execution potential makes this a genuine top-priority vulnerability rather than a high-CVSS-but-low-real-risk case; an IBM vendor advisory with a patch is available.
Malformed compressed data delivered over an IBM MQ channel that has compression enabled can trigger an out-of-bounds heap write, allowing a remote attacker to crash the queue manager and, potentially, execute arbitrary code in the MQ process. The issue affects IBM MQ 9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS / up to 9.3.5.1 CD, 9.4.0.0-9.4.0.25 LTS / up to 9.4.5.1 CD, and 10.0.0.0, with the CVSS base of 9.8 reflecting a network-reachable, unauthenticated worst case, though our assessed vector raises attack complexity to High (AC:H) because the channel must be explicitly configured with compression and reachable by the attacker. Denial of service is the readily achievable outcome, while reliable code execution requires defeating the process's memory protections; no public exploit code has been identified at time of analysis, SSVC rates exploitation as none, and EPSS is low at 0.37% (31st percentile).
Unauthenticated remote code execution affects the Interchange e-commerce platform (the interchange/interchange project) through its admin 'quick question' page, where attacker-supplied yes/no parameters flow into a reparsed [calc] template block and injected Perl is evaluated server-side. The flaw is reachable without authentication in default installations, as confirmed by the upstream fix adding a previously absent [if-mm super] superuser gate, and SSVC rates it Automatable with total technical impact; however, injected code executes inside Interchange's Safe compartment, so unrestricted, full-impact code execution additionally requires the non-default AllowGlobal directive to be enabled on the catalog being accessed. The vendor rates this 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) while our independent assessment rates it AC:H given the sandbox constraint; no public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor patch/advisory is available.
Stack-based buffer overflow in the web management server of PLANET IGS-5225-8P2T4S industrial managed switches allows a remote authenticated administrator to crash the device or, with carefully crafted input, potentially execute arbitrary code on the underlying operating system. Affected devices run V1 firmware before 1.2412b260707 or V2 firmware before 2.2412b260519, and exploitation requires valid administrative credentials plus network reachability to the switch's management interface; the high attack complexity means many payloads will only produce a denial of service rather than code execution. No public exploit has been identified at time of analysis, and PLANET has released fixed firmware for both branches.
Stack-based buffer overflow in the web management server of PLANET IGS-5225-8P2T4S industrial managed switches lets an authenticated remote attacker (PR:L) crash the device for a denial of service or, with greater effort, execute arbitrary code on the underlying operating system. Affected are V1 firmware before 1.2412b260707 and V2 firmware before 2.2412b260519; exploitation requires network reachability to the switch web interface, valid credentials, and high attack complexity (AC:H) to achieve reliable code execution, so a straightforward crash/DoS is the more accessible outcome. There is no confirmed active exploitation (CISA KEV) and no public exploit identified at time of analysis; vendor firmware fixes are available.
Privileged users of PLANET IGS-5225-8P2T4S industrial managed switches running V1 firmware before 1.2412b260707 or V2 firmware before 2.2412b260519 can activate undocumented debug functionality that ships enabled in the embedded software, reaching an OS command execution path that grants root-level access to the device. Exploitation requires high-privilege administrative/management access and local access to the device management plane (CVSS:4.0 AV:L/PR:H), so the realistic threat is a malicious insider or an attacker who has already obtained management credentials rather than an unauthenticated remote compromise. No public exploit code and no confirmed active exploitation were identified at time of analysis, and vendor-released patched firmware is available.
Authenticated code injection in XWiki Rendering (the xwiki-rendering-xml module, versions before 14.10.2) lets any user who can edit their own user profile - or any other document - close the surrounding HTML macro and inject Groovy or Python script macros that execute with programming rights, granting remote code execution and unrestricted read/write access to all wiki contents. Exploitation requires only a low-privilege, authenticated account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, severity 9.9) and needs no victim interaction beyond the affected page being rendered; the attacker reaches the flaw through rendered output that is embedded in an HTML macro without escaping, with exploitable sinks including the user profile (since XWiki syntax 2.0, demonstrably exploitable from XWiki 3.3 Milestone 1) and the extension point org.xwiki.platform.search.ui.docdoesnotexist (added in XWiki 8.3 Milestone 1). No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, though the vendor advisory documents a detailed reproduction payload and the scope change (S:C) combined with high confidentiality, integrity and availability impact makes this a genuine high-priority issue; vendors have released the fix in XWiki 14.10.2 and 15.0 RC1.
Local privilege escalation in Sublime Text for Windows - Sublime Text 4 through Build 4192 and Sublime Text 3 through Build 3207 - lets an authenticated local attacker who already holds an unprivileged account plant a malicious DLL in the user-writable update staging directory under %LOCALAPPDATA%, mark it read-only to defeat the installer's cleanup pass, and have the elevated installer copy the payload into the protected installation directory, where it executes in the context of any higher-privileged user who later launches the editor. The attack is local-only and conditional: it requires a prior foothold on the host, depends on the update staging mechanism being reached, and fires only when an elevated user subsequently opens the application (passive user interaction). Risk is real but situational rather than a mass-exploitation threat, and publicly available exploit code exists in the form of a published gist, so EPSS-style prioritization should focus on multi-user Windows endpoints where a standard user and an administrator both use the same Sublime Text install. No vendor-released patch is identified in the available data at time of analysis.
Remote code execution in ClipBucket v5 (all releases before 5.5.3-#182) allows an authenticated low-privileged user to upload a PHP file that is stored and later executed by PHP-FPM, yielding full server compromise. The photo upload endpoint validates only the file's MIME type/magic bytes but never rewrites the extension, so a payload beginning with valid image magic bytes retains its .php extension on disk (CWE-434, CVSS 4.0 base 8.7 / independently assessed CVSS 3.1 as AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:H). Exploitation requires only a standard account - readily self-registered on default deployments with open registration - plus a web-executable upload directory served by PHP-FPM; there is no unauthenticated path and no public exploit code identified at time of analysis, and the issue is not confirmed actively exploited (not in CISA KEV).
Sandbox escape in vm2 3.12.0 and earlier allows unauthenticated remote attackers who can supply JavaScript to an application embedding vm2's VM or NodeVM to break out of the sandbox and execute arbitrary code on the host, provided the embedder exposes at least one host API returning a host-realm (native) Promise whose rejection value is host-pivotable - the advisory cites a host process object as the example. The flaw is an incomplete rejection-sanitization failure in lib/bridge.js: the sandbox-side Symbol.species and .then neutralization is installed only on the sandbox intrinsic Promise.prototype, so it never applies to host Promises, letting sandboxed code overwrite p.constructor[Symbol.species] and call p.then() without an onRejected handler, after which V8's internal Thrower re-throws the raw host rejection value into an attacker-controlled resolve/reject closure, bypassing handleException and hostPromiseSanitizeReject and yielding an unsanitized, fully functional bridge proxy of the host object. No public exploit identified at time of analysis, but the CVSS 4.0 base score is 10.0 and the issue is fixed in 3.12.1.
Sandbox escape in vm2 through 3.12.0 lets unauthenticated remote attackers execute arbitrary code on the host when the embedding application exposes at least one non-strict (sloppy-mode) host function to the sandbox. By calling such a function with a nullish receiver (`fn()`, `fn.call()`, `Reflect.apply(fn, undefined, [])`, etc.), sandboxed script causes V8 to substitute the host realm’s global object for `this`, which vm2 then wraps and returns as a live proxy of the host global; the attacker can then reach `process` and run commands such as `process.getBuiltinModule('child_process').execSync`. Vendor-released patch: upgrade to 3.12.1; no public exploit identified at time of analysis, but the required pre-condition is common because ordinary JavaScript functions are non-strict by default, and vm2 is deprecated, so unmaintained deployments remain exposed-independent assessment rates this a top-tier priority.
Authenticated, low-privileged users with access to the Cohesity NetBackup Flex OS management shell can inject crafted argument input into a privileged administrative command and achieve arbitrary code execution as root, gaining unrestricted control of the Flex appliance host and every container it runs. The issue is network-reachable with low attack complexity and requires no user interaction, so the only real prerequisite is a valid low-privileged shell account; scoring 9.4 under CVSS 4.0 (assessed 9.1 under CVSS 3.1), it rates as a genuine high-priority vulnerability. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so exploitation is currently limited to attackers who already hold credentials.
Remote code execution in the AF Companion WordPress plugin before version 2.2.0 lets an authenticated user who holds the plugin's low-privileged 'store-management' role upload arbitrary files, including PHP, through an import feature that performs no file-type validation. Because the uploaded PHP is executable by the web server, an attacker with that mid-tier account - a WooCommerce shop-manager-tier role rather than a full administrator - can place and run code on the host with no user interaction and no non-default configuration required. Publicly available exploit code exists for this issue, and the vendor has released version 2.2.0 to fix it; the practical limiting factor is the authenticated mid-tier role, so sites that never delegate store-management accounts to untrusted parties face materially lower risk.
Unauthenticated remote code execution affects HGiga's OAKlouds Custom Page module in the 2.0, 3.0 and 4.0 lines at builds below 26, where an attacker who can reach the Custom Page endpoint can submit malicious serialized content and have it deserialized into arbitrary code running with the web service's privileges. The CVSS 4.0 score of 9.3 reflects the worst case for an unauthenticated network attacker (PR:N, UI:N, AT:N, high confidentiality, integrity and availability impact on the vulnerable system), and the practical limiter is exposure - whether the affected instance is reachable from untrusted networks - rather than any technical precondition. No public exploit code has been identified at time of analysis and the flaw is not currently listed as confirmed actively exploited (CISA KEV), but the low attack complexity, unauthenticated access and full-system impact make this a genuinely high-priority issue for any organization running the affected builds, and a vendor fix is available.
Path traversal in Vvveb CMS 1.0.0 through 1.0.8.4 lets an authenticated user holding the default Editor role's editor/* permission write attacker-controlled PHP content into arbitrary writable files outside the active theme directory, escalating to remote code execution when the traversal target is web-accessible. Exploitation is authenticated (CVSS PR:L) but low-privilege, since the stock Editor role shipped in affected versions grants editor/* by default; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV. The vulnerability is fixed in version 1.0.8.5, which sanitizes the attacker-controlled filename and drops editor/* from the default Editor role.
Authenticated SQL injection in SQLBot before 1.9.0 allows a user with a valid account to achieve operating-system command execution inside the SQLBot container. The attacker submits a crafted sheet["tableName"] value to POST /api/v1/datasource/, SQLBot stores it unsanitized, and the value is later interpolated into datasource cleanup SQL executed by PostgreSQL when that datasource is deleted via DELETE /api/v1/datasource/{id}; a second-order injection that can reach PostgreSQL COPY TO PROGRAM and run arbitrary commands with the privileges of the postgres process. Exploitation is gated by valid credentials, a two-request state dependency (raising attack complexity, AC:H/AT:P), and the postgres role's ability to invoke COPY TO PROGRAM; there is no public exploit identified at time of analysis, and only deployments running releases prior to 1.9.0 are affected.
Authenticated remote code execution in SQLBot (dataease/SQLBot) versions prior to 1.9.0 lets an attacker with datasource-management privileges plant an arbitrary Python module inside the application's Alembic migration directory by abusing attacker-controlled multipart filenames on the POST /api/v1/datasource/parseExcel endpoint, a technique that masquerades as a CWE-22 path-traversal issue but yields module-level code execution on the next SQLBot startup or migration run. Exploitation is not immediate: the upload is written to disk before spreadsheet parsing and validation complete, so the endpoint can return a parse error while the planted file survives, and code execution is deferred until Alembic imports the module (independent assessment scores CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Vendor-released patch: 1.9.0; no public exploit identified at time of analysis, though the upstream advisory and fix commits are public.
Use-after-free code execution in PDFium, Chrome's bundled PDF rendering engine, allows a remote attacker who lures a victim into opening a crafted HTML page to run arbitrary code inside Chrome's renderer sandbox on any build prior to 153.0.8010.52. The bug is network-reachable and low-complexity with no authentication required, but it does require user interaction (the victim must navigate to the attacker-supplied page), and because the CVSS scope is unchanged (S:U) the compromise is contained within the renderer - full system takeover would require chaining a separate sandbox-escape flaw. Google has released a fixed build and there is no public exploit identified at time of analysis, though the CVSS 8.8 score and memory-corruption tag make timely patching advisable.
Heap buffer overflow in PDFium, the PDF rendering engine built into Google Chrome, allows a remote attacker to potentially execute arbitrary code inside the Chrome renderer sandbox on Windows systems running versions prior to 153.0.8010.52. Exploitation requires the victim to open an attacker-supplied crafted PDF (UI:R), so the attack is delivered via social engineering rather than direct network exploitation; no credentials are needed (PR:N) and default Chrome installations render PDFs without any special configuration. The vendor rates this High severity with a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), and although a vendor patch is available, no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV). Because code execution is confined to the renderer sandbox, full host compromise would additionally require a separate sandbox-escape vulnerability not covered by this advisory.
Type confusion in the V8 JavaScript engine of Google Chrome prior to 153.0.8010.52 allows remote, unauthenticated attackers to execute arbitrary code inside the renderer sandbox when a victim is socially engineered into loading a crafted HTML page (CVSS 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is not automatic: it requires user interaction, and because the resulting code execution is confined to the renderer sandbox, turning it into host-level compromise would require chaining a separate sandbox-escape vulnerability. There is no public exploit code identified at time of analysis and the flaw is not listed in CISA KEV, but a vendor patch (Chrome 153.0.8010.52) is available and this is a patch-now item for a ubiquitous product.
Local sandbox escape in Google Chrome on Windows (versions prior to 153.0.8010.52) lets an attacker who can already execute a program on the target host run arbitrary code outside the browser sandbox by abusing incorrect reference resolution in Chrome's Tracing component (CWE-706). The vendor rates it High with a CVSS of 8.1 (AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H), meaning exploitation is local-only, requires no user interaction, but is gated by high attack complexity - consistent with a race or timing-dependent condition that is not reliably repeatable. No public exploit code has been identified at time of analysis, and because a local foothold is a prerequisite, this is realistically a chained sandbox-escape stage rather than a standalone initial-access vulnerability.
Use-after-free in the Dawn (WebGPU) component of Google Chrome on Android before 153.0.8010.52 allows a remote, unauthenticated attacker to potentially execute arbitrary code outside the browser sandbox when a victim renders a crafted HTML page. Exploitation requires the user to load attacker-controlled content (CVSS 9.6, AV:N/AC:L/PR:N/UI:R), and Google rates the bug Chromium security severity Critical; the only affected configuration is Chrome on Android below the fixed 153.0.8010.52 build, and devices already updated are not exposed. There is no CISA KEV listing and no public exploit identified at time of analysis, so the practical risk is driven by the size of the unpatched Android install base rather than by observed attacks.
Use-after-free in Google Chrome's Extensions component allows a remote attacker to execute arbitrary code outside the browser sandbox on any desktop build prior to 153.0.8010.52, provided the victim loads a crafted, attacker-controlled extension. The flaw carries a 9.6 CVSS score (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), meaning no prior authentication to the target is needed, but the attacker must still persuade the user to install or load a malicious extension, which is the real-world limiting factor; the sandbox-scope change (S:C) reflects code execution escaping Chrome's renderer/extensions sandbox. A vendor patch shipping in 153.0.8010.52 is available, and no public exploit code or confirmed active exploitation has been identified at time of analysis. Because Chrome auto-updates aggressively, the exposed population shrinks quickly once the fixed build propagates.
Remote code execution outside the browser sandbox in Google Chrome on Android prior to 153.0.8010.52 is possible when a victim opens a crafted HTML page containing malicious WebGL content that triggers a stack-based buffer overflow. Unauthenticated remote attackers can achieve code execution in the context of the GPU/renderer process with high impact to confidentiality, integrity, and availability, though exploitation requires user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6, Chromium security severity Critical). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; Google has released a fixed build (153.0.8010.52) and the flaw is tracked as EUVD-2026-82476 and VulDB 407131.
Symlink-based archive extraction in Grafana OSS and Grafana Enterprise lets a malicious plugin archive write arbitrary files - including an executable backend binary - outside the plugin installation directory, and that binary then runs with the Grafana server process's privileges, yielding remote code execution. Exploitation is gated on a Grafana operator installing a plugin from an attacker-influenced archive (via the plugin catalog, grafana-cli, GF_INSTALL_PLUGINS, or preinstall configuration), which is the UI:R component of the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H vector; there is no unattended remote trigger against a running server. A key aggravating factor is that plugin archives are extracted before their signature is verified, so enforcing signed plugins does not mitigate this issue, and Grafana Enterprise carries the identical extraction code. No public exploit code has been identified at time of analysis, and the vulnerability is not in CISA KEV; independent assessment rates this a genuine high-priority issue rather than a high-CVSS-but-low-real-risk paper cut.
Memory corruption in OpenSlide's Ventana BIF parser (versions 3.4.1 through 4.0.1) allows a crafted whole-slide image to write attacker-chosen values to attacker-chosen memory offsets, crashing the process that opens the slide or potentially achieving arbitrary code execution. Any application, viewer, or server-side tiling/conversion service that uses the affected library to ingest untrusted Ventana .bif files is exposed, since the defect is not configuration-dependent and affects all supported platforms; exploitation requires a user or process to open the malicious file, and reliable code execution (as opposed to a crash) further depends on controlling heap layout. No public exploit code or confirmed active exploitation was identified at time of analysis, but the underlying write-what-where primitive makes this a high-severity risk for digital-pathology pipelines that accept third-party or uploaded slides.
Unauthenticated remote code execution in Chamilo LMS 2.0.0 and earlier lets any network-reachable attacker run arbitrary code on the server through the CStudio editor plugin's import-project big-upload endpoint, which shipped without an authentication check and without sanitizing attacker-supplied filenames. Graded CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H) with no special prerequisites beyond the CStudio upload flow being deployed and reachable, this is assessed as a genuine top-tier priority for any exposed instance; no public exploit code was identified at time of analysis and no CISA KEV listing applies, though the vendor-released patch in 2.0.1 fully closes the issue.
Arbitrary code execution is possible inside the NetBox Device Type Library's pytest validation harness because the test suite deserializes pull-request-controlled pickle cache files via pickle.load. An unauthenticated contributor can flip USE_LOCAL_KNOWN_SLUGS in tests/test_configuration.py and commit a crafted tests/known-modules.pickle or tests/known-racks.pickle in the same pull request, so the payload fires whenever the tests are run: automatically by the GitHub Actions validation workflow on the PR, or by a maintainer executing pytest locally against the untrusted branch (the user-interaction requirement in the CVSS vector). Affected deployments are the repository's CI pipeline and any maintainer workstation running the suite, not NetBox servers that merely import the library's device definitions; no public exploit code has been identified at time of analysis, and GitHub Actions exposure is bounded by the read-only token granted to pull_request workflows, while a privileged local test run carries full confidentiality, integrity and availability impact.
Loading a crafted legacy X10 'static short' XBM image with SAIL versions prior to 1.0.0 triggers a forward heap buffer overflow in sail_codec_load_frame_v8_xbm() that lets a file-controlled write corrupt process state, reliably crash the consuming application, and potentially achieve code execution depending on the host's memory layout and mitigations. The flaw is reachable through sail_load_from_file, sail_load_from_memory, and sail_start_loading_*, but only when the destination image has an odd row stride (ceil(width/8) odd) and only on the X10 short path - the X11 'static char' path is explicitly unaffected. Exploitation is local and file-based (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8) and requires the victim to open the malicious image; no public exploit code or confirmed active exploitation was identified at time of analysis, and the impact scales with image height.
Heap-based buffer overflow in the SAIL image library's PSD decoder affects versions 0.9.10 and earlier, letting a crafted PSD file corrupt heap memory, reliably crash the host process, and potentially achieve code execution. Any application that passes attacker-controlled PSD data to sail_load_from_file() or sail_load_from_memory() is exposed; the CVSS vector carries PR:N (unauthenticated against the library), but practical exploitation still requires a victim to open or process a malicious image (UI:R), so the vendor's 9.8/UI:N rating overstates real-world risk. No public exploit code or confirmed active exploitation was identified at time of analysis, and the flaw is fixed in SAIL 1.0.0.
Heap-based buffer overflow in the SAIL cross-platform image library version 0.9.10 and earlier allows an attacker who supplies a crafted color-mapped, run-length-encoded TGA file (image_type == 9) to write attacker-controlled bytes past the end of a heap pixel buffer, causing heap corruption, a reliable crash, or potential code execution. The flaw is an incomplete fix for CVE-2026-40494: the earlier pixel-count clamp limits how many pixels are written but never constrains the per-pixel write width, which is derived from an attacker-controlled header bpp value of 9 through 32 (2-4 bytes) while the destination buffer is allocated as one-byte-per-pixel SAIL_PIXEL_FORMAT_BPP8_INDEXED. Although the CVSS vector is AV:N/PR:N, exploitation requires the victim's application to load the malicious image through sail_load_from_file() or sail_load_from_memory(), so a user-interaction condition is inherent; no public exploit code was identified at time of analysis, and the issue is fixed in SAIL 1.0.0. Note that the vendor-published CVSS of 9.8 (UI:N) overstates exploitability relative to the independent assessment of CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
Unauthenticated remote code execution affects Wavelog amateur radio logging software versions 1.8 through 2.4.1 because the installer endpoints /install/ajax.php and /install/includes/interface_assets/triggers.php remain reachable after setup and pass unsanitized input into configuration-writing routines. An attacker who can reach the exposed /install/ path can inject attacker-controlled PHP into configuration files, resulting in code execution on the server, with no authentication or user interaction required (CVSS vector PR:N/UI:N). The issue is fixed in version 2.4.2, and no public exploit identified at time of analysis.
Arbitrary code execution in the CI pipeline of the NetBox devicetype-library repository lets an unauthenticated contributor run attacker-controlled Python on GitHub Actions runners by submitting a pull request that adds a shadowing module (for example tests/git.py to hijack the harness's 'from git import ...') or a tests/conftest.py that pytest auto-imports during collection. The flaw exists because the repository lacks tests/__init__.py and invokes pytest without --import-mode=importlib, so pytest's default prepend import mode places tests/ and the repository root at the front of sys.path, causing PR-supplied files to take precedence over installed packages such as GitPython. Per the assessed vector (AV:N/AC:L/PR:N/UI:R), exploitation is unauthenticated but gated by user interaction: PR-supplied code only executes when a maintainer approves or runs the fork-PR workflow, and by default fork-PR workflows receive a read-only GITHUB_TOKEN with no repository secrets, so token or secret theft is fully realized only where that approval gate is disabled, on workflows with write tokens, or when a maintainer runs the harness locally; no public exploit code was identified at time of analysis, and this is a CI/supply-chain code-execution issue affecting the repository's build pipeline rather than any deployed NetBox instance.
Local privilege escalation to root in NetworkManager-l2tp: a local user who holds NetworkManager VPN-connection-creation permission (typically granted through polkit on a desktop or shared Linux host) can smuggle an arbitrary pppd 'plugin' directive into the root-owned pppd options file by setting the L2TP connection's mru or mtu property to a valid integer followed by trailing non-numeric text, for example '1400 plugin /tmp/evil.so'. Because the plugin directive is consumed by the privileged pppd process when the crafted VPN connection is activated, pppd loads an attacker-controlled shared object and executes code as root. No public exploit code has been identified at time of analysis, there is no confirmed active exploitation, and the flaw is strictly local with no remote or network-facing exposure; the practical bar is the PR:L gate, since an ordinary unprivileged account cannot trigger it unless it has been given VPN management rights.
Authentication bypass in the FaustWP WordPress plugin before 1.8.11 lets an authenticated low-privilege user (PR:L - for example a Subscriber) tamper with a valid authorization-code envelope and obtain an Administrator access token, enabling full WordPress REST API access, administrator-account creation, plugin installation, and ultimately arbitrary code execution (CVSS 8.8, CWE-345). Because the token HMAC does not cover the 16-byte AES-CBC initialization vector, XOR-ing a few bits into the IV deterministically rewrites the first decrypted block so that a Subscriber's "ac|2|<exp>" authorization code becomes "at|1|<exp>" - an admin access token - while the HMAC still validates. Exploitation is network-reachable and needs only a logged-in account able to call GET /generate plus the plugin's headless auth flow being active; no admin privileges and no victim interaction are required. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, though the published patch diff and regression tests make the technique trivially reproducible.
Hard-coded pacman signing key in lxc-ci's Arch Linux image build lets a mirror-position attacker forge trusted packages and execute code as root on affected guests. Images built from images/archlinux.yaml and published before 2026-05-28 embed the same pacman local-signing private key in /etc/pacman.d/gnupg, and every container or VM created from those images inherits it (CWE-321); because the key can be recovered from any published image, the assessed vector (AV:N/AC:H/PR:N/UI:R) positions an unauthenticated remote attacker who operates or intercepts an HTTP package mirror to sign tampered packages that clients accept during a root install or update. Exploitation is gated by three conditions - a pre-2026-05-28 image, attacker mirror/on-path control, and a victim-initiated root package operation - so it is a genuine supply-chain trust failure rather than a fully automatable one; no public exploit identified at time of analysis.
Stack-based buffer overflow in MCC Universal Library for Linux (uldaq) 1.2.1 and earlier lets a local attacker corrupt memory inside any process that loads the library, yielding arbitrary code execution or information disclosure at that process's privilege level. Exploitation requires crafted input to reach the vulnerable parsing routine - realistically an attacker-controlled or spoofed MCC USB data-acquisition device attached to the host, or attacker-supplied data processed by an application linked against uldaq - and needs no credentials and no user interaction (CVSS 4.0 8.6; assessed CVSS 3.1 8.4-equivalent vector AV:L/AC:L/PR:N/UI:N). No public exploit identified at time of analysis, and although impact is high, the local-only attack vector makes this a genuinely high-impact but access-constrained flaw.
Heap-based buffer overflow in rabbitmq-c, the C-language AMQP client library, affects all versions prior to 0.16.0 and is triggered when a malicious or compromised AMQP broker sends an undersized connection.tune frame_max value during the amqp_login() handshake. Because amqp_tune_connection() reallocates the outbound frame buffer using the attacker-supplied value without enforcing AMQP_FRAME_MIN_SIZE, the immediately serialized connection.tune-ok frame overflows the undersized heap allocation, producing memory corruption and likely denial of service, with code execution considered theoretically possible but not demonstrated. Exploitation requires the victim client to initiate a connection to attacker-controlled infrastructure (CVSS 7.1, AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H), or an on-path attacker to inject the malicious tune frame into plaintext, non-TLS AMQP traffic; no public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor-released patch in version 0.16.0 is available.
Unauthenticated remote code execution affects SolarWinds Access Rights Manager 2026.2 and all earlier versions, where a hardcoded static cryptographic key (CWE-321) shipped in default installations allows an attacker to execute arbitrary code with full confidentiality, integrity, and availability impact. Per the vendor CVSS vector (AV:A/AC:L/PR:N/UI:N), no credentials and no user interaction are required, but the attacker must be positioned on an adjacent or same-segment network rather than reaching the service across arbitrary internet paths - a point that conflicts with the advisory's 'remote' wording and should be confirmed with SolarWinds. No public exploit code was identified at time of analysis and the CVE is not listed in CISA KEV, so there is no confirmed active exploitation, though the combination of unauthenticated access, low complexity, and full CIA impact makes this a high-priority fix for any exposed deployment.
Remote code execution in MISP prior to 2.5.47 allows an authenticated attacker who can submit the platform's events/contact form to run arbitrary PHP as the MISP web user. By setting the contact form's 'person' field to a reserved CakePHP console switch such as '-app' and the adjacent 'message' field to a phar:// URI, the attacker redirects the background-job worker's application root into an attacker-controlled archive whose Config/core.php is then included - a deterministic, single-shot exploit requiring authenticated access to the submission endpoint (CVSS 3.1 AV:N/AC:L/PR:L/UI:N, rated 8.7 under CVSS 4.0) and no timing or race condition. Exploitation status per available intelligence: no public exploit identified at time of analysis, EPSS is low at 0.50% (42nd percentile), and CISA SSVC records Exploitation: none, though the flaw is fully fixed only by upgrading to 2.5.47 and the impact of success is full server-side compromise of the web process.
HortusFox-Web releases prior to 6.1 expose the Import/Export data-portability feature to arbitrary file write, letting an authenticated administrator execute OS commands as the web server user by slipping a PHP file into the web-accessible public directory. The flaw carries a CVSS 4.0 score of 8.6 (assessed as CVSS 3.1 AV:N/AC:L/PR:H/UI:N/C:H/I:H/A:H, high confidentiality, integrity and availability impact) and is gated behind administrator privileges plus the operator running an import of attacker-supplied data, so it is not remotely exploitable by an unauthenticated user on a default install. Vendor patching is available via the 6.1 release and the upstream commit 1c7108f; no public exploit code or confirmed active exploitation was identified at time of analysis.
Argument injection in Appwrite before 2.0.0 allows an authenticated user holding the functions.write or sites.write permission to turn a crafted providerRootDirectory value into arbitrary GNU tar command-line arguments, escalating to remote code execution as the builds worker process user via payloads such as --checkpoint-action=exec. The flaw is not admin-only: the assessed CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, vendor score 8.7 under CVSS 4.0) reflects that a low-privileged, authenticated account with deployment-write rights over a reachable Appwrite instance is sufficient, with no user interaction and no non-default configuration required. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; a vendor-released fix is available in Appwrite 2.0.0, making this a genuine high-priority issue rather than a CVSS-inflated one.
Code execution can be achieved through an uncontrolled search path in Dell Server Update Utility (SUU) and its bundled Driver Packs for Windows and Linux at all versions prior to 26.07.01, which load libraries from locations an attacker may be able to control (CWE-427). Exploitation is local and not remotely reachable: per the CVSS vector (AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H) an attacker must already hold low-privileged local access, must be able to plant a malicious library in a directory the utility searches, and must wait for a higher-privileged user or administrator to subsequently run SUU so the planted code loads with that user's privileges. No public exploit code was identified and the flaw is not confirmed as actively exploited (not in CISA KEV); Dell has released a fixed version, 26.07.01, via advisory DSA-2026-422.
Unauthenticated PHP object injection in b2evolution CMS 6.7.8 through 7.2.5 lets remote attackers POST crafted serialized payloads to htsrv/call_plugin.php that bypass the incomplete CVE-2016-8901 validation fix and reach unserialize(), instantiating arbitrary PHP objects with attacker-chosen properties. The vendor rates this 9.2 (CVSS 4.0 AV:N/AC:L/AT:P/PR:N/UI:N with VC/VI/VA:H, so unauthenticated network reach into a PHP unserialize() sink), while the independent assessment scores it high (CVSS 3.1 AV:N/AC:H/PR:N/UI:N, C/I/A:H) because full code execution additionally requires a suitable POP gadget chain to exist in the deployed version or its active plugins; absent such a chain, impact is limited to arbitrary object instantiation and magic-method side effects. No public exploit code has been identified at time of analysis, and the affected branch is end-of-life, making unpatched legacy installs the realistic target.
Sandbox escape in the vm2 Node.js sandboxing library before 3.11.7 lets an attacker who supplies a malicious script file to the vm2 command-line tool execute arbitrary code in the host Node.js process, gaining access to host modules such as fs and child_process. The vulnerable entry point is the CLI utility specifically, not the library's programmatic VM/NodeVM API: an attacker-crafted script uses require(__filename) to re-execute itself in the host realm and slip past the sandbox membrane. Exploitation is local rather than network-facing (CVSS 4.0 AV:L/UI:P, PR:N), requiring a victim or automated job to invoke the vm2 CLI against the attacker-controlled file; the vendor rating is 9.3 (critical), but the local vector and required user interaction make real-world exposure materially narrower than the network-facing vm2 escapes, and there is no public exploit identified at time of analysis.
Sandbox escape in vm2 3.9.6 through 3.11.6 lets attacker-supplied JavaScript running inside a NodeVM break out and execute arbitrary code in the host Node.js process when three conditions line up: the host runs Node.js 24 or newer, the embedder has explicitly allowlisted the node:test builtin, and the sandboxed code is under attacker control. The bypass exists because vm2's family-based DANGEROUS_BUILTINS check does not recognise Node.js 24's scheme-only 'node:test' key, so the module is placed in the generic host-passthrough loader, and a single 'node:' prefix strip in requireImpl() means require('node:node:test') resolves to that stored key; forwarded node:test.run() calls reach the host implementation, which spawns a separate Node process and honours attacker-supplied execArgv values such as --eval=<JavaScript>. Vendor severity is 9.4 (CVSS 4.0) and our independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, a genuine full sandbox escape to host code execution whose real-world reachability is constrained by the hard Node.js 24+ and non-default node:test allowlist prerequisites; no public exploit identified at time of analysis. Fixed in vm2 3.11.7.
Sandbox escape leading to remote code execution affects the vm2 Node.js sandbox library before version 3.11.7 when the embedding application enables require.external without an explicit require.root that excludes node_modules. Under that configuration, attacker-supplied JavaScript running inside the sandbox can require vm2's own package, construct an unrestricted NodeVM instance, and then execute arbitrary host OS commands through child_process, yielding a complete escape from the sandbox to the underlying operating system. Exploitation requires two operator-chosen, non-default preconditions (running untrusted code in vm2 AND the permissive require configuration), so deployments that leave require.external disabled or pin require.root away from node_modules are not exposed; no public exploit code was identified at time of analysis, and the vendor-released fix is version 3.11.7.
Sandbox escape in the vm2 npm library versions 3.10.2 through 3.11.6, when running on Node.js 26, allows attacker-supplied JavaScript to break out of the sandbox and reach the host Function constructor and process object, resulting in arbitrary code execution. The escape is unauthenticated and requires no special vm2 configuration - no require.external, builtin allowlists, or unsafe options - but it is gated on the Node.js 26 / V8 14.6 runtime, so the same vm2 versions on other Node.js major versions are not affected by this finding. No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical prerequisite is that a deployment accepts and executes untrusted code inside vm2, which is the library's core threat model.
Sandbox escape and arbitrary native code execution in vm2 3.11.3 through 3.11.6 occurs when a NodeVM sandbox is configured to allow the host crypto builtin: sandboxed JavaScript can reach crypto.setEngine() and hand it a filesystem path pointing at an attacker-supplied shared library (for example one shipped inside an untrusted plugin package already unpacked to disk), which OpenSSL passes to the operating system's dynamic loader and whose constructor then executes in the host process. Exploitation needs the crypto builtin alone - fs, process, module, child_process, worker_threads, vm and inspector access are all unnecessary - and there is no public exploit code or confirmed active exploitation (no CISA KEV listing) at time of analysis, though the reporter-assigned score of 9.4 reflects the severity if those prerequisites are met. Real-world urgency is gated by deployment-specific factors: the crypto builtin must be explicitly exposed to the sandbox and the host must already contain an attacker-writable native library, so a patched release or a tightened builtin allow-list fully removes the attack surface.
Native code execution outside the sandbox affects vm2 versions 3.11.3 through 3.11.6 when the host node:sqlite builtin is exposed to a NodeVM sandbox - either explicitly or through the wildcard builtin: ['*'] - which is not a default configuration. Sandboxed plugin code can create an in-memory DatabaseSync with extension loading turned on, resolve an attacker-supplied native library via a __dirname-derived path, and call loadExtension(), causing SQLite to load that library into the Node.js host process and execute its native entry point with host privileges; the vm.readonly() wrapper prevents property assignment but leaves host-authority callables reachable, and a 'node:node:sqlite' double-prefix quirk in the resolver/prefix-stripping logic lets the sandbox reach the configured builtin. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV) - the vendor released vm2 3.11.7 to fix it. Real-world priority is strongly gated by configuration: exploitation requires all of permitting node:sqlite in the sandbox, enabling SQLite extension loading, and having an attacker-controlled .so/.dll on disk within the plugin package.
Sandbox escape leading to remote code execution in vm2 3.11.6 lets untrusted code inside the sandbox reach a live proxy to a host-realm object and run commands with the host process privileges, for example through e.detail.mainModule.require('child_process').execSync(...). The flaw is an incomplete fix for GHSA-m283-3h24-438v: registering a rejection handler via Function.prototype.call or .apply indirection (p.then.call(p, undefined, cb)) bypasses the identity check at lib/bridge.js:1624, so the raw host Error and its non-primitive own properties are handed to sandbox code. Exploitation is conditional: the embedder must bridge an async host Promise into the sandbox and that Promise must reject with an Error carrying a non-primitive own property that references a host object (for example err.detail = process); direct p.then(undefined, cb), .bind and Reflect.apply forms are correctly sanitised. Upgrade to vm2 3.11.7 closes the bypass; no public exploit identified at time of analysis.
Sandbox escape and remote code execution in vm2 versions 3.11.4 through 3.11.6 allow JavaScript executed inside a NodeVM to break out and run arbitrary commands with the privileges of the host Node.js process. The flaw is reachable only in a specific, non-default configuration where the NodeVM is created with a truthy `nesting` value and an array-shaped `require` option (for example `new NodeVM({nesting: true, require: []})`); in that case the array satisfies a guard intended to reject nesting without an explicit require configuration, and the resulting resolver falls back to a nesting override that permits the sandboxed code to require the host `vm2` module and construct an inner NodeVM with an attacker-chosen builtin allowlist such as `child_process`. Exploitation requires no authentication or user interaction (CVSS 4.0 vector reports PR:N/UI:N) beyond the ability to supply code the sandbox runs, which is vm2's intended threat model; there is no public exploit code or CISA KEV confirmation of active exploitation at time of analysis, but the impact is complete confidentiality, integrity, and availability loss on the host, and the vendor CVSS 4.0 score of 9.5 is consistent with that assessed impact.
Sandbox escape in vm2 before 3.11.8 allows unauthenticated remote attackers to achieve full remote code execution and host process information disclosure by crafting a host-wrapped AggregateError that is revisited within a single exception-handler traversal, bypassing handleException's cycle detection and exposing unsanitized host proxies in the errors array. The flaw is an incomplete fix for Error.cause sanitization, and exploitation requires the host application to execute attacker-controlled JavaScript inside a vulnerable vm2 instance, which is vm2's normal use case, though the malformed-error and traversal condition is non-trivial (CVSS AC:H/AT:P). No public exploit identified at time of analysis; environments that do not run untrusted code in vm2, or that have migrated off the deprecated vm2, are not exposed.
Path traversal in HUBzero CMS through 2.2.32 lets authenticated project members write files to arbitrary paths outside the project repository, potentially achieving code execution when the written file lands in a web-servable, executable location. The flaw lives in the com_projects file-upload API (filefsv1_0.php upload/download tasks and filesv1_0.php chunkedUploadTask) and the projects/files plugin, where the 'subdir' and chunked-upload 'flowIdentifier' parameters flow unsanitized into move_uploaded_file/copy and base64-derived temp-directory paths. Exploitation is remote and needs no user interaction but requires a low-privileged project-member account (CVSS v4.0 PR:L); vendor fix commits are published, yet no public exploit code has been identified at time of analysis and the issue is not known to be actively exploited.
Unauthenticated remote code execution in Migratico Lite, a WordPress site-migration plugin, affects all versions up to and including 2.6.8 and lets a remote attacker who can reach an affected site inject and execute arbitrary code with the privileges of the web server. The vendor-disclosed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H = 10.0, reported by Patchstack) requires no authentication and no user interaction, so any WordPress installation running an affected plugin version is potentially exposed; our independent assessment keeps the same network/authentication profile but scores scope as unchanged (S:U), giving an effective base score of 9.8. Exploitation is tempered by practical limits: Migratico Lite is a niche migration plugin with a modest install base, and the sparse public advisory does not disclose the vulnerable endpoint or parameter, so no public exploit code has been identified at time of analysis and weaponization currently depends on an attacker locating the injection sink themselves. There is no CISA KEV entry for this CVE.
Remote code execution as root on FatPipe MPVPN, WARP, and IPVPN appliances running the end-of-life 10.1.2r60p100 firmware is possible when an attacker can reach the management interface and submit a crafted authentication request that overflows a fixed-size stack buffer in /usr/sbin/auth_user_pass. The vendor score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects unauthenticated, no-interaction exploitation with high confidentiality, integrity, and availability impact, but real-world exposure is gated: the management interface is disabled by default and must be affirmatively enabled by the customer, and WAN access control lists are recommended to restrict reachability to trusted administrative networks. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; because 10.1.2r60p100 is end-of-life, no patched firmware version has been identified, so exposure persists until the appliance is decommissioned or tightly network-isolated.
Stack-based buffer overflow in Dell OpenManage Server Administrator (OMSA) versions prior to 11.1.0.3 allows an attacker who already holds high privileges on the OMSA service to achieve remote code execution over the network. Exploitation is constrained by the CVSS PR:H prerequisite-only compromised administrative accounts, malicious insiders, or chaining from another privilege-granting flaw can trigger it-but no user interaction is required and attack complexity is low. No public exploit code or CISA KEV active exploitation is identified in the available intelligence.
Remote code execution in Dell OpenManage Server Administrator (OMSA) managed-node installations prior to 11.1.0.3: a heap-based buffer overflow (CWE-122) that an attacker holding administrator-level privileges on the OMSA service can trigger over the network without user interaction, gaining code execution on the managed host with full confidentiality, integrity, and availability impact. The flaw scores 7.2 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and affects Windows, RHEL 8.10, RHEL 9.4, SLES 15, and Ubuntu 22.04 managed nodes. No public exploit code and no confirmed active exploitation were identified at time of analysis; the high-privilege prerequisite keeps this a privileged-user-to-code-execution escalation rather than a pre-authentication internet-facing exploit, with risk rising where OMSA is exposed to untrusted networks or chained after an authentication bypass such as CVE-2026-81475 in the same DSA-2026-403 bundle.
Unauthenticated remote code execution in the wpShopGermany IT-RECHT KANZLEI WordPress plugin affects every release from 1.6 up to but not including 2.4. The plugin builds its API authentication token from data the requester supplies and creates that token as a side effect of the routine that is supposed to validate it, so an attacker can compute a valid token without any credentials and use the access it grants to write arbitrary files on the server, which in a PHP/WordPress context converts directly into code execution. No authentication or user interaction is required - only network reachability to the plugin's token-authenticated API endpoint - and publicly available exploit code exists (the finding was published by WPScan). Our independent assessment rates the realistic vector as AC:L/PR:N/UI:N/S:U with high confidentiality, integrity and availability impact, a step more severe than the vendor's 9.0 AC:H/S:C rating; the practical brake on this issue is deployment scope, since this is a niche legal-compliance plugin rather than a mass-market component.
Unauthenticated arbitrary file upload in the Multi Uploader for Gravity Forms WordPress plugin (all versions up to and including 1.1.9) lets attackers write executable files to the affected site's server through the move_file() chunked-upload handler, which applies insufficient file-type validation, making remote code execution possible. Exploitation requires the plugin to be installed and active alongside the commercial Gravity Forms plugin and a publicly reachable form that exposes a multi-uploader field; the CVSS vector (PR:N/UI:N) confirms no authentication or victim interaction is needed, though RCE additionally depends on the uploaded file landing in a web-executable location. Risk is rated high-priority (CVSS 9.8), with the practical exposure narrowed by the plugin's niche deployment and its Gravity Forms dependency; no public exploit code and no CISA KEV active-exploitation entry were identified at time of analysis.
Unauthenticated arbitrary file upload in the Paid Downloads WordPress plugin (all versions up to and including 3.15) lets remote attackers bypass authorization and file-type checks in the admin_request_handler function to place attacker-controlled files on the server, which can lead to remote code execution. The flaw is reachable without credentials because is_admin() returns true for requests to /wp-admin/admin-post.php, and the handler performs neither a capability check nor an extension/content validation; per assessment, the AC:H rating reflects that reliable code execution depends on server configuration - Apache deployments with AllowOverride enabled may have retrieval of the uploaded file blocked by a plugin-placed .htaccess, confining dependable RCE to nginx, LiteSpeed, or Apache with AllowOverride None, while the upload and authorization bypass itself succeeds on any stack. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV, but the unauthenticated upload primitive combined with a CVSS 8.1 score makes this a high-priority, patch-dependent risk for any site running the plugin.