Unauthenticated blind SQL injection in the JNews - Pay Writer WordPress plugin (versions through 12.0.1) allows remote attackers to extract sensitive data from the site's database by inferring information through boolean or time-based queries. The critical severity (CVSS 9.3) stems from network reachability, low complexity, and high confidentiality impact, but exploitation requires that this specific companion plugin be installed and active-the base JNews theme alone is insufficient. No public exploit code or active exploitation has been identified at time of analysis.
Blind SQL injection in the VibeThemes WPLMS WordPress learning-management plugin affects every release prior to 1.9.9.8.2, letting an attacker who can reach the vulnerable endpoint infer and extract database contents - including WordPress user records and other sensitive tables - through a network-reachable, low-complexity attack (CWE-89, reported CVSS base 9.3). Exploitation status: no public exploit identified at time of analysis, and no CISA KEV listing. Sources disagree on prerequisites - the reported vector carries PR:N/S:C/C:H/I:N/A:L (unauthenticated, changed scope) while our independent assessment scores CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (low-privilege authenticated, unchanged scope), so the minimum privilege level required should be verified against the Patchstack advisory before treating the issue as anonymously exploitable.
Authentication bypass in the FalkorDB Bolt endpoint (src/bolt/bolt_api.c) affects all releases before 4.20.0 and lets a remote, unauthenticated attacker run graph queries without credentials, scored 9.2 Critical under the vendor's CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H) and assessed as high-impact under an independent CVSS 3.1 vector of AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Exploitation is gated by two concrete preconditions: the operator must have explicitly enabled the Bolt listener by setting BOLT_PORT (disabled by default, so stock deployments are not exposed), and the flaw only fires when the backing Redis answers an empty AUTH probe with an error other than WRONGPASS - specifically LOADING during dataset load, MASTERDOWN during replication failover, or OOM under memory pressure; in steady state with a password configured, the probe returns WRONGPASS and authentication is enforced normally. No public exploit code has been identified and the issue is not in CISA KEV, so the realistic risk sits with intentionally exposed Bolt endpoints that can be driven into those transient Redis states.
Account takeover in Pingvin Share X 0.19.0 through 1.21.x allows remote attackers to seize arbitrary accounts - including administrator accounts - by registering a victim's email address on an enabled OAuth/OIDC provider that does not enforce email verification, then signing in through the OAuth flow, which auto-links to the victim's existing account without any email_verified check and bypasses TOTP. Successful exploitation yields full read/write access to the victim's files and settings as well as any administrative privileges the victim holds. The attack is unauthenticated (CVSS:3.1 PR:N/UI:N) but is not universally exploitable: it requires that the instance has an OAuth/OIDC provider routed through GenericOidcProvider, that automatic OAuth email linking is active, and that the attacker knows the victim's email address and can register it unverified on that provider - the AC:H/AT:P conditions reflected in both the assessed CVSS:3.1 vector (8.1) and the vendor's CVSS:4.0 score of 9.2. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis; vendor-released fix is available in 1.22.0.
Server-side template injection in Wizarr before 2026.9.1 allows an authenticated user with privileges to create or edit wizard steps - or an administrator who imports an attacker-supplied wizard bundle - to execute arbitrary Python in the context of the application process. Because the stored step Markdown is compiled by the application's non-sandboxed Jinja2 environment with application globals exposed, successful exploitation can run operating-system commands as the application user, disclose the Flask SECRET_KEY, reach connected media-server service credentials and the database, and inject stored cross-site scripting into pages rendered at GET /wizard/{server}/{idx}. The issue is rated 9.1 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) and is fixed in 2026.9.1; no public exploit code was identified at the time of analysis, and the PR:H prerequisite narrows the realistic attacker population to trusted-but-malicious insiders or admins socially engineered into importing a hostile bundle.
Token validation bypass in Apache CXF's STSTokenValidator and Security Token Service (STS) allows unauthenticated remote attackers to impersonate another user by presenting a forged UsernameToken or self-signed SAML Assertion whose 32-bit Java hash collides with an entry already held in the validated-token cache. Because a cache hit is treated as proof of prior validation, the forged token is accepted without password validation, signature trust verification, or any call to the STS, and can subsequently be exchanged through STS validation or renewal for STS-signed tokens issued for the victim identity. Exploitation is constrained in practice: the target deployment must use STSTokenValidator or STS token validation/renewal with the validated-token cache enabled, and a legitimately validated token for the identity being impersonated must already be present in that cache; no public exploit code has been identified at time of analysis, KEV status is negative, and EPSS is low (~0.17%, 6th percentile), yet the headline CVSS of 9.1 reflects high confidentiality and integrity impact if the preconditions are met. Vendor patches are available in 4.2.4, 4.1.9, and 3.6.13.
Session-substitution in Privasys RA-TLS Clients (the Rust ratls_client crate and the Go ratls package, challenge-mode verifiers) prior to 0.5.0 lets an attacker who already possesses an enclave TLS private key relay a genuine attestation quote onto a different, attacker-terminated TLS connection, so the client accepts that connection as coming from the attested enclave. The flaw is an origin/session-binding gap: the quote's ReportData was checked against the certificate public key and the client nonce but never against the live TLS session, allowing a captured quote to be replayed onto an unrelated handshake and granting full session confidentiality and integrity loss (CVSS 4.0 9.1 Critical, VC:H/VI:H, AV:N with PR:N - unauthenticated from the verifier's perspective). Exploitation is gated by the attacker's pre-existing enclave private key and by the deployment running challenge mode on a build that exposes the RA-TLS channel binder; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the vendor-released patch is version 0.5.0.
Quote relay in the TDX/GPU RA-TLS certificate issuer of Privasys Enclave OS Virtual lets a relying party accept an attacker-terminated TLS connection as a genuine attested enclave, defeating the confidentiality guarantee of the confidential VM. All TDX and GPU-enabled builds prior to tdx-v0.2.43 and tdx-gpu-v0.6.27 are affected; exploitation is remote and unauthenticated per the CVSS vector (AV:N/PR:N) but is gated by a demanding precondition - the attacker must already hold a valid enclave TLS private key and be positioned to terminate or relay the victim's TLS session (AC:H, AT:P), which is why real-world exploitability is materially lower than the 9.1 base score suggests. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; vendor-released fixes exist in tdx-v0.2.43 and tdx-gpu-v0.6.27.
Attestation bypass in the Privasys rustls fork (versions prior to privasys-v0.8.1) lets an attacker who already holds a genuine enclave's TLS private key relay that enclave's RA-TLS quote onto a separate, attacker-terminated TLS 1.3 connection, causing the relying party to treat the attacker's connection as the attested enclave. Because the channel just needs to be mounted over the network with no privileges and no user interaction, the published CVSS 4.0 base score is 9.1 (Critical), though the same vector records AC:H and AT:P - reflecting that the attacker must first obtain the enclave private key and then successfully replay a valid quote, which materially constrains real-world exploitation. The flaw is fixed in privasys-v0.8.1 via a 32-byte channel binder derived from the TLS 1.3 handshake key schedule; no public exploit code was identified at time of analysis and the issue is not listed as actively exploited.
RA-TLS session binding bypass in Privasys Go before privasys-v0.5.1-go1.26.5 allows remote attackers who already possess a valid enclave TLS private key to relay a genuine attestation quote onto a different TLS connection, causing a relying party to accept an attacker-terminated handshake as an attested enclave connection. The flaw stems from challenge-mode RA-TLS certificates binding quote ReportData to the certificate public key and client nonce but not to the active TLS session (CWE-346). No public exploit code has been identified, and exploitation requires both a stolen enclave TLS private key and a verifier that does not independently bind attestation to the session channel; the vendor has released a fix in privasys-v0.5.1-go1.26.5.
Attestation bypass in PrivaSys Enclave OS Mini before wasm-v0.40.0 allows an attacker who already possesses a valid enclave RA-TLS private key to relay a genuine SGX/TDX attestation quote onto a TLS connection the attacker terminates, so a relying party accepts an attacker-controlled channel as the attested enclave. The root cause is a missing TLS-session channel binding (CWE-346): in challenge-response mode the quote's ReportData folded only the certificate public-key hash and the client nonce, so nothing in the quote committed to the specific handshake, making a relayed quote valid on any connection. CVSS 4.0 rates this 9.1 (network reachable, unauthenticated per PR:N, no user interaction, high confidentiality and integrity impact), but the independent assessment (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) and the AT:P metric correctly temper it: exploitation presupposes a prior enclave key compromise and a challenge-mode deployment, and no public exploit has been identified at time of analysis.
Man-in-the-middle attackers can impersonate any TLS server contacted by Apache CXF's optional Netty-based HTTP client transport, because cxf-rt-transports-http-netty-client validates the server certificate chain against the configured trust store but never checks that the certificate's hostname matches the host actually being called - a gap present over both HTTP/1.1 and HTTP/2 and present even with disableCNCheck left at its secure default of false. Applications running Apache CXF before 3.6.13, 4.1.9 or 4.2.4 that use this transport for outbound TLS calls are affected; an unauthenticated attacker who already holds a traffic-interception position and any certificate issued by a CA in the client's trust store (for example, a free publicly issued certificate for an attacker-controlled domain) can read or modify exchanged messages and credentials. No public exploit identified at time of analysis, and exploitation is gated by the requirement for an on-path MITM position plus a trusted-chain certificate, which is reflected in our assessed vector returning High attack complexity rather than the published AC:L; EPSS is correspondingly low at 0.11% (1st percentile), so this is a serious TLS trust failure rather than an immediate mass-exploitation priority. Vendor fixes are available in 3.6.13, 4.1.9 and 4.2.4.
Unauthenticated access to the STTP-based data publisher in Grid Protection Alliance openPDC, the openPDC Docker image, and openHistorian default configurations allows remote attackers to connect to the interface and exchange data without credentials, resulting in a confidentiality exposure scored CVSS 5.3 (C:L, I:N, A:N). Exploitation requires the STTP listener to be network-reachable and authentication/TLS to remain disabled, and impact is limited to data access/exchange with no stated ability to alter measurements or disrupt availability. No public exploit identified at time of analysis, and the expected OT network segmentation around these systems is a key mitigating factor.
Stored cross-site scripting in Progress Telerik Report Server versions prior to 12.2.26.1007 allows an authenticated report author to execute arbitrary script in another user's session by embedding javascript: or vbscript: URLs in report navigation actions or HTML text-box links. When a higher-privilege user, such as an administrator, views the malicious report and triggers the embedded navigation, the script runs in the web report viewer's origin, enabling privilege escalation in multi-user deployments. The vulnerability has a CVSS score of 8.9, requires authentication and user interaction, and no public exploit has been identified at time of analysis.
Factory default administrator credentials on Red Lion Controls 700 Series devices remain active and cannot be removed by configuring additional administrator accounts, so an attacker who can reach the device's management interface can log in with administrative privileges on a device that operators believe is fully hardened. The independent assessment rates this as a high-impact, effectively unauthenticated network-reachable issue (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N), acknowledging that the supplied CVSS 4.0 vector marks PR:H while the defining feature - publicly known default credentials - means no legitimate account or privilege is required in practice. The practical limiting factor is reachability: ICS/OT networks are often segmented, so real-world exposure depends on whether the management interface is accessible from an attacker-controlled segment; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and no vendor fix version is disclosed in the available data.
Path traversal in Apache Camel Karavan 3.18.0 through 4.22.0 allows an authenticated user of any role to write arbitrary files outside the project directory by supplying a project file name containing '../' sequences, leading to overwrite of application configuration or classpath files and potential remote code execution in the Karavan container. The flaw is present in default behavior and requires only a valid account (CVSS 8.8, PR:L). No public exploit code or active exploitation has been identified at time of analysis, but the high impact and low privilege requirement make this a genuine high-priority issue.
Heap-based out-of-bounds write in FalkorDB's Bolt/WebSocket handling (all versions before 4.20.0) allows a remote unauthenticated attacker to crash the server and potentially corrupt heap memory by sending a WebSocket frame with a 64-bit extended payload length to the Bolt port. The flaw spans ws_read_frame in src/bolt/ws.c and buffer_apply_mask in src/bolt/buffer.c, where the only length check is an ASSERT() that is compiled out of release builds, so the masked XOR operation runs past the end of the receive buffer. Impact is limited to deployments that explicitly enable the Bolt endpoint via BOLT_PORT, which is disabled by default; no public exploit code has been identified at time of analysis.
Heap memory disclosure and denial of service in FalkorDB before 4.18.4 stem from an out-of-bounds read in the RDB deserialization routine BufferSerializerIOv2_ReadBuffer, which trusts a sub-buffer length field taken from the incoming stream and validates it only with an ASSERT() that is compiled out of release builds. Unauthenticated remote attackers who can drive a Redis replication exchange - for example by acting as a replication master against a network-reachable instance with no requirepass/ACL configured - can supply a crafted RDB stream to read past the end of a heap allocation, crashing the server or leaking heap memory (CVSS 8.8, high confidentiality and availability impact). No public exploit code has been identified at time of analysis, and the vendor has released a fix in FalkorDB 4.18.4, so residual risk is concentrated on unauthenticated, network-exposed deployments that have not yet upgraded.
Any authenticated user of Apache Camel Karavan 4.0.0 up to (but not including) 4.22.1 - regardless of role - can push arbitrary Kubernetes resources into the cluster through the deployment workflow. When a deployment is started, Karavan unmarshals the project's kubernetes.yaml and applies every resource it contains without restricting resource kinds, rejecting security-sensitive pod options (hostNetwork, hostPID, hostIPC, hostPath volumes, host ports, privileged containers, privilege escalation, added capabilities), or pinning a target namespace. The vendor score is 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), while the independent assessment scores it scope-changed (S:C) because successful exploitation escapes the Karavan namespace boundary; the practical blast radius is capped by the RBAC permissions granted to Karavan's Kubernetes service account. There is no CISA KEV listing and no public exploit code identified at time of analysis, and the issue is fixed in 4.22.1.
Ordinary authenticated users of clustered Nginx UI deployments can read the cluster node token from the JSON responses of /api/nodes and /api/nodes/:id and replay it in the X-Node-Secret header to be authenticated as a trusted peer node, crossing the node-to-node authentication boundary. Because the leaked secret is accepted by AuthRequired and mapped to the synthetic initUser principal, the attacker can reach sensitive management operations on any network-reachable cluster member, including configuration synchronization and service restarts. Affected versions are 2.0.0 through 2.4.x; the issue is fixed in Nginx UI 2.5.0. No public exploit code or confirmed active exploitation was identified at time of analysis, although the upstream fix commit is publicly visible.
Privilege escalation, filesystem access, and remote code execution in Dell Secure Connect Gateway (SCG) Policy Manager allow a low-privileged, authenticated remote attacker to move from limited access to full control of the affected host. Exploitation requires an existing low-privileged foothold on a network-reachable Policy Manager instance running a version prior to the fixed release; no victim interaction is needed and attack complexity is low (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8). There is no public exploit identified at time of analysis and the issue is not in CISA KEV; EPSS is 0.33% (24th percentile), so signals are mostly consistent and indicate a serious but not emergency-grade issue, with realistic risk concentrated where Policy Manager is exposed to untrusted networks or low-privilege credentials are easy to obtain.
Credential exposure in Nginx UI 2.0.0 through 2.4.x allows anyone who recovers the Node.Secret master credential to bypass password, JWT, session, and second-factor checks and obtain persistent administrative API access to configuration and secret material. Versions in that range accept the Node.Secret through the node_secret query parameter on HTTP and WebSocket authentication paths instead of requiring the X-Node-Secret header, so the credential can leak into access logs, reverse-proxy logs, browser history, Referer headers, configuration URLs, and deployment environment data. Exploitation is conditional rather than trivial: node/cluster authentication must actually be in use, the secret must have been transmitted as a query parameter in practice, and the attacker must have read access to one of those sinks; no public exploit code has been identified at time of analysis, and the vendor rates this 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) while our independent assessment scores it AV:N/AC:H/PR:N/UI:N with the same High confidentiality, integrity, and availability impact.
Missing second-factor step-up enforcement in the Nginx UI cluster API (versions 2.0.0 through 2.4.x) allows anyone holding a valid session token to perform node CRUD operations, read or replace stored node credentials, change namespaces, and trigger cluster-wide Nginx reload or restart actions without re-verifying a one-time password. The api/cluster router is protected by AuthRequired but omits RequireSecureSession, so a stolen or persisted JWT belonging to an OTP-enabled user is sufficient; the flaw is an incomplete fix for CVE-2026-84315 and was corrected in version 2.5.0. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and exposure is limited to clustered/multi-node deployments reachable on the network, so this is a high-priority issue for that specific population rather than a mass-internet emergency.
Memory corruption in the Zephyr RTOS LE Audio Broadcast Sink (subsys/bluetooth/audio/bap_broadcast_sink.c) lets an attacker within Bluetooth radio range write attacker-chosen bytes into static .bss state by broadcasting a crafted Basic Audio Announcement (BASE) with more subgroups or a larger metadata LTV than the sink's fixed arrays can hold. No pairing, bonding, GATT connection, or user interaction is required (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 8.8); the target must be a build with CONFIG_BT_BAP_BROADCAST_SINK enabled and must be periodic-advertising-synced to the attacker's source, or to an advertiser whose address and SID the attacker impersonates (periodic advertising data is unauthenticated). Impact includes corruption of adjacent Bluetooth-audio state with potential remote code execution in the Bluetooth RX thread, plus out-of-bounds disclosure via the BAS receive-state notification; no public exploit code or confirmed active exploitation was identified at time of analysis. The issue is a genuine high-priority flaw rather than a CVSS-inflated paper risk, and an upstream fix is available.
WordPress sites running the BuddhaThemes ColorFolio theme (directory slug 'colorit') through version 1.3 expose an authenticated PHP object injection path, because the theme deserializes untrusted input without validating it (CWE-502), letting an attacker with a low-privilege account on the site supply crafted serialized data. CVSS 3.1 rates it 8.8 (High) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, meaning the flaw is network-reachable, low-complexity, and needs no victim interaction, but full confidentiality, integrity, and availability impact is gated on the presence of a usable PHP object-injection (POP) gadget chain in the theme, WordPress core, or another installed plugin - without one the realized impact is substantially reduced. No public exploit code and no confirmed in-the-wild exploitation were identified from the available sources at time of analysis; exploitation also requires that the specific vulnerable ColorFolio version be installed and active.
PHP object injection in the BuddhaThemes Neo | Barber Shop WordPress theme (slug neocut), affecting all versions through 3.5, lets an authenticated attacker with a low-privileged account (subscriber or contributor level) deliver a crafted serialized PHP object to the theme's unsafe deserialization routine, potentially reaching high confidentiality, integrity and availability impact if a usable POP gadget chain exists. The issue carries CVSS 8.8 via vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, and no public exploit code has been identified at time of analysis (no CISA KEV listing). Because the required authentication level, the niche deployment of this specific theme, and the dependence on gadget-chain availability all limit practical exploitation, this is a genuine high-priority issue but short of critical-emergency status.
Cross-site request forgery in Nginx UI versions 2.0.0 through 2.4.x lets a remote attacker drive a logged-in administrator's browser into performing authenticated, state-changing management operations - including rewriting Nginx configuration through POST /api/configs, triggering config reloads, and invoking other admin endpoints - because the AuthRequired middleware accepts the browser-managed JWT cookie as a valid API credential while management routes generally enforce neither a CSRF token nor Origin/Referer validation. Exploitation requires the victim to be a currently logged-in administrator who is induced to visit an attacker-controlled page (UI:R); per the CVSS vector the attacker needs no credentials of their own (PR:N), but a targeted account protected by OTP/Passkey step-up, or an endpoint requiring secure-session proof, is not exploitable. The attacker cannot read cross-origin responses, so impact is blind configuration tampering and service disruption rather than data exfiltration; the issue is fixed in 2.5.0, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Authorization bypass in Dell Secure Connect Gateway (SCG) Policy Manager lets an authenticated, low-privileged user tamper with a user-controlled key to reach resources and actions reserved for higher-privileged accounts, resulting in elevation of privileges with high impact to confidentiality, integrity, and availability. Only SCG Policy Manager builds below the vendor-fixed release are affected; exploitation requires an existing valid low-privileged account plus network reachability to the product interface, so fully unauthenticated outsiders cannot trigger it. Risk is real but not emergency-grade: EPSS is low at 0.18 percent (7th percentile), CISA SSVC rates exploitation as none and automatable as no, and no public exploit has been identified at time of analysis. Vendor-released patches are available through Dell advisory DSA-2026-385.
Improper X.509 certificate validation in Dell Secure Connect Gateway (SCG) Policy Manager lets an unauthenticated attacker who has already attained a man-in-the-middle position on the network path to the appliance substitute a forged or untrusted certificate and hijack the affected TLS session, with the potential to disrupt service, expose data, and execute code in the context of the connection. Exploitation is not opportunistic: per the independent assessment the vector is AV:N/AC:H/PR:N/UI:R, so an attacker must both intercept the network path and induce a victim or client to initiate or complete the affected TLS handshake, which meaningfully limits exposure where the Policy Manager sits on a trusted management segment. Risk is currently low-to-moderate in practice - EPSS is 0.18% (7th percentile), no public exploit code has been identified at time of analysis, and CISA SSVC records Exploitation: none - although the vendor CVSS of 8.8 (High) reflects total confidentiality, integrity, and availability impact if the MITM precondition is met.
Privilege escalation in Dell Secure Connect Gateway (SCG) Policy Manager allows an authenticated, network-reachable low-privileged user to bypass authorization by manipulating a user-controlled key (object/resource identifier) that the application trusts, escalating to a higher-privileged role with high impact to confidentiality, integrity, and availability (CVSS 3.1 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Only installations running versions below the patched build are affected; the vulnerability is not remotely exploitable without credentials, requires no victim interaction, and per available intelligence there is no public exploit code and no confirmed active exploitation (CISA KEV not listed, SSVC exploitation: none, EPSS 0.18% / 6th percentile). The independence assessment rates this a credible but not emergency-level priority: the attacker must first hold valid low-privilege credentials, but once inside can turn a benign identifier into an elevation-of-privilege primitive.
Elevation of privilege in Dell Secure Connect Gateway (SCG) Policy Manager lets an attacker who already holds a valid low-privileged account and network reachability to the appliance invoke privileged functionality that lacks a proper authorization check, producing high confidentiality, integrity, and availability impact (CVSS 8.8, AV:N/AC:L/PR:L/UI:N). Exploitation is not remote-unauthenticated - a pre-existing low-privileged credential is a hard prerequisite. No public exploit code or confirmed active exploitation has been identified at time of analysis; EPSS is 0.16% (5th percentile), CISA SSVC rates exploitation as none and automatable as no, and a vendor patch is available.
Physical access to a Red Lion 700 Series managed switch (HMS Networks / Red Lion Controls) lets an attacker boot the device from factory settings without authentication, log in with the default administrative credentials, and then save configuration changes so they survive the next normal reboot. The result is a persistent administrative compromise of the switch: confidentiality impact is limited, but integrity impact is high because routing, VLAN, and access-control configurations can be altered at will. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, and the practical risk is strongly constrained because the attack requires hands-on access to the hardware (CVSS AV:P) and the default credentials must still be valid on first factory boot.
Unauthenticated visitors can execute shortcodes registered on a WordPress site running Kirki before 6.3.2 by submitting a comment, and can read private custom fields of the page being viewed, because the plugin renders shortcodes held in comment text and displays comments regardless of their moderation status. The vulnerability carries a CVSS 3.1 base score of 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N), with the high attack complexity reflecting that real-world impact depends on which shortcodes a site has registered and whether comments are enabled; publicly available exploit code exists, though there is no CISA KEV listing confirming active exploitation at time of analysis. A vendor patch is available in Kirki 6.3.2.
Remote code execution in ILIAS LMS versions before 9.24, 10.12, and 11.5 lets an authenticated author who holds question-pool (QTI) import rights upload a crafted question-import archive that writes a .htaccess file plus a PHP payload into the web-served image directory, resulting in code execution as the web server user. The defect is an unrestricted file upload (CWE-434) in the QTI image-handling security class ilQtiMatImageSecurity, reached through the standard question import path with no non-default configuration required. Exploitation requires a legitimate, permissioned authoring account rather than anonymous access, no public exploit code has been identified at time of analysis, and vendor-released fixes are available in 9.24, 10.12, and 11.5; instances that limit QTI import rights to vetted staff face materially lower realistic risk.
Sandbox escape and kernel-level out-of-bounds write in the Zephyr RTOS userspace subsystem: an unprivileged user-mode thread that holds an assigned resource pool can pass a size near SIZE_MAX to the k_object_alloc_size() syscall (or the thread-stack branch via k_thread_stack_alloc()), causing an unsigned integer wrap-around in dynamic_object_create() so that a few-byte heap chunk is allocated while the object descriptor is registered under the caller's requested type. The subsequent init syscall (for example k_mutex_init(), k_sem_init(), or k_thread_create()) then writes a full kernel object over the truncated allocation, giving a supervisor-mode heap overflow of attacker-influenced size and content that corrupts sys_heap chunk metadata and adjacent kernel objects, and - when CONFIG_GEN_PRIV_STACKS is set - plants an attacker-influenced wild pointer as a user thread's privileged stack base. This is a local, high-priority privilege-escalation issue (CVSS 8.8, AV:L/PR:L/S:C) rather than a remotely reachable one: exploitation requires code execution as an unprivileged thread inside the CONFIG_USERSPACE sandbox on a build that also enables CONFIG_DYNAMIC_OBJECTS (or CONFIG_DYNAMIC_THREAD under userspace) and that assigns a resource pool to the calling thread; no public exploit code was identified at time of analysis and the flaw is not in CISA KEV. The vendor has published a fix that rejects both overflowing computations and frees the partially built descriptor.
Command injection in the Argo CD repo-server allows anyone holding repository create/update privileges to execute arbitrary shell commands on the repo-server by configuring an SSH Git repository with a proxy URL whose hostname contains shell metacharacters. The flaw affects all Argo CD releases from v2.11.0 onward (v2.10.20 and earlier are not vulnerable) and carries a CVSS v3.1 score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); exploitation requires delegated repository or repository-credential-template write access (PR:L), not anonymous access, and no user interaction is needed once the malicious proxy is stored. No public exploit code and no confirmed active exploitation were identified at time of analysis, and vendor patches are available in v3.3.15, v3.4.10, v3.5.4, and v3.6.0-rc2.
PHP Object Injection in the Quiz And Survey Master plugin for WordPress (versions up to 11.2.7) allows an authenticated attacker with low privileges to execute arbitrary code or manipulate files via crafted serialized input. The vulnerability is network-reachable with low complexity and no user interaction, and can lead to full site compromise if a suitable gadget chain is present. No public exploit code has been identified at the time of analysis.
Attackers can forge state-changing requests in the Featured Image from URL WordPress plugin through 6.0.7, allowing them to cause an authenticated administrator to perform unintended actions, but only if the administrator interacts with attacker-controlled content (UI:R). The input CVSS of 8.8 overstates impact; independent assessment rates confidentiality and integrity as Low and availability as None. No public exploit code identified at time of analysis; consult the Patchstack advisory for remediation.
Unbounded memory allocation in Xerial snappy-java before 1.1.10.9 lets unauthenticated remote attackers exhaust the JVM heap by declaring an oversized uncompressed length in a compressed stream header, triggering OutOfMemoryError and denial of service. Any application that passes externally supplied bytes to Snappy.uncompress, Snappy.uncompressString, SnappyInputStream or SnappyFramedInputStream - for example Kafka, Hadoop/Spark or other services using snappy-java transitively - is in scope, and a handful of crafted bytes can force allocations of up to 2 GB before decompression validates the data. Impact is limited to availability (CVSS:4.0 base 8.7; assessed CVSS:3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with no data disclosure or modification, and no public exploit was identified at time of analysis; the practical constraint is reachability, since applications that only decompress trusted internal data are not meaningfully exposed.
SmarterMail before build 9777 fails to revalidate the role claim embedded in JWT access and refresh tokens when a token is redeemed at POST /api/v1/auth/refresh-token, so an authenticated attacker (PR:L) who holds a refresh token issued before an administrator demotion can replay it to mint a new access token that still carries the higher-privilege role, such as DomainAdmin or SysAdmin. The exposure is bounded by the token's natural expiry and only matters in environments where privileged accounts are actually demoted or revoked, since the attacker must either be the demoted user or have captured their pre-demotion token. No public exploit code has been identified at time of analysis, there is no KEV listing, and the independent assessment rates this a credible mid-to-high priority issue rather than an emergency.
Server-side request forgery in Dell Secure Connect Gateway (SCG) Policy Manager allows a remote attacker who already holds high-privilege (administrative) credentials to coerce the appliance into issuing requests to attacker-chosen destinations, causing information disclosure, unauthorized access, and bypass of protection mechanisms (CWE-918; CVE-2026-78024). The scope-change metric (S:C) indicates forged requests can affect systems beyond the vulnerable component, and the assessed vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N confirms the exploitation prerequisite is authenticated administrator access - this is the primary limiting factor and means unauthenticated or low-privileged remote users cannot trigger it. At time of analysis there is no public exploit identified and no confirmed active exploitation (CISA KEV: no; SSVC exploitation: none), EPSS is only 0.20% (9th percentile), and a vendor patch is available, so this ranks as a moderate, non-urgent priority despite its 8.7 'High' base score.
Remote code execution in SmarterMail builds before 9777 allows an attacker who already holds a SysAdmin-scoped access token to escape the Volume Mount script-directory containment and execute code as the SmarterMail service account with SYSTEM-level privileges. The chain abuses administrative endpoints - domain-put to provision a mail domain with an arbitrary FileStore root inside the trusted Scripts directory, AddOrUpdateMount to disclose the Scripts path, and global-mail to clear the upload extension blacklist - then uploads a malicious script through the ordinary mail file-storage upload API so that saving a CommandMount triggers RunScript before validation, yielding a reverse shell. Exploitation is post-authentication and access-gated by the required high-privilege token, no public exploit has been identified at time of analysis, and the vendor has released a fix in build 9777 (Oct 8, 2026).
An out-of-bounds stack write in the MariaDB CONNECT storage engine's DOS table type lets an authenticated user crash the server and potentially achieve code execution by supplying a crafted column definition and value. The flaw is an incorrect boundary check in the CONNECT value conversion routine that permits a one-byte null write past a stack buffer at an attacker-controlled offset (CWE-787), and it affects MariaDB from 10.6.1 up to the fixed releases 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3 and 13.0.2. Exploitation requires the non-default CONNECT engine to be installed and enabled plus privileges to create CONNECT tables of table_type 'dos' with a crafted numeric definition such as double(255,30); the vendor rates it CVSS 8.5 while the independent assessment is slightly lower (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) because authentication, a non-default engine, and high attack complexity are needed, and no public exploit code was identified at time of analysis.
Blind SQL injection in the tagDiv Opt-In Builder WordPress plugin (slug td-subscription) through version 1.7.6 allows remote authenticated attackers with low privileges to extract sensitive data from the site's database via inference-based queries. The flaw is a CWE-89 improper neutralization of special elements in SQL commands; exploitation requires a valid low-privilege account (e.g., subscriber or contributor) and no user interaction, making sites with open registration the primary exposure. Assessed severity is high for confidentiality (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), and no public exploit identified at time of analysis.
Bluetooth authentication bypass in SwitchBot Door Lock Series allows an attacker within BLE range to manipulate the lock's communication protocol and bypass electronic lock and access controls without valid credentials, a PIN, or app pairing (PR:N, UI:N). The root cause is CWE-1204 cryptographic misuse, specifically weak initialization vector or related BLE protocol weaknesses, and exploitation is non-remote and does not scale because it requires per-target physical proximity within roughly 10 meters and interaction with live Bluetooth traffic. No public exploit identified at time of analysis; the risk is a targeted physical-intrusion issue that is narrower in reach than the 8.5 score alone suggests.
Code execution inside the gVisor sentry process is achievable by a local attacker holding standard container privileges on any platform running a gVisor build prior to release 20260831.0, due to a use-after-free/double-free of the MemoryFile backing an in-sandbox overlay filesystem in the virtual filesystem (VFS) mount layer. The issue is local-only and requires authenticated in-sandbox access (CVSS 4.0 vector AV:L/PR:L), and the resulting code execution lands in the sentry, which remains confined by host-level Linux seccomp and namespace boundaries rather than directly in the host kernel, so a single exploitation does not automatically yield host-kernel compromise or cross-tenant escape. No public exploit code was identified at time of analysis, but the trigger path is documented in the upstream fix's regression tests.
Blind SQL injection in the Metagauss ProfileGrid WordPress plugin (all versions through 6.0.0.2) lets an authenticated low-privilege user, such as a self-registered member of a community site, inject arbitrary SQL into a vulnerable plugin query and infer database contents through response timing or boolean differences. The issue is network-reachable, low complexity, and requires no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N, reported base score 8.5), with the practical barrier lowered because ProfileGrid is a user-profile/community plugin that frequently permits open self-registration; the independent assessment rates confidentiality impact as High, integrity Low, availability None. No public exploit code and no confirmed active exploitation were identified at time of analysis. The specific vulnerable endpoint and parameter are not named in the available data, so defenders cannot pin the trigger to a specific setting.
Blind SQL injection in the Taskbuilder WordPress plugin (all versions up to and including 6.0.5) allows an attacker who holds a valid low-privilege account to inject SQL through a plugin endpoint or parameter that fails to neutralize special elements, potentially exposing arbitrary data from the site's WordPress database. The vulnerability requires authentication (CVSS vector PR:L) and the plugin installed and active; the specific vulnerable feature, endpoint, and parameter are not named in the available advisory text, which limits targeted exploitation somewhat. At time of analysis there is no public exploit identified, no indication of confirmed active exploitation (not in CISA KEV), and no exact patched version confirmed, so this is a credible-but-not-urgent remediation priority - sites that allow open registration or host many low-privilege accounts carry the highest relative risk.
Blind SQL injection in the VibeThemes WPLMS WordPress e-learning theme, affecting all releases through version 4.973, lets an attacker with a logged-in low-privilege account inject SQL into backend queries and extract database contents through inference-based techniques. The authentication requirement (PR:L in the CVSS vector) is the main limiting factor, but it is a weak barrier in practice because many WPLMS-based learning sites allow open student or subscriber self-registration, effectively lowering the entry cost to near-anonymous. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); independent assessment classifies it as a genuine, elevated-priority problem rather than an emergency, with high confidentiality impact (C:H), limited integrity exposure (I:L), and no confirmed availability impact (A:N).
Blind SQL injection in the UpSolution Core WordPress plugin (us-core) through version 9.3 lets an attacker who already holds a low-privilege authenticated WordPress session inject SQL through a vulnerable parameter and extract database contents by inference (boolean/time-based) rather than by reading query output directly. Our independent assessment is more conservative than the vendor-advisory score of 8.5: with impact confined to confidentiality (C:H/I:N/A:N) and a mandatory PR:L session prerequisite, the effective severity is closer to 6.5, making this a genuine but conditional priority rather than a drop-everything emergency. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.