Dell ECS, versions 3
Description
Dell ECS, versions 3
AI Analyst Comment
Remediation
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Search and filter 21553 vulnerabilities with AI analyst insights
Dell ECS, versions 3
Dell ECS, versions 3
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Dell ECS, versions 3
Dell ECS, versions 3
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Dell PowerProtect Data Manager, version(s) prior to 19
Dell PowerProtect Data Manager, version(s) prior to 19
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers
Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers
Executive Summary:
A high-severity vulnerability has been discovered in the web-based management interface for Keepalived servers. A remote attacker could potentially exploit this flaw to execute arbitrary commands on the underlying system, leading to a full server compromise. This vulnerability poses a significant risk to the availability and integrity of critical network services managed by Keepalived.
Vulnerability Details
CVE-ID: CVE-2026-22265
Affected Software: Keepalived Multiple Products
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: A command injection vulnerability exists within the web management interface (such as Roxy-WI) used to configure Keepalived services. An authenticated attacker with low-level privileges can inject malicious shell commands into input fields responsible for updating Keepalived configuration parameters. Due to insufficient input validation, these commands are executed on the server with the privileges of the web service account, which could allow an attacker to escalate privileges and gain complete control over the host system.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 7.5. Successful exploitation could lead to remote code execution on servers that are fundamental to maintaining high-availability infrastructure. The potential consequences include significant service disruption, unauthorized access to sensitive network traffic and data, and the ability for an attacker to pivot deeper into the corporate network. The compromise of a Keepalived server could disable critical failover capabilities, leading to extended downtime and direct financial and reputational damage.
Remediation Plan
Immediate Action: Apply vendor security updates immediately across all affected systems. Prioritize patching for systems with internet-facing management interfaces. Before applying the patch, review access logs for any unusual or suspicious activity related to the management interface to identify potential prior compromise.
Proactive Monitoring: Monitor web server and application logs for suspicious requests to configuration endpoints, particularly those containing shell metacharacters (e.g., |, ;, &&, $()). Monitor systems for unexpected processes spawned by the web server's user account and for any unusual outbound network connections that could indicate a successful compromise.
Compensating Controls: If patching cannot be performed immediately, restrict network access to the management interface to a limited set of trusted administrative IP addresses using a firewall. If available, deploy a Web Application Firewall (WAF) with rules designed to detect and block command injection attack patterns.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of January 17, 2026, there are no publicly available proof-of-concept exploits or observed in-the-wild attacks targeting this vulnerability. However, vulnerabilities of this type are often quickly weaponized by threat actors due to their high impact. Organizations should assume that an exploit will become available in the near future.
Analyst Recommendation
This vulnerability presents a high risk to the availability and security of the organization's core network services. Given the severity score of 7.5, we recommend treating this as a critical priority for remediation. All teams responsible for managing Keepalived infrastructure should immediately apply the vendor-supplied patches. While this CVE is not yet on the CISA KEV list, its potential impact warrants an emergency change-management cycle to mitigate the risk of exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Suricata is a network IDS, IPS and NSM engine
Suricata is a network IDS, IPS and NSM engine
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Suricata is a network IDS, IPS and NSM engine
Suricata is a network IDS, IPS and NSM engine
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Suricata is a network IDS, IPS and NSM engine
Suricata is a network IDS, IPS and NSM engine
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Suricata is a network IDS, IPS and NSM engine
Suricata is a network IDS, IPS and NSM engine
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Salvo is a Rust web backend framework
Salvo is a Rust web backend framework
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Salvo is a Rust web backend framework
Salvo is a Rust web backend framework
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
iccDEV provides a set of libraries and tools that allow for the interaction, manipulation, and application of International Color Consortium (ICC) col...
iccDEV provides a set of libraries and tools that allow for the interaction, manipulation, and application of International Color Consortium (ICC) color management profiles
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
LibreChat is a ChatGPT clone with additional features. Prior to v0.8.2-rc2, LibreChat's MCP stdio transport accepts arbitrary commands without validat...
LibreChat is a ChatGPT clone with additional features. Prior to v0.8.2-rc2, LibreChat's MCP stdio transport accepts arbitrary commands without validation, allowing any authenticated user to execute shell commands as root inside the container through a single API request. This vulnerability is fixed in v0.8.2-rc2.
Executive Summary:
A critical vulnerability has been discovered in the LibreChat application, which allows any authenticated user to take complete control of the application's underlying container. This flaw enables an attacker to execute arbitrary commands with the highest privileges (root), potentially leading to data theft, complete service disruption, and further unauthorized access into the corporate network. Immediate patching is required to mitigate this high-risk vulnerability.
Vulnerability Details
CVE-ID: CVE-2026-22252
Affected Software: LibreChat is a ChatGPT clone with additional Multiple Products
Affected Versions: All versions prior to v0.8.2-rc2
Vulnerability: The vulnerability exists within the MCP (Multi-Container Platform) stdio transport component of LibreChat. This component fails to properly validate or sanitize user-supplied input. An authenticated attacker can craft a malicious API request containing arbitrary shell commands, which are then passed directly to the system's shell and executed with root privileges inside the application container.
Business Impact
This vulnerability is rated as critical severity with a CVSS score of 9.1. Successful exploitation grants an attacker full administrative control (root access) over the LibreChat container. This could lead to severe consequences, including the exfiltration of sensitive data such as conversation logs, user credentials, and API keys stored within the environment. An attacker could also disrupt or completely disable the service, pivot to attack other internal network resources, or use the compromised system for malicious activities like hosting malware or launching further attacks, posing a significant risk to data confidentiality, integrity, and availability.
Remediation Plan
Immediate Action: Immediately upgrade all instances of LibreChat to version v0.8.2-rc2 or a later version, which contains the fix for this vulnerability. After patching, review API and system logs for any signs of compromise, such as unusual commands or outbound connections, that may have occurred prior to the update.
Proactive Monitoring: Implement continuous monitoring of LibreChat application and container logs. Specifically, look for suspicious API requests containing shell command syntax (e.g., ls, cat, curl, ;, &&). Monitor for unexpected processes running within the container and unusual outbound network traffic, which could indicate a successful breach.
Compensating Controls: If immediate patching is not feasible, consider implementing the following controls:
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of January 12, 2026, there are no known public exploits available for this vulnerability. However, given the low complexity of exploitation for an authenticated user and the high impact (root-level RCE), it is highly probable that proof-of-concept exploits will be developed and released publicly in the near future. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog.
Analyst Recommendation
Given the critical CVSS score of 9.1 and the potential for complete system compromise, it is imperative that organizations using the affected versions of LibreChat treat this vulnerability with the highest priority. The recommended course of action is to apply the security patch and upgrade to version v0.8.2-rc2 or later immediately. Do not wait for public exploitation to be reported; the risk of data breach and further network intrusion is severe.
Update LibreChat is a ChatGPT clone with additional Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
A flaw has been found in itsourcecode News Portal Project 1
A flaw has been found in itsourcecode News Portal Project 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
GLPI is an open-source asset and IT management software package that provides ITIL Service Desk features, licenses tracking and software auditing
GLPI is an open-source asset and IT management software package that provides ITIL Service Desk features, licenses tracking and software auditing
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OPEXUS eComplaint before version 9
OPEXUS eComplaint before version 9
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OPEXUS eCasePortal before version 9.0.45.0 allows an unauthenticated attacker to navigate to the 'Attachments.aspx' endpoint, iterate through predicta...
OPEXUS eCasePortal before version 9.0.45.0 allows an unauthenticated attacker to navigate to the 'Attachments.aspx' endpoint, iterate through predictable values of 'formid', and download or delete all user-uploaded files, or upload new files.
---METADATA---
VENDOR: OPEXUS
PRODUCT: eCasePortal
AFFECTED_VERSIONS: Before 9.0.45.0
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
OPEXUS eCasePortal versions prior to 9.0.45.0 contain an insecure direct object reference vulnerability in the 'Attachments.aspx' endpoint, allowing unauthorized file access and manipulation.
Executive Summary:
An unauthenticated file access vulnerability in OPEXUS eCasePortal allows attackers to download, delete, or upload files, posing a severe risk to data integrity.
Vulnerability Details
CVE-ID: CVE-2026-22234
Affected Software: OPEXUS eCasePortal
Affected Versions: Before 9.0.45.0
Vulnerability: The 'Attachments.aspx' endpoint lacks proper authorization controls, allowing an unauthenticated attacker to iterate through 'formid' values. This permits unauthorized access to sensitive user-uploaded files and modification of the file repository.
Business Impact
This vulnerability allows for the unauthorized disclosure of sensitive documents and potential data destruction, which could lead to severe reputational damage and regulatory non-compliance. With a CVSS score of 9.8, the risk of total data breach is significant.
Remediation Plan
Immediate Action: Upgrade OPEXUS eCasePortal to version 9.0.45.0 or later to patch the authorization flaw.
Proactive Monitoring: Audit access logs for the 'Attachments.aspx' endpoint to identify patterns of sequential 'formid' requests indicative of enumeration attacks.
Compensating Controls: Restrict access to the eCasePortal application via network-level controls or a VPN to limit exposure to untrusted entities.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of Jan 8, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Immediate patching is required to prevent unauthorized access to sensitive attachments. Administrators should verify the integrity of the file system following any potential unauthorized access attempts.
Update OPEXUS eCasePortal before version Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
OPEXUS eCASE Audit allows an authenticated attacker to modify client-side JavaScript or craft HTTP requests to access functions or buttons that have b...
OPEXUS eCASE Audit allows an authenticated attacker to modify client-side JavaScript or craft HTTP requests to access functions or buttons that have been disabled or blocked by an administrator
Executive Summary:
A high-severity vulnerability has been identified in OPEXUS eCASE Audit products, tracked as CVE-2026-22230. This flaw allows an authenticated user to bypass security restrictions by manipulating client-side code, enabling them to access features and perform actions that should be administratively blocked, potentially leading to unauthorized data access or system changes.
Vulnerability Details
CVE-ID: CVE-2026-22230
Affected Software: modify Multiple Products
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability exists because security controls, such as disabling buttons or functions in the user interface, are enforced on the client side (in the user's web browser) rather than on the server. An authenticated attacker can exploit this by using browser developer tools to modify the client-side JavaScript or by intercepting and crafting custom HTTP requests directly to the server's backend. This allows the attacker to call functions and access application features that their user role is not authorized to use, effectively bypassing the business logic and access controls implemented by the administrator.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 7.6. Exploitation could lead to significant business consequences, including unauthorized access to sensitive audit data, modification or deletion of records, and escalation of privileges within the application. This undermines the principle of least privilege and segregation of duties, creating risks of data breaches, compliance violations, and internal fraud. The integrity and confidentiality of the data managed by the affected OPEXUS products are at direct risk.
Remediation Plan
Immediate Action: Apply the security updates provided by the vendor across all affected systems immediately to patch the vulnerability. Before and after patching, organizations should review application and server access logs for any signs of unauthorized or anomalous activity that could indicate prior exploitation.
Proactive Monitoring: Monitor application logs for direct API calls or function executions that do not correspond to the normal user interface workflow. Scrutinize activity from authenticated users that appears to access or modify data or settings outside of their defined roles. Network monitoring can also help detect crafted HTTP requests that differ from standard application traffic.
Compensating Controls: If immediate patching is not feasible, consider implementing the following controls:
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of January 10, 2026, there are no known public proof-of-concept exploits or active attacks targeting this vulnerability. However, the nature of client-side control bypass vulnerabilities makes them relatively straightforward for a skilled, authenticated attacker to discover and exploit manually.
Analyst Recommendation
Given the high severity (CVSS 7.6) and the direct risk to data integrity and access controls, it is strongly recommended that organizations prioritize the deployment of the vendor-supplied patches. Although this vulnerability is not currently listed on the CISA KEV list and requires an attacker to be authenticated, the potential for privilege escalation and unauthorized data access presents a significant risk. Organizations should apply the updates, verify successful implementation, and maintain vigilant monitoring for any signs of exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A security vulnerability has been detected in code-projects Online Reviewer System 1
A security vulnerability has been detected in code-projects Online Reviewer System 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A security flaw has been discovered in code-projects Online Reviewer System 1
A security flaw has been discovered in code-projects Online Reviewer System 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenS100 is vulnerable to remote code execution via an unsandboxed Lua interpreter. Attackers can execute arbitrary commands by tricking a user into i...
OpenS100 is vulnerable to remote code execution via an unsandboxed Lua interpreter. Attackers can execute arbitrary commands by tricking a user into importing a malicious S-100 portrayal catalogue.
---METADATA---
VENDOR: OpenS100
PRODUCT: OpenS100 (S-100 Viewer)
AFFECTED_VERSIONS: Prior to commit 753cf29
---END_METADATA---
Description Summary:
OpenS100 is vulnerable to remote code execution via an unsandboxed Lua interpreter. Attackers can execute arbitrary commands by tricking a user into importing a malicious S-100 portrayal catalogue.
Executive Summary:
A critical remote code execution vulnerability in OpenS100 allows unauthenticated attackers to gain full control over the host process by providing a malicious portrayal catalogue.
Vulnerability Details
CVE-ID: CVE-2026-22208
Affected Software: OpenS100 S-100 Viewer
Affected Versions: Prior to commit 753cf29
Vulnerability: This vulnerability stems from an unrestricted Lua interpreter within the Portrayal Engine that lacks sandboxing. An unauthenticated attacker can leverage standard libraries like 'os' and 'io' via a crafted S-100 catalogue to execute arbitrary system commands when the catalogue is imported.
Business Impact
A successful exploit results in a total compromise of the OpenS100 process, allowing for unauthorized data access, lateral movement within the network, and persistent system control. The CVSS score of 9.6 reflects the critical nature of this flaw, as it permits remote code execution with minimal user interaction beyond importing a file.
Remediation Plan
Immediate Action: Update OpenS100 to a version containing commit 753cf29 or later to ensure the Lua interpreter is properly sandboxed.
Proactive Monitoring: Monitor system logs for unusual process spawning from the OpenS100 application and review all imported S-100 catalogues for suspicious Lua scripts.
Compensating Controls: Implement strict file-integrity monitoring and restrict the application's ability to execute shell commands using OS-level security policies or containers.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of Feb 17, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
The severity of this vulnerability cannot be overstated, as it allows for complete system takeover via a common user workflow. Organizations utilizing OpenS100 must prioritize updating to the latest patched version immediately to mitigate the risk of remote code execution.
Update Unknown Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
SPIP versions prior to 4
SPIP versions prior to 4
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
SPIP versions prior to 4
SPIP versions prior to 4
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
wpDiscuz before 7
wpDiscuz before 7
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability was identified in code-projects Online Reviewer System 1
A vulnerability was identified in code-projects Online Reviewer System 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
wpDiscuz before 7
wpDiscuz before 7
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
wpDiscuz before 7
wpDiscuz before 7
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw versions prior to 2026
OpenClaw versions prior to 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenClaw versions prior to 2026.3.12 suffer from an authorization bypass in the WebSocket path, allowing authenticated users to self-declare administr...
OpenClaw versions prior to 2026.3.12 suffer from an authorization bypass in the WebSocket path, allowing authenticated users to self-declare administrative privileges.
---METADATA---
VENDOR: OpenClaw
PRODUCT: OpenClaw
AFFECTED_VERSIONS: Versions prior to 2026.3.12
---END_METADATA---
Description Summary:
OpenClaw versions prior to 2026.3.12 suffer from an authorization bypass in the WebSocket path, allowing authenticated users to self-declare administrative privileges.
Executive Summary:
Authenticated attackers can escalate their privileges to full administrative access by exploiting a flaw in OpenClaw's WebSocket authorization logic.
Vulnerability Details
CVE-ID: CVE-2026-22172
Affected Software: OpenClaw
Affected Versions: Versions prior to 2026.3.12
Vulnerability: This vulnerability is an authorization bypass within the WebSocket connection path. Authenticated users (using shared tokens or passwords) can self-declare elevated scopes, such as operator.admin, without proper server-side verification, allowing them to perform admin-only operations.
Business Impact
This privilege escalation vulnerability allows any user with basic access to take control of the entire OpenClaw gateway. This could result in unauthorized configuration changes, data manipulation, and total loss of administrative control. The CVSS score of 9.9 reflects the nearly total impact on confidentiality, integrity, and availability.
Remediation Plan
Immediate Action: Update OpenClaw to version 2026.3.12 or later to ensure that user scopes are strictly bound and verified on the server side.
Proactive Monitoring: Review administrative logs for actions performed by non-admin accounts and monitor WebSocket connection requests for unauthorized scope declarations.
Compensating Controls: Implement strict network segmentation to limit access to the OpenClaw interface to only trusted administrative workstations until the patch is applied.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of Mar 20, 2026, there is no public information indicating active exploitation. However, the logic flaw is significant and easily exploitable by anyone with valid low-level credentials.
Analyst Recommendation
Organizations using OpenClaw must treat this as a critical priority. The ability for a standard user to elevate themselves to an administrator constitutes a complete breakdown of the security model. Applying the patch immediately is the only effective way to mitigate this risk.
Update OpenClaw versions Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
OpenClaw versions prior to 2026
OpenClaw versions prior to 2026
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability was found in itsourcecode Event Management System 1
A vulnerability was found in itsourcecode Event Management System 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Software installed and run as a non-privileged user may conduct improper GPU system calls to force GPU to write to arbitrary physical memory pages
Software installed and run as a non-privileged user may conduct improper GPU system calls to force GPU to write to arbitrary physical memory pages
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A web page that contains unusual WebGPU content loaded into the GPU GLES render process and can trigger write UAF crash in the GPU GLES user-space sha...
A web page that contains unusual WebGPU content loaded into the GPU GLES render process and can trigger write UAF crash in the GPU GLES user-space shared library
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A web page that contains unusual WebGPU content loaded into the GPU GLES render process and can trigger a write UAF crash in the GPU GLES user-space s...
A web page that contains unusual WebGPU content loaded into the GPU GLES render process and can trigger a write UAF crash in the GPU GLES user-space shared library
---METADATA---
VENDOR: Unknown
PRODUCT: GPU GLES Library
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A use-after-free (UAF) vulnerability in the GPU GLES user-space shared library can be triggered by malicious WebGPU content.
Executive Summary:
A use-after-free vulnerability in the GPU GLES shared library could allow an attacker to trigger crashes or potentially execute code via malicious web content.
Vulnerability Details
CVE-ID: CVE-2026-22165
Affected Software: GPU GLES shared library
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability is a write use-after-free (UAF) crash condition occurring within the GPU GLES user-space shared library. It is triggered when processing specifically crafted WebGPU content, which may lead to memory corruption within the rendering process.
Business Impact
A CVSS score of 8.1 highlights the critical nature of this flaw, as it can be weaponized through web browsers to achieve remote code execution. This poses a severe risk to end-user workstations, potentially leading to unauthorized data exfiltration or system takeover.
Remediation Plan
Immediate Action: Ensure that all web browsers and associated GPU drivers are updated to the latest versions provided by the vendor.
Proactive Monitoring: Utilize endpoint detection and response (EDR) solutions to monitor for suspicious process crashes or anomalous memory access patterns in web browser renderers.
Compensating Controls: Use browser-based security features or extensions that restrict execution of WebGPU content from untrusted domains.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of May 3, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Organizations should prioritize the update of browser environments and graphics drivers to mitigate this high-severity UAF vulnerability. Immediate patching is recommended to prevent potential exploitation via malicious web-based content.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
An Authentication Bypass by Primary Weakness vulnerability [CWE-305] vulnerability in Fortinet FortiOS 7
An Authentication Bypass by Primary Weakness vulnerability [CWE-305] vulnerability in Fortinet FortiOS 7
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability was identified in code-projects Online Music Site 1
A vulnerability was identified in code-projects Online Music Site 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability was determined in code-projects Online Music Site 1
A vulnerability was determined in code-projects Online Music Site 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Improper access control in Hashtopolis server web-interface chunk activity component for versions prior to 0
Improper access control in Hashtopolis server web-interface chunk activity component for versions prior to 0
---METADATA---
VENDOR: Hashtopolis
PRODUCT: Server
AFFECTED_VERSIONS: 0 up to (excluding) 0.14.8
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
Hashtopolis server contains an authorization bypass vulnerability in the web interface chunk activity component, allowing authenticated users to access unauthorized data.
Executive Summary:
An authorization bypass vulnerability in the Hashtopolis server allows authenticated users to access sensitive data, posing a significant risk to data confidentiality.
Vulnerability Details
CVE-ID: CVE-2026-22104
Affected Software: Hashtopolis Server
Affected Versions: 0 up to (excluding) 0.14.8
Vulnerability: The application suffers from an improper access control flaw (CWE-639) within the chunk activity component of the web interface. This vulnerability requires the attacker to have low-level privileges to successfully exploit the authorization bypass.
Business Impact
The successful exploitation of this vulnerability leads to unauthorized access to sensitive information, potentially resulting in data exfiltration or the compromise of internal processing tasks. With a CVSS score of 7.1, this represents a high-severity risk that could undermine the integrity of password cracking or distributed computing operations managed by the server.
Remediation Plan
Immediate Action: Update the Hashtopolis server to version 0.14.8 or later to incorporate the vendor-supplied security patch.
Proactive Monitoring: Review web interface access logs for unusual patterns or access requests to the chunk activity component that deviate from standard operational behavior.
Compensating Controls: Implement strict network access controls to limit access to the Hashtopolis interface to trusted administrative subnets, reducing the attack surface.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of July 19, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is fundamentally exploitable due to the lack of proper server-side authorization checks on user-supplied keys.
Analyst Recommendation
Given the potential for unauthorized data access, administrators should treat this update with high priority. We strongly recommend applying the patch to version 0.14.8 immediately to prevent potential exploitation by malicious actors who have gained low-level access to the environment.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The EVbee DC-80 web server contains a command injection vulnerability in the NPC start endpoint on port 8090, enabling unauthenticated remote code exe...
The EVbee DC-80 web server contains a command injection vulnerability in the NPC start endpoint on port 8090, enabling unauthenticated remote code execution.
---METADATA---
VENDOR: EVbee
PRODUCT: DC-80
AFFECTED_VERSIONS: 0 up to (excluding) 1.5.1
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The EVbee DC-80 web server contains a command injection vulnerability in the NPC start endpoint on port 8090, enabling unauthenticated remote code execution.
Executive Summary:
The EVbee DC-80 is susceptible to a critical command injection vulnerability that permits unauthenticated remote attackers to execute arbitrary system commands.
Vulnerability Details
CVE-ID: CVE-2026-22103
Affected Software: EVbee DC-80
Affected Versions: 0 up to (excluding) 1.5.1
Vulnerability: This vulnerability (CWE-77) stems from improper neutralization of special elements used in a command within the NPC start endpoint. An unauthenticated attacker can interact with the service on port 8090 to inject and execute arbitrary commands with the privileges of the web application.
Business Impact
The ability to execute arbitrary commands on the target device allows for full system compromise, data theft, and the potential for the device to be used as a pivot point for further network attacks. With a CVSS score of 9.3, this flaw poses an extreme risk to the security posture of the infrastructure hosting the affected units.
Remediation Plan
Immediate Action: Update the EVbee DC-80 firmware to version 1.5.1 or later immediately.
Proactive Monitoring: Monitor network traffic for anomalous command patterns directed at port 8090 and audit system logs for unexpected process execution.
Compensating Controls: Use network segmentation to isolate the DC-80 management interfaces from public-facing networks and implement strict firewall rules to limit access to port 8090.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is highly dangerous as it provides a direct vector for OS-level command execution.
Analyst Recommendation
The severity of this command injection vulnerability cannot be overstated, as it allows unauthenticated attackers to hijack the device completely. Immediate patching to version 1.5.1 is required to secure the device against potential exploitation.
Update EVbee DC-80 to the latest version. Monitor for exploitation attempts and review access logs.
An unauthenticated arbitrary file write vulnerability in the EVbee DC-80 webserver allows attackers to overwrite system files via a crafted POST reque...
An unauthenticated arbitrary file write vulnerability in the EVbee DC-80 webserver allows attackers to overwrite system files via a crafted POST request.
---METADATA---
VENDOR: EVbee
PRODUCT: DC-80
AFFECTED_VERSIONS: 0 up to (excluding) 1.5.1
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
An unauthenticated arbitrary file write vulnerability in the EVbee DC-80 webserver allows attackers to overwrite system files via a crafted POST request.
Executive Summary:
The EVbee DC-80 contains a critical arbitrary file write vulnerability that can lead to remote code execution or system denial of service.
Vulnerability Details
CVE-ID: CVE-2026-22102
Affected Software: EVbee DC-80
Affected Versions: 0 up to (excluding) 1.5.1
Vulnerability: This is an improper input validation vulnerability (CWE-20) where the webserver fails to sanitize the filename parameter in the Content-Disposition header. This allows an unauthenticated remote attacker to write to arbitrary file locations on the underlying operating system.
Business Impact
Successful exploitation carries a high risk of total system compromise, including the ability to overwrite critical system configuration files or inject malicious shell scripts. Given the CVSS score of 9.3, this vulnerability represents a critical threat to data integrity, system availability, and potential unauthorized access to the operational environment.
Remediation Plan
Immediate Action: Update the EVbee DC-80 firmware to version 1.5.1 or later immediately.
Proactive Monitoring: Review web server access logs for suspicious POST requests containing unusual filename parameters or path traversal sequences.
Compensating Controls: Deploy a Web Application Firewall (WAF) configured to inspect and block malformed Content-Disposition headers and restrict access to the web management interface from untrusted networks.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's inherent exploitability is high due to the lack of required authentication.
Analyst Recommendation
This is a critical vulnerability that permits full control over file system writes without authentication. Administrators must prioritize updating the affected EVbee DC-80 units to version 1.5.1 as soon as possible to neutralize the risk of remote code execution.
Update EVbee DC-80 to the latest version. Monitor for exploitation attempts and review access logs.
The OCPP DataTransfer message `ReserveLogin` is vulnerable to command injection
The OCPP DataTransfer message `ReserveLogin` is vulnerable to command injection
---METADATA---
VENDOR: EVbee
PRODUCT: DC-80
AFFECTED_VERSIONS: EVbee DC-80: 0 up to (excluding) 1.5.1
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The EVbee DC-80 charging station is vulnerable to OS command injection via the OCPP ReserveLogin DataTransfer message.
Executive Summary:
The EVbee DC-80 charging station is susceptible to OS command injection, allowing authenticated attackers to execute arbitrary system commands.
Vulnerability Details
CVE-ID: CVE-2026-22100
Affected Software: EVbee DC-80
Affected Versions: EVbee DC-80: 0 up to (excluding) 1.5.1
Vulnerability: This vulnerability (CWE-78) occurs within the OCPP ReserveLogin DataTransfer message function. The application fails to properly neutralize special characters in the input, allowing a user with high privileges to inject and execute arbitrary OS commands on the device.
Business Impact
The CVSS score of 8.6 underscores the severity of this command injection vulnerability. A successful exploit grants the attacker complete control over the underlying operating system of the charging station, which could lead to full system compromise, persistent backdoor installation, or the ability to manipulate charging behavior maliciously.
Remediation Plan
Immediate Action: Update the EVbee DC-80 firmware to version 1.5.1 or later immediately to patch the command injection vulnerability.
Proactive Monitoring: Audit logs for any irregular activity or command execution attempts associated with the ReserveLogin message.
Compensating Controls: Restrict administrative access to the charging station management interface to trusted users and networks only, limiting the potential pool of attackers.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of July 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While it requires high privileges for successful exploitation, the potential for total system compromise makes it a critical concern.
Analyst Recommendation
Firmware version 1.5.1 addresses the improper neutralization of input in the OCPP messages. All operators must apply this patch to eliminate the command injection vector and ensure the continued integrity and security of their charging infrastructure.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability has been found in D-Link DIR-823X 250416
A vulnerability has been found in D-Link DIR-823X 250416
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The charging station does not require authentication for Bluetooth commands to perform actions
The charging station does not require authentication for Bluetooth commands to perform actions
---METADATA---
VENDOR: EVbee
PRODUCT: DC-80
AFFECTED_VERSIONS: EVbee DC-80: 0 up to (excluding) 1.5.4
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The EVbee DC-80 charging station lacks authentication for Bluetooth commands, allowing unauthorized parties to execute commands.
Executive Summary:
The EVbee DC-80 charging station is vulnerable to unauthorized command execution via Bluetooth due to improper authentication, posing a high risk of remote manipulation.
Vulnerability Details
CVE-ID: CVE-2026-22099
Affected Software: EVbee DC-80
Affected Versions: EVbee DC-80: 0 up to (excluding) 1.5.4
Vulnerability: This vulnerability (CWE-287) exists because the device fails to perform any authentication checks for commands sent over Bluetooth. An unauthenticated attacker within proximity can send arbitrary commands to the charging station.
Business Impact
Successful exploitation allows an attacker to gain full control over the charging station's operations. Given the CVSS score of 8.7, this represents a high-severity risk that could lead to physical damage to the charging hardware, service disruption, or unauthorized use of the charging infrastructure, resulting in financial loss and operational downtime.
Remediation Plan
Immediate Action: Update the EVbee DC-80 firmware to version 1.5.4 or later immediately.
Proactive Monitoring: Monitor Bluetooth access logs for unusual or unauthorized pairing and command execution attempts.
Compensating Controls: If firmware updates cannot be applied immediately, restrict physical access to the device or disable Bluetooth interfaces if they are not required for operation.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of July 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the lack of any authentication mechanism for wireless command interfaces.
Analyst Recommendation
The severity of this vulnerability necessitates immediate action, particularly for units deployed in public or accessible locations. Administrators must prioritize the firmware update to version 1.5.4 to enforce necessary authentication controls and prevent unauthorized command execution.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The EVbee DC-80 writes sensitive information, including passwords and charging card UIDs, to log files in plaintext, leading to potential credential e...
The EVbee DC-80 writes sensitive information, including passwords and charging card UIDs, to log files in plaintext, leading to potential credential exposure.
---METADATA---
VENDOR: EVbee
PRODUCT: DC-80
AFFECTED_VERSIONS: EVbee DC-80: 0 up to (excluding) 1.5.1
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The EVbee DC-80 writes sensitive information, including passwords and charging card UIDs, to log files in plaintext, leading to potential credential exposure.
Executive Summary:
A critical information disclosure vulnerability in the EVbee DC-80 exposes sensitive credentials and user data within system log files.
Vulnerability Details
CVE-ID: CVE-2026-22098
Affected Software: EVbee DC-80
Affected Versions: EVbee DC-80: 0 up to (excluding) 1.5.1
Vulnerability: This is an improper validation of log file contents (CWE-532) issue. The application logs sensitive data, such as administrative passwords and charging card UIDs, in an unauthenticated, accessible format.
Business Impact
The exposure of plaintext passwords and unique identifiers poses a significant risk of account takeover and unauthorized service usage. With a CVSS score of 9.2, this vulnerability could facilitate large-scale identity theft or unauthorized billing, leading to significant reputational and financial damage.
Remediation Plan
Immediate Action: Update the EVbee DC-80 firmware to version 1.5.1 or later to sanitize log output.
Proactive Monitoring: Audit existing log files for exposed sensitive data and rotate any potentially compromised credentials immediately.
Compensating Controls: Implement strict file-system permissions to limit access to log directories and utilize log management systems to redact sensitive information in transit.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous as it provides a persistent repository of sensitive data for any attacker with read access to the system.
Analyst Recommendation
Addressing this vulnerability is essential for protecting user privacy and system security. Administrators must apply the provided firmware update and conduct a thorough audit of existing logs to ensure that compromised credentials are revoked and replaced.
Update EVbee DC-80 to the latest version. Monitor for exploitation attempts and review access logs.
The EVbee DC-80 firmware update mechanism lacks cryptographic signature validation, allowing unauthenticated remote attackers to execute arbitrary cod...
The EVbee DC-80 firmware update mechanism lacks cryptographic signature validation, allowing unauthenticated remote attackers to execute arbitrary code via malicious firmware uploads.
---METADATA---
VENDOR: EVbee
PRODUCT: DC-80
AFFECTED_VERSIONS: EVbee DC-80: 0 up to (excluding) 1.5.1
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The EVbee DC-80 firmware update mechanism lacks cryptographic signature validation, allowing unauthenticated remote attackers to execute arbitrary code via malicious firmware uploads.
Executive Summary:
A critical vulnerability in the EVbee DC-80 firmware update process allows for remote code execution due to a lack of cryptographic signature verification.
Vulnerability Details
CVE-ID: CVE-2026-22097
Affected Software: EVbee DC-80
Affected Versions: EVbee DC-80: 0 up to (excluding) 1.5.1
Vulnerability: This is an improper check for cryptographic signature (CWE-347) vulnerability. The device fails to validate the integrity of firmware updates, permitting an unauthenticated attacker to inject and execute arbitrary code.
Business Impact
Successful exploitation grants an attacker full control over the device, potentially leading to total system compromise. Given the CVSS score of 9.3, the impact is severe, as it could result in unauthorized power grid interaction, data theft, or permanent denial-of-service for EV charging infrastructure.
Remediation Plan
Immediate Action: Update the EVbee DC-80 firmware to version 1.5.1 or later immediately.
Proactive Monitoring: Review device access logs for unauthorized firmware update requests or unusual file upload activity.
Compensating Controls: Restrict network access to the device management interface to trusted administrative subnets via firewall rules.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is highly exploitable due to the lack of authentication required for the update interface.
Analyst Recommendation
This is a critical security flaw that requires immediate attention. Organizations utilizing EVbee DC-80 hardware must prioritize the transition to firmware version 1.5.1 to prevent potential remote command execution and maintain the integrity of their charging network.
Update EVbee DC-80 to the latest version. Monitor for exploitation attempts and review access logs.
The EVbee DC-80 web server on port 8090 lacks authentication, permitting unauthorized sensitive data exposure and file uploads.
The EVbee DC-80 web server on port 8090 lacks authentication, permitting unauthorized sensitive data exposure and file uploads.
---METADATA---
VENDOR: EVbee
PRODUCT: DC-80
AFFECTED_VERSIONS: 0 up to (excluding) 1.5.1
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
The EVbee DC-80 web server on port 8090 lacks authentication, permitting unauthorized sensitive data exposure and file uploads.
Executive Summary:
Critical authentication bypass in the EVbee DC-80 web server allows unauthenticated attackers to access sensitive configuration data and perform arbitrary file uploads.
Vulnerability Details
CVE-ID: CVE-2026-22096
Affected Software: EVbee DC-80
Affected Versions: 0 up to (excluding) 1.5.1
Vulnerability: The web server component of this device fails to enforce any authentication for its management interface (CWE-306). This allows remote attackers to access configuration files containing passwords or upload malicious files to the device.
Business Impact
This vulnerability provides an attacker with administrative-level access to the device. The potential for credential harvesting and the ability to upload files can lead to complete device takeover, which in industrial or charging infrastructure environments, could result in prolonged operational downtime and safety risks.
Remediation Plan
Immediate Action: Update the EVbee DC-80 firmware to version 1.5.1 or later to address the authentication deficiency.
Proactive Monitoring: Monitor the device network traffic for any unexpected file transfers or unauthorized login attempts to the web management interface.
Compensating Controls: Place the management interface behind a VPN or firewall and restrict access to specific, trusted management workstations.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The device's exposure to the network is the primary factor in its exploitability.
Analyst Recommendation
Given the ease of access and the potential for complete device compromise, immediate firmware updates are required. Organizations should ensure that management interfaces for infrastructure hardware like the DC-80 are never exposed to the public internet.
Update EVbee DC-80 to the latest version. Monitor for exploitation attempts and review access logs.
The network diagnosis endpoint on EVbee DC-80 chargers (port 8090) is vulnerable to command injection, enabling unauthenticated remote code execution.
The network diagnosis endpoint on EVbee DC-80 chargers (port 8090) is vulnerable to command injection, enabling unauthenticated remote code execution.
---METADATA---
VENDOR: EVbee
PRODUCT: DC-80
AFFECTED_VERSIONS: 0 up to (excluding) 1.5.1
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The network diagnosis endpoint on EVbee DC-80 chargers (port 8090) is vulnerable to command injection, enabling unauthenticated remote code execution.
Executive Summary:
A critical command injection vulnerability in the EVbee DC-80 charger allows unauthenticated remote attackers to execute arbitrary system commands.
Vulnerability Details
CVE-ID: CVE-2026-22095
Affected Software: EVbee DC-80
Affected Versions: 0 up to (excluding) 1.5.1
Vulnerability: The device exposes a network diagnosis endpoint on port 8090 that fails to sanitize user-supplied input, leading to a command injection vulnerability. This allows an unauthenticated attacker to inject and execute arbitrary system-level commands on the charging station.
Business Impact
The CVSS score of 9.3 reflects the high severity of this flaw, as it allows for full control of the affected charging hardware. An attacker could potentially disrupt charging services, manipulate hardware operation, or use the compromised device as a pivot point to attack other internal network infrastructure.
Remediation Plan
Immediate Action: Update the EVbee DC-80 firmware to version 1.5.1 or later to sanitize input on the network diagnosis endpoint.
Proactive Monitoring: Monitor network traffic directed at port 8090 for unusual diagnostic requests or common command injection patterns (e.g., shell operators like ';', '|', or '&&').
Compensating Controls: If an update cannot be applied immediately, isolate the device from public internet access using a firewall, specifically blocking or restricting access to port 8090.
Exploitation Status
Public Exploit Available: No (No confirmed weaponized exploit or public PoC identified).
Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the vulnerability is highly exploitable due to the lack of authentication, no public evidence of widespread targeting exists at this time.
Analyst Recommendation
This vulnerability represents a significant risk to the integrity of EVbee charging infrastructure. Administrators should prioritize firmware updates to version 1.5.1. Until such updates are applied, it is strongly recommended to restrict network access to the device to prevent unauthorized access to the vulnerable port 8090.
Update EVbee DC-80 to the latest version. Monitor for exploitation attempts and review access logs.
The EVbee Service Android app fails to validate server certificates and uses weak encryption, allowing network-based attackers to intercept and manipu...
The EVbee Service Android app fails to validate server certificates and uses weak encryption, allowing network-based attackers to intercept and manipulate communication with charging stations.
---METADATA---
VENDOR: EVbee
PRODUCT: EVbee Service
AFFECTED_VERSIONS: 0 up to (excluding) 1.4.7.10
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The EVbee Service Android app fails to validate server certificates and uses weak encryption, allowing network-based attackers to intercept and manipulate communication with charging stations.
Executive Summary:
A critical security flaw in the EVbee Service app enables man-in-the-middle attacks, allowing unauthorized access to sensitive charging station communication.
Vulnerability Details
CVE-ID: CVE-2026-22093
Affected Software: EVbee EVbee Service
Affected Versions: 0 up to (excluding) 1.4.7.10
Vulnerability: The application performs improper certificate validation and relies on weak RC4 encryption with a hardcoded key. This allows an unauthenticated attacker positioned on the network path to decrypt, intercept, and manipulate traffic between the mobile application and the EVbee server.
Business Impact
With a CVSS score of 9.5 (Critical), this vulnerability poses a severe risk to service integrity. An attacker could intercept access codes for charging stations, potentially leading to unauthorized usage, service disruption, or further exploitation of the connected infrastructure.
Remediation Plan
Immediate Action: Update the EVbee Service application to version 1.4.7.10 or higher immediately.
Proactive Monitoring: Review network traffic patterns for signs of intercepted or anomalous encrypted communication originating from the EVbee Service application.
Compensating Controls: Advise users to avoid using the application on untrusted or public Wi-Fi networks until the update is applied, as these environments are most susceptible to man-in-the-middle interception.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of July 13, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The reliance on hardcoded encryption keys significantly lowers the barrier for an attacker to perform successful interception.
Analyst Recommendation
The combination of improper certificate validation and weak, hardcoded encryption creates a significant security gap. Users must update the application immediately to ensure that communications are properly secured and that the risk of interception is eliminated.
Update EVbee EVbee Service to the latest version. Monitor for exploitation attempts and review access logs.
Because O+ Connect's IPC service does not authenticate clients, external applications can escalate privileges and perform sensitive actions through th...
Because O+ Connect's IPC service does not authenticate clients, external applications can escalate privileges and perform sensitive actions through the IPC channel
---METADATA---
VENDOR: O+ Connect
PRODUCT: O+ Connect
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
The O+ Connect IPC service fails to authenticate clients, allowing external applications to escalate privileges and perform sensitive actions.
Executive Summary:
An authentication bypass vulnerability in the O+ Connect IPC service allows unauthorized applications to gain elevated privileges, presenting a severe risk to host security.
Vulnerability Details
CVE-ID: CVE-2026-22078
Affected Software: O+ Connect
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability exists because the Inter-Process Communication (IPC) service lacks adequate client authentication. This allows unauthenticated external applications to interact with the service, execute privileged commands, and perform sensitive actions.
Business Impact
This vulnerability creates a critical path for privilege escalation, which could allow an attacker to gain full control over the O+ Connect service and potentially the underlying host. With a CVSS score of 7.3, the risk of unauthorized system manipulation and data exfiltration is high, posing a significant threat to the security posture of the organization.
Remediation Plan
Immediate Action: Apply the latest security patches provided by the vendor to remediate the IPC authentication flaw.
Proactive Monitoring: Audit IPC communication logs and monitor for unauthorized applications attempting to interface with the O+ Connect service.
Compensating Controls: Restrict system-level permissions for non-essential applications to minimize the impact of potential privilege escalation.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 29, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
The ability for external applications to escalate privileges via an unauthenticated IPC channel is a significant security failure. Organizations must treat this as a high-priority remediation item and ensure that all updates addressing IPC authentication are deployed immediately.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Loading arbitrary external URLs through WebView components introduces malicious JS code that can steal arbitrary user tokens
Loading arbitrary external URLs through WebView components introduces malicious JS code that can steal arbitrary user tokens
---METADATA---
VENDOR: OPPO
PRODUCT: OPPO Health
AFFECTED_VERSIONS: 6.2.9
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
A vulnerability in the OPPO Health application allows the loading of arbitrary external URLs within WebView components, leading to potential token theft.
Executive Summary:
The OPPO Health application is vulnerable to arbitrary URL loading in its WebView component, which can be leveraged to steal sensitive user authentication tokens.
Vulnerability Details
CVE-ID: CVE-2026-22072
Affected Software: OPPO Health
Affected Versions: 6.2.9
Vulnerability: The application fails to properly validate input when loading URLs in WebView components. This allows an unauthenticated attacker to inject malicious JavaScript code into the user session, facilitating the theft of sensitive session tokens.
Business Impact
The ability for an attacker to steal user tokens creates a significant risk of unauthorized account access and data compromise. With a CVSS score of 8.3, this vulnerability is critical for mobile users who store sensitive health data within the application, as the impact includes potential leakage of private information.
Remediation Plan
Immediate Action: Check the official OPPO security portal for the latest application update and install version 6.2.9 or later if available.
Proactive Monitoring: Review application access logs for unusual redirects or connections to unauthorized external domains.
Compensating Controls: Use mobile device management (MDM) policies to restrict network traffic for the application if an update is not immediately available.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of August 17, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is tied to input validation failures, which are common targets for automated exploitation attempts in mobile ecosystems.
Analyst Recommendation
Users of the OPPO Health application should remain vigilant and apply updates as soon as they are released by the vendor. The potential for unauthorized access to health data necessitates a swift response to any security updates issued by OPPO.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
ColorOS Assistant has an unauthenticated start-download channel, leading to file path traversal
ColorOS Assistant has an unauthenticated start-download channel, leading to file path traversal
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Executive Summary:
A high-severity vulnerability has been identified in Dell ECS software, which could allow a remote, unauthenticated attacker to compromise affected systems. Successful exploitation could lead to a complete system takeover, resulting in significant data breaches, loss of data integrity, and service disruption. Organizations are urged to apply the vendor-provided security updates immediately to mitigate this critical risk.
Vulnerability Details
CVE-ID: CVE-2026-22273
Affected Software: Dell ECS
Affected Versions: Dell ECS versions 3.x. See vendor advisory for specific affected versions.
Vulnerability: This vulnerability allows for remote code execution due to improper input validation within the management API of the Dell ECS platform. An unauthenticated remote attacker can send a specially crafted HTTP request to a vulnerable API endpoint. This request can bypass security checks and inject arbitrary commands, which are then executed on the underlying operating system with the privileges of the web service account, potentially leading to a full system compromise.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 8.8. A successful exploit could have a severe impact on business operations. An attacker could gain unauthorized access to exfiltrate, modify, or delete vast amounts of sensitive object storage data, leading to regulatory fines and reputational damage. Furthermore, the attacker could cause a denial-of-service condition, rendering critical storage infrastructure unavailable and disrupting business-critical applications that rely on it. The compromised appliance could also serve as a pivot point for launching further attacks against the internal network.
Remediation Plan
Immediate Action: Apply the security updates provided by Dell to all affected ECS systems immediately. After patching, review system and access logs for any anomalous activity or indicators of compromise that may have occurred prior to the update.
Proactive Monitoring: Implement enhanced monitoring on Dell ECS management interfaces. Look for unusual or malformed API requests, unexpected outbound network connections from ECS appliances, and the creation of suspicious processes or files on the system. Correlate access logs with known authorized administrative activity to identify potential unauthorized access.
Compensating Controls: If immediate patching is not feasible, restrict network access to the ECS management interface to a dedicated and trusted administrative network or specific IP addresses. If the interface must be exposed, place it behind a Web Application Firewall (WAF) with rules designed to inspect and block malicious command injection patterns.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of January 25, 2026, there are no known public exploits or reports of this vulnerability being actively exploited in the wild. However, given the high severity and the potential for unauthenticated remote code execution, it is highly probable that threat actors will develop and deploy exploits in the near future.
Analyst Recommendation
Given the high CVSS score of 8.8, this vulnerability presents a critical risk to the organization. Although it is not currently listed on the CISA KEV list, its severity makes it a prime candidate for future inclusion. We strongly recommend that all affected Dell ECS systems are patched on an emergency basis. If patching is delayed for any reason, the compensating controls outlined above must be implemented immediately to reduce the attack surface and mitigate the risk of compromise.