---METADATA---
VENDOR: flycart
PRODUCT: UpsellWP
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
The UpsellWP (checkout-upsell-and-order-bumps) software contains a Blind SQL Injection vulnerability caused by improper neutralization of special elements within SQL commands.

Executive Summary:
The flycart UpsellWP software is vulnerable to a High-severity Blind SQL Injection attack that could result in the unauthorized disclosure of sensitive e-commerce database content.

Vulnerability Details

CVE-ID: CVE-2026-32459

Affected Software: flycart UpsellWP

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: A Blind SQL Injection vulnerability exists in the checkout-upsell-and-order-bumps component of UpsellWP. The software does not correctly handle special elements in SQL commands, allowing an attacker to probe the database and extract information through inference.

Business Impact

A successful exploit could allow an attacker to access sensitive sales data, customer information, and configuration settings. Given the CVSS score of 8.5, this vulnerability presents a high risk to the confidentiality and integrity of the e-commerce environment, potentially leading to data breaches and loss of revenue.

Remediation Plan

Immediate Action: Update the UpsellWP plugin to the latest secure version immediately to patch the SQL injection vulnerability.

Proactive Monitoring: Monitor database performance for latency that might indicate time-based blind SQL injection attempts and review access logs for suspicious query strings.

Compensating Controls: Implement a Web Application Firewall (WAF) to filter malicious SQL input and ensure that database accounts use the principle of least privilege.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 15, 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

This High-severity vulnerability in UpsellWP requires immediate remediation to protect the underlying database from unauthorized access. Administrators should apply the available vendor patch as the primary defense mechanism to ensure the continued security of the e-commerce platform and its data.

---METADATA---
VENDOR: Canon Production Printing
PRODUCT: PRISMAproduction
AFFECTED_VERSIONS: 6.5 or earlier
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
A deserialization of untrusted data vulnerability exists in Canon Production Printing PRISMAproduction version 6.5 and earlier.

Executive Summary:
A deserialization vulnerability in PRISMAproduction could allow an adjacent attacker to achieve unauthorized code execution or system impact.

Vulnerability Details

CVE-ID: CVE-2026-3245

Affected Software: Canon Production Printing PRISMAproduction

Affected Versions: 6.5 or earlier

Vulnerability: This is a deserialization of untrusted data flaw (CWE-502) that allows for the execution of arbitrary code or other malicious operations. The attack vector is identified as adjacent, meaning the attacker must be on the same local network segment.

Business Impact

Successful exploitation allows an attacker to compromise the integrity and availability of the PRISMAproduction system. Given the CVSS score of 7.5, this vulnerability represents a severe threat to production environments, potentially causing significant operational downtime or data loss.

Remediation Plan

Immediate Action: Apply the vendor-provided security updates available through the Canon Production Printing support portal.

Proactive Monitoring: Monitor network traffic for unusual deserialization patterns or unexpected process execution within the PRISMAproduction environment.

Compensating Controls: Implement network segmentation to isolate the PRISMAproduction software from untrusted network segments, limiting the reach of potential adjacent attackers.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of August 3, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Deserialization vulnerabilities are inherently dangerous due to the potential for remote code execution.

Analyst Recommendation

Given the potential for code execution, organizations should prioritize patching their PRISMAproduction software. Ensure that all security advisories from Canon are reviewed and that the recommended updates are tested and deployed in accordance with organizational maintenance windows.

---METADATA---
VENDOR: Cwicly
PRODUCT: Cwicly
AFFECTED_VERSIONS: <= 1.4.4
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A remote code execution vulnerability exists in the Cwicly plugin for WordPress, allowing authenticated users with contributor-level access to execute arbitrary code.

Executive Summary:
An authenticated remote code execution vulnerability in the Cwicly WordPress plugin allows attackers with contributor-level access to compromise the host server.

Vulnerability Details

CVE-ID: CVE-2026-32444

Affected Software: Cwicly

Affected Versions: <= 1.4.4

Vulnerability: This is a code injection vulnerability that allows authenticated users to bypass security controls and execute arbitrary code on the server. The attack requires authenticated access, specifically at the contributor level or higher.

Business Impact

The ability for an authenticated user to execute arbitrary code on the underlying server represents a total system compromise. This allows attackers to install backdoors, steal sensitive site data, or leverage the server for further attacks, potentially leading to significant reputational and operational damage given the high CVSS score of 9.9.

Remediation Plan

Immediate Action: Update the Cwicly plugin to the latest version. If a patch is not yet available, immediately deactivate and remove the plugin from the WordPress installation until a secure version is released.

Proactive Monitoring: Audit WordPress user accounts and capabilities to ensure that no unauthorized users have contributor-level access or higher.

Compensating Controls: Employ a Web Application Firewall (WAF) with rules configured to detect and block common code injection patterns directed at WordPress plugins.

Exploitation Status

Public Exploit Available: No confirmed public weaponized exploit available.

Analyst Notes: As of Aug 18, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The requirement for authenticated access significantly reduces the attack surface compared to unauthenticated remote execution flaws.

Analyst Recommendation

Due to the critical severity and the potential for total system compromise, immediate attention is required. Administrators should verify the current plugin version and apply updates or mitigations without delay to prevent potential abuse by malicious actors with existing low-level site access.

---METADATA---
VENDOR: codepeople
PRODUCT: CP Contact Form with Paypal
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
The CP Contact Form with Paypal (cp-contact-form-with-paypal) software is susceptible to Blind SQL Injection due to improper neutralization of special elements in SQL commands.

Executive Summary:
A High-severity Blind SQL Injection vulnerability in the codepeople CP Contact Form with Paypal plugin allows attackers to potentially access and exfiltrate sensitive database records.

Vulnerability Details

CVE-ID: CVE-2026-32433

Affected Software: codepeople CP Contact Form with Paypal

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability is a Blind SQL Injection located in the cp-contact-form-with-paypal component. It arises from the failure to properly sanitize user inputs used in database operations, enabling attackers to execute unauthorized queries and extract data.

Business Impact

The impact of this vulnerability includes the potential exposure of contact form submissions, transaction details, and user account information. With a CVSS score of 8.5, the risk to the organization's data confidentiality is high, potentially leading to identity theft or the compromise of financial transaction records.

Remediation Plan

Immediate Action: Apply the vendor-provided security patches for CP Contact Form with Paypal immediately to eliminate the injection vulnerability.

Proactive Monitoring: Review application and database logs for any signs of automated scanning or unusual SQL syntax originating from public-facing forms.

Compensating Controls: Restrict database user permissions to the minimum necessary and utilize a Web Application Firewall (WAF) to detect and block SQL injection patterns.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 15, 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

This vulnerability poses a significant threat to any site utilizing the CP Contact Form with Paypal plugin. It is imperative that administrators prioritize the application of the official patch to mitigate the risk of unauthorized database interactions and ensure the security of user-submitted data.

---METADATA---
VENDOR: levelfourdevelopment
PRODUCT: WP EasyCart
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
The levelfourdevelopment WP EasyCart (wp-easycart) software is vulnerable to Blind SQL Injection through improper neutralization of special elements used in SQL commands.

Executive Summary:
WP EasyCart is affected by a High-severity Blind SQL Injection vulnerability that could permit attackers to gain unauthorized access to sensitive e-commerce and customer database information.

Vulnerability Details

CVE-ID: CVE-2026-32422

Affected Software: levelfourdevelopment WP EasyCart

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: A Blind SQL Injection vulnerability exists within the wp-easycart component. This flaw allows an attacker to manipulate database queries by submitting crafted input, bypassing standard security checks to infer the contents of the database through application behavior.

Business Impact

For e-commerce platforms, this vulnerability is particularly critical as it may expose customer payment history, personal identifiable information (PII), and order details. The CVSS score of 8.5 reflects the high potential for data compromise, which could lead to financial loss, legal liabilities, and a total loss of consumer confidence.

Remediation Plan

Immediate Action: Upgrade WP EasyCart to the patched version immediately to close the SQL injection vector and secure the database.

Proactive Monitoring: Regularly audit database access logs and monitor for anomalous response times that could indicate time-based blind SQL injection attempts.

Compensating Controls: Implement strict input validation and use prepared statements where possible, while leveraging a WAF to provide an additional layer of defense against injection attacks.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 15, 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

Given the sensitive nature of e-commerce data handled by WP EasyCart, this High-severity vulnerability must be addressed with the highest urgency. Security teams should ensure that the latest vendor patches are applied across all production environments immediately to safeguard customer and business data.

---METADATA---
VENDOR: David Lingren Media
PRODUCT: Media Library Assistant
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A Blind SQL Injection vulnerability exists in David Lingren Media Library Assistant (media-library-assistant) due to improper neutralization of special elements in SQL commands.

Executive Summary:
The David Lingren Media Library Assistant software contains a High-severity Blind SQL Injection vulnerability that enables unauthorized actors to query the database and exfiltrate sensitive data.

Vulnerability Details

CVE-ID: CVE-2026-32399

Affected Software: David Lingren Media Library Assistant

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The media-library-assistant component is susceptible to Blind SQL Injection. The software fails to adequately sanitize input used in SQL statements, allowing an attacker to execute arbitrary database commands and observe the application's response to reconstruct database contents.

Business Impact

This vulnerability poses a severe threat to the confidentiality of the organization's data assets. Given the CVSS score of 8.5, an attacker could compromise the entire database, leading to the theft of sensitive media metadata, user information, or administrative credentials, which may result in significant reputational damage.

Remediation Plan

Immediate Action: Administrators should immediately update to the most recent version of the Media Library Assistant plugin to address this critical security flaw.

Proactive Monitoring: Enable comprehensive query logging on the database server and monitor for repeated, structured queries that suggest automated exploitation attempts.

Compensating Controls: Utilize a Web Application Firewall (WAF) to intercept and neutralize SQL injection payloads before they reach the vulnerable application component.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 15, 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

This vulnerability represents a high-risk entry point for attackers seeking to compromise database integrity. Organizations should prioritize the deployment of the official security update immediately to mitigate the risk of data loss and unauthorized system access.

---METADATA---
VENDOR: delphiknight
PRODUCT: Geo to Lat
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
The Geo to Lat (geo-to-lat) software contains a Blind SQL Injection vulnerability due to improper neutralization of special elements within SQL commands.

Executive Summary:
The delphiknight Geo to Lat software is vulnerable to a High-severity Blind SQL Injection flaw that could allow an attacker to extract sensitive information from the backend database.

Vulnerability Details

CVE-ID: CVE-2026-32368

Affected Software: delphiknight Geo to Lat

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability is a Blind SQL Injection residing in the geo-to-lat component. It occurs when the application fails to properly sanitize user-supplied input before using it in a database query, allowing an attacker to infer data through boolean or time-based responses.

Business Impact

A successful exploit of this vulnerability could lead to the unauthorized extraction of sensitive data, including user credentials and proprietary site information. With a CVSS score of 8.5, this High-severity flaw represents a significant risk to data confidentiality and integrity, potentially resulting in regulatory non-compliance and loss of customer trust.

Remediation Plan

Immediate Action: Apply the latest security patches provided by delphiknight immediately to remediate the underlying SQL injection flaw.

Proactive Monitoring: Implement database activity monitoring to detect unusual query patterns and review application logs for suspicious parameters or high volumes of Boolean-based requests.

Compensating Controls: Deploy a Web Application Firewall (WAF) with updated SQL injection protection rules to filter and block malicious traffic targeting this vulnerability.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 15, 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 High-severity rating of this SQL injection vulnerability necessitates immediate attention from security administrators. It is strongly recommended that the primary remediation—applying the vendor-supplied patch—be completed without delay to prevent unauthorized database access and potential data exfiltration.

---METADATA---
VENDOR: Rob Felty
PRODUCT: Collapsing Categories (WordPress Plugin)
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
The Collapsing Categories plugin for WordPress is vulnerable to Blind SQL Injection, which could lead to unauthorized database access and information disclosure.

Executive Summary:
A high-severity Blind SQL Injection vulnerability in the Collapsing Categories WordPress plugin allows attackers to compromise database security and extract sensitive site information.

Vulnerability Details

CVE-ID: CVE-2026-32366

Affected Software: robfelty Collapsing Categories (collapsing-categories)

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The plugin is susceptible to Blind SQL Injection due to inadequate input sanitization in its database query logic. This allows an attacker to send crafted requests that manipulate SQL execution, facilitating the extraction of sensitive data through inference.

Business Impact

The CVSS score of 8.5 highlights the critical nature of this flaw. Successful exploitation could result in the theft of administrative credentials and sensitive site data, potentially leading to unauthorized content modification or complete site defacement.

Remediation Plan

Immediate Action: Update the Collapsing Categories plugin to the latest available version immediately to mitigate the SQL Injection risk.

Proactive Monitoring: Review web server logs for repetitive requests to the plugin's endpoints that appear to be testing logical conditions or inducing time delays.

Compensating Controls: Implement a robust Web Application Firewall (WAF) to filter out common SQL Injection attack patterns and restrict database user privileges to the minimum necessary.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 15, 2026, there is no public information indicating active exploitation. However, automated vulnerability scanners often target plugins with these types of flaws.

Analyst Recommendation

Immediate remediation via patching is the only effective way to address this high-severity vulnerability. Administrators should prioritize this update to ensure the continued security of their WordPress installation and its underlying data.

---METADATA---
VENDOR: Mullvad
PRODUCT: Mullvad VPN
AFFECTED_VERSIONS: < 2026.2-beta1
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Mullvad VPN is vulnerable to local privilege escalation and path hijacking due to improper search path and privilege management.

Executive Summary:
A critical privilege escalation and security validation flaw in the Mullvad VPN client could allow a local attacker to achieve full system compromise.

Vulnerability Details

CVE-ID: CVE-2026-32323

Affected Software: Mullvad VPN

Affected Versions: < 2026.2-beta1

Vulnerability: This vulnerability involves an uncontrolled search path (CWE-427), insufficient verification of data authenticity (CWE-345), and improper privilege management (CWE-269), requiring an authenticated local user to initiate.

Business Impact

A local attacker could exploit these flaws to gain elevated privileges on the host system, potentially leading to total system compromise, data theft, or persistence. With a CVSS score of 7.3, this represents a significant risk for any workstation or server where the VPN client is installed.

Remediation Plan

Immediate Action: Update the Mullvad VPN client to version 2026.2-beta1 or later immediately to resolve the identified search path and validation issues.

Proactive Monitoring: Monitor system logs for unauthorized attempts to escalate privileges or unexpected modification of application binary paths.

Compensating Controls: Ensure that local user accounts have the principle of least privilege applied and that host-based integrity monitoring is active.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 19, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The complexity of the attack requires local access, which reduces the immediate risk profile for remote environments.

Analyst Recommendation

Users and administrators should prioritize updating the Mullvad VPN client across all managed endpoints. Failure to patch allows local users to potentially bypass security controls and gain administrative-level access to the underlying operating system.

---METADATA---
VENDOR: Ella
PRODUCT: Ella Core (5G Core)
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
Ella Core, a 5G core for private networks, contains a security vulnerability that could impact the availability or integrity of private cellular communications.

Executive Summary:
A high-severity vulnerability in the Ella Core 5G platform poses a critical risk to the security and operational stability of private 5G networks.

Vulnerability Details

CVE-ID: CVE-2026-32319

Affected Software: Ella Core

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability exists within the Ella Core 5G network stack. While specific technical details are limited, the high CVSS score suggests an attacker could potentially disrupt network services or intercept communication metadata within the private 5G environment.

Business Impact

With a CVSS score of 7.5, this flaw could lead to the disruption of mission-critical communications in industrial or enterprise settings. Exploitation could result in network downtime, unauthorized access to network management functions, and potential espionage within the private cellular infrastructure.

Remediation Plan

Immediate Action: Coordinate with the vendor to apply the latest security patches to the Ella Core 5G infrastructure as soon as possible.

Proactive Monitoring: Monitor network signaling traffic for anomalies and review administrative access logs for the 5G core management interface.

Compensating Controls: Isolate the 5G core management network from the public internet and use strong network segmentation to limit the impact of a potential breach.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 15, 2026, there is no public information indicating active exploitation. Because this affects critical infrastructure components, the impact of a successful attack is exceptionally high.

Analyst Recommendation

Security teams managing private 5G networks must treat this as a critical priority. Immediate patching and the implementation of robust network isolation are essential to protect the integrity of the cellular core.

---METADATA---
VENDOR: OneUptime
PRODUCT: OneUptime
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
OneUptime, an observability and monitoring platform, contains a vulnerability that could allow attackers to interfere with service monitoring or access sensitive configuration data.

Executive Summary:
A high-severity vulnerability in the OneUptime monitoring platform could allow an attacker to compromise the visibility and integrity of critical online services.

Vulnerability Details

CVE-ID: CVE-2026-32308

Affected Software: OneUptime

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability resides within the OneUptime solution, a platform designed for managing service uptime. The flaw likely allows an attacker to bypass standard access controls to view or modify monitoring configurations, potentially masking service outages or intercepting alert data.

Business Impact

The CVSS score of 7.6 indicates a high-risk scenario where the reliability of an organization's monitoring infrastructure is compromised. An exploit could lead to undetected downtime, loss of operational visibility, and the exposure of infrastructure metadata, causing significant reputational and financial damage.

Remediation Plan

Immediate Action: Immediately update the OneUptime platform to the latest available version to address the identified security flaw.

Proactive Monitoring: Audit user activity logs within the OneUptime dashboard for unauthorized configuration changes or unusual administrative logins.

Compensating Controls: Utilize a Web Application Firewall (WAF) to filter incoming traffic to the OneUptime management interface and implement multi-factor authentication (MFA) for all users.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 15, 2026, there is no public information indicating active exploitation of this vulnerability. However, the importance of monitoring tools makes them high-value targets for attackers seeking to hide their tracks.

Analyst Recommendation

Organizations relying on OneUptime for operational visibility must treat this vulnerability as a high priority. Apply the vendor-provided security updates immediately to ensure the continued integrity of your monitoring and alerting pipeline.

---METADATA---
VENDOR: OneUptime
PRODUCT: OneUptime
AFFECTED_VERSIONS: Prior to 10.0.23
---END_METADATA---

Description Summary:
OneUptime versions prior to 10.0.23 are vulnerable to SQL injection in the telemetry aggregation API due to improper interpolation of user-controlled parameters into ClickHouse queries.

Executive Summary:
An authenticated attacker can execute arbitrary SQL queries within ClickHouse, leading to full database compromise and potential remote code execution in OneUptime environments.

Vulnerability Details

CVE-ID: CVE-2026-32306

Affected Software: OneUptime

Affected Versions: Prior to 10.0.23

Vulnerability: This vulnerability involves a SQL injection flaw where the telemetry aggregation API accepts unsanitized parameters and appends them directly to ClickHouse SQL queries. An authenticated user can bypass intended query logic to perform unauthorized data modifications or read sensitive telemetry data across all tenants.

Business Impact

A successful exploit poses a critical risk to data confidentiality and integrity, as an attacker could gain access to sensitive telemetry data belonging to all system tenants. Given the CVSS score of 9.9, the impact is severe, potentially allowing for remote code execution via ClickHouse table functions and total system takeover. This could result in significant service disruption and loss of customer trust.

Remediation Plan

Immediate Action: Update OneUptime to version 10.0.23 or later immediately to apply necessary input validation and parameterized query bindings.

Proactive Monitoring: Review ClickHouse logs for unusual query patterns, specifically those involving the .append() method or unexpected table function calls.

Compensating Controls: Implement strict network-level access controls to the ClickHouse interface and utilize a Web Application Firewall (WAF) to filter suspicious API parameters.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the critical nature of the flaw and the ease of SQL injection, the potential for exploitation is extremely high for unpatched systems.

Analyst Recommendation

The severity of this SQL injection vulnerability cannot be overstated, as it grants deep access to the underlying data infrastructure. Organizations using OneUptime must prioritize the update to version 10.0.23 immediately. Failure to remediate this flaw exposes the entire telemetry dataset and the host environment to complete compromise.

---METADATA---
VENDOR: Locutus
PRODUCT: Locutus
AFFECTED_VERSIONS: Prior to 3.0.14
---END_METADATA---

Description Summary:
The Locutus library prior to version 3.0.14 is vulnerable to arbitrary code execution because the create_function implementation passes unsanitized input to the Function constructor.

Executive Summary:
Applications using the Locutus library are at risk of arbitrary code execution if they pass user-controlled data to the vulnerable create_function utility.

Vulnerability Details

CVE-ID: CVE-2026-32304

Affected Software: Locutus

Affected Versions: Prior to 3.0.14

Vulnerability: In version 3.x, the create_function(args, code) utility directly passes its parameters to the new Function() constructor without any sanitization. This allows an unauthenticated attacker to inject and execute arbitrary JavaScript code if the application uses this function with external input.

Business Impact

With a CVSS score of 9.8, this vulnerability allows for remote code execution in the context of the application using the library. If used in a server-side Node.js environment, this could lead to a full server compromise. In a client-side environment, it could lead to widespread Cross-Site Scripting (XSS) and data theft.

Remediation Plan

Immediate Action: Update the Locutus library to version 3.0.14 or later, where the dangerous use of the Function constructor has been addressed.

Proactive Monitoring: Audit source code to identify any instances where create_function is called using data derived from user input (e.g., URL parameters, form fields).

Compensating Controls: Implement a strict Content Security Policy (CSP) to disallow unsafe-eval, which can prevent the execution of code generated via the Function constructor.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 13, 2026, there is no public information indicating active exploitation. This vulnerability is a regression or a similar pattern to previous flaws in the library, making it a known target for researchers.

Analyst Recommendation

Developers using Locutus must immediately update to version 3.0.14. Beyond patching, it is strongly recommended to avoid using functions that dynamically generate code from strings, as these are inherently difficult to secure. Prioritize this update to prevent potential RCE or high-impact XSS attacks.

---METADATA---
VENDOR: OpenClaw
PRODUCT: OpenClaw
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
The OpenClaw personal AI assistant is vulnerable to a security flaw that could allow for unauthorized interactions or data exposure.

Executive Summary:
The OpenClaw personal AI assistant contains a high-severity vulnerability that could lead to unauthorized access or the compromise of user-specific AI data.

Vulnerability Details

CVE-ID: CVE-2026-32302

Affected Software: OpenClaw Personal AI Assistant

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects the OpenClaw AI assistant framework. While the specific mechanism is not detailed, the high CVSS score suggests an unauthenticated or low-privileged attacker could potentially manipulate the assistant's logic or access private user data.

Business Impact

The impact of this vulnerability is substantial, as reflected by its CVSS score of 8.1. A successful exploit could result in the exposure of sensitive personal information handled by the AI or allow an attacker to execute unauthorized commands, leading to a complete loss of confidentiality and integrity for the affected user profile.

Remediation Plan

Immediate Action: Apply the latest security updates provided by the OpenClaw maintainers to all deployed instances of the assistant.

Proactive Monitoring: Monitor API logs and assistant interaction history for anomalous requests or unexpected behavioral changes in the AI's responses.

Compensating Controls: Restrict network access to the OpenClaw interface using a VPN or firewall to ensure only trusted users can interact with the service.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 15, 2026, there is no public information indicating active exploitation of this vulnerability. The high severity score suggests that the technical barrier to entry for exploitation may be relatively low.

Analyst Recommendation

Given the high CVSS score of 8.1, this vulnerability requires immediate attention. Security teams should ensure that all personal AI assistant deployments are updated to the latest version to prevent unauthorized data access and maintain the privacy of the AI ecosystem.

---METADATA---
VENDOR: Centrifugo
PRODUCT: Centrifugo
AFFECTED_VERSIONS: Prior to 6.7.0
---END_METADATA---

Description Summary:
Centrifugo versions prior to 6.7.0 are vulnerable to Server-Side Request Forgery (SSRF) when using dynamic JWKS endpoints, allowing unauthenticated attackers to trigger outbound HTTP requests.

Executive Summary:
Unauthenticated attackers can exploit an SSRF vulnerability in Centrifugo to scan internal networks or access sensitive metadata services by manipulating JWT claims.

Vulnerability Details

CVE-ID: CVE-2026-32301

Affected Software: Centrifugo

Affected Versions: Prior to 6.7.0

Vulnerability: This is an unauthenticated SSRF vulnerability triggered during the JWT verification process. When Centrifugo is configured to use dynamic JWKS URLs, an attacker can craft a JWT with malicious iss or aud claims that are interpolated into the fetch URL, forcing the server to make requests to attacker-controlled internal or external destinations.

Business Impact

With a CVSS score of 9.3, this vulnerability poses a significant risk to internal infrastructure. Attackers can use the Centrifugo server as a proxy to bypass firewalls, conduct internal port scanning, or interact with sensitive internal services like cloud metadata APIs. This can lead to further credential theft and lateral movement within the network.

Remediation Plan

Immediate Action: Update Centrifugo to version 6.7.0 or later, which implements proper validation for interpolated JWKS URL variables.

Proactive Monitoring: Review outbound network logs from Centrifugo instances for requests to unexpected IP addresses or internal service endpoints.

Compensating Controls: Implement strict egress filtering on the Centrifugo host to prevent it from initiating connections to internal network segments or unauthorized external domains.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 13, 2026, there is no public information indicating active exploitation of this vulnerability. SSRF vulnerabilities are particularly dangerous in cloud environments where metadata services are accessible via local HTTP requests.

Analyst Recommendation

Centrifugo administrators should prioritize the update to version 6.7.0. If dynamic JWKS endpoints are utilized, the risk is immediate and severe. Ensure that the Centrifugo service is running with the least privilege necessary and that network-level protections are in place to limit the scope of potential SSRF attacks.

---METADATA---
VENDOR: Angeet
PRODUCT: ES3 KVM
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
The Angeet ES3 KVM contains an OS command injection vulnerability in the 'cfg.lua' script, allowing authenticated attackers to execute arbitrary system commands.

Executive Summary:
The Angeet ES3 KVM switch is vulnerable to a critical command injection flaw that allows authenticated users to execute OS-level commands and gain full control of the device.

Vulnerability Details

CVE-ID: CVE-2026-32298

Affected Software: Angeet ES3 KVM

Affected Versions: See vendor advisory

Vulnerability: The 'cfg.lua' script fails to properly sanitize user-supplied variables. An authenticated attacker can exploit this lack of validation to inject and execute arbitrary OS-level commands on the underlying operating system of the KVM device.

Business Impact

A compromise of a KVM (Keyboard, Video, Mouse) switch provides an attacker with direct access to the servers connected to the device. With a CVSS score of 9.1, this vulnerability poses a severe risk of data theft and hardware-level manipulation within a data center or server room environment.

Remediation Plan

Immediate Action: Apply the latest firmware update from Angeet for the ES3 KVM and change all administrative passwords immediately.

Proactive Monitoring: Monitor the KVM's management interface for unusual activity and review any available system logs for evidence of shell command execution.

Compensating Controls: Place the KVM management interface on a dedicated, isolated management network and restrict access to authorized administrators only.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Mar 17, 2026, there is no public information indicating active exploitation of this vulnerability. Command injection in KVM devices is a high-impact flaw due to the privileged position these devices hold in infrastructure.

Analyst Recommendation

Administrators should prioritize updating the firmware of all Angeet ES3 KVM units. Because this vulnerability allows for full OS-level access, it could be used as a pivot point for broader network attacks if left unpatched.

---METADATA---
VENDOR: Angeet
PRODUCT: ES3 KVM
AFFECTED_VERSIONS: See vendor advisory for affected versions
---END_METADATA---

Description Summary:
The Angeet ES3 KVM allows a remote, unauthenticated attacker to write arbitrary files, including configuration files or system binaries, leading to potential system takeover.

Executive Summary:
The Angeet ES3 KVM is vulnerable to a critical remote, unauthenticated arbitrary file write vulnerability that could allow an attacker to gain full control over the device.

Vulnerability Details

CVE-ID: CVE-2026-32297

Affected Software: Angeet ES3 KVM

Affected Versions: See vendor advisory for affected versions

Vulnerability: This vulnerability allows a remote, unauthenticated attacker to write arbitrary files to the Angeet ES3 KVM system. By exploiting an insecure file upload or writing function, an attacker can overwrite critical system binaries or configuration files, effectively bypassing all authentication mechanisms.

Business Impact

The impact of this vulnerability is severe, as it allows for a complete compromise of the KVM (Keyboard, Video, Mouse) switch. An attacker could gain persistent access to the device, intercept sensitive console data, or move laterally into the connected server infrastructure, causing massive data breaches and operational downtime.

Remediation Plan

Immediate Action: Immediately update the Angeet ES3 KVM firmware to the latest version. If a patch is unavailable, disconnect the device from the network or place it behind a restrictive firewall.

Proactive Monitoring: Monitor network traffic for unauthorized file transfer protocols targeting the KVM device and review system integrity for modified binaries.

Compensating Controls: Disable any unnecessary remote management features and ensure the device is only accessible through a dedicated, isolated management network or a secure VPN.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 19, 2026, there is no public information indicating active exploitation of this vulnerability. However, because this flaw allows unauthenticated remote access, it is an extremely high-value target for attackers.

Analyst Recommendation

This vulnerability is of the highest priority due to its unauthenticated remote nature and the potential for full system compromise. Administrators must apply the primary firmware update immediately or isolate the device from the network to prevent catastrophic exploitation.

---METADATA---
VENDOR: Deno Land
PRODUCT: Deno
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A vulnerability in the Deno runtime environment could allow for unauthorized code execution or security sandbox escape during the processing of JavaScript or TypeScript.

Executive Summary:
A high-severity vulnerability in the Deno runtime poses a significant risk of unauthorized execution or system compromise for applications utilizing this runtime.

Vulnerability Details

CVE-ID: CVE-2026-32260

Affected Software: Deno Land Deno Runtime

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability resides within the Deno runtime, a secure environment for JavaScript and TypeScript. The flaw may allow an attacker to bypass standard security restrictions or execute arbitrary code within the context of the runtime, potentially leading to a sandbox escape.

Business Impact

A successful exploit could lead to the complete compromise of applications running on the Deno platform. This includes unauthorized data access, system-level execution, and potential lateral movement within the hosting environment. The CVSS score of 8.1 reflects a high severity, indicating that the impact on confidentiality, integrity, and availability is substantial.

Remediation Plan

Immediate Action: Update the Deno runtime to the latest patched version immediately to ensure all security fixes are applied.

Proactive Monitoring: Review application logs for unexpected crashes or anomalous system calls that may indicate an attempted runtime exploit.

Compensating Controls: Use containerization and least-privilege execution environments to limit the potential blast radius if the runtime is compromised.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 14, 2026, there is no public information indicating active exploitation of this vulnerability. The complexity of runtime vulnerabilities often delays public exploit releases, but the risk remains high for unpatched systems.

Analyst Recommendation

The Deno runtime is often chosen for its security-first approach; therefore, a high-severity vulnerability in its core execution engine requires urgent attention. We strongly recommend that development teams update their Deno environments to the latest version immediately to maintain the security posture of their applications.

---METADATA---
VENDOR: Kan
PRODUCT: Kan Project Management Tool
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
The Kan open-source project management tool is affected by a high-severity vulnerability that may allow for significant unauthorized access or data compromise.

Executive Summary:
The Kan project management tool contains a high-severity vulnerability that poses a significant risk to organizational data integrity and system availability.

Vulnerability Details

CVE-ID: CVE-2026-32255

Affected Software: Kan Project Management Tool

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects Kan, an open-source project management application. While specific technical details regarding the flaw (such as the specific vulnerable parameter) are limited in the current summary, the high CVSS score suggests a significant weakness, potentially involving remote access or data manipulation by an attacker.

Business Impact

A successful exploit could lead to the unauthorized disclosure of sensitive project data, loss of intellectual property, or complete disruption of project management workflows. With a CVSS score of 8.6, the severity is classified as High, indicating that a successful attack could have devastating consequences for business operations and data confidentiality.

Remediation Plan

Immediate Action: Apply the latest security patches or version updates provided by the Kan open-source maintainers immediately to close the vulnerability.

Proactive Monitoring: Review application logs for unauthorized login attempts, unusual data export activities, or modifications to project permissions.

Compensating Controls: Deploy a Web Application Firewall (WAF) to filter suspicious traffic and restrict access to the project management interface to known internal IP addresses via a VPN.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of March 19, 2026, there is no public information indicating active exploitation of this vulnerability. However, the high CVSS score of 8.6 suggests that once technical details are released, the vulnerability will be a prime target for attackers.

Analyst Recommendation

The severity of this vulnerability (CVSS 8.6) demands an urgent response from IT administrators. All instances of the Kan project management tool should be updated to the latest secure version immediately to prevent potential remote exploitation and data theft.

---METADATA---
VENDOR: Chartbrew
PRODUCT: Chartbrew
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---

Description Summary:
A vulnerability exists in Chartbrew, an open-source web application for database and API data visualization.

Executive Summary:
A high-severity security vulnerability in Chartbrew requires immediate attention to protect database and API connectivity.

Vulnerability Details

CVE-ID: CVE-2026-32252

Affected Software: Chartbrew

Affected Versions: See vendor advisory

Vulnerability: The specific nature of this vulnerability is pending full disclosure; however, it affects the core application responsible for connecting to databases and APIs.

Business Impact

The CVSS score of 7.7 indicates a high-risk vulnerability. Since Chartbrew interfaces directly with databases and APIs, a successful exploit could lead to unauthorized data access, potential data manipulation, or exposure of sensitive credentials, severely impacting organizational data integrity.

Remediation Plan

Immediate Action: Review the official Chartbrew security advisory and apply the latest security updates or patches provided by the vendor.

Proactive Monitoring: Monitor database and API access logs for anomalous queries or unauthorized connection attempts.

Compensating Controls: Ensure the Chartbrew application is isolated behind a secure network perimeter and that database credentials are scoped with the principle of least privilege.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Apr 12, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the application, the potential for exploitation is high.

Analyst Recommendation

Administrators should immediately verify their Chartbrew version and apply available updates. Given the application's access to sensitive data, proactive patching is essential to maintain security posture.

---METADATA---
VENDOR: OpenEMR
PRODUCT: OpenEMR
AFFECTED_VERSIONS: Prior to 8.0.0.2
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
OpenEMR versions prior to 8.0.0.2 contain a command injection vulnerability in the backup functionality, allowing authenticated attackers to execute arbitrary system commands.

Executive Summary:
A critical command injection vulnerability in OpenEMR allows authenticated attackers to execute arbitrary system commands, potentially leading to full server compromise.

Vulnerability Details

CVE-ID: CVE-2026-32238

Affected Software: OpenEMR

Affected Versions: Prior to 8.0.0.2

Vulnerability: The vulnerability is a command injection flaw within the application's backup functionality caused by insufficient input validation. An authenticated attacker can leverage this flaw to execute arbitrary commands at the system level.

Business Impact

Successful exploitation grants an attacker the ability to execute commands with the privileges of the web server, leading to complete system compromise, data exfiltration, or the disruption of critical medical records services. With a CVSS score of 9.1, this vulnerability represents an extreme risk to the availability and confidentiality of the electronic health records (EHR) platform.

Remediation Plan

Immediate Action: Update the OpenEMR installation to version 8.0.0.2 or higher to resolve the input validation flaw.

Proactive Monitoring: Review application logs for anomalous system calls or unexpected processes being spawned by the web server user.

Compensating Controls: Ensure that the OpenEMR application is running with the principle of least privilege, restricting the web server's ability to execute shell commands.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Mar 19, 2026, there is no public information indicating active exploitation of this vulnerability. However, the high severity rating necessitates prompt patching to prevent potential unauthorized access.

Analyst Recommendation

Given the critical nature of the vulnerability and the potential for full system compromise, organizations should treat this update as a high-priority task. Apply the provided patch immediately to secure the environment against potential command injection attacks.