PHP Object Injection in the Agricola WordPress theme (versions ≤ 1.21.0 by AxiomThemes) lets unauthenticated remote attackers inject crafted serialized PHP objects that are deserialized by the application, and with a suitable POP gadget chain this can escalate to arbitrary file operations, SQL manipulation, or remote code execution. Rated CVSS 9.8 and disclosed by Patchstack (EUVD-2026-53878), it requires no authentication or user interaction. No public exploit identified at time of analysis and it is not listed in CISA KEV.
PHP Object Injection in the Agora WordPress theme (by AncoraThemes) affects all versions up to and including 1.9, allowing remote unauthenticated attackers to inject serialized PHP objects that are deserialized by the application. Because exploitation requires no authentication and no user interaction over the network, a successful attack can lead to full compromise (arbitrary code execution, data theft, or site takeover) when a suitable gadget chain is present in the theme or its plugin ecosystem. Reported by Patchstack (EUVD-2026-53996); no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
PHP Object Injection in the AncoraThemes 'Advice' WordPress theme (versions up to and including 1.18.0) lets unauthenticated remote attackers pass attacker-controlled serialized data into an unsafe PHP deserialization sink (CWE-502). Because a suitable POP (property-oriented programming) gadget chain in the theme or a co-installed plugin can then be triggered, this can escalate to arbitrary file operations, data disclosure, or remote code execution. Rated CVSS 9.8; reported by Patchstack, with no public exploit identified at time of analysis.
Unauthenticated PHP Object Injection in the Adrena WordPress theme (AncoraThemes) affects all versions up to and including 1.2.14, allowing remote attackers with no authentication to inject crafted serialized PHP objects that are deserialized by the theme. Exploitation can lead to full compromise (confidentiality, integrity and availability all High) when a suitable gadget chain is present in the WordPress core, an active plugin, or another theme. This flaw carries a CVSS 9.8 rating and was disclosed by Patchstack; no public exploit code has been identified and it is not listed in CISA KEV, so there is no public exploit identified at time of analysis.
Unauthenticated PHP Object Injection in the Accalia WordPress theme (by AncoraThemes) affects all versions up to and including 1.5.3, allowing remote attackers to inject crafted serialized PHP objects that are deserialized by the application. When a suitable POP (property-oriented programming) gadget chain is present in the theme, its plugins, or WordPress core, this can lead to remote code execution, data disclosure, or site takeover. The issue was reported by Patchstack and carries a CVSS 9.8; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Unauthenticated PHP Object Injection in the Abogado WordPress theme (by AncoraThemes) affects all versions up to and including 1.18, allowing remote attackers to inject crafted serialized PHP objects without authentication. If a suitable POP (property-oriented programming) gadget chain is present in the theme, its bundled plugins, or WordPress core, this can escalate to arbitrary file operations, SQL injection, or remote code execution. Reported by Patchstack; no public exploit identified at time of analysis and the flaw is not listed in CISA KEV.
Insecure deserialization in the Abelle WordPress theme (ThemeREX) versions 1.22 and earlier lets unauthenticated remote attackers inject crafted PHP objects that the application deserializes, enabling PHP Object Injection. Because attacker-supplied serialized data reaches unsafe unserialize() logic without authentication, an adversary can potentially achieve remote code execution, data tampering, or full site compromise depending on available gadget chains in WordPress core, the theme, or co-installed plugins. There is no public exploit identified at time of analysis, but the flaw carries a CVSS 9.8 rating reflecting network-reachable, unauthenticated, high-impact exploitation.
PHP Object Injection in the A.Williams (Alisha Williams) WordPress theme by AxiomThemes affects all versions up to and including 1.3.1, allowing remote unauthenticated attackers to inject crafted serialized PHP objects into an unsafe deserialization sink. When a suitable POP gadget chain is present in the theme or co-installed plugins, this can escalate to arbitrary file operations, SQL injection, or remote code execution. No public exploit identified at time of analysis, and the vulnerability is not listed in CISA KEV; the 9.8 CVSS reflects theoretical worst-case impact rather than confirmed active exploitation.
Unauthenticated PHP Object Injection in the 69 Clothing WordPress theme (versions up to and including 1.2.11.1) lets remote attackers submit crafted serialized data that is unsafely deserialized, potentially triggering property-oriented programming (POP) gadget chains for code execution, data theft, or file manipulation. Reported by Patchstack and tracked as EUVD-2026-53989, it carries a critical CVSS 9.8 with no authentication required. There is no public exploit identified at time of analysis, but the network-reachable, unauthenticated nature makes it a high-priority patching target for any WordPress site running this theme.
PHP Object Injection in the WPBruiser {no- Captcha anti-Spam} WordPress plugin (versions ≤ 3.1.43) allows remote unauthenticated attackers to inject crafted serialized objects that are deserialized by the plugin, enabling arbitrary object instantiation and, when combined with a suitable POP gadget chain, code execution or data compromise. The flaw carries a CVSS 9.8 (AV:N/AC:L/PR:N/UI:N) and is reported by Patchstack (EUVD-2026-53983). No public exploit code was identified at time of analysis and it is not listed in CISA KEV, so there is no confirmed active exploitation.
Privilege escalation in WSO2 API Manager and related Carbon-based products allows a low-privileged user, using a validly issued token, to invoke product-level Admin REST APIs that should be restricted, potentially resulting in full administrative account takeover. The flaw stems from insufficient scope/privilege restriction on issued tokens (CWE-269) and affects API Manager, API Control Plane, Universal Gateway, Traffic Manager, and the Carbon REST API common/utility components. No public exploit identified at time of analysis; exploitation requires the attacker to already hold a low-privileged account and obtain a token for it.
Privilege escalation in the Frontend Admin by DynamiApps WordPress plugin (versions up to and including 3.29.10) lets remote unauthenticated attackers elevate their privileges, per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H vector rated 9.8 Critical. The flaw (CWE-266, Incorrect Privilege Assignment) stems from the plugin's frontend user-management forms exposing role/capability assignment without proper authorization, enabling an attacker to gain administrator-level access to the WordPress site. No public exploit identified at time of analysis and the CVE is not on CISA KEV, but the CVSS profile indicates trivially weaponizable network-based abuse.
SQL injection in Loca Software Informatics Technology Ltd. Co. CMS (all versions up to and including build 06082026) allows remote unauthenticated attackers to inject arbitrary SQL through improperly neutralized input, per CVSS PR:N. Disclosed by Turkey's national CERT (TR-CERT/USOM), the flaw carries a critical 9.8 score with full confidentiality, integrity, and availability impact, but there is no public exploit identified at time of analysis and it is not listed in CISA KEV. The vendor was contacted but did not respond, so no fix is available.
Memory corruption (double-free) in the Linux kernel's SMB/CIFS client SMB2_close replay path can be triggered when a mounted SMB server returns a replayable error and a subsequent SMB2_close_init() fails, causing the same response buffer to be freed twice. It affects Linux stable kernels across the 6.6.x through 7.x series before the fixed releases; while the CNA-assigned CVSS is 9.8 with no public exploit identified at time of analysis, real-world abuse requires the victim host to communicate with a malicious or compromised SMB server, making this primarily a client-side memory-corruption/DoS concern rather than trivial remote code execution.
Access control bypass in Open Library Foundation VuFind versions 11.0.3 and 4.1 allows unauthenticated remote attackers to invoke controller functions that should be restricted. The AbstractBase::validateAccessPermission logic returns an 'access denied' response to the requester but fails to halt request processing, so the protected function still executes server-side. Categorized as an authentication/authorization bypass (CWE-863) with a reported CVSS 9.8; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Unsafe deserialization in Apache CXF's JMS transport allows any party able to publish to the service's JMS destination to achieve denial of service or, where a compatible deserialization gadget chain is present on the application classpath, remote code execution within the CXF process. All Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 are affected when the JMS transport is in use. No public exploit code or CISA KEV listing has been identified at time of analysis, though the vulnerability class (CWE-502 with unrestricted ObjectInputStream) is well-understood and tooling such as ysoserial makes it routinely exploitable wherever gadget libraries are present.
Sandbox escape in Google Chrome for Linux (versions before 151.0.7922.109) stems from a use-after-free in the Aura windowing subsystem, letting a remote attacker who lures a victim to a crafted HTML page corrupt memory and potentially break out of the renderer sandbox. Google rated the Chromium severity Critical (CVSS 9.6, scope-changed), but there is no public exploit identified at time of analysis and CISA's SSVC framework records exploitation status as 'none'. Because a full sandbox escape gives attacker code the privileges of the browser process on the host, this is a high-priority patch despite the absence of observed exploitation.
Sandbox escape in Google Chrome for Android before 151.0.7922.109 stems from a use-after-free in the WebGL graphics component (CWE-416), letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Chromium rates this Critical and CVSS scores it 9.6 with a scope change (S:C), reflecting the cross-boundary sandbox escape. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but Chrome WebGL memory-corruption bugs are historically high-value exploitation targets.
Sandbox escape in Google Chrome's Web Authentication (WebAuthn) component before 151.0.7922.109 lets a remote attacker who lures a victim to a crafted HTML page corrupt memory via a use-after-free and potentially break out of the renderer sandbox. Rated High by Chromium and scored CVSS 9.6 (scope-changed), it affects the vast installed base of desktop Chrome; Google has shipped a fixed Stable-channel build. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Sandbox escape in Google Chrome for Android before 151.0.7922.109 stems from an out-of-bounds write in ANGLE, Chrome's OpenGL ES/GPU translation layer, allowing a remote attacker who lures a victim to a crafted HTML page to corrupt GPU-process memory and potentially break out of the renderer sandbox. Chromium rates the issue Critical and a vendor patch is available, but there is no public exploit identified at time of analysis and CISA SSVC records exploitation status as none. The high CVSS 9.6 reflects the scope-changing sandbox-escape potential rather than confirmed in-the-wild use.
Sandbox escape in Google Chrome desktop versions prior to 151.0.7922.109 stems from a use-after-free in the Payments component, letting a remote attacker who lures a victim to a crafted HTML page potentially break out of the renderer sandbox. Rated High by Chromium and scored CVSS 9.6 due to a scope change, though exploitation requires user interaction (visiting a malicious page). There is no public exploit identified at time of analysis and no CISA KEV listing, but Chrome renderer/sandbox-escape bugs are historically high-value targets.
Sandbox escape in Google Chrome's Media component on Windows (versions prior to 151.0.7922.109) lets a remote attacker break out of the renderer sandbox by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and CVSS 9.6 because a successful escape yields full confidentiality, integrity, and availability impact beyond the sandboxed process. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though Chrome UAF media bugs are historically attractive targets.
Sandbox escape in Google Chrome's Codecs component (versions prior to 151.0.7922.109) allows a remote attacker to break out of the renderer sandbox when a victim views a crafted HTML page, via insufficient validation of untrusted input (CWE-20). Rated CVSS 9.6 with a changed scope, the flaw affects the desktop Stable channel across all platforms and is fixed in 151.0.7922.109. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Server-Side Request Forgery combined with CSRF in Eclipse GlassFish's DownloadServlet ContentSources handler allows a remote attacker to exfiltrate the administrative `gfresttoken` to an attacker-controlled host when an authenticated administrator visits a malicious page. Affecting Eclipse GlassFish 8.0.x prior to 8.0.4, successful token theft yields full control of the GlassFish administrative domain until the token expires, effectively an unauthenticated takeover of the management plane. No public exploit identified at time of analysis, and the issue is not in CISA KEV, but the CVSS 9.6 rating and low attack complexity make it high priority.
File inclusion in TinyAGI 0.0.20 exposes server-side files to remote unauthenticated attackers through the buildSystemPrompt function in packages/server/src/routes/agents.ts. Exploitation requires no privileges or user interaction, and a publicly available proof-of-concept exists via GitHub issue #283. No patch has been released - the vendor has not responded to the responsible disclosure despite being notified through the project's issue tracker.
File inclusion via unsanitized path input in TinyAGI 0.0.20's Message API Endpoint exposes server-side files to remote unauthenticated attackers. The vulnerable surface is the `collectFiles` function in `packages/core/src/response.ts`, which accepts externally controlled file paths without adequate validation (CWE-73). Publicly available exploit code exists via GitHub issue #282, and the project maintainer had not issued a patch or response at time of disclosure - compounding risk for any internet-exposed deployments.
Missing authorization in TinyAGI 0.0.20's Message API Endpoint allows remote unauthenticated attackers to invoke the processMessage function without any access control enforcement, yielding limited but real confidentiality, integrity, and availability impact. A publicly available proof-of-concept exploit is referenced in GitHub issue #284, and the project maintainer has not responded to the responsible disclosure, leaving no patch available at time of analysis. The combination of unauthenticated network exploitability, live POC, and vendor silence makes this a material risk for any deployment exposing the endpoint to untrusted networks.
Unauthenticated remote information disclosure in heshengtao super-agent-party (up to version 0.4.1) allows remote attackers to read sensitive file content by manipulating the tool_name or tool_params arguments passed to the get_file_content function via the execute_tool_manually endpoint in server.py. The flaw requires no authentication and no user interaction, and a public proof-of-concept exploit is available on GitHub. No patch has been issued; the vendor did not respond to coordinated disclosure.
Server-side request forgery in heshengtao's super-agent-party (versions 0.4.0-0.4.1) enables remote unauthenticated attackers to coerce the application into issuing arbitrary HTTP requests to internal or otherwise restricted network destinations. The flaw exists in the sanitize_proxy_url function within server.py on the extension_proxy route, where the url argument is insufficiently validated before being acted upon. A public proof-of-concept exploit is available via GitHub Gist, lowering the barrier to exploitation; the vendor did not respond to responsible disclosure, and no patch has been released.
Server-side request forgery (SSRF) in JeecgBoot's AI RAG chat endpoint (/airag/chat/send) exposes unauthenticated remote attackers a direct path to make the application server issue arbitrary HTTP requests to internal or external network resources. All versions up to and including 3.9.2 are affected, with the flaw residing in the Anonymous Chat Attachment Parser component - meaning no login is required to trigger it. Public exploit code exists via a GitHub issue (no public exploit identified as actively exploited per CISA KEV), and no vendor-released patch is available at time of analysis.
SQL injection in SourceCodester Computer Repair Shop Management System 1.0 exposes the `/classes/Master.php?f=delete_product` endpoint to unauthenticated remote attackers who can manipulate the `id` parameter to execute arbitrary SQL against the backend database. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms no authentication or user interaction is required, and a public proof-of-concept exploit has been disclosed on GitHub. Impact is assessed as limited (VC:L/VI:L/VA:L) with no scope change to subsequent systems, though the availability of exploit code meaningfully lowers the bar for opportunistic abuse of any internet-exposed instance.
Authentication bypass in WSO2 Identity Server and multiple WSO2 platform products (API Manager, Open Banking AM/IAM/KM, Traffic Manager, Universal Gateway, API Control Plane, Identity Server as Key Manager) lets an attacker skip intermediate multi-factor challenges when the Conditional (Adaptive) Authentication script is configured with a particular multi-step callback/re-execution pattern, resulting in unauthorized takeover of a targeted user account. The flaw stems from the adaptive script failing to enforce completion of all required steps, and carries a high CVSS of 9.4 (C:H/I:H). There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the affected components underpin enterprise SSO/MFA and open-banking IAM, making impact severe where the vulnerable flow exists.
Broken end-to-end encryption in OpenReception's appointment booking software before 1.0.4 lets any unauthenticated network attacker register their own ML-KEM-768 public key as an encryption recipient for any tenant's staff via POST /api/tenants/{tenantId}/staff/{staffId}/crypto. Because the handler logs an 'Unauthorized crypto key storage attempt' warning but inserts the row anyway, the attacker silently becomes a co-recipient of every future patient appointment for that tenant and can decrypt all payloads, defeating the platform's claim that even administrators cannot read sensitive data. No public exploit identified at time of analysis, but the CVSS 9.4 rating and full technical detail in the GHSA advisory make this a high-priority patch.
Stored Cross-Site Scripting in the Slick Slider WordPress plugin before 0.5.3 allows any authenticated user holding the Contributor role or higher to inject persistent JavaScript through an unsanitized shortcode attribute value that is rendered directly into an HTML attribute. The payload executes in the browser of any user - including administrators - who subsequently views the affected post, enabling session hijacking, credential theft, or privilege escalation. A publicly available proof-of-concept exploit exists and a vendor patch (version 0.5.3) has been released; no active exploitation has been confirmed by CISA KEV at time of analysis.
Stored Cross-Site Scripting in the Child Pages Card WordPress plugin (all versions before 1.09) allows contributors and higher-privileged authenticated users to inject persistent JavaScript payloads via unsanitized shortcode attributes. When an administrator or other privileged user views a page containing the malicious shortcode, the injected script executes in their browser, enabling session hijacking or unauthorized privileged actions. A public exploit is available via WPScan; no confirmed active exploitation (CISA KEV) has been observed, though the public PoC meaningfully lowers the barrier to abuse.
Missing capability check in the SEO Redirection Plugin for WordPress (versions before 9.19) exposes authenticated AJAX endpoints to any logged-in user, regardless of role. A subscriber-level account - the lowest WordPress user tier - can invoke the unprotected action to enumerate all configured 301 redirect rules, revealing source and destination URLs that may disclose internal site architecture, campaign tracking patterns, or sensitive path structures. No public exploitation in the wild has been confirmed by CISA KEV, but a proof-of-concept is publicly available per WPScan, raising the probability of opportunistic abuse against unpatched sites.
Unauthenticated arbitrary file write in Dinky v1.2.5 and its byte-identical development branch lets anyone who can reach the HTTP port (8888 by default) overwrite files as the Dinky service account, because the POST /download/uploadFromRsByLocal handler feeds a caller-supplied path straight into new File(path) and transferTo(dest) with no validation. The route is exempt from Sa-Token auth and guarded only by a header check against a dinkyToken whose default value is hardcoded in source and shipped to every install, so the guard is effectively no guard. The researcher (VulnCheck) demonstrated full remote code execution by shadowing Dinky.class on the writable, chmod-777 classpath and by planting attacker JavaScript in the served index.html; there is no public exploit identified at time of analysis and it is not in CISA KEV, but the disclosure describes a working demonstration.
Denial-of-service in Mermaid's radar-beta diagram renderer allows an attacker who can supply diagram input to trigger unbounded CPU and memory consumption by setting the `ticks` parameter to an arbitrarily large integer. Affected npm package versions >= 11.6.0 and < 11.16.1 perform no upper-bound validation on the `ticks` value, causing the JavaScript process - whether a browser tab or a server-side renderer - to freeze indefinitely until the OS terminates it due to OOM. A proof-of-concept is publicly available in the advisory. No KEV listing exists and no EPSS score is provided.
Infinite-loop denial of service in Mermaid's XY chart renderer allows any party that can supply diagram input to crash the JavaScript process or browser tab. The `setXAxisRangeData()` function in npm/mermaid enters an unbounded loop when an x-axis range is defined with identical start and end values, growing an array until memory is exhausted or a `RangeError: Invalid array length` is thrown. A proof-of-concept is publicly embedded in the GitHub security advisory (GHSA-2v8p-3f2j-5mp7), making exploitation trivial; no CISA KEV listing has been issued.
Request smuggling primitive in h2 (pip/h2) versions 4.4.0 and below enables network-accessible attackers to craft HTTP/2 header blocks containing duplicate Host headers that the library forwards verbatim to consuming applications. When a consumer downgrades the HTTP/2 request to HTTP/1.1 - a common pattern in reverse proxy and gateway architectures - the resulting HTTP/1.1 request carries two Host header lines, violating RFC 7230 and creating an ambiguity that downstream servers may interpret differently, enabling cache poisoning, security control bypass, or session hijacking. No active exploitation confirmed (not in CISA KEV); no public exploit code identified at time of analysis; fix is available in v4.4.1.
SQL injection in the miniOrange WP OAuth Server WordPress plugin (all versions up to and including 6.2.0) lets remote unauthenticated attackers inject arbitrary SQL through the plugin's OAuth request handling, per CVSS:3.1 PR:N. The flaw carries a critical 9.3 score with a changed-scope confidentiality impact, meaning attacker-controlled queries can reach data beyond the intended authorization boundary. Reported by Patchstack (CVE-2026-65520 / EUVD-2026-53969); no public exploit identified at time of analysis.
Unauthenticated SQL injection in the Simply Schedule Appointments WordPress plugin (versions up to and including 1.6.12.10) lets remote attackers inject arbitrary SQL through the plugin's appointment/booking request handling, exposing the underlying WordPress database without any login. Because the CVSS vector is PR:N/UI:N with a scope change (S:C) and high confidentiality impact, any WordPress site running a vulnerable version is reachable over the network by anonymous users. There is no public exploit identified at time of analysis, and the CVE is not listed in CISA KEV; EPSS data was not provided.
SQL injection in the WordPress File Upload plugin (by nickboss) affects all versions up to and including 5.1.7 and is reachable by unauthenticated remote attackers (CVSS 9.3, AV:N/PR:N). Because the CVSS scope is Changed with high confidentiality impact, a crafted request can coerce the plugin into executing attacker-controlled SQL, exposing WordPress database contents such as user records and secrets. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV; it was reported through Patchstack.
SQL injection in the Qode Tours WordPress plugin (versions up to and including 3.1.3.1) lets remote unauthenticated attackers inject arbitrary SQL through the plugin's tour/booking functionality. Because no authentication or user interaction is required (CVSS 9.3, PR:N/UI:N) and the scope is changed, an attacker can extract sensitive data from the WordPress database, such as user records and credential hashes. Reported by Patchstack; no public exploit identified at time of analysis and not listed in CISA KEV.
Unauthorized retrieval of other customers' payment receipt images is possible in PeproDev WooCommerce Receipt Uploader (≤ 2.8.0) because the plugin's token-based attachment access mechanism never validates that a requested attachment ID belongs to the order the token was issued for. Unauthenticated network attackers can forge or repurpose a token - trivially obtained by placing any order - to iterate over attachment IDs and exfiltrate payment receipts uploaded by unrelated customers, potentially exposing financial documents containing banking details or PII. A publicly available proof-of-concept exists per WPScan reporting (EUVD-2026-53719); no CISA KEV listing indicates widespread active exploitation has not been confirmed, though SSVC rates the attack as automatable.
ProfileGrid WordPress plugin (all versions before 6.0.0.0) exposes group member lists and member identifiers to unauthenticated visitors due to a handler registered without any authorization checks, completely bypassing the plugin's member-visibility settings for private and closed groups. Any unauthenticated visitor who can reach the WordPress site can enumerate group members and their identifiers across all group types, including those the site owner intended to restrict. A publicly available exploit exists per WPScan, and the SSVC classification flags this as automatable - though EPSS at 0.14% (4th percentile) indicates exploitation has not become widespread despite the low barrier to entry.
tourmaster WordPress plugin (all versions before 5.4.9) exposes exported customer booking and order data via a fixed, predictable file path inside its publicly accessible web directory, with no authentication or access control enforcing download restrictions. Any unauthenticated network attacker who knows or can derive the static export file URL can retrieve personally identifiable information - names, contact details, and booking records - after an administrator has triggered an export. A publicly available proof-of-concept exists per WPScan, and exploitation is fully automatable (SSVC), though EPSS sits at 0.14% and no CISA KEV listing exists at time of analysis.
Open email relay in the Estatik Real Estate Plugin for WordPress (before 4.3.3) allows unauthenticated remote attackers to send arbitrary emails through any affected WordPress site by submitting crafted property inquiry form requests with controlled recipient address, subject, body, and Reply-To header. The plugin's anti-spam check is trivially bypassed and provides no constraint on recipient routing, effectively turning victim sites into spam or phishing infrastructure. A publicly available exploit exists per WPScan; EPSS sits at 0.14% (3rd percentile) and CISA KEV does not list active exploitation, suggesting limited but plausible abuse given SSVC confirms the attack is automatable.
Local privilege escalation in Sophos Endpoint for macOS (before 2026.1.1) and Sophos Home for macOS (before 10.11.6) allows any local user to execute arbitrary code with root privileges. The flaw stems from improper authorization (CWE-285) in the security agent's privileged components, so a low-privileged or unprivileged local account can fully compromise the host. No public exploit identified at time of analysis, but the CVSS 9.3 rating and scope change to root make this a high-priority patch for macOS fleets.
Unauthenticated IDOR write in PeproDev WooCommerce Receipt Uploader (all versions ≤ 2.8.0) allows any remote attacker to submit or manipulate receipt uploads without credentials or authorization checks, bypassing the WordPress nonce and capability verification that WooCommerce plugins are expected to enforce. The plugin remains unpatched as of the time of writing, and a publicly available proof-of-concept exploit exists via WPScan. Despite automation potential (SSVC: Automatable yes), EPSS sits at 0.10% (1st percentile) and CISA has not listed this in KEV, indicating limited observed real-world exploitation to date.