Local privilege escalation in the NVIDIA GPU Display Driver kernel-mode layer lets an attacker who already holds low-privileged code execution on a Windows or Linux host - including code running inside a vGPU guest VM - drive the driver into an error path that mishandles reference counts, producing a use-after-free. The corrupted object is kernel memory, so successful exploitation can yield code execution, escalation of privileges, denial of service, information disclosure, and data tampering (CVSS 7.8, AV:L/AC:L/PR:L/UI:N); it is not remotely reachable and requires a vulnerable driver version to be installed. The GeForce, RTX/Quadro/NVS, and Tesla driver families are in scope, and no public exploit code has been identified at the time of analysis.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux lets an already-authenticated, low-privileged user trigger a format string defect (CWE-134) and potentially achieve code execution, privilege escalation, data tampering, denial of service, and information disclosure; NVIDIA rates it 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack surface is strictly local - there is no remote vector - so real risk concentrates on multi-user and multi-tenant GPU systems such as HPC clusters, ML/AI training nodes, shared engineering workstations, and cloud GPU instances, where a low-privileged tenant could reach the driver while other users' data and the host remain in scope. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; the impact rating of total confidentiality, integrity, and availability loss is consistent with memory corruption inside a privileged driver context.
Local privilege escalation and kernel memory-safety compromise on Linux systems running NVIDIA GPU Display Drivers allow an unprivileged local user to cause improper release of kernel-mode memory resources, leaving a mapping accessible after the underlying memory has been reused. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla driver lines and carries a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning an attacker who already holds a local login can potentially achieve code execution, denial of service, information disclosure, privilege escalation, and data tampering without user interaction. No public exploit has been identified at time of analysis and the issue is not confirmed as actively exploited, but the local-only vector makes it most dangerous on shared or multi-tenant GPU hosts where one unprivileged tenant could compromise the kernel and other workloads.
Local privilege escalation and memory-protection bypass in NVIDIA GPU Display Driver for Linux allows an unprivileged local user to execute code at higher privilege, tamper with data, disclose information, or cause denial of service. The flaw is in the kernel-mode layer and affects GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest Driver/Virtual GPU Manager deployments, with a CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N). No public exploit identified at time of analysis, and no CISA KEV active-exploitation signal is present; the assessed attack path requires prior local access on the host or inside a vGPU guest.
Arbitrary code execution on OpenClaw Windows Node hosts before version 2026.7.1 is achievable by an attacker who already holds gateway or agent access to a node, because the system.run tool's environment-variable sanitizer maintains an incomplete denylist (CWE-184). The attacker supplies variables such as GIT_CONFIG_*, GIT_PAGER, DOTNET_STARTUP_HOOKS, or JAVA_TOOL_OPTIONS alongside a request that runs an allowlisted tool (git, dotnet, java), causing that otherwise-permitted tool to load and execute attacker-controlled code or commands when it is next invoked; this requires the attacker to pass the tool's own arguments unchanged, which is why the attack-complexity/attack-requirements component is elevated. Exploitation is not remote-unauthenticated-it presumes prior gateway or agent access (PR:L), it is Windows-only, and it depends on at least one of git, dotnet, or java being present and reachable through system.run. No public exploit code or confirmed active exploitation was identified at time of analysis; the vendor has released a fixed build.
An out-of-bounds read in the NVIDIA Display Driver for Windows kernel module allows local attackers to cause denial of service and disclose sensitive kernel memory. Affected products include GeForce, RTX/Quadro/NVS, and Tesla driver lines on Windows; exploitation requires local access with no elevated privileges or user interaction. No public exploit code has been identified, and the vulnerability is not remotely exploitable.
Certificate hostname verification is silently skipped in CPython's TLS stack when an application enables SSLContext.check_hostname but supplies no server_hostname (None or an empty string) to SSLContext.wrap_bio(), asyncio.create_connection(), or asyncio.loop.start_tls(). In that exact state SSLObject still validates the certificate chain but never matches the peer's identity against the requested name, so an unauthenticated attacker holding a man-in-the-middle position on the connection path and a certificate chaining to a CA the client trusts can intercept traffic while the program believes hostname checking succeeded. Exploitation is gated by two independent conditions - the application-side misconfiguration and an active network-intercept position - no public exploit code has been identified at time of analysis, and applications that pass a valid non-empty server_hostname are completely unaffected regardless of patch status.
Out-of-bounds write in PCRE2, the regular-expression library embedded in PHP, nginx, Apache httpd, Git and numerous language runtimes, allows memory corruption when a consuming application compiles an attacker-controlled pattern through the JIT compilation API in the manner described by the vendor advisory. Only releases before 10.49 are affected, and exploitation is gated on two conditions holding at once: the application must accept untrusted, user-supplied regexes and must route them through PCRE2's JIT path, so default library presence alone does not imply exploitability. The assessed vector is network-reachable with high attack complexity and no privileges required (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L, base 7.6); no public exploit code and no CISA KEV entry were identified at time of analysis. A vendor patch is available per the advisory, so upgrading to a fixed release remediates.
Blind SQL injection in WPTasty Business Directory plugin versions through 6.4.27 allows an authenticated attacker with high privileges to infer database contents without direct query output, using boolean- or time-based inference. The CVSS vector indicates network exploitability, no user interaction, and high confidentiality impact, but the PR:H requirement means the attacker must already hold a privileged WordPress account, so this is a plausible but not urgent priority. No public exploit has been identified at time of analysis, and KEV status is not indicated.
SQL injection in the Category Discount WooCommerce WordPress plugin (slug woo-product-category-discount, CVE-2026-96828) affects all versions up to and including 5.18 and allows an authenticated WordPress Administrator to inject arbitrary SQL through the plugin's admin-side functionality, yielding high-impact confidentiality exposure (CVSS 7.6, C:H/I:N/A:L, S:C). The PR:H prerequisite is the dominant limiting factor: only the highest-privilege role can reach the vulnerable code, so this is realistically a post-account-compromise or insider-abuse vector rather than an opportunistic unauthenticated attack. No public exploit code has been identified at time of analysis, the issue is not listed in CISA KEV, and no EPSS score was supplied; Patchstack is credited with reporting the flaw.
SQL injection in the Melapress Admin Notices Manager WordPress plugin (versions up to and including 1.6.0) allows an authenticated WordPress Administrator to inject arbitrary SQL into a plugin-handled parameter, giving the attacker read access to data outside the plugin's own tables. The assessed vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L scores 7.6, but the PR:H requirement means exploitation presupposes top-tier site access; the practical threat model is multi-admin sites, delegated or agency-managed installs, or an attacker who has already escalated a lower-privilege foothold to administrator. No public exploit code has been identified and the issue is not listed in CISA KEV; no EPSS score was supplied with the available intelligence, so no exploit-probability estimate is asserted here.
Authenticated SQL injection in the weDevs WP ERP plugin for WordPress, affecting all releases up to and including 1.17.9, allows an attacker with Author-level or higher WordPress privileges to inject arbitrary SQL and read data from the site's database. The vulnerability is network-reachable and requires no user interaction, and because the CVSS scope is marked as changed (S:C) with high confidentiality impact (C:H), a successful injection can reach data beyond the plugin's own tables, including other plugins' and core WordPress content. Exploitation is privilege-gated by the PR:H rating, so exposure concentrates on multi-author, membership or community sites where Author accounts are handed to third parties; there is no public exploit identified at time of analysis and no confirmed vendor patch version in the available intelligence, making this a genuine but privilege-gated risk.
SQL injection in the Estatik WordPress plugin (versions <= 4.3.5) allows an authenticated attacker with administrator privileges to read sensitive data from the WordPress database. The vulnerability is a CWE-89 SQL injection in an admin-side function, requiring high privileges (PR:H) but no user interaction. No public exploit code has been identified at the time of analysis, and the primary risk is in environments where administrator access is delegated or on multisite installations where raw database access is not otherwise available.
Authenticated SQL injection in the Quiz Cat WordPress plugin (versions 3.1.1 and earlier) allows an attacker holding at least the WordPress Author role to send crafted requests that are woven into backend SQL statements, giving read access to sensitive database contents such as user records and stored quiz data, with secondary potential to alter or disrupt data. Exploitation is remote and requires no user interaction, but it is gated behind the Author privilege, so the realistic exposure surface is multi-author, membership, and user-generated-content sites that hand Author accounts to untrusted or numerous users; anonymous visitors and Subscriber- or Contributor-only accounts cannot trigger it. No public exploit code has been identified at time of analysis. The reported CVSS is 7.6 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L), while our independent assessment is slightly more conservative at AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L - both agree the dominant impact is confidentiality loss.
SQL injection in WP Activity Log 5.6.6 and earlier allows an authenticated WordPress administrator to inject SQL through an admin-accessible plugin function, potentially reading sensitive database contents and causing limited integrity or availability impact. The vulnerability requires a high-privileged admin account per the PR:H vector, so it is not exploitable by unauthenticated visitors or lower-privileged users; no public exploit code was identified at time of analysis. The supplied base CVSS is 7.6, and the independent assessment uses CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L, while the provided NVD-style vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L.
Denial of service in Apache WSS4J (2.x before 2.4.4, 3.x before 3.0.6, and 4.x before 4.0.2) allows unauthenticated remote attackers to force excessive CPU and memory consumption by sending crafted WS-Security messages whose derived-key Length and Offset values are not validated by the library. The issue is a CWE-20 improper input validation flaw rated by the vendor at CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so the rated impact is availability only, although the same unchecked bounds could in principle yield cryptographically weak derived keys. Vendor patches are available in 4.0.2, 3.0.6, and 2.4.4; CISA SSVC lists Exploitation: none with Automatable: yes, and no public exploit identified at time of analysis.
Unauthenticated file write in Kiteworks Email Protection Gateway lets any attacker who can reach the appliance's administrative upload endpoint push files containing attacker-controlled content onto the underlying filesystem, because that handler performs no authentication or authorization check (CWE-306, CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N). The directly reachable impact is integrity-only - no standalone code execution is achievable, since achieving RCE would require chaining a separate vulnerability to relocate the written file into an executable location. No public exploit code exists and no confirmed active exploitation was identified at time of analysis, so risk is genuine but bounded, concentrated on deployments that expose the management/upload interface to untrusted networks rather than those that firewall it to a management VLAN.
Unauthenticated server-side request forgery (SSRF) in Kiteworks Secure Data Forms before 9.5.0 allows remote attackers to force the server to issue arbitrary outbound network requests and read back the responses, exposing internal-only services, cloud metadata endpoints, and other network-restricted resources. Exploitation requires no authentication (PR:N) and no user interaction (UI:N); our independent assessment rates it CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, reflecting the high confidentiality impact of reading internal responses rather than the vendor's C:N/I:H weighting. No public exploit code or confirmed active exploitation was identified at time of analysis.
XML Signature Wrapping protections in Apache WSS4J's streaming (StAX) code path can be bypassed, allowing a remote unauthenticated attacker to deliver a SOAP message whose Body is unsigned yet still satisfies a WS-SecurityPolicy requiring the Body to be signed. The root cause is that a signature reference using the WS-Security STR-Transform permanently sets an internal 'inside signed content' flag, which causes the WS-SecurityPolicy enforcer to stop evaluating SignedParts and SignedElements for the remainder of the message; signature verification itself is not broken, and the DOM-based code is unaffected. Only deployments on the streaming path that enforce such a policy are exposed: affected versions are below 2.4.4, 3.0.0 through 3.0.5, and 4.0.0 through 4.0.1, and no public exploit code or confirmed active exploitation was identified at time of analysis. Vendor-released patches are available as 4.0.2, 3.0.6, and 2.4.4.
Improper authentication in Kiteworks Email Protection Gateway allows a remote, unauthenticated sender to make the gateway act against the Kiteworks platform as an identity it never verified, and to provision a new platform account for an identity the gateway does not already know - ultimately yielding control of a single platform account. Exploitation requires only network reachability to the gateway's message-processing path plus an inbound message asserting an identity; no credentials, privileges, or user interaction are involved (CVSS:3.1/AV:N/AC:L/PR:N/UI:N). No public exploit identified at time of analysis, and there is no evidence of active exploitation or public tooling; the vendor's CVSS 3.1 score is 7.5 with integrity-only impact, while independent assessment raises the confidentiality component to High (C:H/I:H/A:N) because account takeover implies read access to that account's data, though the realistic blast radius remains a single platform account rather than the underlying appliance.
Directory traversal in agent-zero 1.7 through 1.10 allows remote attackers to write files to arbitrary locations outside the intended file-browser directory via the save_file_b64 method, with the evaluated CVSS vector indicating PR:N/UI:N and high integrity impact according to the authoritative assessment. No CISA KEV listing was provided, and no public exploit identified at time of analysis; EPSS is 0.33% (24th percentile), and the supplied CVSS 3.1 score is 7.5, though the independent assessment shifts the impact from confidentiality to integrity (C:N/I:H/A:N) because exploitation concerns unauthorized file writes rather than reads.
Directory traversal in Bisheng 2.3.0, 2.4.0, and 2.4.0-beta1 allows unauthenticated remote attackers to read arbitrary files from the server filesystem through the Linsight task-execution endpoint implemented in src/backend/bisheng/linsight/domain/task_exec.py. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates no authentication or user interaction is required against default configurations, with impact bounded to confidentiality - disclosure only, no code execution or file modification. Publicly available exploit code exists (SSVC exploitation status 'poc'; a public gist accompanies the report), but the vulnerability is not confirmed actively exploited (no CISA KEV entry), and EPSS is low at 0.33% (24th percentile), so priority should be driven by whether an organization actually exposes a Bisheng instance to untrusted networks.
Directory traversal in Agent Zero 1.7 through 1.10 lets the AI agent's file-browser component read files anywhere on the host, because FileBrowser is initialized with the host root as its workspace rather than a confined sandbox. The CVSS 3.1 vector is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), which models unauthenticated network access, but the practical risk is gated by whether the Agent Zero UI is exposed to untrusted networks; Agent Zero is often a local single-operator tool, so the AV:N/PR:N rating only applies when that interface is deliberately reachable without an authentication layer. At time of analysis there is no confirmed active exploitation (no CISA KEV entry) and no public exploit identified at time of analysis, and EPSS is 0.33% (24th percentile), indicating low predicted exploitation activity; reference material consists of a GitHub issue and a gist.
Remote, unauthenticated denial of service in Pexip Infinity (all releases before 38.2, plus 39.0, 39.1, and 40.0) lets an attacker who can reach a node's media service send crafted input that triggers a software abort and crashes the affected process. The vulnerability carries a CVSS 3.1 base score of 7.5 (High), driven entirely by availability impact (A:H) with no confidentiality or integrity loss, and requires only network reachability to the media-plane service - no credentials, no user interaction, and no non-default configuration. There is no CISA KEV listing and no public exploit code identified at time of analysis, so the practical risk is concentrated in internet-facing or broadly reachable Conferencing Nodes, while nodes segmented behind firewalls or restricted to trusted media peers face reduced exposure.
Unauthenticated remote attackers can abort the media process in Pexip Infinity, causing a denial of service on conferencing nodes that are reachable from an untrusted network. The root cause is improper input validation in the media implementation (CWE-617, a reachable assertion/software abort): crafted media input drives the software into an unrecoverable abort rather than failing gracefully. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) confirms this is availability-only - no confidentiality or integrity impact and no code execution - and affected releases are Pexip Infinity before 38.2, plus 39.0, 39.1 and 40.0. No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical exposure driver is whether media-processing interfaces are directly reachable, since deployments that restrict media to trusted networks or front it with session border controls materially reduce reachability.
Malformed media-plane input to Pexip Infinity before 41.1 can trigger an assertion failure and abort the media process, causing a denial of service. The flaw is remotely reachable without authentication or user interaction (CVSS 3.1 AV:N/AC:L/PR:N/UI:N, availability-only impact), though practical exposure depends on whether the media services are reachable from untrusted networks. No public exploit code or confirmed active exploitation was identified at the time of analysis.
Unauthenticated denial of service in Apache WSS4J lets remote attackers exhaust server memory by sending SOAP messages that carry a specially crafted X.509 certificate: the certificate's SubjectKeyIdentifier extension declares a length of 0x7FFFFFFF, and an integer overflow in WSS4J's DER bounds check allows the oversized allocation to pass validation, so an eleven-byte extension can trigger an approximately 2 GB allocation. Because the certificate is decoded while resolving the signature's key reference - before the message is authenticated - no credentials are required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), and repeated requests can drive an exposed WS-Security endpoint to OutOfMemory conditions. Affected releases are WSS4J 4.0.0 through 4.0.1, 3.0.0 through 3.0.5, and all versions before 2.4.4; impact is limited to availability, with no code execution or data disclosure path identified. No public exploit code, EPSS score, or CISA KEV entry is present in the provided data, so risk is driven by Apache's "important" severity rating and the pre-authentication nature of the flaw rather than confirmed active exploitation.
Incorrect authorization in JetBrains YouTrack before version 2026.2.19197 allows guest users to strip a workflow action's visibility restriction and then execute that action, altering workflow behavior on the instance. The flaw is network-reachable and rated CVSS 7.5 with a PR:N vector, though practical exposure depends on guest access being enabled on the target instance - a configuration in which the guest context supplies the effective precondition; disabling guest access removes the attack surface entirely. Impact is limited to integrity of workflow actions (no confidentiality or availability effect), there is no public exploit identified at time of analysis, EPSS is low (0.29%, roughly 19th percentile), CISA SSVC records exploitation status as none, and the vendor has released a patch in 2026.2.19197.
Denial of service in Pexip Infinity 30.0 through 40.x allows unauthenticated remote attackers to render a node inaccessible by sending input that the web server fails to validate properly (CWE-770). The flaw is network-reachable and low-complexity with no authentication (PR:N) or user interaction (UI:N) required, and its sole impact is availability - there is no confidentiality or integrity loss - with CVSS 3.1 scored 8.6. No public exploit code and no confirmed active exploitation were identified at time of analysis; risk is concentrated in deployments whose management or conferencing web interface is exposed to untrusted networks.
Unauthenticated remote attackers can cause a denial of service against Pexip Infinity conferencing deployments by sending malformed signaling messages that trigger a software abort. The vulnerability, tracked as CVE-2026-103100, affects all versions before 40.1 and stems from improper input validation (CWE-617). No public exploit identified at time of analysis, but the flaw is remotely reachable with low complexity and high availability impact, making prompt patching critical for internet-exposed signaling interfaces.
Command injection in Kiteworks Core lets an authenticated administrator with elevated privileges run arbitrary operating-system commands as root on the affected appliance node, so an admin-only function can be turned into full host compromise. The flaw is remotely reachable and needs no user interaction (CVSS:3.1/AV:N/AC:L/PR:H/UI:N, base score 7.2), but PR:H is the dominant limiting factor: no unauthenticated or low-privilege path is indicated, so practical exploitation presupposes an insider or stolen high-privilege administrative credentials. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV, keeping real-world urgency moderate and dependent on the value of the credentials required.
OS command injection in Kiteworks Core appliances running versions before 9.5.0 allows an authenticated administrator to upload a configuration package whose contents are not sufficiently validated, resulting in arbitrary operating-system command execution that may run with elevated privileges on the underlying appliance. The attack requires a valid administrator account with access to the configuration-package upload functionality in the administrative interface (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2 High), so the high-privilege prerequisite is the dominant constraint and the realistic scenario is a malicious, compromised, or coerced administrator rather than opportunistic unauthenticated remote exploitation; the assessed vector is internally consistent and concurred with. No public exploit code and no confirmed active exploitation were identified at time of analysis, and successful exploitation yields full compromise of confidentiality, integrity, and availability on the affected appliance.
An out-of-bounds read in Eclipse ThreadX NetX Duo's MQTT-over-WebSocket transport (the setter path) lets a malicious or compromised broker - or a man-in-the-middle on the WebSocket connection - crash the embedded network stack and potentially disclose a limited amount of adjacent memory. Affected builds are NetX Duo 6.4.4 through 6.5.1.202602, and only firmware that actually compiles in and uses the MQTT client over WebSocket is exposed; devices running plain MQTT/TCP or no MQTT are unaffected. Exploitation is not confirmed as active (not in CISA KEV) and no public exploit code has been identified at time of analysis, but CISA SSVC rates the issue Automatable with partial technical impact, so the practical risk is a conditional availability problem rather than an emergency, with a confidentiality impact the vendor's original CVSS score omits but which the independent assessment reflects as C:L/A:H.
Authenticated path traversal in the WordPress Creator LMS plugin (WPFunnels) affects all versions up to and including 1.2.19 and allows a user holding only Contributor-level privileges to manipulate file paths and reach files outside the intended directory, primarily exposing sensitive data with limited integrity and availability effects. Exploitation requires a valid low-privilege account - self-registration must be enabled or an account otherwise obtained - and is rated high complexity (AC:H), meaning success depends on specific, not-guaranteed conditions; the issue is remote, needs no user interaction, and no public exploit has been identified at time of analysis. It is not confirmed actively exploited (no CISA KEV listing), and while the vendor-supplied CVSS of 7.5 and the scorer's high confidentiality/integrity/availability ratings read alarming, the practical risk is moderate because the attack is gated behind an authenticated Contributor role and elevated complexity.
Unauthenticated sensitive data exposure in the WordPress plugin BackupEase through version 2.2.2 lets any remote, network-reachable visitor retrieve information the plugin was never intended to expose, with confidentiality impact rated High and no integrity or availability effect (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N). Because the vector carries PR:N and UI:N, no account, credential, or victim interaction is required - the only prerequisite is that the plugin be installed at an affected version and its vulnerable endpoint reachable over HTTP(S). There is no public exploit identified at time of analysis, the issue is not confirmed actively exploited (no CISA KEV listing), and no EPSS score was provided in the available intelligence; Patchstack is credited as the reporting source.
Unauthenticated sensitive data exposure in the WordPress plugin StifLi Backup Tools affects all versions up to and including 2.2.7, allowing any remote attacker who can reach an affected site to retrieve information the plugin was never intended to expose without logging in first (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Impact is confidentiality-only - no data modification or denial of service - so the practical damage is the leak of backup-related information that could feed follow-on attacks such as credential theft or targeted exploitation. At the time of analysis there is no public exploit code identified and no confirmation of active exploitation (the CVE is not in CISA KEV), though the low attack complexity and zero authentication requirement make the flaw trivially reachable for anyone who knows or discovers the exposed endpoint; no EPSS score was supplied, and the risk is moderated mainly by the plugin's niche deployment footprint rather than by any technical barrier.
Unauthenticated access control failure in the WebToffee WordPress Backup & Migration plugin (slug wp-migration-duplicator) through version 1.6.0 allows remote attackers to read protected resources without credentials or user interaction; the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (base 7.5) reflects a high confidentiality impact with no integrity or availability effect. Any WordPress site with this plugin installed and active at or below 1.6.0 is exposed, while sites that have upgraded past 1.6.0 or that do not run the plugin are unaffected. No public exploit code has been identified at time of analysis, and this CVE is not listed in CISA KEV.
Remote unauthenticated attackers can delete arbitrary content, including customer reviews, on WordPress/WooCommerce sites that have the Customer Reviews for WooCommerce plugin installed and active at version 5.120.0 or earlier. The flaw is a missing authorization check (CWE-862) on a network-accessible endpoint, requiring no authentication or user interaction (CVSS 3.1 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). No public exploit code or confirmed active exploitation has been identified at time of analysis, and the risk is a genuine but bounded priority because impact is confined to availability/data loss rather than site compromise.
Unauthenticated attackers can modify arbitrary data or trigger protected operations in WordPress sites using the WP Express Checkout (Accept PayPal Payments) plugin versions up to and including 2.4.9, because the plugin fails to enforce authorization controls (CWE-862). The flaw is remotely exploitable without user interaction or credentials, with a CVSS 3.1 base score of 7.5 reflecting high integrity impact but no confidentiality or availability loss. No public exploit code or active exploitation has been identified at time of analysis, but a Patchstack advisory exists and administrators should treat the issue as high priority given the unauthenticated attack vector.
Unauthenticated remote attackers can modify or create data in WordPress sites running the Bookly appointment booking plugin versions up to and including 28.2 due to missing authorization checks (CWE-862). The vulnerability has a CVSS score of 7.5 with a vector indicating network exploitable, low complexity, no privileges required, and no user interaction, resulting in high integrity impact but no confidentiality or availability impact. No public exploit code has been identified at the time of analysis, and the issue is assessed as priority-worthy on exploitability but with a bounded impact profile.
Unauthenticated Broken Access Control in the Hostinger Migrator WordPress plugin (version 1.0 and earlier) lets any remote attacker reach a plugin endpoint that performs no authorization check, exposing migration and backup artifacts such as database dumps, file archives and site configuration data. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, score 7.5) the impact is a high-confidentiality breach with no integrity or availability effect, exploitable against default installations with no credentials, user interaction or special configuration. No public exploit identified at time of analysis, and no EPSS score or CISA KEV entry was supplied; the practical risk is bounded by the plugin's niche adoption and the fact that migration plugins are often left active only briefly during a site move, so sites that have deactivated or removed the plugin since migrating are not exposed.
Privilege escalation in the WordPress plugin Import and Export Users and Customers (Javier Carazo) at versions up to and including 2.5.2 lets an authenticated low-privileged account - specifically a Subscriber - reach higher-privileged roles, giving full compromise of the site's confidentiality, integrity, and availability (CVSS 3.1 base 7.5, High). The advisory-supplied vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H means the attack is network-reachable and needs no victim interaction, but the High Attack Complexity rating reflects a non-trivial precondition (a specific plugin state, ordering, or crafted import payload) that limits how reliably it can be pulled off; it does require the attacker to already hold a Subscriber account, which is trivial on sites with open registration enabled. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so exploitation is currently assessed as a targeted-risk rather than a mass-scanning risk; no EPSS probability was supplied with this record.
Unauthenticated arbitrary file download in the NextGEN Gallery WordPress plugin affects every site running version 4.5.0 or earlier, allowing a remote attacker with no credentials required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N, base score 7.5) to retrieve files that are readable by the web server process. Rooted in a path-traversal weakness (CWE-22) in the plugin's file download handling, the impact is confined to confidentiality - typical targets are wp-config.php, database credentials, environment files, and backup archives - with no file write or code execution. No public exploit code and no CISA KEV entry are associated with this CVE at time of analysis, though the reachable default-configuration attack path makes it a genuine priority rather than a paper-tiger high-CVSS issue.
GravityExport Lite for Gravity Forms versions up to and including 2.7.2 contains a broken access control vulnerability (CWE-862) that allows unauthenticated remote attackers to bypass authorization and access sensitive export data, resulting in high confidentiality impact. The CVSS 3.1 base score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating a low-complexity, network-exploitable flaw with no integrity or availability impact. Exploitation requires the plugin to be installed on a site with Gravity Forms, but no authentication or user interaction is needed; no public exploit code is currently identified.
Unauthenticated arbitrary file read in the Product Designer App plugin for WordPress (all versions up to and including 1.1.3) lets any remote visitor retrieve the contents of files on the web server through the plugin's 'svg' parameter. The only access control on the vulnerable AJAX endpoint is a nonce and token that the plugin prints as JavaScript globals on any page rendering the [pdapp-studio-page] shortcode, so an anonymous attacker who loads such a page can lift those values and pass them along with a crafted traversal path. Per the supplied assessment the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (7.5 High) reflects a fully remote, unauthenticated, low-complexity, no-interaction confidentiality-only flaw; no CISA KEV entry and no public exploit code were identified in the provided data, and no EPSS score was supplied, so exploitation status is assessed as unproven but technically trivial once a shortcode-bearing page exists.
Unauthenticated time-based blind SQL injection in the Motors - Car Dealership & Classified Listings plugin for WordPress (all versions up to and including 1.4.109) lets remote attackers inject SQL through the 'stm_lat' and 'stm_lng' parameters and infer sensitive database contents one timed request at a time. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no account, privileges, or user interaction are needed - only that the plugin is installed and the geo-location endpoint that consumes these latitude/longitude parameters is reachable, which is the case in default configurations. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); exploitation is viable but inherently slow and noisy, since each extracted bit requires a distinct delayed response, so the practical risk is slow, stealthy exfiltration of database contents (hashes, user data, listing records) rather than rapid mass compromise.
Local file inclusion in the Simply Schedule Appointments WordPress plugin (all versions up to and including 1.6.12.27) allows remote attackers to include and execute arbitrary .php files present on the server via the 'ssa_locale' GET parameter, enabling access-control bypass, disclosure of sensitive data, and PHP code execution whenever attacker-controlled .php content can be placed on the host. The published CVSS 3.1 base score is 7.5 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), but our independent assessment rates the vector as PR:N (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), because the locale filter in class-translation.php is registered unconditionally during plugins_loaded and its callback returns the raw 'ssa_locale' parameter without any nonce or capability check, so the subscriber-level authentication requirement in the published vector is not a genuine barrier in practice. High attack complexity reflects the fact that including an already-present .php file yields information disclosure or access-control bypass, while executing attacker-supplied PHP additionally requires an upload feature or writable path that can host a .php file; no public exploit code has been identified at time of analysis, and there is no CISA KEV entry indicating confirmed active exploitation.
Stored cross-site scripting in the Robin Image Optimizer WordPress plugin (versions 2.0.0 up to but not including 2.0.8) lets unauthenticated users submit content that is persisted and later rendered as script in the browser of anyone viewing the affected page, including administrators. The flaw is conditional: the bundled HTML parser only re-emits unescaped values into element attributes when the plugin's non-default image delivery mode is enabled, so installations running the default mode are not exposed. Vendor-released patch: 2.0.8; no public exploit identified at time of analysis, and CISA's SSVC assessment records exploitation as none and the issue as not automatable, making this a real but situational stored-XSS risk rather than an emergency.
Directory traversal in Handlebars.java before 4.5.5 lets unauthenticated remote attackers read arbitrary files outside the configured template base directory in Spring MVC applications that use the handlebars-springmvc integration. The flaw specifically affects handlebars-springmvc 4.5.3 and 4.5.4, where the path-containment check added for CVE-2026-63490 validates template locations as raw percent-encoded strings while the template file is ultimately opened through a URL handler that percent-decodes the path, so a request-derived view name containing %2e%2e/ slips past both the view-resolver and loader-side checks. Exploitation is not confirmed in the wild and no public exploit code has been identified at time of analysis, but it requires two non-default conditions to hold simultaneously: a file: template location prefix and a Handlebars view name derived from untrusted request input, which keeps real-world priority moderate despite the 7.5 CVSS score. Impact is limited to confidentiality (arbitrary file read); integrity and availability are unaffected.
Unauthenticated path traversal in the Kiteworks Core appliance setup interface allows an attacker who can reach that interface to write a file to any location writable by the appliance service account, enabling integrity compromise of the appliance or a denial-of-service condition that persists until an operator intervenes. The exposure is narrow: the setup interface is not reachable on a fully configured appliance in its default configuration, so exploitation is realistically limited to the transient provisioning window of a new appliance or a non-default configuration that leaves setup exposed, which is why AC:H applies despite PR:N and UI:N (CVSS 7.4). No public exploit code and no confirmed active exploitation were identified at time of analysis, and the flaw does not by itself provide code execution.