Insecure deserialization in the service console interface of openPDC and openHistorian lets an attacker submit a crafted serialized object graph to a function that deserializes client-supplied data, potentially achieving remote code execution under the privileges of the affected service account. Grid Protection Alliance's openPDC, its Docker image, and openHistorian are all affected, with CPE data indicating no version restriction (all releases). Whether the flaw is remotely exploitable without credentials depends entirely on configuration: deployments without Windows Authentication are reachable by an unauthenticated network attacker (the CVSS 4.0 vector carries PR:N), while deployments with Windows Authentication require the attacker to already hold valid authenticated access. No public exploit code or confirmed in-the-wild exploitation has been identified at time of analysis, but the assessed CVSS:3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity, and availability impact) and the absence of user interaction make this a genuine high-priority issue for exposed, unauthenticated console interfaces in OT environments.
Buffer overflow in the optional lwIP SMTP client application module lets an unauthenticated remote attacker corrupt memory by supplying oversized input that the client fails to length-check, yielding high confidentiality, integrity, and availability impact on embedded and OT devices that use the module. The vendor-supplied CVSS 4.0 score is 9.3 (AV:N/AC:L/AT:N/PR:N/UI:N), while our independent assessment rates it CVSS 3.1 AV:N/AC:H/PR:N/UI:N because successful exploitation requires the optional apps/smtp module to be compiled into the build and actively used, and generally requires the attacker to control the SMTP server the device talks to (or to be positioned to MITM that session) or to control the email field data (recipient, subject, body) handed to the client. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the affected version is a wildcard in the CPE, so the precise vulnerable lwIP releases remain unconfirmed; the issue is tracked through the ICS-CERT advisory ICSA-26-279-02 and its CSAF machine-readable counterpart.
Remote unauthenticated attackers can gain full administrative control of openPDC deployments provisioned from the official published Docker image, because that image embeds a fixed administrative credential that is not forced to change on first use. Exploitation requires only network reachability to the management interface and retention of the default credential; source-built or manually provisioned instances that set their own credentials are not affected. No public exploit code has been identified at time of analysis, though the vulnerable condition is inherent to the image and the CVSS 4.0 base score is 9.3, highlighting the severity for exposed deployments.
Plaintext credential storage in Red Lion Controls' 700 Series industrial devices exposes usernames, passwords, and unchanged factory-default credentials to anyone who can obtain the device configuration file, and at least one retrieval path - an SNMP-initiated TFTP export - is described as requiring no authentication. Administrators can also read the configuration through the CLI or export it via TFTP from the web interface, but those routes presume existing privileged access; the unauthenticated SNMP path is the exception that drives the risk rating. CISA ICS advisory ICSA-26-281-01 documents the issue, and our assessment scores it as a confidentiality-only, remotely reachable information-disclosure flaw (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N, 7.5 High) rather than the 9.3 the CNA vector implies; no public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis.
Red Lion Controls 700 Series devices expose SNMP functions that can be used to perform administrative operations - retrieving configuration files, modifying user accounts or device settings, and initiating firmware or bootloader upgrades or downgrades - while the vendor's description states these actions require no authentication at all (CWE-306, missing authentication for a critical function). The issue is rated 9.3 in the published CVSS v4.0 score, and the independent assessment scores it as critical (CVSS 3.1 base AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), reflecting full compromise of confidentiality and integrity and a scope change from the network service to the device itself; availability is not scored as impacted. No CISA KEV listing or public proof-of-concept is present in the supplied intelligence, so the current status is no public exploit identified at time of analysis. One caveat worth resolving early: the published v4.0 vector carries PR:L (some privilege/credential), which contradicts the description's 'without any authentication' - confirm the exact SNMP access requirement against the vendor advisory before de-prioritizing, because if the description is correct the real-world severity is closer to the independent PR:N assessment.
Weak, reversible encryption of usernames and passwords stored in the configuration file of Red Lion Controls 700 Series devices lets an attacker who holds the documented default credentials read the configuration and recover additional system credentials for reuse elsewhere on the device or network. The affected product line is captured by CPE cpe:2.3:a:red_lion_controls:700_series:*:*:*:*:*:*:*:*, meaning the vendor tracks the issue at the product-line level rather than against a specific firmware build, and the flaw is classified as CWE-257 (storage of passwords in a recoverable format). Our independent assessment rates this CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N - network reachable but requiring the attacker to already possess valid credentials (PR:L), with confidentiality-only impact - which is substantially lower than the CVSS 4.0 base score of 9.3 reported in the source data; there is no CISA KEV listing and no public exploit code identified at time of analysis, and EPSS data was not provided. Real-world risk therefore concentrates on deployments that retain default credentials and expose the management interface to untrusted networks, and on whether the recovered credentials are reused in a way that grants further access.
Unrestricted file upload in the PX-lab Zombify WordPress plugin (versions up to and including 1.7.7) lets remote attackers push a dangerous file type, such as a PHP web shell, into a web-accessible location and execute it on the server. The supplied CVSS vector rates this 10.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), reflecting full compromise of confidentiality, integrity and availability with scope change, and the vector indicates unauthenticated exploitation with no user interaction, though the Patchstack-sourced advisory does not itself document the precise access level required and defenders should verify whether any privilege is needed in their configuration. No CISA KEV listing and no public exploit code were identified at time of analysis, so real-world impact is currently gated by whether this niche plugin is deployed and its upload path is reachable; where it is, this is a genuine high-priority issue rather than a high-score-but-low-risk case.
Authenticated low-privilege tenant users of iFlytek Astron Agent prior to 1.1.2 can run arbitrary Python as root inside the core-workflow container by submitting a workflow Code node, because the shipped default configuration routes dynamic code execution to an unsandboxed LocalExecutor that exposes the full set of Python builtins. From that foothold the attacker can read shared service and database credentials and use them to bypass application-level tenant checks, read or modify other tenants' data, and disrupt shared services (CVSS 9.9, scope-changed, CWE-95). Exploitation requires a valid tenant account plus the ability to create or run a workflow containing a Code node; no public exploit identified at time of analysis, and the vendor-released patch is version 1.1.2.
SQL injection in JetBrains Exposed before 1.5.1 enables unauthenticated remote attackers to execute arbitrary SQL against downstream applications that pass attacker-controllable, unescaped string arguments into several affected SQL functions. The library itself is not directly exploitable; exploitation requires a hosting application to route untrusted input into the vulnerable function calls, so applications that only pass literals or use parameterized/escaped paths are unaffected. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) describes a worst-case nominal impact of full confidentiality, integrity, and availability loss; no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Remote code execution in iStoreOS (istoreos-24.10.7 and earlier) lets an attacker who can reach the web management interface supply a crafted task_id value that tasks-lib.lua processes without sanitization and evaluates as Lua code, resulting in arbitrary command execution with the privileges of the management service. The vendor-published CVSS is 9.8 (AV:N/AC:L/PR:N/UI:N), but the primary disclosure is titled 'authorized-rce' and our independent assessment scores the vector at PR:L, meaning a valid authenticated session on the management UI is the realistic prerequisite - a significant limiting factor because iStoreOS router/NAS admin interfaces are typically not exposed to the internet. No CISA KEV entry and no confirmed public exploit code were identified at time of analysis, and EPSS is low at 0.27% (18th percentile), so exploitation is currently opportunistic rather than rampant.
Weak authentication throttling in Dell Secure Connect Gateway (SCG) Policy Manager allows unauthenticated remote attackers to mount sustained credential-guessing attacks against the login interface, potentially leading to privilege elevation, bypass of protection mechanisms, and unauthorized access to a management platform that brokers connectivity into managed Dell infrastructure. All SCG Policy Manager builds prior to the fixed release are affected (the Dell advisory cites 5.34.00.16, while ENISA EUVD data cites 5.36.00.16 - the discrepancy should be verified against the vendor advisory before patching decisions). The flaw is rated CVSS 9.8 (AV:N/AC:L/PR:N/UI:N) and CWE-307, but exploitability is gated by credential strength and attempt volume: CISA's SSVC assessment rates it as not automatable and records no observed exploitation, EPSS is only 0.26% (16th percentile), and no public exploit code has been identified at time of analysis.
Remote code execution in Netcore B11 Enterprise-level full Gigabit 9-port shop wireless router firmware v1.3.241114.024540 and earlier is caused by OS command injection in the www/cgi-bin/upgrade handler, allowing a network attacker to run arbitrary commands through the router's HTTP management interface. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity, and availability impact, so unauthenticated exploitation is possible when that endpoint is reachable. No CISA KEV confirmation was provided and no public exploit identified at time of analysis; EPSS is 0.24% (14th percentile), indicating low predicted exploitation activity despite the critical severity score.
Cryptographic signature spoofing in the Sipay Virtual POS Module for PrestaShop (versions 26.8.1 up to but not including 26.9.1) allows unauthenticated remote attackers to forge or bypass the module's signature verification of payment data, letting them inject fabricated signed payment/JWT payloads that the store treats as legitimate gateway traffic and thereby tamper with payment and order state. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) exploitation is network-reachable with no authentication and no user interaction, and the integrity impact is the dominant concern; the exposure is limited to merchants who have the Turkish Sipay payment-gateway module installed and active at an affected version, not default PrestaShop installations. No public exploit identified at time of analysis, and no CISA KEV listing is associated with this issue.
Signature spoofing in the Sipay Electronic Money and Payment Services OpenCart Virtual POS Module (versions 26.8.2 up to but not including 26.9.1) lets unauthenticated remote attackers bypass cryptographic signature verification and submit forged or tampered payment tokens, most plausibly spoofed JWTs in the payment callback/token-verification flow, which can expose payment data and permit unauthorized manipulation of transaction processing. The flaw is network-reachable with no authentication or user interaction required (CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N, CWE-347), and an independent assessment narrows the impact to high confidentiality and integrity loss without an availability component, giving a 9.1-equivalent severity rather than the originally cited 9.8. At time of analysis there is no public exploit identified and the issue is not listed in CISA KEV, but exploitation requires only that a store runs the vulnerable module version with its callback endpoint reachable. Reported by TR-CERT; a vendor fix is available in 26.9.1.
Insufficiently protected credentials in Rocket Software Rocket Remote Desktop 18.0.8583.1 can expose account secrets to an attacker who can reach the credential material, potentially compromising downstream systems that use those credentials. The CVE feeds rate the issue as 9.8 with CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, but our independent assessment is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N: local, authenticated, and confidentiality-only, because realistic impact depends on local access to a stored credential blob or a man-in-the-middle position on session traffic, and the exact exposed feature is not specified in the one-line description. EPSS is 0.14 percent at the 3rd percentile, and no public exploit identified at time of analysis or CISA KEV entry was provided.
Authenticated administrators of Nginx UI releases 2.3.8 through 2.4.x can achieve remote code execution on the host by abusing the backup restore endpoint to overwrite live configuration with attacker-controlled nginx command settings. The attacker submits attacker-controlled portable backup key material along with a matching manifest to POST /api/restore; because the restore flow trusts the supplied key and treats the backup as 'portable', it decrypts the attacker's payload and replaces the live app.ini, including the protected TestConfigCmd value, after which a call to POST /api/nginx/test executes the restored command inside the Nginx UI runtime. The issue is rated CVSS 9.4 (CVSS 4.0) and CVSS 3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H, is fixed in version 2.5.0, and at time of analysis there is no public exploit identified and no confirmed active exploitation (not listed in CISA KEV); the practical barrier is the high-privilege authenticated session required, so exposure is limited to instances where an admin account or session can be obtained by an untrusted party.
FalkorDB instances that explicitly enable the optional Bolt wire-protocol endpoint can be crashed, and possibly have arbitrary code executed, by an unauthenticated remote attacker who sends a single crafted Bolt RESET message with an attacker-chosen 16-bit chunk size. The vulnerability is a heap-based out-of-bounds write (CWE-787) in BoltReadHandler in src/bolt/bolt_api.c present before version 4.20.0; the size check is performed only with ASSERT(), which is compiled out of release builds, so production binaries provide no runtime guard. Exploitation requires the Bolt port (BOLT_PORT) to be enabled and network-reachable - it is disabled by default and is the decisive precondition that sharply limits the exposed population; with no CISA KEV entry and no public exploit code identified at time of analysis, reliable denial of service is the confirmed impact while remote code execution remains a theoretical possibility that has not been demonstrated.
Remote attackers who can issue Redis replication commands to a FalkorDB instance before 4.18.1 can trigger a double-free/use-after-free in the RDB graph decoder, causing a denial of service (redis-server crash) or potentially arbitrary code execution in the redis-server process. The root cause is a buffer-size validation in RdbLoadDeletedNodes/RdbLoadDeletedEdges that relies on ASSERT(), which is compiled out in release builds, so a deleted-nodes buffer whose byte length is not a multiple of sizeof(NodeID) passes unchecked, is freed, then read and freed again. Exploitation is unauthenticated (CVSS PR:N) on instances without a password or otherwise reachable by an untrusted replication source; no public exploit code has been identified at time of analysis, and reliable code execution depends on heap layout.
Unauthenticated remote access to x64dbg-MCP Server prior to version 1.1 lets any network client that can reach the plugin's HTTP/SSE listener execute arbitrary x64dbg commands, attach to processes by PID, read and write debuggee memory, and write files to arbitrary paths. The listener binds to 0.0.0.0 by default and, before the fix, Bearer token authentication was optional and disabled by default, so a default installation with a running x64dbg GUI is fully controllable without credentials (CWE-306), matching the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. No public exploit code was identified at time of analysis and the issue is not in CISA KEV; no EPSS score was supplied, so exploitation likelihood rests on exposure of ports 9094 (x64) or 9095 (x32).
Unauthenticated path traversal in gvproxy, the network forwarder shipped in the gvisor-tap-vsock package (used by Podman Desktop, Red Hat OpenShift/CRC tooling and related Red Hat products), lets an attacker who can reach the /services/forwarder/expose control endpoint supply an arbitrary socket path that is passed unsanitised to os.Remove, resulting in deletion of arbitrary files on the host. The defect is reachable without credentials (PR:N) but requires adjacent/guest-side network access to the forwarder API (AV:A), which is normally bound to the virtual network rather than exposed as a routed internet service; impact is limited to integrity and availability (no data disclosure). No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV); an upstream fix exists in gvisor-tap-vsock PR #718. The vendor score of 9.3 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H) reflects low-complexity, unauthenticated access combined with a scope change and High integrity/availability impact, and the actual risk depends heavily on whether the forwarder control API is reachable by an untrusted guest or adjacent host.
Stored cross-site scripting in the Contao CMS comments bundle lets an unauthenticated visitor submit a comment whose email or website metadata is rendered without sufficient attribute and URL encoding by listComments() in comments-bundle/contao/dca/tl_comments.php, so attacker-controlled script executes in the Contao backend origin when a backend user opens the Comments module. All Contao releases from 4.0.0 up to (but not including) 5.3.50 and 5.7.12 are affected, and successful exploitation requires a privileged backend user to view the Comments module (CVSS 9.3, AV:N/AC:L/PR:N/UI:R/S:C); no public exploit code has been identified at time of analysis and there is no indication of confirmed active exploitation. Critically, moderation is not a mitigating control because unpublished/pending comments remain visible to moderators, so an unapproved malicious comment still triggers in that user's session.
Unauthenticated blind SQL injection in the WordPress plugin EduAdmin Booking (MultiNet Interactive AB) before version 6.0.0 allows remote attackers to inject SQL through the plugin's request handling and extract data from the underlying WordPress database, including booking records, customer details, and potentially user credential hashes. The supplier-rated CVSS 3.1 base score is 9.3 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L), while our reassessment is more conservative at AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, because blind SQL injection normally produces confidentiality-only impact without the claimed scope change; under either vector the flaw is network-reachable and, per the supplied vector, requires no authentication or user interaction, although the exact vulnerable parameter or endpoint is not identified in the available data. Risk is real but bounded: exploitation requires an active installation of this specific plugin, and no public exploit identified at time of analysis, with no CISA KEV listing and no public PoC in the supplied intelligence.
Unauthenticated blind SQL injection in tagDiv Opt-In Builder (td-subscription) versions through 1.7.6 allows remote attackers to extract sensitive data from the underlying WordPress database via crafted input to the plugin's subscription/opt-in functionality. The vendor-reported CVSS 3.1 score is 9.3 (S:C), but an independent assessment revises the scope to unchanged (S:U) and confirms high confidentiality impact without integrity or availability impact. No public exploit identified at time of analysis.
Off-origin preview framing in TinaCMS (tinacms <= 3.13.0 and @tinacms/app <= 2.5.13) lets an unauthenticated attacker who convinces a signed-in editor to open a crafted link such as `#/~//attacker.example/p` make the admin load and trust an attacker-controlled iframe, which is then accepted as the legitimate preview over the admin↔preview postMessage channel. Because the admin executes any GraphQL operation coming from that frame using the editor's own token, the attacker gains the editor's content API read and write access, exposing or modifying protected content. Exploitation needs only one click by an authenticated editor against a default configuration; no public exploit code was identified at time of analysis, and vendor-released patches are available in tinacms 3.14.0 and @tinacms/app 2.5.14.
Stack-based buffer overflow in FalkorDB versions before 4.18.4 allows remote attackers who can issue Redis replication commands - for example against a network-reachable instance with no password configured - to crash the graph database and possibly achieve code execution by supplying a crafted RDB stream whose entity property count is unbounded. The decoder sizes two variable-length arrays on the thread stack from that attacker-controlled count and then fills them with attacker-supplied values, so a single malformed RDB payload overflows the stack (CWE-121). No public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor has released FalkorDB 4.18.4 moving large property sets to the heap; CVSS 4.0 rates this 9.2 with AV:N/AC:H/PR:N/UI:N, where the high attack complexity reflects the difficulty of converting the overflow into reliable arbitrary code execution rather than a denial of service.
Account takeover in PHPNuxBill through 2025.3.20 allows unauthenticated remote attackers who know a valid customer username to brute-force the six-digit otp_code in the customer password-reset flow at system/controllers/forgot.php; because the pre-patch code has no attempt limit or lockout, an attacker can guess the OTP within its roughly 600-second validity window and then read the newly set password from the HTTP response. The vendor has published an upstream fix and advisory, but no public exploit identified at time of analysis, and the independent assessment rates this as a genuine high-priority issue requiring only a known username and default configuration.
Unauthenticated SQL injection in the PHPNuxBill radius.php FreeRADIUS REST endpoint allows remote attackers to read arbitrary data from the application database - including customer records and stored credentials - by injecting crafted username, macAddr, or nasid parameters into the accounting or authenticate actions, which are interpolated directly into whereRaw() queries. All versions through 2025.3.20 are affected per the vendor advisory and CPE data (cpe:2.3:a:hotspotbilling:phpnuxbill:*:*), and exploitation requires only network reachability of radius.php, with no authentication and no user interaction. The supplier-scored CVSS 4.0 vector (9.3) asserts high confidentiality, integrity, and availability impact, whereas our independent assessment scopes the realistic impact to confidentiality loss (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N); no public exploit code or confirmed active exploitation was identified at time of analysis, so the decisive risk factor is whether radius.php is exposed beyond the trusted RADIUS/NAS segment.
Unauthenticated blind SQL injection in the Shinetheme Traveler WordPress theme (all versions from initial release through 3.2.9) lets a network-based attacker inject arbitrary SQL into a vulnerable query and infer database contents through boolean- or time-based responses, yielding high confidentiality impact with no integrity or availability loss of note. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L, base 9.3) describes a low-complexity, no-authentication, no-user-interaction attack with a scope change, indicating the vulnerable component can affect resources beyond its own security boundary - such as the underlying WordPress database. At time of analysis there is no CISA KEV entry and no public exploit code identified at time of analysis, and the unauthenticated classification is Patchstack-reported and unverified: if the real prerequisite turns out to be subscriber- or author-level access, authentication would become the primary limiting factor.
Blind SQL injection in the wpdreams Ajax Search Pro WordPress plugin, affecting all versions through 4.29.1, lets unauthenticated remote attackers inject crafted input into the plugin's public-facing search/AJAX query path and infer database contents one bit at a time. Because the vector is PR:N/UI:N, no credentials or victim interaction are needed, making any internet-exposed WordPress site running the vulnerable plugin a candidate target. No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV); exploitation demands many iterative automated requests rather than a single direct query, but a successful attack can yield sensitive data such as user password hashes, secret keys, and PII.
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.
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.
Authentication bypass in Apache CXF's OidcClientCodeRequestFilter renders the max_age authentication-freshness check inoperative, allowing stale OIDC sessions to be accepted regardless of age when a relying party has configured setMaxAgeOffset to enforce step-up re-authentication. The defect stems from a milliseconds/seconds unit mismatch and inverted comparison polarity, silently defeating session-age validation; affected releases are Apache CXF 4.2.0 before 4.2.4, 4.0.0 before 4.1.9, and 3.6.x before 3.6.13. Vendor patches are available, no public exploit identified at time of analysis, and EPSS is low (0.23%), though exploitation requires the non-default setMaxAgeOffset setting, limiting real-world impact to deployments that opt into max_age policies.