Memory-exhaustion denial of service in pypdf versions prior to 6.17.0 allows remote attackers to inflate application memory usage by supplying a crafted PDF whose /PageLabels /Nums dictionary declares a Roman-numeral numbering style (/S /R) with an extremely large start value (/St), causing the library to construct a numeral string proportional to that value. The CVSS:4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, VA:H) indicates an unauthenticated, network-reachable, low-complexity attack with high availability impact and no confidentiality or integrity effect, but the practical precondition is that the consuming application must actually invoke pypdf's page-label retrieval on attacker-supplied documents - applications that never read page labels are unaffected. No public exploit code has been identified at time of analysis and there is no CISA KEV entry; the vendor released a fix in 6.17.0 that rejects Roman start values above 3,999.
PHP object injection in the Photo Gallery by 10Web WordPress plugin (versions up to and including 1.8.46) allows an authenticated user with Contributor-level privileges to pass crafted serialized data into a plugin code path that calls unserialize(), which under CVSS 3.1 scores 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Successful exploitation can corrupt or disclose data and, if a usable PHP gadget chain exists in the plugin, WordPress core, or another active plugin, can escalate to arbitrary code execution on the web server; no user interaction is required once the low-privileged account exists. At the time of analysis there is no CISA KEV listing and no public exploit code identified, and authentication as Contributor or higher is a firm prerequisite, so exposure is concentrated on sites that grant Contributor+ roles to untrusted users or leave open registration enabled.
PHP object injection in the Schema & Structured Data for WP & AMP plugin (all versions up to and including 1.66) lets an authenticated attacker with a Contributor-level WordPress account feed crafted serialized input into a plugin deserialization path, and the vendor's CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8 High) rates that as low-complexity, network-reachable and capable of full confidentiality, integrity and availability impact once a usable POP gadget chain is available in the plugin, WordPress core or another installed component. Authentication is mandatory and there is no unauthenticated route, but no user interaction is required after the attacker holds a qualifying account; the practical exposure therefore depends on whether the site permits open registration or loosely manages Contributor roles. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so the primary risk is post-authentication privilege escalation rather than opportunistic mass exploitation.
Authentication bypass in Trex MES allows unauthenticated attackers positioned on the same adjacent network segment to invoke a critical function without supplying credentials, delivering full confidentiality, integrity, and availability impact (CVSS 3.1 base 8.8, vector AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Exploitation is limited to attackers who can reach the MES host over the local or OT network - the flaw is not reachable from the public internet - but no privileges or user interaction are required and attack complexity is low, so any host on that segment can trigger it against affected builds through 2026-09-29. No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied; the practical exposure depends almost entirely on how tightly the MES network is segmented.
Cross-site request forgery in the WordPress plugin Blacklist Manager - WooCommerce Anti-Fraud, Blacklist & Checkout Verification (versions through 2.3.1) lets a remote, unauthenticated attacker forge state-changing requests that execute with the privileges of a logged-in victim who loads attacker-controlled content. Exploitation is not autonomous: it requires an authenticated user with a live session - typically an administrator or shop manager - on a site where WooCommerce and this plugin are both installed and active, and that user must be tricked into visiting a malicious page (CVSS UI:R, PR:N means the attacker needs no credentials of their own, not that the victim is anonymous). The published CVSS 3.1 base score of 8.8 (C:H/I:H/A:H) appears inflated for a CSRF issue; our independent assessment rates it AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L, reflecting high integrity impact but limited confidentiality and availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Remote code execution in the CartFlows WordPress plugin affects versions 3.2.0 and earlier, allowing an authenticated user with Contributor role or higher to execute arbitrary code on the hosting server. The flaw is a PHP include/require path-control weakness (CWE-98) with a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires a valid low-privileged account but no user interaction. No public exploit was identified at time of analysis, and the practical exposure depends on whether the site grants Contributor access to untrusted users.
Authenticated Contributor-level users can exploit a PHP Object Injection vulnerability in Themify Builder versions up to and including 7.8.1. The flaw, caused by unsafe deserialization (CWE-502), allows an attacker with a Contributor account to inject a serialized PHP object, potentially leading to remote code execution or full site compromise if a usable PHP gadget chain exists in the WordPress installation. The vendor-assigned CVSS score is 8.8 (High), and no public exploit code has been identified at the time of analysis.
PHP object injection in the quantumcloud Conversational Forms for ChatBot WordPress plugin (versions through 1.5.0) lets any authenticated Subscriber-level user reach full confidentiality, integrity, and availability impact, matching the High 8.8 CVSS 3.1 score (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is remote, low-complexity, and requires no user interaction, but real-world severity depends on whether WordPress core or other installed plugins supply a usable PHP POP gadget chain that turns object injection into code execution or destructive file/database operations. No KEV or public-exploit signal was present in the supplied intelligence, so active exploitation is not confirmed from this data.
PHP object injection in the WordPress plugin DesignSetGo 2.8.0 and earlier allows an authenticated user with Contributor-level access to submit a crafted serialized payload, which the plugin then deserializes, potentially leading to data theft, file manipulation, or remote code execution depending on which PHP gadget chains are reachable in the site's loaded code. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) confirms remote, low-complexity exploitation requiring only a low-privileged authenticated account and no user interaction, and the impact is assessed as high across confidentiality, integrity, and availability - though the practical outcome depends on the presence of a usable gadget chain. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV (not confirmed actively exploited); no EPSS score was supplied, but the self-registerable nature of the Contributor role on many sites keeps the real-world risk elevated.
PHP object injection in the WordPress plugin Go Live Update Urls (Mat Lipe) version 7.0.8 and earlier allows an authenticated attacker holding at least the Contributor role to pass crafted serialized data that the plugin deserializes, potentially leading to full confidentiality, integrity, and availability impact on the affected site if a usable PHP gadget chain is present in the plugin, WordPress core, or another installed theme/plugin. The vulnerability is network-reachable with low attack complexity, requires only low-privileged authentication (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 8.8 High) and no user interaction; exploitation additionally depends on the availability of a viable POP gadget chain, a common but not universal precondition. At the time of analysis there is no public exploit identified and no confirmation of active exploitation (not listed in CISA KEV), and no vendor-released fixed version is confirmed in the available data. Risk triage should treat this as a high-priority issue for any site running the vulnerable plugin where Contributor accounts are easily obtainable (for example, open self-registration).
PHP object injection in the 10Web Booster WordPress plugin (versions up to 2.33.6) allows an authenticated Contributor to inject a malicious PHP object, potentially leading to remote code execution if a suitable gadget chain is present. The vulnerability is network-exploitable, requires no user interaction, and has a CVSS score of 8.8, but exploitation depends on the availability of a POP chain within the plugin or other installed components. No public exploit code has been identified at time of analysis.
PHP object injection in the WordPress plugin SEO Plugin by Squirrly SEO (through version 14.2.5) allows an authenticated attacker with only Contributor-level access to feed crafted serialized data into PHP's unserialize(), which can escalate to remote code execution, arbitrary file operations, or SQL injection if a usable POP gadget chain is reachable in the plugin, WordPress core, or another installed plugin. The flaw scores CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), so it is a genuine high-priority issue, but the practical blast radius depends on two prerequisites: the site must permit untrusted or self-registered Contributor accounts, and a viable gadget chain must exist. No public exploit code has been identified at time of analysis and the vulnerability is not known to be actively exploited (not in CISA KEV); it is not exploitable by fully unauthenticated visitors.
Stored cross-site scripting in the Verge3D Publishing and E-Commerce WordPress plugin before 4.13.1 lets unauthenticated attackers upload a file whose contents are never validated and which the plugin then serves back with an attacker-controlled content type, so the embedded JavaScript executes in the browser of any user who opens the uploaded file's URL. Exploitation requires the target site to expose the plugin's file storage/upload feature and depends on a victim opening the attacker-supplied file link (UI:R), so it is not an automatic drive-by compromise; no public exploit code was identified at time of analysis and CISA's SSVC evaluation records exploitation as 'none'. Sites running version 4.13.1 or later are not affected, and the vendor has released a fix.
Stored cross-site scripting in the WordPress plugin All in One Files Upload (versions 2.0.3 through 2.0.16) lets unauthenticated visitors upload SVG files containing active content that executes in the site's origin when a victim opens or previews the file, potentially handing an attacker administrator-level control of the site if a privileged user is the one who opens it. Exploitation requires no authentication (CVSS vector PR:N) and no non-default configuration, since the plugin itself whitelists SVG uploads and fails to verify the authenticity of its public upload requests, but it does require victim interaction (UI:R) and is assessed as not automatable per SSVC. No public exploit code has been identified at time of analysis and CISA KEV does not list this CVE, though independent scoring disagrees with the vendor-side 8.8 rating: our assessment scores scope change with limited confidentiality and integrity impact (S:C/C:L/I:L/A:N) because the realized impact depends entirely on a privileged victim opening the stored file, which is why the urgency signals conflict.
Remote, unauthenticated requests to the WatchGuard Fireware OS authentication login interface can crash the management daemon, producing a denial of service on affected Firebox appliances. The root cause is a NULL pointer dereference (CWE-476) triggered by a specially crafted request to the login endpoint; impact is confined to availability of the management daemon, with no confidentiality or integrity loss and no code execution. Exploitation requires only network reachability to the management/authentication interface (assessed CVSS:3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), and no public exploit code or confirmed active exploitation has been identified at time of analysis (the CVE is not listed in CISA KEV). The published score of 8.7 reflects the CVSS 4.0 vector, while the independent assessment treats this as a genuine but bounded availability risk whose real-world severity hinges on how widely the login interface is exposed.
Authentication bypass in AiSOC 7.5.0 through 11.x lets unauthenticated remote attackers subscribe to realtime WebSocket/SSE channels belonging to any tenant, exposing live alerts, cases, agent events, and graph updates. The realtime edge verifies subscription tickets with a hard-coded HS256 key committed to the repository, and per the patch commit that constant was the effective key in every shipped deployment because no docker-compose or make manifest ever passed AISOC_REALTIME_JWT_SECRET to either the API or the realtime service. Version 12.0.0 removes the fallback entirely and generates a real secret, so only deployments that explicitly set the variable are unaffected; no public exploit code identified at time of analysis, and the assessed impact is confidentiality-only against a very small deployment footprint.
Stored cross-site scripting in Kiteworks Core before version 9.5.0 allows an authenticated user with only low privileges to submit content that executes arbitrary JavaScript in the browser session of any other user who later views it, potentially enabling full account takeover of higher-privileged users such as administrators. The issue scores 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N = High) because a successful attack crosses the browser privilege boundary into the victim's session, yielding high confidentiality and integrity impact while availability is unaffected. No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation is constrained by two prerequisites: the attacker must already hold a valid low-privileged account, and a second user must subsequently render the stored payload in the web UI.
Stored cross-site scripting in Kiteworks Core allows an authenticated user to store crafted content that executes arbitrary JavaScript in another user's authenticated session when that victim previews the shared content, potentially enabling session compromise or account takeover. Affected deployments are Kiteworks Core versions before 9.5.0, and exploitation requires a valid platform account plus victim interaction with the preview rendering path. No public exploit code or CISA KEV listing has been identified at time of analysis, and the independent assessment classifies this as a moderate-priority, contingent-risk finding rather than an urgent one.
The anonymous form-rendering endpoint in Kiteworks' Advanced Forms / Secure Data Forms component returns more information than a published form needs, letting anyone who knows or can guess a published form's web address retrieve the form owner's Kiteworks account profile (including personal details) plus portions of the deployment's configuration settings. No authentication or user interaction is required against a default deployment that serves published forms, and the exposed data does not include passwords, authentication tokens, or MFA secrets. Scoring is CVSS 3.1 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N), driven entirely by confidentiality loss with a scope change since an unauthenticated viewer gains data belonging to a different security authority; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Arbitrary command execution on Windows hosts is achievable through OpenClaw Windows Node versions prior to 2026.7.1, where the system.run exec-approval policy can be evaded by an authenticated connected gateway or agent holding the PR:L role. The ExecShellWrapperParser fails to split commands on pipe operators or extract command-substitution/subexpression syntax, so a denied command placed behind an allowed prefix (for example `benign | denied` or `echo $(denied)`) is never surfaced to the allow/deny ruleset and executes anyway; the failure only yields a bypass where a restrictive exec-approval policy is actually configured, and the impact is confined to Windows targets. No public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited (no CISA KEV listing); vendor-released patch 2026.7.1 is available.
Unauthenticated remote code execution affects Taskcluster deployments running versions prior to 100.3.0 that expose the GraphQL endpoint to an anonymous role. The vulnerable code path is the GraphQL `filter: JSON` argument on list/search queries (clients, roles, secrets, worker pools, denylist addresses, artifacts, hooks, namespaces), which was parsed with the `sift` library using improper input validation (CWE-20); a crafted filter payload can lead to code execution on the web-server, giving full confidentiality, integrity, and availability impact (assessed CVSS 3.1 9.8, raw vendor CVSS 4.0 8.7). Exploitation is network-reachable and needs no authentication or user interaction, but is conditional on the deployment granting an anonymous role access to GraphQL; no active exploitation (CISA KEV) or public exploit code has been identified at time of analysis, and the vendor-released patch is version 100.3.0.
Authenticated users holding the backend 'manager' role in yii2-starter-kit through 4.2.0 can upload PHP scripts through the backend file-storage upload action and then request them from the web-accessible storage directory, achieving remote code execution as the web server user. The defect is an unrestricted file upload (CWE-434) with a CVSS 4.0 base score of 8.7 (PR:L, fully consistent with the assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H): exploitation is gated on manager-level authentication, on the backend file-storage module being enabled and reachable, and on the storage directory being served without script-execution restrictions, which is the default starter-kit layout. No public exploit code identified at time of analysis, and the practical priority is tempered by the authentication prerequisite and the niche footprint of the product, though the impact is total for any live deployment that meets those preconditions.
Unbounded HTTP request-header buffering in Corvusoft restbed 5.0.0 and earlier allows remote unauthenticated attackers to exhaust server heap memory and kill the process, producing a denial of service against any network-reachable service built on the framework. The attack requires nothing more than opening TCP connections and streaming header bytes indefinitely without ever sending the terminating blank line, so the server keeps growing its header buffer until memory is exhausted; no credentials, feature flags, or user interaction are involved (CVSS:4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VA:H, assessed as CVSS:3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Impact is confined to availability - there is no data disclosure or code execution - and no public exploit code has been identified at time of analysis, though the technique is straightforward to reproduce by hand. Exposure is materially reduced where a reverse proxy or load balancer in front of restbed enforces its own header-size and header-timeout limits.
Unauthenticated HTTP requests to LightLLM through 1.2.0 can halt and wedge inference workers on any deployment started with the --enable_rl flag, because the reinforcement-learning control routes (/pause_generation, /abort_request, /flush_cache, /init_weights_update_group) are mounted on the public API with no authentication check (CWE-306). An attacker who can merely reach the API over the network can pause generation, abort in-flight requests, repeatedly flush the cache, or disturb weight-update groups, degrading or fully interrupting service availability, with no data disclosure or modification possible through these routes. Risk is bounded by the non-default RL configuration and by network exposure of the API; no public exploit identified at time of analysis.
Decryption of sensitive diagnostics bundles in AJA HELO Plus firmware before 2.1.7 allows unauthenticated remote attackers to recover highly sensitive server information from any device they can reach. The firmware embeds a static AES passphrase in obfuscated form, so an attacker who reverse engineers the publicly available firmware image once can decrypt diagnostics exports pulled from the unauthenticated diagnostics endpoint on every affected device. Exploitation requires no authentication, no user interaction, and no non-default configuration, with network reachability to the device's management/diagnostics interface as the primary limiting factor; no public exploit code has been identified at time of analysis, and a vendor fix is available in firmware 2.1.7.
Memory exhaustion in the CODESYS Gateway Client lets an attacker-controlled gateway crash the client by supplying a crafted response whose size field is trusted without an upper bound, driving uncontrolled resource allocation (CWE-770) and a total loss of availability on the affected client. The vendor scores this 8.7 (CVSS 4.0 AV:N/AC:L/AT:N/PR:N/UI:N, driven entirely by VA:H with VC:N/VI:N), and our independent assessment is consistent: remote denial of service with no confidentiality, integrity, or code-execution impact. The real limiting factor is not credentials or user interaction but endpoint control - the attacker must be able to impersonate or redirect the gateway the client connects to; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Man-in-the-middle attackers can intercept and decrypt sensitive BVMS traffic across versions 4.5 through 12.3 because the product relies on a hard-coded cryptographic key (CWE-321), allowing unauthorized access to confidential data and, per the assessed impact, tampering with protected communications. The flaw is remotely reachable and requires no credentials (PR:N) or user interaction (UI:N), and it carries a high severity rating of 8.7 with a scope change reflecting impact beyond the vulnerable component. Risk is materially gated by the high attack complexity (AC:H): the attacker must first obtain a man-in-the-middle position on the network path between BVMS components, so it is not exploitable purely remotely against an isolated, well-segmented deployment. No confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis.
MISP before 2.5.48 lets an authenticated user holding the delegation permission (perm_delegate) retarget an existing event-delegation record to any event on the instance by injecting an 'id' or 'event_id' field into the delegation submission, because the controller authorizes only the event named in the URL but persists the entire caller-supplied record. The injected row grants the attacker's organisation read access to the targeted event and, if the target organisation accepts the delegation, transfers ownership of that event and deletes the original record - a confidentiality and integrity impact rated 8.7 (CVSS:4.0) and assessed as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L. Exploitation requires two concrete preconditions: an account with perm_delegate and the non-default, instance-wide MISP.delegation setting enabled; there is no public exploit identified at time of analysis, but a vendor fix is available in 2.5.48 (commit d1f5684f9).
Memory exhaustion and parser panics in the Go implementation of Apache PLC4X (PLC4Go) allow a malicious PLC device, or an attacker able to inject or spoof frames on the industrial network path, to crash or exhaust the client application, resulting in denial of service. The flaws affect Go module github.com/apache/plc4x/plc4go from 0.11.0 up to but not including 1.0.0 and include unbounded wire-claimed array and buffer allocations, unchecked indexing of ADS and KNXnet/IP responses, zero-length framing that breaks ADS and EIP message boundaries, unlimited recursion in recursive protocol types, and 16-bit length/position arithmetic in generated serializers that wraps and can cause payloads larger than 8 KB to be mis-framed. CVSS vector indicates no authentication is required (PR:N) and no public exploit has been identified at time of analysis; exploitation is limited to environments where a PLC4Go client talks to untrusted or attacker-reachable industrial endpoints, and impact is availability only.
Denial of service in Apache PLC4X (PLC4J Java) from 0.10.0 before 1.0.0 allows a remote, unauthenticated attacker who can impersonate an OPC UA server to exhaust the client application's memory or stack during connection setup. The defects are triggered while the secure channel and session are established, before server identity is bound, so trusting a configured server does not prevent exploitation. No public exploit identified at time of analysis; vendor CVSS 4.0 score is 8.7 and the independent CVSS 3.1 assessment confirms AV:N/AC:L/PR:N/UI:N with availability-only impact (A:H).
NULL pointer dereference in Pgpool-II allows an unauthenticated remote attacker to crash the watchdog process when the high-availability clustering feature is enabled and network-reachable. This is an availability-only impact (no confidentiality or integrity loss) and is limited to HA deployments where watchdog is configured; single-node or non-HA installations are unaffected. No public exploit identified at time of analysis, and the vendor has not yet released a patch.
Stack-based buffer overflow in Pgpool-II (versions 3.5.x through 4.7.2) allows unauthenticated remote attackers to crash the connection pooler process by sending a crafted message, causing a denial of service against Pgpool-II and the PostgreSQL databases it fronts. The vendor-assigned CVSS 4.0 score of 8.7 reflects strictly availability-only impact (VC:N/VI:N/VA:H), and no public exploit code has been identified at time of analysis. Exploitation requires only network reachability to the Pgpool-II listening socket; instances on internal or firewalled networks are at reduced risk.
An out-of-bounds write (CWE-787) in Pgpool-II, the PostgreSQL connection pooler, allows an authenticated attacker who already holds valid low-privileged credentials to cause abnormal termination of the Pgpool-II process or, depending on memory layout and build hardening, to achieve arbitrary code execution. Affected branches span 3.5.x through 4.2.x as well as 4.3.0-4.3.20, 4.4.0-4.4.17, 4.5.0-4.5.12, 4.6.0-4.6.7 and 4.7.0-4.7.2; exploitation is remote (AV:N), low complexity and requires no user interaction, but the PR:L authentication prerequisite makes this a post-authentication flaw rather than an unauthenticated internet-facing one. The vendor score is 8.7 (CVSS 4.0) and the independent assessment maps it to 8.8 (CVSS 3.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); no public exploit code has been identified at time of analysis and there is no CISA KEV listing confirming active exploitation.
Malformed signaling input delivered to Pexip Infinity deployments running versions before 41.0 can abort the signaling software, denying conferencing service to users of the affected node. The issue is network-reachable and carries a CVSS 3.1 base of 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H), with the severity driven almost entirely by the high availability impact plus the scope-change component rather than by any loss of confidentiality or integrity. The CVSS vector's PR:N indicates no privilege requirement, but exploitation still carries an access precondition: the attacker must be able to reach the WebRTC/API signaling entry point and participate in a gateway call, so internet-facing nodes that permit open WebRTC/API gateway calling are directly at risk while internal-only or call-restricted deployments are substantially less exposed. There is no public exploit identified at time of analysis, and the fixed release (Pexip Infinity 41.0) is available.
OpenSave through 2.4.0 contains a path-validation bypass (CWE-73) in which a paired peer can supply save paths that fall outside the operator's configured save locations, enabling arbitrary file read and write on the target instance via the manifest request handler and sync routes. The CVSS 4.0 base score of 8.6 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H) reflects high confidentiality and integrity impact with no user interaction and low attack complexity, though the attacker must already be a paired peer of the target (authenticated, PR:L), so an unpaired remote party cannot reach the flaw. No public exploit code and no confirmed active exploitation were identified at time of analysis, but a public advisory and the affected source locations are documented, making the issue straightforward to reason about for anyone already inside a peer trust relationship.
Privilege escalation in MISP before 2.5.48 allows an authenticated user who holds the tag editor permission (perm_tag_editor) to smuggle sibling User and Organisation records into tag collection create or edit requests, which the affected controller then persists alongside the intended tag collection - letting the attacker create or modify accounts and escalate to site administrator. Exploitation requires network access to the instance and a delegated tag-editor role; no user interaction or administrative rights are needed, and the accompanying source fix (commit 96f735e7b) shipped in MISP 2.5.48. No public exploit code was identified at time of analysis, and instances that never delegate perm_tag_editor to non-administrative accounts are not exposed to an unprivileged external actor.
Authenticated administrative users of Digiwin EasyFlow .NET can exploit an arbitrary file upload vulnerability to place and execute .NET web shell backdoors, achieving remote code execution on the server. The CVSS 4.0 base score is 8.6, but the high privilege requirement (PR:H) confines risk to insider threats or cases where admin credentials are already compromised. No public exploit or confirmed active exploitation exists at time of analysis.
Code execution in BcAddonMigrator 5.2.0 and earlier allows an authenticated administrative user to run arbitrary PHP by supplying a baserCMS4-style addon package whose config.php holds attacker-controlled code. The migration routine BcAddonMigrator5Component::migrateAddonConfig calls PHP's include on the uploaded config.php, so the file's contents execute with the web server's privileges during conversion, and the same code path can read or delete arbitrary files on the host. The CVSS 4.0 base score is 8.6, but the decisive limiting factor is PR:H - the attacker must already hold administrator rights - and no public exploit code or CISA KEV entry was identified at the time of analysis.
Authenticated SQL injection in the Event Tickets WordPress plugin through version 5.29.5 allows any account holding the Contributor role to inject arbitrary SQL through plugin-supplied input, giving read access to data well beyond what the plugin itself stores (CVSS 3.1: 8.5, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L). The practical barrier is the Contributor authentication requirement, which limits mass exploitation but is trivially satisfied on sites with open registration or large numbers of low-trust contributors; the Scope:Changed rating reflects that successful injection can expose the broader WordPress database, not just plugin tables. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor has not published a fixed version in the available data, so this is a genuine mid-to-high priority issue rather than an emergency.
SQL injection in GamiPress WordPress plugin versions 8.0.2 and earlier allows unauthenticated attackers to read sensitive data from the database. Our independent assessment indicates no user interaction or authentication is required (PR:N), though the originally provided CVSS vector specifies PR:L, creating a discrepancy that should be verified with the vendor. No public exploit code has been identified at time of analysis.
Arbitrary file write during plugin installation in ZeroClaw before 0.8.5 (when built with the plugins-wasm feature) lets attackers place files outside the plugins directory by supplying a crafted manifest.toml whose wasm_path field contains '..' or absolute/root/drive-prefix components; overwriting shell startup files or similar executed content yields code execution under the victim's account. The attack is local (AV:L) and unauthenticated per the assessed vector (PR:N), but it requires user interaction (UI:P/UI:R) - the victim must be persuaded to install the attacker-supplied plugin package - and only functions when plugin signature verification is left in its default Disabled mode, making the path check the sole gate. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has released a fix in v0.8.5.
SQL injection in the WordPress plugin Media Library Assistant (version 3.41 and earlier) allows an authenticated Contributor-level account to inject arbitrary SQL into the plugin's media/attachment query handling, reading database content such as user password hashes, private or draft posts, and stored configuration secrets. The issue is remotely exploitable with low complexity and no user interaction, and the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L) yields a base score of 8.5 (High), reflecting confidentiality-only impact plus a scope change that lets the injection reach tables outside the plugin itself. There is no public exploit identified at time of analysis and no CISA KEV entry, so the practical barrier to abuse is obtaining a Contributor account - realistic on sites with open registration, multi-author blogs, or guest-post/membership setups, but not on locked-down single-admin installs.
Authenticated SQL injection in the Easy Pricing Tables WordPress plugin affects versions up to and including 4.1.2, allowing any account holding at least the Contributor role to inject arbitrary SQL into the site's database and read sensitive data such as user credential hashes, password reset tokens, and stored configuration. Exploitation requires a valid logged-in account with Contributor privileges, needs no user interaction, and is network-reachable; no public exploit code has been identified at time of analysis, and the issue is not reported as actively exploited. Realistic exposure is concentrated on multi-author sites, membership or community sites with open registration granting Contributor, or any site where an attacker can obtain low-privilege credentials, while single-admin sites with registration disabled are at substantially lower risk.
Improper validation of a client-supplied SID over a local IPC named pipe in the Cato Networks SDP Client for Windows (versions before 6.12.6) lets a local, low-privileged user coerce the client's SYSTEM-level service into deleting arbitrary files with SYSTEM privileges, resulting in high integrity and availability impact on the affected endpoint. Exploitation is purely local - it requires an authenticated local user (PR:L per the CVSS vectors) with the ability to reach the client's local IPC named pipe, no user interaction, and the affected client installed and running on the target Windows host; there is no remote or network-facing attack path. This is confirmed neither as actively exploited (no CISA KEV listing) nor as having public exploit code: no public exploit identified at time of analysis, and the bounded local scope makes it a genuine but non-emergency privilege-escalation and file-tampering primitive rather than a remotely exploitable critical issue.
Improper verification of the source of ADS discovery responses in Apache PLC4X (CWE-940) allows an attacker on the adjacent network to redirect subsequent connections to an arbitrary host by spoofing a UDP discovery response, potentially exposing ADS route credentials. Affected versions are PLC4Go 0.11.0-<1.0.0, PLC4J ADS/Modbus 0.10.0-<1.0.0, and PLC4J EtherNet/IP 0.11.0-<1.0.0. Exploitation requires the consuming application to invoke the opt-in discovery API and act on discovered items; no public exploit identified at time of analysis. Upgrade to 1.0.0 to fix.
Command injection in the Ziroom ZHOME A0101 smart-home gateway running firmware 1.0.1.0 allows a remote, high-privilege authenticated attacker to execute arbitrary operating-system commands on the device by supplying shell metacharacters in the 'url' argument of the /api/ZRnetwork/ping diagnostic endpoint. Publicly available exploit code exists - the reporting researcher published a proof-of-concept write-up on GitHub - and the vendor was contacted early about the disclosure but never responded, so no vendor-released patch is available and no CISA KEV entry or EPSS score was provided in the source data. The published CVSS 4.0 score of 8.5 is driven upward by subsequent-system (SC:H/SI:H/SA:H) metrics that our independent assessment considers inflated for a single embedded gateway; the practical risk is bounded by the PR:H administrative authentication prerequisite in the vector and by the fact that consumer smart-home management interfaces such as this are normally reachable only from the LAN.
Denial of service in the npm package @angular/router when Server-Side Rendering (SSR) is enabled on Node.js allows an unauthenticated remote attacker to crash the SSR worker by exhausting the V8 old-space heap. Numeric matrix-parameter or outlet names (e.g. /a;990;2522) are stored as array-indexed properties on plain parameter objects, causing V8 to allocate dense HOLEY_ELEMENTS backing stores sized to the largest index, producing roughly 350x memory amplification (~20-25 KB of heap per 11-byte path segment) and a fatal 'JavaScript heap out of memory' error. Exploitation requires the app to run Angular SSR on Node.js, to parse user-controlled URLs directly through @angular/router, and an edge/reverse proxy that forwards semicolons and deep paths; roughly 12-22 concurrent 8 KB-path requests or 50-100 concurrent 1-2 KB-path requests are enough to kill a 256-512 MiB worker. Client-side Angular SPAs without SSR are not affected, and no public exploit code has been identified at time of analysis; the only impact is availability (no confidentiality or integrity impact).
Cross-tenant data disclosure in Soft Machine workspaces running version 0.2.247 and prior lets any peer Fly Machine on the same private 6PN mesh read arbitrary files under a workspace's /workspace root and pull entire project trees as tar archives through the unauthenticated /file/<path> and /archive/<dir> endpoints exposed on 0.0.0.0:8080. Exploitation is bounded by network topology rather than open to the internet: an authenticated tenant that controls another sm-ws-* machine in the same Fly app/org can reach peer workspaces (discoverable via the unauthenticated _instances.internal TXT record) with no further authentication, credentials, origin check, or user interaction, while single-tenant or network-isolated deployments are unreachable by outside parties. At time of analysis no public exploit code has been identified and no vendor patch is available, but the missing trust boundary between workspace owner and co-tenants makes this a genuine confidentiality risk anywhere multiple tenants share a Fly org.
Stored cross-site scripting in MISP's event graph preview lets an authenticated user who can create or modify an event graph entry persist a malicious preview_img value that executes in the browser of a second user who opens the graph and triggers the preview popover. The stored value is concatenated directly into an img src attribute in app/webroot/js/event-graph.js, so a crafted string can break out of the attribute context and inject arbitrary JavaScript in the MISP origin, enabling session/cookie theft or actions performed as the victim; exploitation is bounded by the required prior authentication (PR:L) and mandatory victim interaction, and no public exploit code or confirmed active exploitation was identified at time of analysis. Only MISP instances running versions prior to fix commit 92c7ccc43, which landed after v2.5.48, are affected, making internet-exposed multi-user deployments the realistic risk surface.
Cross-tenant record tampering in MISP (Malware Information Sharing Platform) versions before 2.5.48 lets any authenticated user holding the basic write role (perm_add) overwrite attribute values, re-parent objects into their own events, or soft-delete rows owned by other organizations and events they have no read access to. The root cause is that the CakePHP ORM's set() gives precedence to an attacker-supplied nested key matching the model alias, so MISP's sanitization (primary-key stripping, event_id/object_id pinning) is applied to the outer flat record while the ORM actually persists the inner attacker-controlled one; the independent assessment confirms this is a fully remote, low-complexity exploit (PR:L, no UI) with integrity-only impact that extends across tenants (SI:H), and no public exploit code or in-the-wild activity has been identified at time of analysis. A vendor fix is available via upstream commit 9485ae40d, with the affected range ending at MISP 2.5.48.