Race in Updater in Google Chrome on Mac prior to 149
Description
Race in Updater in Google Chrome on Mac prior to 149
AI Analyst Comment
Remediation
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Search and filter 18466 vulnerabilities with AI analyst insights
Race in Updater in Google Chrome on Mac prior to 149
Race in Updater in Google Chrome on Mac prior to 149
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Heap buffer overflow in WebRTC in Google Chrome on Windows prior to 149
Heap buffer overflow in WebRTC in Google Chrome on Windows prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A heap buffer overflow vulnerability exists in the WebRTC component of Google Chrome on Windows, potentially allowing for arbitrary code execution.
Executive Summary:
A heap buffer overflow in the Google Chrome WebRTC component poses a significant risk of remote code execution on affected Windows systems.
Vulnerability Details
CVE-ID: CVE-2026-12466
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is a heap buffer overflow vulnerability located within the WebRTC implementation of the browser. It likely requires a user to interact with malicious web content to trigger the memory corruption flaw.
Business Impact
A successful exploit of this vulnerability could allow an attacker to execute arbitrary code within the context of the browser. Given the CVSS score of 8.8, this represents a high-severity risk that could lead to full system compromise, data exfiltration, or the installation of persistent malware on user endpoints.
Remediation Plan
Immediate Action: Update all instances of Google Chrome on Windows to version 149 or later immediately.
Proactive Monitoring: Monitor endpoint logs for suspicious child processes spawned by the Google Chrome browser or unusual network activity following web browsing sessions.
Compensating Controls: Ensure that Endpoint Detection and Response (EDR) solutions are active to identify and block memory-based exploitation attempts.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 18, 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
Browser-based vulnerabilities are frequent targets for threat actors seeking initial access. IT administrators must prioritize the deployment of the latest Chrome security updates to all managed endpoints to mitigate the risk of arbitrary code execution.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Race in Safe Browsing in Google Chrome on Mac prior to 149
Race in Safe Browsing in Google Chrome on Mac prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A race condition vulnerability exists within the Safe Browsing component of Google Chrome for macOS, potentially allowing for memory corruption or bypass of security features.
Executive Summary:
A race condition in the Google Chrome Safe Browsing component on macOS presents a high-severity risk of unauthorized system interaction.
Vulnerability Details
CVE-ID: CVE-2026-12454
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is a race condition vulnerability within the Safe Browsing module. The vulnerability requires a local attacker to potentially leverage timing discrepancies to gain unauthorized access or manipulate browser security states.
Business Impact
Successful exploitation of this race condition could lead to a compromise of browser security controls, potentially exposing the user to malicious content that the Safe Browsing feature is designed to block. Given the CVSS score of 8.3, this flaw poses a significant risk to organizational data integrity and endpoint security if leveraged to deliver further payloads.
Remediation Plan
Immediate Action: Update Google Chrome to version 149 or later immediately to incorporate the necessary race condition fixes.
Proactive Monitoring: Monitor endpoint security logs for unusual browser process behavior or unauthorized attempts to modify browser configurations.
Compensating Controls: Ensure that endpoint protection software is active and configured to detect and block suspicious code execution originating from web browser processes.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 20, 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 vulnerability represents a significant risk to the security posture of macOS workstations. Administrators should prioritize the deployment of the latest Google Chrome updates to all managed devices to mitigate the risk of exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Downloads in Google Chrome on Android prior to 149
Use after free in Downloads in Google Chrome on Android prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A use-after-free vulnerability in the Downloads component of Google Chrome on Android allows potential memory corruption and system instability.
Executive Summary:
A high-severity use-after-free vulnerability in Google Chrome’s Android download manager could allow for remote code execution.
Vulnerability Details
CVE-ID: CVE-2026-12452
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability is a use-after-free flaw within the download management system of the browser. An unauthenticated attacker could exploit this by tricking a user into downloading a malicious file, leading to memory corruption.
Business Impact
The CVSS score of 8.8 highlights the severity of this issue. Since the vulnerability resides in the download handler, it poses a direct risk to mobile devices, potentially allowing attackers to gain persistence or access sensitive files on the Android device.
Remediation Plan
Immediate Action: Update Google Chrome on all Android devices to version 149 or later via the Google Play Store.
Proactive Monitoring: Review logs for unusual download activity or failed file-handling operations on corporate mobile devices.
Compensating Controls: Implement mobile device management (MDM) policies to restrict unauthorized file downloads and enforce strict application sandboxing.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 18, 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
Mobile endpoints are often overlooked in patch management cycles. It is critical to ensure all Android devices are updated to version 149 to prevent attackers from leveraging this download-based vulnerability to compromise mobile assets.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Inappropriate implementation in WebView in Google Chrome on Android prior to 149
Inappropriate implementation in WebView in Google Chrome on Android prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome (Android WebView)
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
An inappropriate implementation vulnerability exists in the WebView component of Google Chrome on Android versions prior to 149.
Executive Summary:
A high-severity implementation flaw in Google Chrome’s Android WebView could lead to unauthorized access or security bypass for applications relying on the browser engine.
Vulnerability Details
CVE-ID: CVE-2026-12448
Affected Software: Google Chrome (Android WebView)
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is an implementation error within the WebView component, which allows applications to display web content. An attacker could potentially leverage this flaw to bypass security controls, though the specific attack vector typically requires interaction with a malicious web resource.
Business Impact
With a CVSS score of 8.8, this vulnerability is critical for organizations that utilize WebView in custom Android applications. Successful exploitation could allow an attacker to bypass sandbox protections, potentially leading to unauthorized access to user data or malicious code execution within the context of the vulnerable application.
Remediation Plan
Immediate Action: Update the Google Chrome / WebView component to version 149 or later via the Google Play Store or system update channels.
Proactive Monitoring: Monitor for anomalous application crashes or unexpected behavior in Android applications that utilize the WebView component.
Compensating Controls: Ensure that applications using WebView implement strict Content Security Policies (CSP) to mitigate potential web-based attacks.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 18, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the ubiquity of WebView, the potential for widespread exploitation is high.
Analyst Recommendation
Organizations must prioritize updating all Android devices and applications that rely on the WebView component. Regular updates to the Chrome browser engine are the only effective method to mitigate this implementation-level vulnerability.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Heap buffer overflow in WebRTC in Google Chrome prior to 149
Heap buffer overflow in WebRTC in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A heap buffer overflow vulnerability in the WebRTC component of Google Chrome could lead to remote code execution.
Executive Summary:
A critical heap buffer overflow in Google Chrome’s WebRTC implementation presents a substantial risk of remote code execution.
Vulnerability Details
CVE-ID: CVE-2026-12447
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability is a heap buffer overflow within the WebRTC subsystem, which handles real-time communication. An unauthenticated attacker can trigger this overflow by sending specially crafted packets, potentially leading to arbitrary code execution.
Business Impact
With a CVSS score of 8.8, this vulnerability is highly dangerous as it affects the WebRTC stack, which is frequently used for modern communication tools. Successful exploitation could lead to total system compromise, bypassing standard browser security boundaries.
Remediation Plan
Immediate Action: Update all instances of Google Chrome to version 149 or higher immediately.
Proactive Monitoring: Monitor for unexpected network traffic or spikes in WebRTC-related service usage that may indicate exploitation.
Compensating Controls: Use a network-level firewall or Web Application Firewall to inspect and filter suspicious traffic patterns associated with WebRTC.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 18, 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
Heap buffer overflows are classic vectors for remote code execution. Given the ubiquity of WebRTC, it is imperative that all browser instances are updated to version 149 immediately to close this critical security gap.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Web Authentication in Google Chrome prior to 149
Use after free in Web Authentication in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A use-after-free vulnerability in the Web Authentication component of Google Chrome allows potential attackers to compromise browser security.
Executive Summary:
A high-severity use-after-free vulnerability in Google Chrome’s Web Authentication module could allow attackers to execute arbitrary code.
Vulnerability Details
CVE-ID: CVE-2026-12443
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This flaw is a use-after-free vulnerability within the Web Authentication API. An unauthenticated attacker can exploit this by directing a user to a malicious site, potentially leading to memory corruption and code execution.
Business Impact
The CVSS score of 8.8 reflects the high potential for system-level impact. Exploitation of the Web Authentication component could bypass critical security controls, potentially leading to unauthorized access to sensitive web applications and services.
Remediation Plan
Immediate Action: Apply the latest security updates provided by Google to move to Chrome version 149 or later.
Proactive Monitoring: Monitor network traffic for unusual authentication attempts or patterns consistent with browser-based exploitation.
Compensating Controls: Utilize endpoint detection and response (EDR) solutions to identify and block suspicious process spawning originating from the browser.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 18, 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
Authentication modules are high-value targets for attackers. Organizations must prioritize patching this vulnerability to prevent potential session hijacking or persistent access gained through memory corruption.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Passwords in Google Chrome on Android prior to 149
Use after free in Passwords in Google Chrome on Android prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A use-after-free vulnerability in the password management component of Google Chrome on Android may lead to unauthorized access or system instability.
Executive Summary:
A critical use-after-free vulnerability in Google Chrome on Android poses a significant risk to user credentials and device security.
Vulnerability Details
CVE-ID: CVE-2026-12442
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability involves a use-after-free condition within the password management subsystem. An unauthenticated attacker could trigger this flaw to achieve code execution or sensitive information disclosure via a malicious web request.
Business Impact
With a CVSS score of 8.8, this vulnerability represents a severe threat to mobile endpoint security. Compromise of the password manager could lead to the exposure of stored corporate credentials, resulting in unauthorized access to internal systems and potential data breaches.
Remediation Plan
Immediate Action: Update Google Chrome on all Android devices to version 149 or later via the Google Play Store.
Proactive Monitoring: Monitor mobile device management (MDM) platforms for outdated browser versions and ensure all devices are running patched software.
Compensating Controls: Enforce organizational policies requiring the use of enterprise-grade password managers rather than browser-native storage where possible.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 18, 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
Mobile security is a critical vector for corporate data access. Security teams should mandate an immediate update to version 149 for all Android devices to mitigate the risk of credential theft and remote exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in File Input in Google Chrome on Linux prior to 149
Use after free in File Input in Google Chrome on Linux prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A use-after-free vulnerability exists in the File Input component of Google Chrome on Linux, potentially allowing for arbitrary code execution.
Executive Summary:
A high-severity use-after-free vulnerability in Google Chrome on Linux exposes users to potential remote code execution and system compromise.
Vulnerability Details
CVE-ID: CVE-2026-12441
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability is a use-after-free flaw located within the File Input handler of the browser. An unauthenticated attacker could exploit this memory corruption issue by enticing a user to interact with a specially crafted web page.
Business Impact
The vulnerability carries a CVSS score of 8.8, indicating a high level of risk to organizational endpoints. Successful exploitation could lead to full system compromise, unauthorized data access, and potential lateral movement within the network, significantly impacting business continuity and data integrity.
Remediation Plan
Immediate Action: Update all installations of Google Chrome on Linux to version 149 or later immediately.
Proactive Monitoring: Review system logs for unusual browser crashes or unexpected process behavior that may indicate exploitation attempts.
Compensating Controls: Ensure that browser-based endpoint protection and sandboxing features are fully enabled and up to date to restrict the impact of malicious code execution.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 18, 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 high CVSS score and the critical nature of browser-based memory corruption flaws, organizations must prioritize this update. Deploy the vendor-provided patch across all Linux workstations immediately to neutralize the risk of remote exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in Digital Credentials in Google Chrome prior to 149
Use after free in Digital Credentials in Google Chrome prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: prior to 149
---END_METADATA---
Description Summary:
A Use-After-Free (UAF) vulnerability in Google Chrome's Digital Credentials component allows for potential remote code execution or system instability.
Executive Summary:
A high-severity Use-After-Free vulnerability in Google Chrome allows attackers to execute arbitrary code through specially crafted web content.
Vulnerability Details
CVE-ID: CVE-2026-12439
Affected Software: Google Chrome
Affected Versions: prior to 149
Vulnerability: This is a memory corruption vulnerability (Use-After-Free) located in the Digital Credentials implementation. An attacker can trigger this condition by enticing a user to visit a malicious website, potentially leading to arbitrary code execution within the browser's context.
Business Impact
With a CVSS score of 8.8, this flaw is highly dangerous as it allows for browser-based attacks that can bypass security boundaries. Successful exploitation could lead to data theft, session hijacking, or the installation of malicious software on the end-user's device.
Remediation Plan
Immediate Action: Update Google Chrome to version 149 or later to incorporate the vendor's security fixes.
Proactive Monitoring: Monitor endpoint logs for abnormal browser crashes or unexpected behavior that may indicate an attempted UAF exploit.
Compensating Controls: Use endpoint protection software that can detect and block known exploit patterns and maintain strict browser security policies.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of Jun 18, 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
Browser-based UAF vulnerabilities are frequently targeted by attackers. It is critical that all enterprise environments push the update to version 149 immediately to ensure user protection.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Inappropriate implementation in WebView in Google Chrome on Android prior to 149
Inappropriate implementation in WebView in Google Chrome on Android prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome on Android
AFFECTED_VERSIONS: Versions prior to 149
---END_METADATA---
Description Summary:
An inappropriate implementation vulnerability in the WebView component of Google Chrome on Android may allow for unauthorized behavior by malicious applications.
Executive Summary:
Google Chrome on Android contains a high-severity WebView implementation vulnerability that could lead to unauthorized access or execution of malicious processes.
Vulnerability Details
CVE-ID: CVE-2026-12438
Affected Software: Google Chrome on Android
Affected Versions: Versions prior to 149
Vulnerability: This is an inappropriate implementation vulnerability within the WebView component, which allows Android apps to display web content. The flaw could potentially be exploited by a malicious application to bypass security restrictions and interact with web content in an unauthorized manner.
Business Impact
The WebView component is integral to many Android applications, and a compromise here could allow for cross-site scripting or the exposure of sensitive session data within the app. With a CVSS score of 8.3, this flaw poses a significant risk to the mobile security posture of organizations that allow Android devices in their enterprise environment.
Remediation Plan
Immediate Action: Ensure all Android devices across the organization are updated to Google Chrome version 149 or later to remediate the WebView vulnerability.
Proactive Monitoring: Utilize Mobile Device Management (MDM) solutions to track and enforce minimum version compliance across the device fleet.
Compensating Controls: Restrict the installation of untrusted or non-vetted applications on corporate-managed Android devices to reduce the attack surface for WebView-based exploitation.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 20, 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
Mobile security is a critical pillar of a modern enterprise strategy; therefore, this update should be pushed to all managed mobile devices immediately. IT administrators should verify that the Chrome browser and the underlying system WebView are updated to the patched version to prevent potential exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Use after free in WebShare in Google Chrome on Windows prior to 149
Use after free in WebShare in Google Chrome on Windows prior to 149
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: Prior to 149
---END_METADATA---
Description Summary:
A use-after-free vulnerability in the WebShare component of Google Chrome on Windows allows for potential exploitation.
Executive Summary:
A use-after-free vulnerability in the Google Chrome WebShare feature on Windows platforms creates a significant risk of arbitrary code execution.
Vulnerability Details
CVE-ID: CVE-2026-12437
Affected Software: Google Chrome
Affected Versions: Prior to 149
Vulnerability: This vulnerability is a use-after-free flaw located within the WebShare component of Google Chrome. It occurs when the browser improperly handles memory, potentially allowing an unauthorized attacker to trigger a crash or execute code by manipulating the browser's state.
Business Impact
Successful exploitation can lead to browser compromise, potentially allowing an attacker to escape the browser sandbox or execute arbitrary code on the underlying operating system. With a CVSS score of 8.3, the vulnerability presents a high risk to end-user systems, necessitating swift remediation to prevent potential data theft or system infection.
Remediation Plan
Immediate Action: Update all instances of Google Chrome to version 149 or later immediately to resolve the memory management issue.
Proactive Monitoring: Monitor for browser-related crashes or unexpected behavior that may indicate attempts to exploit memory corruption flaws.
Compensating Controls: Employ browser-based security policies and ensure that end-users are running supported, patched operating systems to provide defense-in-depth.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 20, 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 that browser vulnerabilities are frequently targeted, upgrading to the patched version of Google Chrome is critical. Security teams should enforce the update across all managed endpoints to ensure users are protected against this high-severity memory vulnerability.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The Pravel SignUp & SignIn WordPress plugin contains an authentication bypass vulnerability allowing unauthenticated attackers to reset any user passw...
The Pravel SignUp & SignIn WordPress plugin contains an authentication bypass vulnerability allowing unauthenticated attackers to reset any user password and achieve full account takeover.
---METADATA---
VENDOR: Pravel
PRODUCT: SignUp & SignIn
AFFECTED_VERSIONS: Up to and including 1.0.0
---END_METADATA---
Description Summary:
The Pravel SignUp & SignIn WordPress plugin contains an authentication bypass vulnerability allowing unauthenticated attackers to reset any user password and achieve full account takeover.
Executive Summary:
A critical authentication bypass vulnerability in the Pravel SignUp & SignIn plugin allows unauthenticated attackers to hijack any user account, including administrative accounts.
Vulnerability Details
CVE-ID: CVE-2026-12417
Affected Software: Pravel SignUp & SignIn
Affected Versions: Up to and including 1.0.0
Vulnerability: The plugin's pravel_change_password() AJAX handler lacks nonce verification and capability checks, while using a flawed equality check that allows unauthenticated attackers to reset passwords by supplying empty parameters.
Business Impact
Successful exploitation results in total account takeover, providing attackers with administrative access to the WordPress environment. Given the CVSS score of 9.8, this represents a critical risk that could lead to unauthorized data exfiltration, site defacement, and the installation of persistent malicious backdoors.
Remediation Plan
Immediate Action: Update the Pravel SignUp & SignIn plugin to the latest version immediately to patch the insecure AJAX handler.
Proactive Monitoring: Review admin-ajax.php access logs for unusual POST requests containing the pravel_change_password action and unexpected user ID targets.
Compensating Controls: Implement a Web Application Firewall (WAF) rule to block unauthorized access to the wp-admin/admin-ajax.php endpoint if immediate patching is not feasible.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of Jun 24, 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 presents a severe risk to site integrity and security. Administrators must prioritize updating the plugin to the latest version to eliminate the possibility of unauthenticated account takeover and privilege escalation.
Update pravel SignUp & SignIn to the latest version. Monitor for exploitation attempts and review access logs.
The Invoice Generator WordPress plugin contains an account takeover vulnerability via an insecure password reset function that allows unauthenticated...
The Invoice Generator WordPress plugin contains an account takeover vulnerability via an insecure password reset function that allows unauthenticated attackers to hijack any user account.
---METADATA---
VENDOR: Pravel
PRODUCT: Invoice Generator
AFFECTED_VERSIONS: Up to and including 1.0.0
---END_METADATA---
Description Summary:
The Invoice Generator WordPress plugin contains an account takeover vulnerability via an insecure password reset function that allows unauthenticated attackers to hijack any user account.
Executive Summary:
A critical vulnerability in the Pravel Invoice Generator plugin allows unauthenticated attackers to perform full account takeover of any user, including administrators.
Vulnerability Details
CVE-ID: CVE-2026-12416
Affected Software: Pravel Invoice Generator
Affected Versions: Up to and including 1.0.0
Vulnerability: The vulnerability exists in the pravel_invoice_change_password() function, which lacks both nonce verification and authorization checks. Because the function utilizes a loose equality comparison for activation codes, an unauthenticated attacker can bypass the reset process to set an arbitrary password for any target account.
Business Impact
Successful exploitation results in full unauthorized administrative control over the affected WordPress site. This leads to complete data compromise, potential distribution of malicious content, and total loss of system integrity. With a CVSS score of 9.8, this flaw represents the highest level of risk to business continuity and data security.
Remediation Plan
Immediate Action: Immediately update the Pravel Invoice Generator plugin to the latest available patched version.
Proactive Monitoring: Review WordPress user logs for unexpected password changes or the creation of new administrative accounts.
Compensating Controls: Deploy a Web Application Firewall (WAF) to block unauthorized requests to the pravel_invoice_change_password() AJAX endpoint.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of Jun 24, 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 critical nature of this vulnerability and the ease of exploitation, immediate action is required to prevent unauthorized access. Site administrators must prioritize updating the plugin and auditing user accounts to ensure no unauthorized modifications have occurred.
Update pravel Invoice Generator to the latest version. Monitor for exploitation attempts and review access logs.
The Invoice Generator plugin for WordPress is vulnerable to unauthenticated privilege escalation, allowing attackers to modify arbitrary user accounts...
The Invoice Generator plugin for WordPress is vulnerable to unauthenticated privilege escalation, allowing attackers to modify arbitrary user accounts and hijack administrator sessions.
---METADATA---
VENDOR: Pravel
PRODUCT: Invoice Generator
AFFECTED_VERSIONS: Up to and including 1.0.0
---END_METADATA---
Description Summary:
The Invoice Generator plugin for WordPress is vulnerable to unauthenticated privilege escalation, allowing attackers to modify arbitrary user accounts and hijack administrator sessions.
Executive Summary:
The Invoice Generator plugin for WordPress contains a critical privilege escalation flaw that allows unauthenticated attackers to gain full administrative control over the application.
Vulnerability Details
CVE-ID: CVE-2026-12415
Affected Software: Pravel Invoice Generator
Affected Versions: Up to and including 1.0.0
Vulnerability: The plugin fails to perform capability checks or nonce verification on the pravel_invoice_edit_account() AJAX function. This allows an unauthenticated attacker to manipulate user account data via POST requests, facilitating account takeover through the password reset mechanism.
Business Impact
This vulnerability carries a CVSS score of 9.8, reflecting its potential for total system compromise. A successful exploit grants an attacker administrative access, leading to full data exfiltration, modification of financial documentation, and the potential for persistent backdoors within the WordPress environment, resulting in severe reputational and operational damage.
Remediation Plan
Immediate Action: Update the Invoice Generator plugin to the latest available version immediately to patch the missing capability check.
Proactive Monitoring: Review web server access logs for anomalous POST requests directed at wp-admin/admin-ajax.php involving user account modifications.
Compensating Controls: Implement a Web Application Firewall (WAF) rule to block or challenge unauthorized AJAX requests targeting the identified vulnerable function.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of Jun 27, 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 flaw cannot be overstated, as it provides a direct path to administrative takeover without authentication. Administrators must prioritize updating the plugin immediately. If an immediate update is not possible, the plugin should be deactivated until the patch is applied to prevent unauthorized access.
Update pravel Invoice Generator to the latest version. Monitor for exploitation attempts and review access logs.
Broken Access Control in the devLXDInstancePatchHandler component of Canonical LXD allows an untrusted guest to mount, read, and overwrite another gue...
Broken Access Control in the devLXDInstancePatchHandler component of Canonical LXD allows an untrusted guest to mount, read, and overwrite another guest's custom storage volume via a crafted device PATCH request over /dev/lxd when security
---METADATA---
VENDOR: Canonical
PRODUCT: LXD
AFFECTED_VERSIONS: See vendor advisory
---END_METADATA---
Description Summary:
A broken access control vulnerability in the devLXDInstancePatchHandler component of Canonical LXD allows unauthorized storage volume access between guests.
Executive Summary:
Canonical LXD is affected by a broken access control vulnerability that permits untrusted guests to read or overwrite the storage volumes of other instances.
Vulnerability Details
CVE-ID: CVE-2026-12411
Affected Software: Canonical LXD
Affected Versions: See vendor advisory
Vulnerability: The flaw exists in the devLXDInstancePatchHandler component, which improperly validates device PATCH requests. An untrusted guest can exploit this to mount and manipulate custom storage volumes belonging to other guests, effectively breaking the isolation boundaries of the LXD container environment.
Business Impact
The CVSS score of 8.4 highlights the severity of this privilege escalation and cross-container compromise. This vulnerability allows for significant data exposure and integrity loss, as an attacker could potentially modify or steal sensitive data across container boundaries, threatening the entire multi-tenant infrastructure.
Remediation Plan
Immediate Action: Apply all security patches released by Canonical for the LXD package immediately.
Proactive Monitoring: Review LXD audit logs for suspicious or unauthorized device PATCH requests or unexpected volume mounting activities.
Compensating Controls: Where possible, isolate highly sensitive workloads on separate physical hosts to provide an additional layer of security beyond container isolation.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of June 27, 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 potential for cross-container data access, this vulnerability must be treated with high urgency in multi-tenant or shared-hosting environments. Administrators should audit their LXD configurations and apply the necessary patches as soon as they become available.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The E2Pdf – Export Pdf Tool for WordPress plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1
The E2Pdf – Export Pdf Tool for WordPress plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1
---METADATA---
VENDOR: E2Pdf
PRODUCT: Export Pdf Tool for WordPress
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
The E2Pdf – Export Pdf Tool for WordPress plugin is vulnerable to a missing authorization flaw, potentially exposing sensitive PDF generation functions to unauthorized users.
Executive Summary:
The E2Pdf plugin for WordPress contains a missing authorization vulnerability that could allow unauthorized access to sensitive functionality.
Vulnerability Details
CVE-ID: CVE-2026-12407
Affected Software: E2Pdf – Export Pdf Tool for WordPress
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability is caused by a missing authorization check on critical plugin functions, allowing an attacker to perform actions without the required administrative permissions. This flaw effectively bypasses intended security controls within the plugin's framework.
Business Impact
With a CVSS score of 8.8, this flaw represents a significant risk, as it may allow unauthorized users to generate or export sensitive documents. This could result in unauthorized data exposure and potential non-compliance with data protection regulations.
Remediation Plan
Immediate Action: Update the E2Pdf plugin to the latest version released by the vendor.
Proactive Monitoring: Review audit logs for unauthorized access to PDF generation or export functions within the WordPress environment.
Compensating Controls: Restrict access to the WordPress administrative dashboard and plugin configuration pages to authorized IP addresses only.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 18, 2026, there is no public information indicating active exploitation of this vulnerability. However, the potential for unauthorized data exfiltration necessitates immediate remediation.
Analyst Recommendation
Administrators should prioritize updating the E2Pdf plugin immediately. Ensuring that all plugins are running the latest version is critical to maintaining the security and confidentiality of site data.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The Ninja Forms – The Contact Form Builder That Grows With You plugin for WordPress is vulnerable to unauthorized access of data due to a missing auth...
The Ninja Forms – The Contact Form Builder That Grows With You plugin for WordPress is vulnerable to unauthorized access of data due to a missing authorization check on the 'ninja-forms-views/token/refresh' REST callback in all versions up to, and including, 3
---METADATA---
VENDOR: WordPress
PRODUCT: Ninja Forms
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
The Ninja Forms plugin for WordPress is vulnerable to unauthorized data access due to a missing authorization check on the 'ninja-forms-views/token/refresh' REST API endpoint.
Executive Summary:
A missing authorization check in the Ninja Forms plugin allows unauthenticated attackers to potentially access sensitive data via the REST API.
Vulnerability Details
CVE-ID: CVE-2026-1239
Affected Software: WordPress Ninja Forms
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability stems from a missing capability check on the ninja-forms-views/token/refresh REST callback. An unauthenticated attacker can invoke this function to potentially retrieve sensitive tokens or data managed by the plugin.
Business Impact
Successful exploitation of this vulnerability could lead to unauthorized access to sensitive user or form data, violating data privacy regulations. With a CVSS score of 7.5, this high-severity flaw represents a significant risk to the integrity and confidentiality of the WordPress environment.
Remediation Plan
Immediate Action: Update the Ninja Forms plugin to the latest available version provided by the vendor to ensure the authorization check is properly implemented.
Proactive Monitoring: Review REST API access logs for unusual requests directed at the ninja-forms-views endpoint.
Compensating Controls: Implement a Web Application Firewall (WAF) rule to block unauthorized access attempts to the vulnerable REST API path until an update can be applied.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of July 1, 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 ease of interacting with REST API endpoints, this vulnerability poses a clear risk of unauthorized data exposure. Organizations should prioritize patching this plugin immediately and audit their WordPress environment for any suspicious API activity.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
A flaw was found in the AAP Gateway Envoy proxy configuration
A flaw was found in the AAP Gateway Envoy proxy configuration
---METADATA---
VENDOR: Red Hat
PRODUCT: Red Hat Ansible Automation Platform
AFFECTED_VERSIONS: 2.6 for RHEL 9 and 2.6
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A flaw in the Red Hat Ansible Automation Platform Gateway Envoy proxy configuration allows for authentication bypass through spoofing.
Executive Summary:
A critical authentication bypass vulnerability in the Red Hat Ansible Automation Platform Gateway proxy allows unauthenticated attackers to spoof identity, potentially leading to unauthorized system control.
Vulnerability Details
CVE-ID: CVE-2026-12382
Affected Software: Red Hat Ansible Automation Platform 2.6
Affected Versions: 2.6 for RHEL 9 (fixed in 0:2.6.20260422-1.el9ap and later); 2.6 (fixed in 1777311120 and later)
Vulnerability: This is an authentication bypass vulnerability (CWE-290) located in the Envoy proxy configuration of the AAP Gateway. The issue allows remote, unauthenticated attackers to bypass authentication mechanisms by spoofing requests.
Business Impact
Successful exploitation allows an attacker to bypass authentication, which could lead to full unauthorized access to the automation platform. With a CVSS score of 8.2, this poses a high risk to the integrity of automated workflows and the security of managed infrastructure across the enterprise.
Remediation Plan
Immediate Action: Apply the vendor-provided security errata (RHSA-2026:13508 or RHSA-2026:13545) immediately to update the AAP Gateway components.
Proactive Monitoring: Monitor proxy logs for unusual traffic patterns or requests that originate from unexpected sources or bypass standard authentication headers.
Compensating Controls: Ensure that the AAP Gateway is not exposed to the public internet and utilize network segmentation to limit access to the management interface.
Exploitation Status
Public Exploit Available: No (exploit_available: false)
Analyst Notes: As of July 17, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The nature of the flaw, involving proxy configuration, suggests that internal security controls are insufficient if the proxy itself is compromised.
Analyst Recommendation
Given the high impact on integrity and the critical nature of automation platforms, organizations must treat this update with high priority. Apply the provided Red Hat errata as soon as possible to ensure the integrity of your automation environment.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The SlimStat Analytics plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'fh' (fingerprint) parameter in all versions up to, a...
The SlimStat Analytics plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'fh' (fingerprint) parameter in all versions up to, and including, 5
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The Appointment Booking Calendar Plugin and Scheduling Plugin WordPress plugin through 1
The Appointment Booking Calendar Plugin and Scheduling Plugin WordPress plugin through 1
---METADATA---
VENDOR: WordPress
PRODUCT: Appointment Booking Calendar Plugin and Scheduling Plugin
AFFECTED_VERSIONS: 0 through 1.1.28
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The Appointment Booking Calendar Plugin for WordPress is vulnerable to insecure deserialization of untrusted data, potentially leading to remote code execution.
Executive Summary:
An insecure deserialization vulnerability in the Appointment Booking Calendar Plugin for WordPress could allow an unauthenticated attacker to achieve remote code execution.
Vulnerability Details
CVE-ID: CVE-2026-12378
Affected Software: WordPress Appointment Booking Calendar Plugin and Scheduling Plugin
Affected Versions: 0 through 1.1.28
Vulnerability: The plugin is susceptible to insecure deserialization (CWE-502), which occurs when untrusted data is processed without adequate validation. This flaw can be triggered by an attacker without requiring authentication.
Business Impact
This vulnerability carries a CVSS score of 8.1, indicating a high risk of total system compromise. Successful exploitation could grant an attacker full control over the web server, leading to sensitive data exfiltration, malware installation, and complete loss of system availability.
Remediation Plan
Immediate Action: Update the plugin to the latest version immediately to resolve the deserialization flaw.
Proactive Monitoring: Monitor server logs for unexpected execution of system commands or spikes in traffic to booking-related endpoints.
Compensating Controls: Use a WAF to inspect incoming traffic for serialized objects or malicious payloads frequently associated with deserialization attacks.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of July 9, 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 potential for remote code execution, this vulnerability should be treated with extreme urgency. Organizations using this plugin must verify their current version and apply the patch as soon as possible to prevent potential compromise.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The Uncanny Automator Pro WordPress plugin was distributed with a backdoor, allowing unauthenticated attackers to gain administrative access and exfil...
The Uncanny Automator Pro WordPress plugin was distributed with a backdoor, allowing unauthenticated attackers to gain administrative access and exfiltrate site credentials.
---METADATA---
VENDOR: Uncanny Owl
PRODUCT: Uncanny Automator Pro
AFFECTED_VERSIONS: 7.3.0.5
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The Uncanny Automator Pro WordPress plugin was distributed with a backdoor, allowing unauthenticated attackers to gain administrative access and exfiltrate site credentials.
Executive Summary:
A supply chain compromise of the Uncanny Automator Pro plugin has introduced a backdoor that grants unauthenticated attackers full administrative control over affected WordPress sites.
Vulnerability Details
CVE-ID: CVE-2026-12375
Affected Software: Uncanny Owl Uncanny Automator Pro
Affected Versions: 7.3.0.5
Vulnerability: The plugin was distributed with malicious, hidden functionality (CWE-912) following a compromise of the vendor's distribution infrastructure. This backdoor allows unauthenticated attackers to hijack administrator sessions and beacon sensitive security keys to external servers.
Business Impact
This vulnerability is catastrophic, as it facilitates complete takeover of the WordPress instance. With a CVSS score of 9.8, the impact includes full loss of site confidentiality, integrity, and availability, potentially leading to widespread data breaches and the deployment of persistent malware.
Remediation Plan
Immediate Action: Update the Uncanny Automator Pro plugin to version 7.3.0.6 or later immediately.
Proactive Monitoring: Audit administrator accounts for unauthorized additions and monitor outgoing network traffic for suspicious connections to unknown external IP addresses.
Compensating Controls: If an immediate update is not feasible, disable the plugin entirely until the site can be audited for signs of compromise and updated.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of July 7, 2026, there is no public information indicating widespread active exploitation of this specific backdoor. However, given the nature of the supply chain compromise, the risk of targeted exploitation is extremely high.
Analyst Recommendation
Organizations using Uncanny Automator Pro must treat this as a high-priority incident. Beyond applying the patch, administrators should perform a comprehensive security audit of their WordPress environment to ensure that no backdoors or unauthorized administrative accounts were created while the vulnerable version was active.
Update Unknown uncanny-automator-pro to the latest version. Monitor for exploitation attempts and review access logs.
The Text to Speech for WP (AI Voices by Mementor) plugin for WordPress is vulnerable to sensitive information exposure in all versions up to, and incl...
The Text to Speech for WP (AI Voices by Mementor) plugin for WordPress is vulnerable to sensitive information exposure in all versions up to, and including, 1
---METADATA---
VENDOR: WordPress
PRODUCT: Text to Speech for WP (AI Voices by Mementor)
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
The Text to Speech for WP plugin for WordPress is vulnerable to sensitive information exposure in all versions up to and including 1.
Executive Summary:
A sensitive information exposure vulnerability in the Text to Speech for WP plugin could lead to the unauthorized disclosure of private data.
Vulnerability Details
CVE-ID: CVE-2026-1233
Affected Software: WordPress Text to Speech for WP (AI Voices by Mementor)
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The plugin fails to properly protect sensitive information, allowing unauthorized access to data that should be restricted. This exposes the WordPress installation to potential data privacy concerns.
Business Impact
With a CVSS score of 7.5, this high-severity vulnerability could lead to the unauthorized disclosure of sensitive organizational or user data. This creates significant compliance risks and could result in reputational damage if private information is exposed.
Remediation Plan
Immediate Action: Update the "Text to Speech for WP" plugin to the latest version.
Proactive Monitoring: Review logs for unauthorized access to sensitive plugin endpoints or data directories.
Compensating Controls: Ensure that sensitive information is not stored within the paths accessible by the plugin if the plugin is not strictly necessary.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of April 5, 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
Security teams must prioritize updating this plugin to prevent data exposure. If no update is available, consider disabling the plugin to mitigate the risk to sensitive information.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
Use-after-free in the Networking: HTTP component
Use-after-free in the Networking: HTTP component
---METADATA---
VENDOR: Unknown
PRODUCT: Networking HTTP Component
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A use-after-free vulnerability in the Networking HTTP component could potentially lead to arbitrary code execution or system instability.
Executive Summary:
A high-severity use-after-free vulnerability in the Networking HTTP component presents a critical risk of memory corruption and potential system compromise.
Vulnerability Details
CVE-ID: CVE-2026-12291
Affected Software: Networking HTTP Component
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is a use-after-free vulnerability occurring within the HTTP processing logic. This flaw typically occurs when memory is accessed after it has been freed, which can be manipulated to trigger crashes or execute arbitrary code.
Business Impact
Memory corruption vulnerabilities are highly dangerous as they can lead to remote code execution (RCE) and full system compromise. With a CVSS score of 8.8, this flaw represents a significant threat to the availability and confidentiality of the affected software and the underlying host system.
Remediation Plan
Immediate Action: Apply the relevant security updates provided by the software vendor to address memory management flaws in the HTTP component.
Proactive Monitoring: Monitor system logs for recurring service crashes or memory-related errors that may indicate exploitation attempts.
Compensating Controls: Ensure the application is running with the least privilege necessary and utilize endpoint protection solutions to detect anomalous process behavior.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 20, 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
Due to the severity of use-after-free vulnerabilities, immediate patching is required to prevent potential exploitation. Security teams should prioritize identifying affected instances and scheduling deployment of the vendor's security updates as soon as they become available.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Privilege escalation in the Graphics: WebRender component
Privilege escalation in the Graphics: WebRender component
---METADATA---
VENDOR: Mozilla
PRODUCT: Firefox/Thunderbird
AFFECTED_VERSIONS: Firefox up to 151, Firefox ESR up to (excluding) 115.37.0, Firefox ESR from (including) 140.0 up to (excluding) 140.12.0
---END_METADATA---
Description Summary:
A privilege escalation vulnerability exists in the Graphics: WebRender component of Mozilla products, which can be triggered remotely via user interaction.
Executive Summary:
A privilege escalation flaw in the WebRender component of Mozilla products allows remote attackers to elevate privileges through user interaction.
Vulnerability Details
CVE-ID: CVE-2026-12289
Affected Software: Mozilla Firefox and Thunderbird
Affected Versions: Firefox up to 151, Firefox ESR up to (excluding) 115.37.0, Firefox ESR from (including) 140.0 up to (excluding) 140.12.0
Vulnerability: This is a privilege escalation vulnerability in the Graphics: WebRender component. The attack can be initiated remotely without authentication, though it specifically requires user interaction to execute.
Business Impact
With a CVSS score of 8.8, this vulnerability is considered a high-priority threat. Successful exploitation allows an attacker to gain elevated privileges, potentially leading to full system compromise, data theft, or the installation of malicious software. The requirement for user interaction does not significantly lower the risk in enterprise environments where end-user workstations are frequent targets.
Remediation Plan
Immediate Action: Update to Firefox 152, Firefox ESR 140.12, Firefox ESR 115.37, or Thunderbird 152/140.12 as applicable.
Proactive Monitoring: Review endpoint security logs for signs of unauthorized process execution or unexpected privilege changes following browser activity.
Compensating Controls: Use browser-based security policies to restrict the execution of untrusted scripts and content, and maintain robust endpoint detection and response (EDR) coverage.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 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
Given the potential for privilege escalation and the ubiquity of these browsers, immediate patching is required. Security teams should prioritize the deployment of the specified versions across all managed workstations and servers to close this critical security gap.
Update to patched version immediately. Review user permissions and access controls.
The Shibboleth WordPress plugin before 2.5.4 does not fail closed when its HTTP header identity mode is enabled without an anti-spoofing key, treating...
The Shibboleth WordPress plugin before 2.5.4 does not fail closed when its HTTP header identity mode is enabled without an anti-spoofing key, treating any request that carries identity headers as an authenticated session without verifying them. On a deployment where untrusted client headers reach th
---METADATA---
VENDOR: Shibboleth
PRODUCT: Shibboleth WordPress plugin
AFFECTED_VERSIONS: Shibboleth WordPress plugin versions before 2.5.4.
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The Shibboleth WordPress plugin fails to properly verify identity headers, allowing unauthenticated attackers to spoof sessions and potentially gain administrative access.
Executive Summary:
The Shibboleth WordPress plugin is vulnerable to an improper authentication flaw that allows unauthenticated remote attackers to forge identity headers and gain full administrative control.
Vulnerability Details
CVE-ID: CVE-2026-12281
Affected Software: Shibboleth WordPress plugin
Affected Versions: Shibboleth WordPress plugin versions before 2.5.4.
Vulnerability: This is an improper authentication vulnerability (CWE-287) where the plugin fails to close sessions when HTTP header identity mode is active without an anti-spoofing key. This allows an unauthenticated remote attacker to inject malicious headers and bypass authentication mechanisms entirely.
Business Impact
Successful exploitation poses a critical risk to organizational security, as it grants unauthorized actors full administrative access to the WordPress environment. Given the CVSS score of 8.1, this represents a high-severity threat that could lead to complete data compromise, unauthorized modification of site content, and potential lateral movement into federated identity systems.
Remediation Plan
Immediate Action: Update the Shibboleth WordPress plugin to version 2.5.4 or later immediately.
Proactive Monitoring: Review web server and WordPress access logs for anomalous login activity or requests containing unexpected identity headers.
Compensating Controls: Ensure that the plugin is configured with a robust anti-spoofing key and verify that network-level controls restrict access to identity headers to trusted sources only.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of Jul 15, 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 its potential for total authentication bypass in federated environments.
Analyst Recommendation
This vulnerability presents a significant risk to the integrity and confidentiality of WordPress installations, particularly in academic or enterprise environments using federated authentication. Administrators must prioritize updating the plugin to version 2.5.4 or later to prevent unauthorized administrative access.
Update Unknown Shibboleth to the latest version. Monitor for exploitation attempts and review access logs.
The Frontend File Manager Plugin WordPress plugin through 23
The Frontend File Manager Plugin WordPress plugin through 23
---METADATA---
VENDOR: Unknown
PRODUCT: Frontend File Manager Plugin
AFFECTED_VERSIONS: 0 through 23.6
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
The Frontend File Manager Plugin for WordPress is vulnerable to path traversal and improper file handling, allowing attackers to manipulate file operations.
Executive Summary:
A critical file path manipulation vulnerability in the Frontend File Manager Plugin enables unauthorized file operations, posing a high risk to system integrity.
Vulnerability Details
CVE-ID: CVE-2026-12277
Affected Software: Unknown Frontend File Manager Plugin
Affected Versions: 0 through 23.6
Vulnerability: The plugin suffers from improper control of file names or paths (CWE-73). This allows an attacker to interact with files outside of the intended directory, potentially leading to unauthorized file modification or deletion.
Business Impact
The CVSS score of 8.7 (High) reflects the severity of this vulnerability, as it allows for significant impact on system availability and integrity. Successful exploitation could lead to the deletion of critical system files or the overwriting of configuration files, causing catastrophic service disruption and potential loss of data integrity.
Remediation Plan
Immediate Action: Immediately update to the latest version of the plugin or disable it until a secure patch is confirmed and applied.
Proactive Monitoring: Monitor server logs for unusual file system access patterns and attempts to access files outside of the standard web application directories.
Compensating Controls: Deploy a Web Application Firewall (WAF) to detect and block path traversal patterns (e.g., ../) in HTTP requests.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of July 8, 2026, there is a known public proof-of-concept exploit available for this vulnerability. The risk is elevated due to the availability of exploit code, and immediate remediation is strongly advised.
Analyst Recommendation
Given the existence of a public exploit, the urgency to remediate this vulnerability is extreme. Organizations should prioritize updating or removing this plugin to prevent exploitation, as the technical impact on file integrity is significant.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The Tutor LMS WordPress plugin before 3.9.13 does not, in its Droip and Kirki page-builder integration, perform the enrollment, purchase, and private...
The Tutor LMS WordPress plugin before 3.9.13 does not, in its Droip and Kirki page-builder integration, perform the enrollment, purchase, and private-course capability checks it enforces in its core course handler, allowing authenticated users with subscriber-level access to enroll in paid or priva
---METADATA---
VENDOR: Themeum
PRODUCT: Tutor LMS
AFFECTED_VERSIONS: Tutor LMS WordPress plugin before 3.9.13
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
The Tutor LMS WordPress plugin fails to enforce capability checks in its page-builder integrations, allowing unauthorized access to restricted course content.
Executive Summary:
A vulnerability in the Tutor LMS WordPress plugin allows authenticated users to bypass critical access controls, potentially exposing private or paid course content.
Vulnerability Details
CVE-ID: CVE-2026-12275
Affected Software: Themeum Tutor LMS
Affected Versions: Tutor LMS WordPress plugin before 3.9.13
Vulnerability: The plugin fails to perform necessary enrollment and purchase capability checks within its Droip and Kirki page-builder integrations. This allows authenticated users with subscriber-level access to bypass security restrictions and access private or paid course materials.
Business Impact
With a CVSS score of 7.1, this vulnerability poses a significant risk to the business model of organizations relying on paid course content. Unauthorized access could lead to loss of revenue, intellectual property theft, and reputational damage. The ability of low-privileged users to bypass these checks undermines the integrity of the platform's access control system.
Remediation Plan
Immediate Action: Update the Tutor LMS WordPress plugin to version 3.9.13 or later immediately.
Proactive Monitoring: Monitor site traffic for unusual access patterns to paid or private course pages by subscriber-level accounts.
Compensating Controls: Use a Web Application Firewall (WAF) to inspect requests for unauthorized attempts to access protected course resources.
Exploitation Status
Public Exploit Available: Yes (per public PoC availability)
Analyst Notes: As of July 13, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The flaw is highly exploitable due to the missing capability checks in widely used page-builder integrations.
Analyst Recommendation
The presence of a proof-of-concept makes this vulnerability an immediate concern. Administrators must verify that all instances of the Tutor LMS plugin are updated to version 3.9.13 or later to prevent unauthorized access to restricted course content.
Update Unknown Tutor LMS to the latest version. Monitor for exploitation attempts and review access logs.
Mura Software CMS contains a critical remote code execution vulnerability via the “method” parameter in the “/index.cfm/_api/json/v1/default” endpoint...
Mura Software CMS contains a critical remote code execution vulnerability via the “method” parameter in the “/index.cfm/_api/json/v1/default” endpoint, allowing unauthenticated injection of CFML code.
---METADATA---
VENDOR: Mura Software
PRODUCT: CMS
AFFECTED_VERSIONS: Mura Software CMS: 10.0.712
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
Mura Software CMS contains a critical remote code execution vulnerability via the “method” parameter in the “/index.cfm/_api/json/v1/default” endpoint, allowing unauthenticated injection of CFML code.
Executive Summary:
A critical remote code execution vulnerability in Mura Software CMS allows unauthenticated attackers to execute arbitrary code, posing a severe risk to system integrity and confidentiality.
Vulnerability Details
CVE-ID: CVE-2026-12257
Affected Software: Mura Software CMS
Affected Versions: Mura Software CMS: 10.0.712
Vulnerability: This vulnerability is a code injection flaw (CWE-94) triggered by improper validation of the "method" parameter within POST requests. The attacker requires no authentication (AV:N/AC:L/AT:N/PR:N) to reach the affected endpoint and execute arbitrary ColdFusion Markup Language (CFML) expressions.
Business Impact
The ability for an unauthenticated attacker to execute arbitrary code typically results in a total compromise of the affected server. Given the CVSS score of 9.3, this represents an extreme risk, enabling unauthorized data access, lateral movement within the network, and potential full system takeover.
Remediation Plan
Immediate Action: As there is currently no official patch, administrators should restrict network access to the affected endpoint or disable the vulnerable API functionality if it is not business-critical.
Proactive Monitoring: Monitor server logs for suspicious POST requests directed at "/index.cfm/_api/json/v1/default" containing CFML syntax or unusual Java object instantiations.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block malicious payloads targeting ColdFusion engine parameters and unexpected input in API method calls.
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 due to its unauthenticated nature and the direct execution context of the ColdFusion engine.
Analyst Recommendation
This vulnerability is highly severe and requires immediate attention to prevent potential exploitation. Because no official vendor solution is currently available, prioritize the implementation of network-level access controls and WAF filtering to shield the vulnerable endpoint until a patch is released.
Update Mura Software CMS to the latest version. Monitor for exploitation attempts and review access logs.
Contributor PHP Object Injection in Avada <= 3
Contributor PHP Object Injection in Avada <= 3
---METADATA---
VENDOR: ThemeFusion
PRODUCT: Avada
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A PHP object injection vulnerability exists in the Avada theme, allowing authenticated contributors to execute arbitrary code.
Executive Summary:
The Avada theme is vulnerable to a PHP object injection flaw that allows authenticated contributors to achieve remote code execution, posing a high risk to WordPress site integrity.
Vulnerability Details
CVE-ID: CVE-2026-12256
Affected Software: ThemeFusion Avada
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability is a PHP object injection flaw residing within the Avada theme. It requires the attacker to have at least 'Contributor' level authentication to trigger the malicious payload.
Business Impact
Successful exploitation of this vulnerability allows an attacker to execute arbitrary code on the underlying server. Given the CVSS score of 8.8, this represents a high-severity risk that could lead to full site compromise, data exfiltration, and the installation of persistent backdoors, significantly impacting business operations and data confidentiality.
Remediation Plan
Immediate Action: Update the Avada theme to the latest patched version provided by ThemeFusion.
Proactive Monitoring: Audit WordPress user accounts to ensure only authorized individuals hold Contributor or higher privileges and monitor server logs for suspicious PHP execution patterns.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block malicious serialized PHP objects in HTTP requests.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 18, 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 utilizing the Avada theme must prioritize updating to the latest secure version immediately. Given the potential for remote code execution, restricting user access levels until a patch is applied is strongly advised to mitigate the attack surface.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
In nltk/nltk versions 3
In nltk/nltk versions 3
---METADATA---
VENDOR: NLTK
PRODUCT: NLTK (Natural Language Toolkit)
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A security vulnerability in the NLTK library has been identified that may allow for unauthorized processing or system impact.
Executive Summary:
The NLTK library is affected by a high-severity vulnerability that could permit unauthorized actions within environments utilizing the toolkit.
Vulnerability Details
CVE-ID: CVE-2026-12252
Affected Software: NLTK NLTK
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This issue affects NLTK version 3. The vulnerability involves improper handling of inputs, which could be leveraged by an attacker to impact the system running the toolkit.
Business Impact
The CVSS score of 7.8 indicates a high severity level, suggesting that successful exploitation could lead to significant system compromise. Organizations relying on this library for data processing or natural language tasks face risks including unauthorized code execution or data manipulation, potentially impacting the integrity of the dependent application.
Remediation Plan
Immediate Action: Update the NLTK library to the latest patched version recommended by the maintainers as soon as it becomes available.
Proactive Monitoring: Monitor for suspicious process execution patterns or unexpected resource consumption in environments where NLTK is utilized.
Compensating Controls: Ensure that applications using NLTK run within a restricted environment or container with minimal privileges to limit the impact of a potential compromise.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of July 4, 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 high severity of this vulnerability, immediate action is required to update all instances of the NLTK library. Security teams must ensure that dependency management processes are updated to incorporate the fix as soon as possible to protect the integrity of the application stack.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Invocation of process using visible sensitive information vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus Domain Joine...
Invocation of process using visible sensitive information vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus Domain Joiner allows Excavation
---METADATA---
VENDOR: TUBITAK BILGEM
PRODUCT: Pardus Domain Joiner
AFFECTED_VERSIONS: 0.5.2 up to (excluding) 0.5.4
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
Pardus Domain Joiner is susceptible to an information disclosure vulnerability where sensitive data is exposed during process invocation, enabling potential excavation.
Executive Summary:
A high-severity vulnerability in Pardus Domain Joiner exposes sensitive information during process invocation, increasing the risk of credential or configuration theft.
Vulnerability Details
CVE-ID: CVE-2026-12250
Affected Software: TUBITAK BILGEM Pardus Domain Joiner
Affected Versions: 0.5.2 up to (excluding) 0.5.4
Vulnerability: The application is vulnerable to the invocation of a process using visible sensitive information (CWE-214). This occurs when sensitive parameters or credentials are exposed in plain view, such as in process command lines, during the domain joining operation.
Business Impact
The exposure of sensitive information during system operations can lead to the compromise of domain credentials or other security-sensitive configurations. With a CVSS score of 7.9, this vulnerability poses a high risk of identity theft or unauthorized network access, potentially affecting the integrity and confidentiality of the entire enterprise domain environment.
Remediation Plan
Immediate Action: Update Pardus Domain Joiner to version 0.5.4 or the latest available vendor patch.
Proactive Monitoring: Monitor process execution logs and command-line auditing tools to identify instances where sensitive strings might be exposed by the application.
Compensating Controls: Implement strict environment-level security to limit the visibility of running processes to only those users with a legitimate business need for that information.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of July 6, 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
Security teams must prioritize the update of this software to ensure that sensitive domain-joining credentials are not inadvertently exposed to local users. Promptly applying the patch is the most effective method to prevent potential credential theft and subsequent lateral movement within the network.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
An issue was discovered in Canonical ADSys upstream versions through v0
An issue was discovered in Canonical ADSys upstream versions through v0
---METADATA---
VENDOR: Canonical
PRODUCT: ADSys
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
An unspecified vulnerability exists in Canonical ADSys upstream versions through v0, requiring immediate review of vendor security disclosures.
Executive Summary:
A high-severity vulnerability has been identified in the Canonical ADSys utility, necessitating immediate attention from system administrators to prevent potential security compromise.
Vulnerability Details
CVE-ID: CVE-2026-12249
Affected Software: Canonical ADSys
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is a security issue found in the Canonical ADSys upstream code. Technical details regarding the exploit vector are currently limited, and administrators should consult the vendor's official security bulletin for the specific scope of the flaw.
Business Impact
As a component often involved in Active Directory integration and system management, a vulnerability in ADSys could lead to unauthorized system configuration changes or privilege escalation. With a CVSS score of 8.3, this issue is classified as high-severity and warrants immediate remediation to protect the integrity of managed Ubuntu environments.
Remediation Plan
Immediate Action: Consult the Canonical security advisory and apply all available patches for ADSys immediately.
Proactive Monitoring: Monitor system logs for unusual authentication patterns or unexpected configuration changes on machines utilizing ADSys.
Compensating Controls: Restrict access to configuration management interfaces and ensure that administrative accounts are highly protected until the patch is verified.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 23, 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
Administrators should treat this high-severity advisory with urgency. Canonical frequently updates their security notices; ensure that your patch management systems are configured to pull the latest security updates for ADSys to mitigate this risk.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
NSD from version 4
NSD from version 4
---METADATA---
VENDOR: NLnet Labs
PRODUCT: NSD (Name Server Daemon)
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A vulnerability exists in the NLnet Labs NSD software, potentially allowing for significant service disruption or unauthorized control.
Executive Summary:
The NSD authoritative DNS server is affected by a high-severity vulnerability that could lead to significant operational disruption.
Vulnerability Details
CVE-ID: CVE-2026-12245
Affected Software: NLnet Labs NSD
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability involves a critical flaw in the NSD authoritative DNS server. While specific exploitation vectors are currently limited, such flaws typically involve memory corruption or packet handling errors that can be triggered by unauthenticated remote attackers.
Business Impact
The exploitation of a DNS server presents a severe risk to organizational availability and security posture. Given the CVSS score of 8.7, a successful attack could lead to denial-of-service conditions, resulting in the inability of internal and external clients to resolve critical domain names, thereby causing widespread system downtime and potential redirection of traffic.
Remediation Plan
Immediate Action: Monitor official NLnet Labs security bulletins and apply the latest security patch as soon as it is released.
Proactive Monitoring: Review DNS server logs for anomalous request patterns or sudden spikes in traffic that may indicate exploitation attempts.
Compensating Controls: Ensure the DNS infrastructure is protected by rate-limiting and access control lists (ACLs) to restrict traffic to known, trusted sources.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 25, 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 critical role of DNS in network operations, this vulnerability poses a significant risk to infrastructure stability. Organizations should prioritize patching as soon as the vendor provides an update and maintain rigorous monitoring of DNS traffic to detect any signs of compromise.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
If NSD is configured as secondary for a zone, the primary of that zone can crash NSD with an AXFR containing a DNS message with a special crafted SVCB...
If NSD is configured as secondary for a zone, the primary of that zone can crash NSD with an AXFR containing a DNS message with a special crafted SVCB RR with an rdata size of 65512, that let's an (uint16_t) variable that is used to allocate space needed for the RR wrap (because total size > 65535), causing a heap overflow
---METADATA---
VENDOR: NLnet Labs
PRODUCT: NSD (Name Server Daemon)
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
NSD is vulnerable to a heap overflow during AXFR zone transfers when processing maliciously crafted SVCB resource records.
Executive Summary:
A heap overflow vulnerability in the NSD name server allows a malicious primary zone authority to trigger a crash or potentially execute arbitrary code on a secondary DNS server.
Vulnerability Details
CVE-ID: CVE-2026-12244
Affected Software: NLnet Labs NSD
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability stems from improper handling of SVCB resource record rdata sizes during AXFR transfers, which causes an integer wrap-around in a (uint16_t) variable. This leads to an insufficient memory allocation and a subsequent heap overflow, which can be triggered by an attacker controlling the primary zone.
Business Impact
A successful exploit of this vulnerability could lead to a denial-of-service (DoS) condition by crashing the DNS service, potentially impacting name resolution for the entire organization. With a CVSS score of 8.7, the risk of arbitrary code execution cannot be ruled out, which would allow an attacker to gain a foothold on critical DNS infrastructure.
Remediation Plan
Immediate Action: Update the NSD installation to the latest patched version released by NLnet Labs as soon as it becomes available.
Proactive Monitoring: Monitor DNS server logs for unexpected service crashes and review traffic patterns for large or malformed AXFR requests.
Compensating Controls: Restrict zone transfers (AXFR/IXFR) to trusted IP addresses only to prevent unauthorized primary servers from interacting with your secondary instances.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 25, 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
Maintaining stable DNS infrastructure is critical to overall network availability. Security teams should prioritize patching NSD instances to prevent both service disruption and potential system-level compromise. Regularly audit the list of authorized primary servers for all secondary zone configurations to minimize the attack surface.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
NLTK version 3
NLTK version 3
---METADATA---
VENDOR: NLTK Project
PRODUCT: NLTK
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A security vulnerability has been identified in NLTK version 3 that may lead to potential system compromise.
Executive Summary:
The NLTK library (version 3) is susceptible to a high-severity vulnerability that could result in arbitrary code execution or data exposure.
Vulnerability Details
CVE-ID: CVE-2026-12243
Affected Software: NLTK Project NLTK
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability resides within the processing logic of NLTK version 3. It may allow an attacker to trigger malicious behavior through specially crafted inputs, regardless of the authentication state of the user.
Business Impact
With a CVSS score of 7.5, this vulnerability poses a substantial risk to applications relying on NLTK for natural language processing. Successful exploitation could lead to unauthorized data access or the execution of arbitrary commands, potentially compromising the confidentiality and integrity of the underlying host system.
Remediation Plan
Immediate Action: Update the NLTK library to the latest secure version recommended by the NLTK Project as soon as it becomes available.
Proactive Monitoring: Monitor application logs for unexpected input patterns or unusual system process execution associated with NLTK workloads.
Compensating Controls: Implement input validation and sanitization layers to filter untrusted data before it is processed by the NLTK library.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 30, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the library's widespread use in data processing pipelines, the potential for exploitation is high.
Analyst Recommendation
Security teams should immediately audit their software dependencies to identify the use of vulnerable NLTK versions. Prioritize the application of vendor-provided patches or library updates to eliminate this vector of attack and protect critical data processing environments.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The AdRotate Banner Manager plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 5
The AdRotate Banner Manager plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 5
---METADATA---
VENDOR: WordPress
PRODUCT: AdRotate Banner Manager
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
The AdRotate Banner Manager plugin for WordPress is vulnerable to PHP Code Injection, potentially allowing remote code execution.
Executive Summary:
The AdRotate Banner Manager plugin for WordPress contains a critical PHP Code Injection vulnerability that could allow unauthenticated attackers to execute arbitrary code on the underlying server.
Vulnerability Details
CVE-ID: CVE-2026-12242
Affected Software: WordPress AdRotate Banner Manager
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability involves an improper input validation flaw that permits PHP Code Injection. The vulnerability is exploitable by unauthenticated users, as the plugin fails to properly sanitize inputs before processing them in a dangerous manner.
Business Impact
A successful exploit of this vulnerability results in full server compromise, allowing attackers to read, modify, or delete sensitive application data. Given the CVSS score of 8.8, this represents a high-severity risk to business continuity and data integrity, potentially leading to total system takeover and lateral movement within the WordPress environment.
Remediation Plan
Immediate Action: Update the AdRotate Banner Manager plugin to the latest available version provided by the vendor.
Proactive Monitoring: Inspect web server access logs for suspicious POST requests containing PHP syntax or unexpected file modification timestamps.
Compensating Controls: Implement a Web Application Firewall (WAF) rule to block common code injection patterns and restrict access to the plugin's administrative endpoints.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 25, 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 necessitates immediate attention. Organizations utilizing the AdRotate Banner Manager plugin must prioritize applying the latest security patches to mitigate the risk of remote code execution. If a patch is not immediately available, administrators should consider disabling the plugin until a secure version is released.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The Export User Data plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the unserialize functio...
The Export User Data plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the unserialize function in all versions up to, and including, 2
---METADATA---
VENDOR: WordPress
PRODUCT: Export User Data Plugin
AFFECTED_VERSIONS: All versions up to, and including, 2
---END_METADATA---
Description Summary:
The Export User Data plugin for WordPress is vulnerable to arbitrary file deletion due to improper file path validation in the unserialize function.
Executive Summary:
A critical arbitrary file deletion vulnerability in the Export User Data WordPress plugin allows attackers to remove essential system files, potentially leading to a complete site outage.
Vulnerability Details
CVE-ID: CVE-2026-12240
Affected Software: WordPress Export User Data Plugin
Affected Versions: All versions up to, and including, 2
Vulnerability: The plugin fails to adequately sanitize input before processing it through the unserialize function, allowing an attacker to manipulate file paths. This vulnerability likely requires elevated privileges, though the impact is significant due to the potential for permanent data loss or site destruction.
Business Impact
The ability to delete arbitrary files on the server can result in complete site downtime, loss of configuration, or the removal of critical security files. With a CVSS score of 8.0, this high-severity vulnerability poses an immediate threat to the operational continuity and integrity of the affected WordPress site.
Remediation Plan
Immediate Action: Update the Export User Data plugin to the latest available version, or deactivate and remove the plugin if it is not strictly necessary for business operations.
Proactive Monitoring: Monitor file system integrity and review WordPress administrative audit logs for unusual file deletion activity or unauthorized plugin configuration changes.
Compensating Controls: Implement a Web Application Firewall (WAF) with rules configured to block malicious serialized input and restrict file system access permissions to the minimum necessary for the web server user.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 30, 2026, there is no public information indicating active exploitation of this vulnerability. However, given the ease of triggering file deletion, the potential for exploitation is high.
Analyst Recommendation
Site administrators should treat this vulnerability with urgency. If an update is not immediately available, the safest course of action is to disable the plugin entirely to prevent potential site destruction by unauthorized parties.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
A stored cross-site scripting (XSS) vulnerability exists in the `POST /api/prompts/share` endpoint of parisneo/lollms (latest version)
A stored cross-site scripting (XSS) vulnerability exists in the `POST /api/prompts/share` endpoint of parisneo/lollms (latest version)
---METADATA---
VENDOR: parisneo
PRODUCT: lollms
AFFECTED_VERSIONS: versions prior to 2.2.0
CONFIDENCE: high
MISSING: none
---END_METADATA---
Description Summary:
A stored cross-site scripting (XSS) vulnerability in the parisneo lollms API allows attackers to inject malicious scripts that execute in the context of other users, including administrators.
Executive Summary:
A stored XSS vulnerability in parisneo lollms enables remote attackers to achieve account takeover or session hijacking by injecting malicious scripts into the application Home Feed.
Vulnerability Details
CVE-ID: CVE-2026-12228
Affected Software: parisneo lollms
Affected Versions: versions prior to 2.2.0
Vulnerability: This vulnerability is a stored cross-site scripting flaw located in the create_post function within the backend/routers/social/init.py file. An authenticated attacker can inject malicious JavaScript into the social feature, which is then executed in the browsers of other users who view the Home Feed.
Business Impact
Successful exploitation poses a severe risk to organizational security, as the execution of malicious scripts in an administrator's browser can lead to complete account takeover and session hijacking. Given the CVSS score of 8.7, this is classified as a high-severity issue that could facilitate wormable attacks, potentially compromising the integrity of the entire application environment and exposing sensitive data processed by the LLM system.
Remediation Plan
Immediate Action: Update parisneo lollms to version 2.2.0 or later to apply the necessary input sanitization fixes.
Proactive Monitoring: Review application access logs for unusual POST requests directed at the /api/prompts/share endpoint and monitor for unexpected client-side script execution.
Compensating Controls: Deploy a Web Application Firewall (WAF) with strict XSS filtering rules to inspect and block malicious payloads targeting the social API endpoints.
Exploitation Status
Public Exploit Available: No
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 inherently dangerous due to the lack of input sanitization when handling user-provided content in a shared social context.
Analyst Recommendation
The severity of this vulnerability is elevated by the potential for administrative account compromise. Administrators must prioritize upgrading to version 2.2.0 immediately to eliminate the injection vector and secure the application against unauthorized access and potential wormable exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The Dokan Pro plugin for WordPress is vulnerable to privilege escalation via update_capabilities REST Endpoint in all versions up to, and including, 5
The Dokan Pro plugin for WordPress is vulnerable to privilege escalation via update_capabilities REST Endpoint in all versions up to, and including, 5
---METADATA---
VENDOR: WordPress
PRODUCT: Dokan Pro
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
The Dokan Pro plugin for WordPress is vulnerable to privilege escalation via the update_capabilities REST endpoint, allowing unauthorized users to elevate their access levels.
Executive Summary:
The Dokan Pro plugin for WordPress contains a critical privilege escalation flaw that could allow an attacker to gain unauthorized administrative control over the site.
Vulnerability Details
CVE-ID: CVE-2026-12224
Affected Software: WordPress Dokan Pro
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability involves an insecure REST API endpoint, update_capabilities, which fails to properly validate user permissions. An attacker can exploit this to escalate their current user privileges, potentially gaining full administrative access to the WordPress installation.
Business Impact
With a CVSS score of 8.8, this vulnerability poses a severe risk to the entire web application. Privilege escalation allows an attacker to bypass standard security controls, leading to total site compromise, data exfiltration, or the injection of malicious code, which could result in significant reputational damage and loss of customer trust.
Remediation Plan
Immediate Action: Update the Dokan Pro plugin to the latest version immediately to patch the vulnerable REST endpoint.
Proactive Monitoring: Monitor WordPress user role changes and administrative login activity for any unexpected modifications to user capabilities.
Compensating Controls: Utilize a Web Application Firewall (WAF) to block requests targeting the update_capabilities REST endpoint until the plugin can be updated.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of July 1, 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
Privilege escalation vulnerabilities in plugins are frequently targeted by automated botnets. It is critical to patch the Dokan Pro plugin immediately. Organizations should also perform a security audit of current administrative users to ensure no unauthorized accounts were created during the period the site remained vulnerable.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
A vulnerability was determined in Yealink SIP-T46U 108
A vulnerability was determined in Yealink SIP-T46U 108
---METADATA---
VENDOR: Yealink
PRODUCT: SIP-T46U
AFFECTED_VERSIONS: Yealink SIP-T46U 108.86.0.118
---END_METADATA---
Description Summary:
A buffer overflow in the Yealink SIP-T46U Web FastCGI service allows local network attackers to trigger a crash or potentially execute arbitrary code.
Executive Summary:
A stack-based buffer overflow in the Yealink SIP-T46U Web FastCGI service poses a significant security risk for devices accessible via the local network.
Vulnerability Details
CVE-ID: CVE-2026-12222
Affected Software: Yealink SIP-T46U
Affected Versions: Yealink SIP-T46U 108.86.0.118
Vulnerability: This is a stack-based buffer overflow in the mod_webd.BlueToothTest function within the /api/inner/bttest file. An attacker with local network access can exploit this by sending specially crafted btMac, pin, or reserved arguments to the Web FastCGI service.
Business Impact
The CVSS score of 8.0 indicates a high potential for impact. Successful exploitation could lead to a denial-of-service or arbitrary code execution, resulting in the loss of device confidentiality, integrity, or availability.
Remediation Plan
Immediate Action: Apply the vendor-provided firmware updates. Restrict network access to the device to prevent unauthorized parties from reaching the Web FastCGI interface.
Proactive Monitoring: Monitor for anomalous traffic directed at the /api/inner/bttest endpoint and investigate any unexpected device reboots.
Compensating Controls: Use a firewall or VLAN configuration to ensure the device's management interface is not reachable from untrusted network segments.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of June 15, 2026, a public exploit exists. The vulnerability is highly exploitable by any attacker with access to the local network, necessitating immediate defensive measures.
Analyst Recommendation
The combination of a public exploit and the high CVSS score makes this a critical security issue. Organizations using Yealink SIP-T46U devices should verify their firmware versions and restrict management interface access to prevent exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability was found in Yealink SIP-T46U 108
A vulnerability was found in Yealink SIP-T46U 108
---METADATA---
VENDOR: Yealink
PRODUCT: SIP-T46U
AFFECTED_VERSIONS: Yealink SIP-T46U 108.86.0.118
---END_METADATA---
Description Summary:
A stack-based buffer overflow in the Yealink SIP-T46U firmware upgrade handler allows local network attackers to disrupt service or execute arbitrary code.
Executive Summary:
A stack-based buffer overflow in the Yealink SIP-T46U upgrade handler exposes the device to potential compromise by attackers with local network access.
Vulnerability Details
CVE-ID: CVE-2026-12221
Affected Software: Yealink SIP-T46U
Affected Versions: Yealink SIP-T46U 108.86.0.118
Vulnerability: This is a stack-based buffer overflow in the sprintf function located in the /api/upgrade/upgrade file. Exploitation is possible by manipulating the uid/start_offset arguments within the Firmware Chunk Upload Handler.
Business Impact
The CVSS score of 8.0 confirms the high severity of this vulnerability. Successful exploitation could lead to full device compromise, potentially enabling an attacker to intercept communications or use the device as a pivot point within the local network.
Remediation Plan
Immediate Action: Apply firmware updates from Yealink as soon as they become available. Segment the management network to prevent unauthorized access to device API endpoints.
Proactive Monitoring: Review device access logs for frequent or malformed requests to the /api/upgrade/ path.
Compensating Controls: Implement network-level access control lists (ACLs) to ensure only authorized workstations can communicate with the SIP phone's management interface.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of June 15, 2026, a public exploit is available. The requirement for local network access does not significantly diminish the risk, as an attacker already present on the network can leverage this to escalate their presence.
Analyst Recommendation
Due to the public availability of an exploit, this vulnerability must be treated with high urgency. Administrators should isolate the device management interfaces and monitor for any suspicious traffic targeting the firmware upgrade handlers.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability has been found in Yealink SIP-T46U 108
A vulnerability has been found in Yealink SIP-T46U 108
---METADATA---
VENDOR: Yealink
PRODUCT: SIP-T46U
AFFECTED_VERSIONS: Yealink SIP-T46U 108.86.0.118
---END_METADATA---
Description Summary:
A stack-based buffer overflow in the Yealink SIP-T46U firmware upgrade component allows local network attackers to potentially achieve remote code execution.
Executive Summary:
A critical stack-based buffer overflow vulnerability in Yealink SIP-T46U firmware handling could allow attackers on the local network to compromise the device.
Vulnerability Details
CVE-ID: CVE-2026-12220
Affected Software: Yealink SIP-T46U
Affected Versions: Yealink SIP-T46U 108.86.0.118
Vulnerability: This is a stack-based buffer overflow in the mod_upgrade.SparePartsUpload function within the /api/upgrade/accupgradebychunk component. An attacker with local network access can trigger this by sending malicious data to the Firmware Chunk Upload handler.
Business Impact
With a CVSS score of 8.0, this vulnerability presents a high risk of unauthorized device control. Exploitation could allow an attacker to gain persistent access to telecommunications hardware, facilitating eavesdropping or further network lateral movement.
Remediation Plan
Immediate Action: Apply the latest firmware security updates provided by Yealink. If no update is available, isolate the device management interface from the general network.
Proactive Monitoring: Monitor network traffic for anomalous firmware upload attempts or unexpected API calls to the /api/upgrade/ endpoint.
Compensating Controls: Restrict access to the device's web management interface to trusted administrative IP addresses using network segmentation or ACLs.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of June 15, 2026, a public exploit exists for this vulnerability. While exploitation requires local network access, the potential for device compromise is high and warrants immediate attention.
Analyst Recommendation
Given the availability of a public exploit and the potential for full device compromise, users must restrict access to the affected SIP phone's management interface immediately. Apply any available firmware patches from the manufacturer as soon as they are released.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
PrismX MX100 AP controller developed by BROWAN COMMUNICATIONS has an Arbitrary File Upload vulnerability, allowing privileged remote attackers to uplo...
PrismX MX100 AP controller developed by BROWAN COMMUNICATIONS has an Arbitrary File Upload vulnerability, allowing privileged remote attackers to upload and execute web shell backdoors, thereby enabling arbitrary code execution on the server
Executive Summary:
A high-severity vulnerability has been identified in the BROWAN COMMUNICATIONS PrismX MX100 AP controller. This flaw allows a remote attacker with existing privileges to upload malicious files, which can then be executed to gain complete control over the affected server. Successful exploitation could lead to data theft, network disruption, and further unauthorized access into the corporate network.
Vulnerability Details
CVE-ID: CVE-2026-1222
Affected Software: BROWAN COMMUNICATIONS PrismX MX100 AP controller
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This is an Arbitrary File Upload vulnerability. An attacker who has already obtained privileged credentials for the device's management interface can exploit this flaw by uploading a specially crafted file, such as a web shell. The application fails to properly validate the uploaded file's type or content, allowing the malicious file to be saved to a web-accessible directory on the server. The attacker can then execute the code within the file by navigating to its URL, resulting in arbitrary code execution with the permissions of the web server process.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 7.2. A successful exploit would result in a complete compromise of the PrismX MX100 AP controller. This could allow an attacker to intercept or manipulate network traffic, steal sensitive configuration data, disable wireless network services, or use the compromised controller as a pivot point to launch further attacks against the internal network. The specific risks to the organization include data breaches, operational downtime, and a loss of integrity for the managed network environment.
Remediation Plan
Immediate Action: Apply the security updates provided by BROWAN COMMUNICATIONS to all affected PrismX MX100 AP controllers immediately. Before and after patching, closely monitor devices for any signs of compromise and review historical access and system logs for indicators of exploitation.
Proactive Monitoring: Monitor web server and application logs for suspicious file upload events, particularly files with executable extensions (e.g., .php, .jsp, .sh, .aspx). Scrutinize network traffic for unexpected outbound connections originating from the AP controller. Implement file integrity monitoring on the device's web directories to detect the creation of unauthorized files.
Compensating Controls: If immediate patching is not feasible, implement the following controls:
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of January 20, 2026, there are no known public proof-of-concept exploits or active exploitation campaigns targeting this vulnerability. The vulnerability requires the attacker to be authenticated with privileges, which reduces the risk of widespread, opportunistic attacks. However, threat actors who have already gained a foothold in a network may leverage this vulnerability for privilege escalation or lateral movement.
Analyst Recommendation
Given the high severity score and the potential for complete system compromise, it is strongly recommended that organizations prioritize the immediate application of vendor-supplied patches to all affected controllers. Although this vulnerability is not currently on the CISA KEV list and requires prior authentication, the impact of a successful exploit is severe. If patching is delayed, the compensating controls outlined above, particularly restricting network access to the management interface, should be implemented as a critical interim measure to reduce the attack surface.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A vulnerability was detected in Yealink SIP-T46U 108
A vulnerability was detected in Yealink SIP-T46U 108
---METADATA---
VENDOR: Yealink
PRODUCT: SIP-T46U
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A security vulnerability has been identified in the Yealink SIP-T46U IP phone firmware, potentially allowing for unauthorized system impact.
Executive Summary:
A critical security vulnerability in Yealink SIP-T46U firmware poses a significant risk to enterprise communication infrastructure.
Vulnerability Details
CVE-ID: CVE-2026-12218
Affected Software: Yealink SIP-T46U
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability affects the Yealink SIP-T46U firmware; while specific authentication requirements are currently undisclosed, such flaws often involve improper input validation or insufficient access controls within the device's management interface.
Business Impact
Successful exploitation of this high-severity vulnerability (CVSS 8.0) could lead to unauthorized access to enterprise communication devices. This may result in call interception, eavesdropping, or the pivot of attackers into internal voice-over-IP (VoIP) networks, causing substantial reputational damage and operational disruption.
Remediation Plan
Immediate Action: Administrators should verify the current firmware version of all deployed SIP-T46U units and apply the latest security updates provided by Yealink immediately.
Proactive Monitoring: Review device access logs for unusual login attempts or unexpected configuration changes originating from unauthorized IP addresses.
Compensating Controls: Isolate VoIP devices on a dedicated, firewalled VLAN to restrict management access to trusted administrative subnets only.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 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 high CVSS score, organizations utilizing Yealink SIP-T46U devices must prioritize this update. Ensure that all firmware management is conducted over secure, segmented networks to minimize exposure while awaiting vendor-specific patching guidance.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A security vulnerability has been detected in DVDFab Virtual Drive 2
A security vulnerability has been detected in DVDFab Virtual Drive 2
---METADATA---
VENDOR: DVDFab
PRODUCT: Virtual Drive
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A security vulnerability has been detected in DVDFab Virtual Drive, which may permit unauthorized system-level interactions.
Executive Summary:
A high-severity vulnerability in DVDFab Virtual Drive poses a risk of unauthorized access or system instability on affected hosts.
Vulnerability Details
CVE-ID: CVE-2026-12217
Affected Software: DVDFab Virtual Drive
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability relates to the DVDFab Virtual Drive software, potentially involving improper validation of virtual image files or system drivers that could be exploited to cause system-level impact.
Business Impact
With a CVSS score of 7.8, this flaw represents a significant risk to endpoint integrity. Exploitation could allow an attacker to execute arbitrary code or gain unauthorized control over the system, potentially leading to data exfiltration or system-wide compromise.
Remediation Plan
Immediate Action: Update the DVDFab Virtual Drive software to the most current version available from the vendor.
Proactive Monitoring: Review system logs for unusual driver activity or unexpected application crashes that may indicate an exploitation attempt.
Compensating Controls: Use application control policies to restrict the execution of untrusted software or the mounting of unauthorized virtual drive images.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 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
Organizations should audit their environments for the presence of DVDFab Virtual Drive and apply the necessary patches. If the software is not required for business operations, consider uninstalling it to reduce the attack surface.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A security flaw has been discovered in Qihoo 360 Total Security 6
A security flaw has been discovered in Qihoo 360 Total Security 6
---METADATA---
VENDOR: Qihoo 360
PRODUCT: Total Security
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A security flaw has been discovered in Qihoo 360 Total Security, potentially impacting the effectiveness of the endpoint protection suite.
Executive Summary:
A high-severity vulnerability in Qihoo 360 Total Security could allow attackers to bypass security protections or compromise the host system.
Vulnerability Details
CVE-ID: CVE-2026-12214
Affected Software: Qihoo 360 Total Security
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability involves a security flaw within the Qihoo 360 Total Security suite, potentially allowing an attacker to manipulate the software's protective mechanisms or execute code with elevated permissions.
Business Impact
A CVSS score of 7.8 indicates a high risk to organizational security. Successful exploitation could render the security software ineffective, leaving the host vulnerable to further attacks, malware delivery, or unauthorized access to sensitive local data.
Remediation Plan
Immediate Action: Apply the latest security updates released by Qihoo 360 to all systems running the Total Security suite immediately.
Proactive Monitoring: Monitor security logs for alerts indicating the deactivation or modification of the antivirus software or unexpected system behavior.
Compensating Controls: Ensure that additional layers of security, such as network-level filtering and host-based firewalls, are active to mitigate the risk of exploit delivery.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 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
Security teams must prioritize updating endpoint protection software to ensure that the security suite itself does not become an attack vector. Verify that automatic updates are enabled and functioning across the environment.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
PrismX MX100 AP controller developed by BROWAN COMMUNICATIONS has a Use of Hard-coded Credentials vulnerability, allowing unauthenticated remote atta...
PrismX MX100 AP controller developed by BROWAN COMMUNICATIONS has a Use of Hard-coded Credentials vulnerability, allowing unauthenticated remote attackers to log in to the database using hardcoded database credentials stored in the firmware.
Executive Summary:
A critical vulnerability has been identified in multiple PrismX products, allowing unauthenticated remote attackers to gain full access to the device's database. This is due to hard-coded credentials stored within the device firmware, which could lead to a complete compromise of data confidentiality, integrity, and availability. Immediate patching is required to prevent potential data breaches and system takeover.
Vulnerability Details
CVE-ID: CVE-2026-1221
Affected Software: PrismX Multiple Products
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The PrismX MX100 AP controller firmware contains static, hard-coded database credentials. A remote, unauthenticated attacker can extract these credentials by analyzing the firmware file. Once obtained, the attacker can use these credentials to directly log in to the device's database, bypassing all authentication mechanisms and gaining privileged access to the stored data.
Business Impact
This vulnerability is rated as critical severity with a CVSS score of 9.8. Successful exploitation grants an attacker direct administrative access to the database, posing a significant risk to the organization. Potential consequences include unauthorized access to sensitive configuration data, customer information, or network credentials; modification or deletion of critical data leading to service disruption; and using the compromised device as a pivot point for further attacks within the network. This can result in severe financial loss, reputational damage, and regulatory penalties.
Remediation Plan
Immediate Action: Organizations must immediately apply the security updates provided by the vendor to all affected PrismX products. After patching, it is crucial to monitor systems for any signs of compromise that may have occurred prior to the update and review all database access logs for unauthorized connections.
Proactive Monitoring: Implement enhanced monitoring for database access attempts originating from untrusted or unexpected IP addresses. Network traffic should be monitored for unusual data flows from the database server, which could indicate data exfiltration. System logs should be reviewed for authentication attempts using the now-public hard-coded credentials.
Compensating Controls: If immediate patching is not feasible, implement network segmentation to restrict access to the database port from untrusted networks, such as the internet. Deploy an Intrusion Prevention System (IPS) or Web Application Firewall (WAF) with rules to detect and block login attempts using the known hard-coded credentials. If possible, manually change the default database password on the device, though this may not be supported on all firmware versions.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of the publication date of Jan 20, 2026, there are no known public exploits actively targeting this vulnerability. However, due to the trivial nature of exploiting hard-coded credentials, it is highly likely that threat actors will reverse-engineer the firmware to discover the credentials and weaponize this vulnerability in the near future.
Analyst Recommendation
Given the critical CVSS score of 9.8 and the ease of exploitation, this vulnerability presents a clear and present danger to the organization. We strongly recommend that all affected PrismX products be patched immediately, treating this as the highest priority. Although this CVE is not currently listed on the CISA KEV catalog, its high impact and low attack complexity make it a prime candidate for future inclusion and widespread exploitation. Organizations should assume they are being targeted and act decisively to mitigate this risk.
Update PrismX Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
A vulnerability was determined in ShopXO up to 6
A vulnerability was determined in ShopXO up to 6
---METADATA---
VENDOR: ShopXO
PRODUCT: ShopXO
AFFECTED_VERSIONS: ShopXO up to 6.7.1
---END_METADATA---
Description Summary:
An unauthenticated remote code execution vulnerability in the ShopXO Crontab.php controller allows attackers to manipulate scheduled tasks and bypass authorization.
Executive Summary:
An unauthenticated vulnerability in ShopXO allows remote attackers to bypass authorization mechanisms by manipulating scheduled tasks in the Crontab controller.
Vulnerability Details
CVE-ID: CVE-2026-12204
Affected Software: ShopXO
Affected Versions: ShopXO up to 6.7.1
Vulnerability: This vulnerability stems from improper access control in the Crontab.php controller, which allows an unauthenticated remote attacker to trigger or manipulate scheduled tasks. By bypassing existing authorization checks, an attacker can potentially execute unauthorized actions.
Business Impact
The CVSS score of 7.3 (High) highlights the significant risk of unauthorized access and potential system compromise. If exploited, an attacker could gain control over administrative tasks, leading to data tampering, unauthorized site modifications, or complete system takeover.
Remediation Plan
Immediate Action: Upgrade to the latest version of ShopXO that includes the security patch for Crontab.php authorization vulnerabilities.
Proactive Monitoring: Review web server logs for suspicious requests directed at the Crontab.php controller or unexpected execution of administrative scheduled tasks.
Compensating Controls: Restrict access to administrative controllers and cron-related endpoints using IP whitelisting or by requiring authentication at the web server (e.g., Nginx/Apache) level.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of June 15, 2026, a public exploit is available for this vulnerability. The lack of authentication requirements makes this a high-risk target for automated exploitation.
Analyst Recommendation
This vulnerability is highly critical due to the availability of a public exploit and the lack of required authentication. Organizations running ShopXO should treat this as a high-priority remediation task and apply necessary updates immediately to secure their platform from unauthorized access.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
A security vulnerability has been detected in Ritlabs TinyWeb Server up to 1
A security vulnerability has been detected in Ritlabs TinyWeb Server up to 1
---METADATA---
VENDOR: Ritlabs
PRODUCT: TinyWeb Server
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A security vulnerability has been detected in the Ritlabs TinyWeb Server, affecting versions up to 1.
Executive Summary:
The Ritlabs TinyWeb Server is subject to a high-severity security vulnerability that could lead to unauthorized system access or service disruption.
Vulnerability Details
CVE-ID: CVE-2026-12200
Affected Software: Ritlabs TinyWeb Server
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: The vulnerability affects the core functionality of the TinyWeb Server, potentially allowing for remote exploitation by unauthorized parties. The exact mechanism of the flaw requires careful review of the vendor’s security bulletin.
Business Impact
The CVSS score of 7.3 highlights the significant risk posed to web services hosted on TinyWeb. Successful exploitation could result in full service compromise, unauthorized data disclosure, or total system downtime, severely impacting business continuity.
Remediation Plan
Immediate Action: Apply the latest security patches provided by Ritlabs immediately to secure the web server environment.
Proactive Monitoring: Review server access logs for anomalous requests or attempts to execute unauthorized commands on the host.
Compensating Controls: Place the TinyWeb server behind a robust reverse proxy or WAF that can filter malicious requests before they reach the server.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 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 server software is critical to web operations and should be patched immediately. Ensure that the web server is not exposed to the public internet unless absolutely necessary.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
---METADATA---
VENDOR: Google
PRODUCT: Chrome
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---
Description Summary:
A race condition within the Google Chrome Updater for macOS could allow an attacker to interfere with the update process, potentially leading to unauthorized operations.
Executive Summary:
A high-severity race condition in the Google Chrome Updater for macOS allows for potential unauthorized system-level manipulation.
Vulnerability Details
CVE-ID: CVE-2026-12468
Affected Software: Google Chrome
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability involves a race condition in the browser's updater mechanism. An attacker could potentially exploit the timing of update operations to gain elevated control over the application's lifecycle or security parameters.
Business Impact
An attacker successfully exploiting the updater component could potentially bypass security updates or force the installation of unauthorized code, undermining the integrity of the browser environment. With a CVSS score of 8.3, this represents a major risk to enterprise endpoint security and the reliability of automated patch management processes.
Remediation Plan
Immediate Action: Apply the vendor-provided update to version 149 or higher to patch the race condition within the updater module.
Proactive Monitoring: Review system logs for anomalous activity specifically related to the browser update process or unexpected installation events.
Compensating Controls: Utilize endpoint management tools to strictly control binary execution permissions and prevent unauthorized modifications to application directories.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 20, 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
Maintaining a secure update mechanism is critical for browser integrity. Organizations must immediately update Google Chrome on all macOS systems to ensure that the updater component is no longer susceptible to this race condition.