Local file inclusion that can escalate to PHP code execution affects the All Bootstrap Blocks WordPress plugin in versions up to and including 1.3.31, allowing an authenticated user with contributor-level access or higher to direct the plugin to include arbitrary local files at render time and read their contents. Code execution occurs only where an includable local file already contains PHP, and exploitation additionally requires the plugin's non-default Lightspeed subsystem to be explicitly enabled, so a stock installation is not exposed. No CISA KEV entry has been recorded for this issue, but publicly available exploit code exists and a proof-of-concept is referenced by WPScan, making the risk material for sites that have enabled Lightspeed and grant contributor accounts.
Concurrent downgrade requests against Paymenter 1.5.6 and earlier can double-spend account credit: any authenticated customer with an active, downgradable service can fire parallel requests that each pass the unpinned Service::upgradable check and each credit the same balance, yielding N refunds for one downgrade. The inflated balance is real, spendable store credit, so an attacker can immediately settle invoices or provision services at the operator's expense; no public exploit code or confirmed active exploitation was identified at time of analysis, and the independent assessment rates this a moderate-severity business-logic flaw rather than a system-compromise vector, since it requires a qualifying service, the default credits-on-downgrade setting, and a race window that must be won. Vendor-released patch: 1.5.7.
Local information disclosure in microsandbox before 0.5.10 exposes sandbox secret values - host-side API keys, tokens and environment secrets - to any other local user or co-resident process on the same host, which can simply read them from the sandbox process command line while the sandbox is running. The Rust SDK serializes NetworkConfig secret values into the --network-config argument and passes per-sandbox secrets through repeated --env arguments, keeping them visible in /proc/<pid>/cmdline on Linux and process listings on macOS for the entire sandbox lifetime, with no code execution inside the sandbox and no access to the spawning user's session required. Rated CVSS 3.1 6.5 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N, medium), the flaw is only exploitable on shared/multi-tenant hosts, CI runners and developer systems where an adversary holds a separate local account or co-tenant process, and only leaks data when secrets were actually configured; no public exploit code has been identified at time of analysis, and the issue is fixed in 0.5.10.
Web cache poisoning in the Breeze Cache WordPress plugin before 2.5.15 allows unauthenticated remote attackers to append tracking-related query parameters that the plugin still caches responses for but omits from the page-cache key, causing a page rendered in the attacker's own request context to be stored under the clean URL's cache entry and served to every subsequent visitor. Exploitation requires only that page caching be active in its default configuration - no authentication, no user interaction, and no special setup (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, 6.5) - and publicly available exploit code exists; the issue is not confirmed as actively exploited (not in CISA KEV). Impact is bounded to low confidentiality and integrity effects, exposing one visitor's rendered context to others and altering cached page content until the entry expires or is purged.
Missing ownership verification in the RestroPress WordPress plugin through 3.4.6 lets remote, unauthenticated attackers enumerate which orders are in a recoverable state and inject arbitrary notes into other customers' orders simply by supplying an order identifier to the payment-recovery flow. The flaw is an IDOR-class authorization bypass (CWE-639) with a CVSS 3.1 score of 6.5 on the vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, so no credentials, privileges, or user interaction are required and default configurations are exploitable wherever the plugin's payment/order functionality is in use. Publicly available exploit code exists and the issue was reported by WPScan; impact remains confined to order-state disclosure and note injection (no code execution, no full order-data exfiltration, no destruction), so real-world risk is moderate rather than critical.
Cross-site scripting in the MdPreview component of md-editor-v3 (versions up to and including 6.5.3) lets remote attackers execute JavaScript in the host application's origin by supplying Markdown that contains a crafted fenced-code language string, and because the host can persist that Markdown it escalates to stored XSS for every user who later views the content. User interaction is required - a victim must render the malicious Markdown - and the shipped XSSPlugin does not prevent exploitation, since it only filters existing html_block and html_inline tokens and cannot inspect the renderer-generated HTML that the highlight callback produces. Scored CVSS 3.1 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N); publicly available exploit code exists (a working payload is included in the upstream GHSA advisory), no confirmed active exploitation (no CISA KEV listing), and the vendor-released patch fixes the issue in version 6.5.4.
Authentication bypass by spoofing in Microsoft Fabric lets unauthenticated network attackers impersonate a trusted identity and elevate privileges, with a scope change indicating the bypass can cross the initial authorization boundary to affect resources or tenants beyond the attacker's own. Microsoft and independent assessment both score this CVSS 3.1 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), reflecting full confidentiality, integrity, and availability impact on the affected multi-tenant analytics service. No public exploit code exists and there is no confirmed active exploitation (no CISA KEV listing) at time of analysis, and because Fabric is a Microsoft-operated SaaS, exposure depends on vendor-side remediation rather than customer patching.
Sandbox escape in vm2 through 3.12.0 lets unauthenticated remote attackers execute arbitrary code on the host when the embedding application exposes at least one non-strict (sloppy-mode) host function to the sandbox. By calling such a function with a nullish receiver (`fn()`, `fn.call()`, `Reflect.apply(fn, undefined, [])`, etc.), sandboxed script causes V8 to substitute the host realm’s global object for `this`, which vm2 then wraps and returns as a live proxy of the host global; the attacker can then reach `process` and run commands such as `process.getBuiltinModule('child_process').execSync`. Vendor-released patch: upgrade to 3.12.1; no public exploit identified at time of analysis, but the required pre-condition is common because ordinary JavaScript functions are non-strict by default, and vm2 is deprecated, so unmaintained deployments remain exposed-independent assessment rates this a top-tier priority.
Sandbox escape in vm2 NodeVM before 3.12.1 allows unauthenticated remote attackers to execute arbitrary commands on the host, but only when the application has been configured to allow child_process via builtin:['*'] or an explicit allowlist entry. Exploitation requires the host application to run untrusted JavaScript inside a NodeVM instance and to have this misconfiguration; default configurations that do not allow child_process are not vulnerable. The vendor-supplied CVSS 4.0 vector rates this 10.0, while the independent CVSS 3.1 assessment reflects high attack complexity (AC:H) due to the required misconfiguration. No public exploit code or active exploitation has been identified at time of analysis.
Cross-site request forgery in IBM Common Licensing Agent and ART 9.0.x allows remote attackers to execute unauthorized actions on behalf of an authenticated user, with high integrity impact but no confidentiality or availability impact. Exploitation requires the victim to visit a malicious page while authenticated to the licensing web interface; no public exploit identified at time of analysis. Vendor assigned CVSS 10.0, but independent analysis assesses a more moderate risk due to the UI:R and S:U characteristics typical of CSRF.
SQL injection in the pg_partman PostgreSQL extension before version 5.5.0 lets an authenticated database role that holds the documented partman_user INSERT/UPDATE privileges on the part_config table store SQL text in the writable time_encoder column instead of a legitimate function name. When the pg_partman_bgw background worker next creates a child partition for a text- or UUID-keyed set, that stored SQL is interpolated into a dynamically executed SELECT and runs with the privileges of pg_partman_bgw.role, which the pre-5.5.0 documentation defaults to a superuser such as 'postgres'; because the payload persists in the configuration row, elevated access can be re-established on subsequent maintenance ticks and can lead to database-wide compromise and operating-system command execution as the PostgreSQL service account. The issue is rated CVSS 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) and is fixed in 5.5.0; no public exploit identified at time of analysis, and exploitation requires an attacker to already possess partman_user grants plus a deployment where the background worker runs as a superuser.
Privilege escalation in Azure Database for PostgreSQL allows an authenticated attacker with low privileges to elevate privileges over the network, potentially achieving full control over database resources. With a critical CVSS score of 9.9 due to scope change and high impact, the flaw requires a valid low-privileged identity to exploit; no public exploit code has been identified at time of analysis.
Sandbox escape in vm2 3.12.0 and earlier allows unauthenticated remote attackers who can supply JavaScript to an application embedding vm2's VM or NodeVM to break out of the sandbox and execute arbitrary code on the host, provided the embedder exposes at least one host API returning a host-realm (native) Promise whose rejection value is host-pivotable - the advisory cites a host process object as the example. The flaw is an incomplete rejection-sanitization failure in lib/bridge.js: the sandbox-side Symbol.species and .then neutralization is installed only on the sandbox intrinsic Promise.prototype, so it never applies to host Promises, letting sandboxed code overwrite p.constructor[Symbol.species] and call p.then() without an onRejected handler, after which V8's internal Thrower re-throws the raw host rejection value into an attacker-controlled resolve/reject closure, bypassing handleException and hostPromiseSanitizeReject and yielding an unsanitized, fully functional bridge proxy of the host object. No public exploit identified at time of analysis, but the CVSS 4.0 base score is 10.0 and the issue is fixed in 3.12.1.
SQL injection in IBM Guardium Data Protection 12.2 allows a remote authenticated attacker to execute arbitrary SQL commands against the appliance's back-end database, and the vendor rates it Critical (9.9) on a scope-changed vector while our independent assessment retains high impact on confidentiality, integrity, and availability on a scope-unchanged basis. Exploitation requires valid low-privilege credentials to the Guardium web/management console (CVSS PR:L) with no user interaction (UI:N), so a standard operator or auditor-level account is enough to reach the vulnerable query path, and Guardium is normally deployed on internal management networks rather than exposed to the internet, which meaningfully constrains realistic exposure. No public exploit code exists and there is no evidence of active exploitation at time of analysis (no CISA KEV listing), and a vendor patch is available.
Unauthenticated remote attackers can bypass security restrictions in IBM Guardium Data Protection 12.2 through the ChangeTrackerServlet, which is missing authentication (CWE-306). The vendor CVSS 3.1 vector rates this 9.9 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L), and the independent assessment preserves the unauthenticated network-reachable nature while treating scope as unchanged; no public exploit was identified at time of analysis and there is no CISA KEV confirmation. IBM has published patch information, so affected deployments should be updated and have network access to the management web tier restricted until patched.
Missing authentication in the LoadBalancerServlet of IBM Guardium Data Protection 12.2 allows unauthenticated, network-reachable attackers to invoke privileged load-balancer operations, compromising the integrity and availability of the affected deployment. The flaw is rated 9.9 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N) and maps to CWE-306, so no credentials or user interaction are required; the practical barrier is that the Guardium management interface exposing the servlet must be reachable across the network, and such interfaces are usually confined to segmented internal networks. Impact is concentrated on load-balancer control operations rather than broad data exposure (confidentiality impact is low), and no public exploit identified at time of analysis; the issue is not listed in CISA KEV. IBM has published a patched release through its support advisory.
Cross-workspace impersonation and complete authorization bypass in kcp (kcp-dev) before 0.31.4 and 0.32.x before 0.32.2 let any authenticated tenant forge Kubernetes-style identity headers that the shard accepts as trusted authentication assertions. Because the front-proxy and the server localproxy forward inbound X-Remote-User, X-Remote-Group, and X-Remote-Extra-* headers without clearing them, an attacker with valid credentials for any single workspace can supply values such as X-Remote-Group: system:masters, authorization.kcp.io/warrant, authentication.kcp.io/scopes, or a group used for per-workspace required-group gating to read, write, or delete resources, secrets, RBAC data, APIExports, APIBindings, and LogicalClusters across the installation. Exploitation requires authenticated access (CVSS vector PR:L, AV:N, no UI), yields changed scope per the vendor vector (CVSS 9.9), and no public exploit code or confirmed active exploitation was identified at time of analysis; fixed releases 0.31.4 and 0.32.2 are published.
Privilege escalation and cross-tenant data disclosure in WACRM 0.7.0 and earlier allow any authenticated user - a read-only 'viewer' is sufficient - to self-promote to account owner, relocate their profile into another tenant's account, and then read or modify that tenant's resources, or to directly pull another tenant's AI knowledge-base chunks, all through the default Supabase/PostgREST REST API. The flaw is two-fold: an overly permissive row-level security policy on the profiles table that lets users edit their own account_role and account_id columns, and two SECURITY DEFINER RPCs (match_ai_knowledge_fts, match_ai_knowledge_semantic) that are GRANTed to the authenticated role and trust a caller-supplied p_account_id without any is_account_member check. Rated CVSS 3.1 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, CWE-639); exploitation requires a valid low-privilege JWT but no admin rights, no user interaction, and no non-default configuration, and no public exploit identified at time of analysis - practical risk is tempered mainly by how rarely this self-hosted template is deployed.
AnyCable (anycable-go) through 1.6.14 ships its telemetry subsystem enabled by default with a hardcoded public auth token ('secret' in telemetry/config.go) and derives its cluster fingerprint by hashing the full configuration file plus raw os.Args, which can include values passed via --secret, --jwt_secret, and --http_rpc_secret; an adversary who can MITM or DNS-hijack telemetry.anycable.io can intercept the outbound telemetry POST, and because the client's token is publicly known it offers no protection. The transmitted clusterFingerprint is a SHA256 digest rather than raw plaintext, so meaningful secret recovery additionally depends on low-entropy secrets, and the required network-interception position makes this a moderate-to-low real-world risk best characterized as a hardcoded-credential and telemetry-exposure design flaw rather than a directly exploitable credential leak. Exploitation status: no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV); the GHSA advisory documents only a conceptual DNS-spoofing reproduction. Vendor-released patch: 1.6.15.
Unauthenticated remote code execution in LMDeploy 0.9.2 through 0.15.x lets any attacker who can reach a DistServe/PD-disaggregation deployment's POST /distserve/p2p_connect endpoint run arbitrary code with the privileges of the LMDeploy serving process. The endpoint accepts an attacker-supplied ZeroMQ peer address; the engine connects to it and deserializes the reply with PyZMQ's recv_pyobj(), which is backed by Python pickle and therefore executes code during object reconstruction, before any type or schema check can run. Rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-502); exploitation is unauthenticated only in the default configuration where the operator has not enabled API-key authentication, and no public exploit code has been identified at time of analysis. A vendor patch is available in LMDeploy 0.16.0, which replaces the pickle-based ZeroMQ protocol with JSON plus Pydantic validation.
Signed-request replay in AnyCable's Pusher-compatible REST API (version 1.6.14 and earlier) lets anyone who obtains a single legitimate signed POST request resend it with a completely different body, because the handler folds the caller-supplied body_md5 into the HMAC string but never computes or compares the digest of the body actually received. The same code path omits any auth_timestamp freshness check, so a captured auth_signature remains valid indefinitely. Successful abuse causes the server to broadcast attacker-chosen event content to arbitrary channels within that signed request's application context, enabling forged server-side events, application-state corruption, or phishing messages delivered to WebSocket clients. Exploitation hinges on first capturing a signed request (for example from a TLS-terminating proxy's logs), which is why attack complexity is rated High under CVSS 5.9; no public exploit code was identified at time of analysis and there is no KEV entry.
Out-of-bounds heap write in FluidSynth's command handler lets an attacker supply an out-of-range channel argument to the pitch_bend_range command, which is written through the selected synth channel without bounds checking. The worst-case exposure is unauthenticated remote code execution or denial of service (CVSS 3.1 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) when FluidSynth runs as a TCP command server via new_fluid_server() or 'fluidsynth -s'; absent that network mode, the flaw is only locally reachable through malicious commands fed to the interactive shell on standard input, and applications that embed the library without the shell, command handler, or TCP server are unaffected. The vendor has released a fix in FluidSynth 2.5.6 (spanning affected releases from 1.1.2); no public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV).
Unauthenticated remote code execution in IBM Guardium Data Protection 12.2 lets a network attacker who can reach the appliance interface that processes serialized input run arbitrary code in the context of the affected service, yielding full loss of confidentiality, integrity and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). The root cause is insecure deserialization of untrusted data (CWE-502), and because the assessed vector carries PR:N and UI:N, no credentials or user interaction are needed, so real-world exposure is determined almost entirely by network reachability to the Guardium management/collector segment rather than by the public internet. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV; IBM has published a vendor patch, which keeps this a top-tier remediation priority rather than an actively exploited emergency.
Unauthenticated insecure deserialization in the Change Audit System (CAS) listener of IBM Guardium Data Protection 12.2 allows a network attacker who can reach TCP port 16017 to submit crafted serialized messages that are insecurely deserialized and used for attacker-controlled reflective method dispatch, potentially resulting in unintended code execution on the Guardium appliance with high confidentiality, integrity, and availability impact. The vendor-reported base score is 9.8 (AV:N/AC:L/PR:N/UI:N); our independent assessment keeps the unauthenticated, no-user-interaction profile but applies AC:H, because the practical gating factor is whether an attacker has a network path to the non-standard CAS port rather than any product configuration toggle. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV); IBM has published a vendor patch advisory, and this should be treated as a genuinely high-priority issue for any deployment where port 16017 is reachable from untrusted networks, while remaining lower-risk in segmented or hardened environments where the listener is internal-only.
Heap buffer underflow in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated remote attacker to crash or destabilize the queue manager, and potentially to execute arbitrary code, by submitting a crafted multi-segment message that is reassembled during processing. The dependable outcome is denial of service: reliable code execution is not confirmed, and exploitation requires valid low-privilege credentials (PR:L) plus access to a channel or queue that accepts submitted messages. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; urgency is real but constrained because only the specialized HPE NonStop build is affected, not general IBM MQ distributions.
Authentication bypass in IBM Guardium Data Protection 12.2 lets an unauthenticated remote attacker evade the IP-based access controls guarding the Guardium management interface and reach that interface without satisfying the network allowlist. IBM rates the flaw 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but our independent assessment scores it materially lower (C:L/I:N/A:N) because the bypass defeats the IP filter rather than the interface's own authentication, so real impact hinges on what the management interface permits once reached and whether it applies its own credentials. No public exploit code has been identified at time of analysis, and exploitation is only possible where the management interface is network-reachable and administrators treat IP allowlisting as the primary or sole control; deployments whose management plane is fully segmented behind a firewall with no attacker path are not exposed.
Unauthenticated SQL injection in IBM Guardium Data Protection 12.2 lets a remote attacker submit crafted input that is concatenated into a SQL statement without proper neutralization, enabling execution of arbitrary SQL commands with full confidentiality, integrity, and availability impact (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N). Per the assessed vector, no credentials and no user interaction are required, so any party who can reach the affected interface over the network can attempt exploitation; the practical barrier is deployment exposure, since Guardium management interfaces are normally placed on segmented internal or security-monitoring networks rather than being internet-facing. There is no public exploit code identified at time of analysis and the vulnerability is not listed in CISA KEV, but successful exploitation could allow reading or altering the data Guardium is entrusted to protect, which makes internal-network reachability the key risk factor. The specific injectable endpoint or parameter is not named in the available description, and if the flaw is second-order rather than first-order, real-world exploitation would require more steps than the AC:L rating implies. No EPSS score was supplied with the source data.
Second-order SQL injection in IBM Guardium Data Protection 12.2 allows an unauthenticated remote attacker to submit SQL that is stored and later processed by the generateInsertQuery logic in change-tracker-data.sql, potentially compromising confidentiality, integrity, and availability. The supplied CVSS is 9.8 (AV:N/AC:L/PR:N/UI:N), but our independent assessment raises attack complexity to High because the second-order path requires both initial acceptance/storage of the payload and a subsequent internal operation that builds the INSERT query; this two-stage requirement is the main practical constraint. No public exploit identified at time of analysis or KEV-confirmed active exploitation is present in the supplied data, and IBM has published vendor patch information at its support advisory.
Malformed compressed data delivered over an IBM MQ channel that has compression enabled can trigger an out-of-bounds heap write, allowing a remote attacker to crash the queue manager and, potentially, execute arbitrary code in the MQ process. The issue affects IBM MQ 9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS / up to 9.3.5.1 CD, 9.4.0.0-9.4.0.25 LTS / up to 9.4.5.1 CD, and 10.0.0.0, with the CVSS base of 9.8 reflecting a network-reachable, unauthenticated worst case, though our assessed vector raises attack complexity to High (AC:H) because the channel must be explicitly configured with compression and reachable by the attacker. Denial of service is the readily achievable outcome, while reliable code execution requires defeating the process's memory protections; no public exploit code has been identified at time of analysis, SSVC rates exploitation as none, and EPSS is low at 0.37% (31st percentile).
SQL injection and cross-tenant data exposure flaws in HCL BigFix Service Management allow an attacker who can reach the application's request-handling layer to inject database commands and to manipulate tenant/organization scoping values so that another organization's profile data and PII can be read. The vendor rates this 9.8 Critical using a vector that encodes PR:N, but the advisory text itself states the attack requires an authenticated attacker - an internal contradiction; our independent assessment resolves it as AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, so exploitability hinges on whether a valid account is genuinely required, and the cross-tenant half of the impact only applies to multi-tenant deployments hosting multiple organizations. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no fix version was disclosed in the provided data; organizations should treat the vendor KB article as the authoritative source for patched builds.
Unauthenticated remote code execution affects the Interchange e-commerce platform (the interchange/interchange project) through its admin 'quick question' page, where attacker-supplied yes/no parameters flow into a reparsed [calc] template block and injected Perl is evaluated server-side. The flaw is reachable without authentication in default installations, as confirmed by the upstream fix adding a previously absent [if-mm super] superuser gate, and SSVC rates it Automatable with total technical impact; however, injected code executes inside Interchange's Safe compartment, so unrestricted, full-impact code execution additionally requires the non-default AllowGlobal directive to be enabled on the catalog being accessed. The vendor rates this 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) while our independent assessment rates it AC:H given the sandbox constraint; no public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor patch/advisory is available.
Synology DiskStation Manager (DSM) login logic uses insufficiently random values, letting remote unauthenticated attackers (CVSS PR:N) read or write arbitrary files and mount denial-of-service attacks on NAS devices running DSM before 7.2.1-69057-12, 7.2.2-72806-9, 7.3.2-86009-4, and 7.4-90075. Synology rates the flaw 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), while independent assessment keeps the same impact but raises attack complexity to High, since the attacker must successfully predict or reproduce the weakly-random login value, potentially requiring repeated attempts or offline computation. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but the unaudited attack surface (DSM's web login on typical management ports) and full CIA impact make prompt patching the priority for any internet-reachable instance.
Improper output encoding in the SCGI service of Synology DiskStation Manager (DSM) lets unauthenticated remote attackers read or write arbitrary files on the appliance and mount denial-of-service attacks against it. Every DSM build prior to 7.2.1-69057-12, 7.2.2-72806-9, 7.3.2-86009-4, or 7.4-90075 is affected, and the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, 9.8) confirms no credentials, user interaction, or non-default settings are needed - the only real precondition is network reachability to the SCGI interface, which makes internet-facing NAS units the highest-risk deployments while firewall/VPN-isolated devices carry substantially lower risk. No public exploit code has been identified at the time of analysis and the issue is not in CISA KEV, but the combination of full confidentiality, integrity, and availability impact with no authentication requirement makes rapid patching a priority.
Unauthenticated server-side request forgery (SSRF) in the WordPress plugin 'Generate PDF using Contact Form 7' before version 4.2.2 lets remote attackers force the server to fetch an arbitrary URL - including internal-only resources - and read the fetched content back out of the generated PDF. Exploitation requires only that the site runs the vulnerable plugin and exposes a Contact Form 7 form whose submission triggers PDF generation; no credentials or user interaction are needed (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C, assessed C:H versus the published C:L). A publicly available exploit exists (WPScan), and a vendor fix is available in 4.2.2, so upgrading is the decisive action.
Stored cross-site scripting in IBM Guardium Data Protection 12.2 lets an authenticated user of the web management console inject script that executes in a second user's browser when the affected page is rendered. The vendor scores this 9.6 (scope change, high confidentiality and integrity impact), but the independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, treating the impact as confined to the victim's browser/session context rather than the underlying appliance operating system; the record's 'RCE' tag and the vendor's UI:N rating overstate what a CWE-79 input-neutralization flaw realistically delivers. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and IBM has published a patch advisory. This is a high-CVSS-but-lower-real-risk issue where the vendor scoring and tags overstate severity.
Uncontrolled resource allocation in the VES Collector component of O-RAN-SC SMO OAM (2025-06-10) lets remote, unauthenticated attackers exhaust resources and degrade availability, with no confidentiality or integrity impact (VC:N/VI:N/VA:L). The CVSS 4.0 base of 6.9 reflects network reachability with no privileges or user interaction (AV:N/AC:L/AT:N/PR:N/UI:N) and a proof-of-concept exploit is publicly available via a GitHub gist, though there is no confirmed actively exploited (CISA KEV) status. The upstream project was notified through a bug report (LF-O-RAN-SC Jira SMO-204) but has not responded, so no vendor-released patch is identified at time of analysis; practical exposure is limited to deployments where the VES Collector is reachable on an internal telecom OAM/management plane.
Unauthenticated attackers who can reach the PD Master's /pd_register WebSocket endpoint can register arbitrary nodes in LightLLM through 1.2.0, causing full user prompts routed to the attacker's socket to be disclosed, disrupting service by displacing legitimate nodes, and forcing the PD Master to issue requests toward internal network addresses. The root cause is CWE-306 (missing authentication for a critical function): the registration handler accepts crafted JSON without validating the peer address, and the CVSS 4.0 score of 9.3 with PR:N/UI:N reflects high confidentiality, integrity, and availability impact requiring no credentials or user interaction. No public exploit code or confirmed active exploitation was identified at time of analysis, and practical exposure is limited to multi-node prefill-decode (PD) disaggregated deployments where the endpoint is network-reachable; single-node or properly firewalled deployments are not exposed.
Root shell compromise of NetBackup Flex OS appliances is possible for authenticated, low-privileged users who have access to the NetBackup Flex OS management shell. By supplying a specially formed access credential, such a user can bypass the cryptographic signature verification step of a privileged support command (CWE-347), gaining unrestricted root control over the Flex appliance host and all hosted containers, with complete confidentiality, integrity, and availability impact. The vendor CVSS 4.0 score is 9.4 (PR:L, no user interaction); supplied intelligence does not indicate CISA KEV active exploitation or publicly available exploit code, so no public exploit identified at time of analysis.
CordysCRM before 1.7.2 exposes its SSE notification endpoints anonymously, allowing a remote unauthenticated attacker who can reach the backend HTTP interface to read another user's workflow events, approval requests, mentions, and alerts, inject SYSTEM_HEARTBEAT messages into that user's stream, or close that user's SSE channel. The flaw is missing authentication (CWE-306) in the Shiro public-path whitelist and the controller's trust in a caller-supplied userId; the provided source advisory CVSS 4.0 score is 9.3, while the independent CVSS 3.1 assessment is 8.6 because confidentiality impact is high but integrity and availability impact are limited to a selected user's notification stream. No CISA KEV entry or public exploit code was identified at time of analysis, but exploitation requires only network reachability and a target userId.
Unauthenticated HTTP requests to the OpenShift console's /api/devfile/ and /api/devfile/samples/ endpoints let remote attackers trigger server-side request forgery from the console pod into internal cluster services and exhaust console memory through repeated large requests lacking a Content-Length header. Red Hat rates this 9.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L); our assessment agrees on the unauthenticated, network-reachable SSRF crossing a trust boundary but lowers confidentiality to C:L because only partial internal responses are reflected, producing a lower composite score. Clusters that expose the web console to untrusted networks are most at risk; no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV).
Autobahn Python releases prior to 26.7.1 enforce the maxMessagePayloadSize receive limit against the compressed on-the-wire frame length rather than the inflated message size, so an unauthenticated remote client can send a small permessage-deflate frame that decompresses far past the configured application message cap and is nonetheless allocated, reassembled, validated, and handed to application callbacks. The impact is resource-exhaustion pressure scored at CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, availability-only), and the advisory does not establish confidentiality or integrity impact despite the general 'Information Disclosure' tag; no public exploit identified at time of analysis. Exposure is limited to WebSocket endpoints that negotiate permessage-compress (permessage-deflate or the bzip2/snappy/brotli backends) - endpoints that do not accept a compression extension for the connecting client are unaffected.
TLS certificate validation bypass in AnyIO (pip/anyio) versions before 4.14.2 lets an attacker who already holds an on-path man-in-the-middle position impersonate a server named with a non-ASCII internationalized domain name. AnyIO's TLSStream.wrap() encoded the target host name with IDNA 2003 (via the Python standard library) instead of IDNA 2008 before matching it against the peer certificate, so a host like 'faß.de' was compared against the certificate for 'fass.de' - an attacker can obtain a legitimately CA-issued certificate for that wrong domain and have it validate on the client. Exploitation requires all three of: an application calling connect_tcp(tls=True) or TLSStream.wrap() with an affected unicode host name, a pre-existing connection hijack/redirect the vulnerability does not itself provide, and attacker acquisition of a valid certificate for the IDNA 2003-encoded name; ASCII-only host names are unaffected. No public exploit code has been identified at time of analysis, and patched version 4.14.2 is available.
Unauthenticated attackers can reset the password of any Cotonti account, including administrator accounts, because password-recovery validation tokens in Cotonti through 1.0.0 are derived from md5(microtime()) rather than a cryptographically secure random source, leaving roughly one million predictable candidate values per second. Exploitation requires the attacker to trigger the recovery flow for a target account, read the server's Date header to bootstrap the microtime() timing window, then precompute and probe candidate tokens against the passrecover endpoint before the seed drifts - a timing-constrained but fully unauthenticated attack (assessed CVSS 3.1 AV:N/AC:H/PR:N/UI:N, C:H/I:H/A:H; CVSS 4.0 base 9.2). No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis; any endpoint rate-limiting or short token lifetime further constrains the probing step, so this is a genuine high-priority flaw rather than a CVSS-inflation case.
Bypass of the registration CAPTCHA in the WordPress Clean Login plugin before 1.19 allows unauthenticated attackers to create accounts without solving the challenge when the stored session value is empty. Publicly available exploit code exists, but no confirmed active exploitation (CISA KEV) was reported, and our independent assessment rates this as a genuine low-to-moderate priority issue because the impact is limited to spam and automation abuse rather than compromise of existing accounts or the server. The vendor has released version 1.19 as the fixed release.
The Clean Login WordPress plugin before 1.19 lets unauthenticated attackers create user accounts on sites where registration is disabled, bypassing an administrative control intended to prevent open sign-ups. The registration handler fails to check the site's registration-enabled setting, so even locked-down sites become vulnerable; impact is limited to unauthorized low-privilege account creation (CVSS I:L) with no direct confidentiality or availability loss. Publicly available exploit code exists, and the vendor has released a patched version (1.19).
Unauthenticated visitors can strip the login- and URL-hiding protection from WordPress sites running the Hide My WP Ghost plugin before 7.0.11 by triggering the plugin's own loopback security-check request with a missing or incorrect verification value, causing the concealment to fail open and re-exposing the hidden WordPress login page location. The flaw is network-reachable, low complexity, and requires no authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3), but its impact is deliberately narrow: it only reverts the site to its ordinary, unhidden login posture and does not bypass WordPress authentication, so real-world risk depends on the strength of the underlying credentials and any additional login protections in place. Publicly available exploit code exists and the issue is tracked by WPScan as well as ENISA EUVD-2026-82686; a vendor fix is available in version 7.0.11, and there is no indication of confirmed active exploitation (no CISA KEV listing) and no EPSS score was provided in the source data.
Unauthenticated attackers can strip the hardening protections from the Hide My WP Ghost WordPress plugin (versions before 7.0.11) by supplying a single WooCommerce-looking request parameter, which the plugin accepts as proof of a legitimate WooCommerce request and uses to switch off its firewall, threat detection and login/URL-hiding logic - re-exposing the concealed login and admin URLs on any request. The issue affects default installations where the plugin's protection features are enabled (its core purpose), requires no authentication, user interaction or non-default configuration (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3), and publicly available exploit code exists, with no confirmed active exploitation reported. The impact is indirect - WordPress core authentication is not bypassed - but any site treating this plugin as a meaningful obscurity control effectively loses that protection until it is upgraded to 7.0.11 or later.
Unauthenticated remote attackers can inflate a plugin option in the Really Simple Security WordPress plugin (versions 8.1.6 up to but not including 9.8.3) by supplying arbitrary address values that the plugin uses as storage keys without validation, causing unbounded option growth and slower handling of missing pages. The impact is availability-only degradation (CVSS 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) with no confidentiality or integrity effect, and default configurations are reachable by network unauthenticated exploitation as long as the site is online. Publicly available exploit code exists and WPScan published the finding, but there is no indication of confirmed active exploitation (CISA KEV); sites running 9.8.3 or later are unaffected.
Unauthenticated attackers can overwrite arbitrary appointment records in the Easy Appointments WordPress plugin (versions 4.0 through 4.0.2.2) by sending a request-supplied appointment id to the plugin's public appointment-reservation endpoint, which performs no ownership or authorization check before updating the record. The same missing check lets a follow-on cleanup routine delete the targeted appointments, so booking data on affected sites can be corrupted or removed. Publicly available exploit code exists, but there is no indication of confirmed active exploitation (the CVE is not in CISA KEV), and the impact is bounded - integrity and some availability of appointment records only, with no confidentiality loss and no code execution, which is why the risk is real but moderate rather than critical.
Unauthenticated attackers can add arbitrary products to a WooCommerce cart and check out at the discounted price tied to a Frequently Bought Together campaign in the UpsellWP WordPress plugin (versions 1.4.4 through before 2.2.10), because the plugin never verifies that cart items actually belong to the campaign being applied. The flaw is a business-logic validation gap rather than a data-exposure or availability issue: the manipulation is limited to an integrity impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, base 5.3), with real-world loss scaling to the size of the configured discount and the value of the goods sold. Publicly available exploit code exists, but there is no indication of confirmed active exploitation; the vendor has released a fix, so upgrading to 2.2.10 removes the issue.