Executive Summary:
A high-severity security flaw has been identified in the Shenzhen Sixun Business Management System. This vulnerability could allow a remote attacker to access or manipulate sensitive business data, potentially leading to data breaches and operational disruption. Organizations using the affected software are urged to apply the vendor-supplied security patch immediately to mitigate the risk of exploitation.

Vulnerability Details

CVE-ID: CVE-2025-10374

Affected Software: Shenzhen Sixun Business Management System

Affected Versions: See vendor advisory for specific affected versions. The initial report indicates versions 7 through 11 may be impacted.

Vulnerability: The vulnerability is a flaw within the application's data handling components. A remote, unauthenticated attacker can send a specially crafted request to the system's web interface. This request is improperly validated, allowing the attacker to execute arbitrary commands or queries on the backend database, which could lead to unauthorized access, modification, or exfiltration of sensitive business and customer information.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 7.3. Successful exploitation could have a significant negative impact on the business. Potential consequences include the theft of confidential corporate data, customer personally identifiable information (PII), and financial records. This could lead to severe reputational damage, regulatory penalties for non-compliance with data protection standards, and financial loss from fraud or business interruption.

Remediation Plan

Immediate Action: The primary remediation is to apply the security updates provided by the vendor immediately. System administrators should coordinate with the vendor to obtain the correct patch and schedule an emergency maintenance window for its deployment. After patching, it is crucial to monitor for any signs of post-patch exploitation attempts and thoroughly review historical access logs for indicators of a prior compromise.

Proactive Monitoring: Implement enhanced monitoring of the affected systems. Security teams should look for unusual or malformed queries in application and database logs, unexpected outbound network connections from the application server, and multiple failed access attempts from a single source IP address. Configure alerts for any activity matching known exploitation patterns for this type of vulnerability.

Compensating Controls: If immediate patching is not feasible, implement the following compensating controls to reduce the risk of exploitation:

• Restrict network access to the affected system, allowing connections only from trusted IP addresses and internal networks.
• Deploy a Web Application Firewall (WAF) with rulesets designed to detect and block common web-based attacks, such as SQL injection or command injection.
• Increase the level of logging for the application and underlying systems to better detect and respond to potential incidents.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of September 14, 2025, there are no known public proof-of-concept exploits or active exploitation campaigns targeting this vulnerability. However, given the high severity, it is highly likely that threat actors will analyze the security patch to develop an exploit. The vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities (KEV) catalog.

Analyst Recommendation

Given the high CVSS score of 7.3, this vulnerability presents a significant risk to the organization. We strongly recommend that the vendor-provided security update be applied to all affected systems as a top priority. While there is no evidence of active exploitation at this time, the situation can change rapidly. If patching is delayed, the compensating controls listed above should be implemented immediately to provide a temporary layer of defense.

Executive Summary:
A high-severity vulnerability has been identified in multiple Salia products, specifically affecting the eCharge Hardy Barth Salia PLCC 2 controller. This flaw could potentially allow a remote attacker to disrupt or manipulate electric vehicle charging operations. Organizations utilizing the affected equipment should prioritize the application of vendor-supplied security updates to prevent operational downtime and potential unauthorized use of services.

Vulnerability Details

CVE-ID: CVE-2025-10371

Affected Software: Salia Multiple Products

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The security flaw exists within the Power Line Communication Controller (PLCC) of the affected eCharge systems. An unauthenticated remote attacker could send specially crafted network packets to the device's management interface. Successful exploitation could lead to a denial-of-service condition, rendering the charging station inoperable, or potentially allow unauthorized control over charging sessions, including starting or stopping them without proper authorization.

Business Impact

This vulnerability is classified as High severity with a CVSS score of 7.3. Exploitation could lead to significant business disruption, including service unavailability for customers, leading to revenue loss and reputational damage. Furthermore, if an attacker gains control over charging sessions, it could result in direct financial losses through electricity theft or fraudulent billing. The operational integrity of the charging infrastructure is at risk, potentially impacting service level agreements and customer trust.

Remediation Plan

Immediate Action: The primary remediation is to apply the security updates provided by Salia to all affected devices immediately. After patching, system administrators should review access and operational logs for any signs of compromise or unusual activity that occurred prior to the update.

Proactive Monitoring: Implement enhanced monitoring of network traffic to and from the affected charging stations. Specifically, look for unusual connection attempts, malformed packets targeting the PLCC's known ports, or unexpected device reboots. Monitor charging session logs for anomalies, such as sessions initiated outside of normal business hours or without corresponding payment data.

Compensating Controls: If immediate patching is not feasible, implement network segmentation to isolate the charging station controllers from public-facing networks. Use firewalls to restrict access to the devices' management interfaces, allowing connections only from trusted administrative IP addresses.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of September 14, 2025, there are no known public proof-of-concept exploits or active attacks targeting this vulnerability. However, security researchers and threat actors frequently reverse-engineer patches to develop exploits shortly after a vulnerability is disclosed. The lack of current exploitation does not diminish the urgency of remediation.

Analyst Recommendation

Given the high CVSS score and the direct impact on critical operational technology, we strongly recommend that organizations prioritize the immediate deployment of the vendor-provided patches for CVE-2025-10371. While this vulnerability is not currently on the CISA KEV list, its potential for causing significant operational and financial disruption makes it a critical risk. Organizations should treat this as a high-priority action item to safeguard their charging infrastructure and maintain service continuity.

Executive Summary:
A high-severity vulnerability has been identified in certain Wavlink networking devices, which could allow a remote, unauthenticated attacker to execute arbitrary commands on the device. Successful exploitation could lead to a complete compromise of the affected router, enabling the attacker to intercept network traffic, attack other devices on the internal network, or disrupt network availability. Organizations are urged to apply the vendor-provided security updates immediately to mitigate this significant risk.

Vulnerability Details

CVE-ID: CVE-2025-10359

Affected Software: Wavlink WL-WN578W2

Affected Versions: Firmware version 221110 is confirmed vulnerable. See vendor advisory for a complete list of affected products and versions.

Vulnerability: The vulnerability is an unauthenticated command injection flaw within the device's web management interface. An attacker can send a specially crafted HTTP request to a specific endpoint on the web server. Due to insufficient input sanitization, malicious shell commands embedded within the request's parameters are executed directly by the underlying operating system with root-level privileges, giving the attacker full control over the device without needing any prior authentication.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 7.3. Exploitation could have a severe impact on business operations and data security. A successful attacker could gain complete control of the network device, leading to potential consequences such as eavesdropping on sensitive network traffic (data exfiltration), redirecting users to malicious websites (phishing), disrupting network services (denial of service), or using the compromised device as a pivot point to launch further attacks against the internal corporate network. The integrity, confidentiality, and availability of the network segment managed by the device are all at high risk.

Remediation Plan

Immediate Action:
Identify all vulnerable Wavlink devices on the network and apply the vendor-supplied security updates or firmware patches immediately. After patching, verify that the update was successful and the device is running the new, secure version.

Proactive Monitoring:
Monitor network traffic for anomalous outbound connections originating from the affected devices. Review firewall and web server logs for suspicious or malformed HTTP requests directed at the device's management interface. System administrators should also monitor for any unauthorized configuration changes, unexpected reboots, or high CPU usage on the devices, as these could be indicators of compromise.

Compensating Controls:
If immediate patching is not feasible, implement the following controls to reduce the risk of exploitation:

• Disable remote (WAN-side) access to the device's web management interface.
• Restrict access to the management interface to a dedicated, trusted administrative network or specific IP addresses.
• Use a network firewall or Intrusion Prevention System (IPS) to block access to the vulnerable web endpoints from untrusted sources.

Exploitation Status

Public Exploit Available: false

Analyst Notes:
As of September 14, 2025, there are no known public proof-of-concept exploits or active exploitation campaigns targeting this vulnerability. However, due to the critical nature of command injection vulnerabilities in networking equipment, it is highly probable that threat actors will reverse-engineer the vendor patch to develop an exploit.

Analyst Recommendation

Given the high severity (CVSS 7.3) and the potential for a complete network device takeover without authentication, this vulnerability poses a significant and immediate threat. We strongly recommend that organizations prioritize the identification and patching of all affected Wavlink devices. Although this CVE is not currently listed on the CISA KEV list, its characteristics make it a prime candidate for future inclusion should widespread exploitation occur. Immediate remediation is the most effective strategy to prevent potential compromise.

Executive Summary:
A high-severity vulnerability has been identified in specific Wavlink networking equipment, which could allow a remote attacker to execute arbitrary commands and gain full control of the affected device. Successful exploitation could lead to network traffic interception, redirection to malicious websites, and unauthorized access to the internal network. Organizations are strongly advised to apply the vendor-supplied security update immediately to mitigate this significant risk.

Vulnerability Details

CVE-ID: CVE-2025-10358

Affected Software: Wavlink WL-WN578W2

Affected Versions: Firmware version 221110. See vendor advisory for a complete list of affected products and versions.

Vulnerability: The vulnerability is an authenticated command injection flaw within the web-based management interface of the Wavlink device. An attacker with valid credentials for the management portal can inject and execute arbitrary operating system commands with root privileges by manipulating input parameters in a specific administrative function. This allows the attacker to bypass security restrictions and achieve full administrative control over the underlying operating system of the router.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 7.3. A successful exploit would grant an attacker complete control over a critical network perimeter device. The potential business impact includes the compromise of confidential data through traffic sniffing, disruption of business operations via DNS hijacking or denial-of-service attacks, and the use of the compromised device as a pivot point to launch further attacks against the internal corporate network. This poses a direct risk to data confidentiality, integrity, and availability.

Remediation Plan

Immediate Action: Apply the vendor-provided security updates to all affected Wavlink devices immediately. After patching, verify that the new firmware version has been successfully installed. It is also critical to monitor for any signs of exploitation attempts by reviewing device and network logs for anomalous activity.

Proactive Monitoring: Security teams should actively monitor for signs of compromise. This includes reviewing web server access logs on the device for suspicious requests containing shell metacharacters (e.g., ;, |, &&, $(...)), monitoring for unexpected outbound network connections from the device's management interface, and setting up alerts for any unauthorized configuration changes.

Compensating Controls: If immediate patching is not feasible, implement the following compensating controls:

• Restrict access to the device's web management interface to a dedicated and trusted management network or specific IP addresses.
• Ensure that default administrative credentials have been changed to a strong, unique password.
• Disable remote (WAN) management of the device if not strictly required for business operations.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of September 14, 2025, there is no known public proof-of-concept exploit code, and there are no reports of this vulnerability being actively exploited in the wild. However, vulnerabilities in networking equipment are frequently targeted by threat actors for inclusion in botnets or for use as attack platforms. The simplicity of command injection flaws means that an exploit could be developed rapidly.

Analyst Recommendation

Given the high severity (CVSS 7.3) and the critical role of this network device, we recommend that the vendor-supplied patch be treated as a high-priority action and applied immediately. Although this CVE is not currently on the CISA KEV list, its potential for full device takeover makes it an attractive target for future exploitation. Organizations should prioritize patching and, where patching is delayed, implement the recommended compensating controls to reduce the attack surface.

---METADATA---
VENDOR: Mitsubishi Electric
PRODUCT: FREQSHIP-mini
AFFECTED_VERSIONS: Windows versions 8; See vendor advisory
---END_METADATA---

Description Summary:
Mitsubishi Electric FREQSHIP-mini for Windows contains an incorrect default permissions vulnerability, potentially allowing unauthorized local users to gain elevated system privileges.

Executive Summary:
Mitsubishi Electric FREQSHIP-mini for Windows is affected by an incorrect default permissions vulnerability that could allow local attackers to compromise system integrity.

Vulnerability Details

CVE-ID: CVE-2025-10314

Affected Software: Mitsubishi Electric FREQSHIP-mini

Affected Versions: Windows versions 8; See vendor advisory for specific affected versions

Vulnerability: This vulnerability stems from incorrect default permissions within the FREQSHIP-mini software environment. A local, authenticated attacker could exploit these weak access controls to modify sensitive files or escalate privileges on the host Windows system.

Business Impact

A successful exploit of this vulnerability could lead to unauthorized access to industrial communication data or the underlying operating system. Given the CVSS score of 8.8, the risk is high; an attacker with local access could disrupt industrial workflows, compromise data integrity, or facilitate further lateral movement within the corporate network, leading to significant operational downtime.

Remediation Plan

Immediate Action: Apply the latest security updates provided by Mitsubishi Electric for FREQSHIP-mini immediately to correct the file system permissions.

Proactive Monitoring: Review Windows security logs for unauthorized permission changes or unusual account activity originating from local users.

Compensating Controls: Implement the principle of least privilege (PoLP) by restricting local interactive login access to the Windows host to only essential personnel.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of February 5, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the high CVSS score of 8.8 and the critical nature of industrial software, the potential for exploitation remains significant if systems are left unpatched.

Analyst Recommendation

The high severity rating (8.8) necessitates immediate remediation to prevent local privilege escalation. IT and OT administrators should prioritize the deployment of the vendor-supplied security patch to ensure that default permissions are hardened against unauthorized modification.

Executive Summary:
A high-severity vulnerability has been identified in the "Find And Replace content for WordPress" plugin. This flaw allows low-privileged authenticated users to inject malicious code and arbitrarily replace content on the website, potentially leading to website defacement, redirection of visitors to malicious sites, or theft of sensitive user and administrator data. Immediate patching is required to mitigate the risk of compromise.

Vulnerability Details

CVE-ID: CVE-2025-10313

Affected Software: Find And Replace content for WordPress plugin

Affected Versions: All versions up to, and including, 1

Vulnerability: The vulnerability exists within the far_admin_ajax_fun() function, which is accessible via WordPress's AJAX API. This function fails to perform a capability check, which is a security mechanism to ensure that the user making the request has the appropriate permissions (e.g., administrator) to perform sensitive actions. Because this check is missing, any authenticated user, including those with low-level permissions like a subscriber, can invoke this function to find and replace any content across the website. An attacker can leverage this to either replace legitimate content with misinformation or inject a persistent Cross-Site Scripting (XSS) payload, which will execute in the browsers of all visitors, including administrators.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 7.2. Successful exploitation could have a significant negative impact on the business. The ability to arbitrarily replace content can lead to website defacement, causing severe reputational damage and loss of customer trust. The Stored XSS component allows an attacker to steal session cookies from authenticated users, potentially leading to account takeover, including the hijacking of administrator accounts. This could result in a full site compromise, data breaches, or the use of the website to host phishing campaigns or distribute malware to visitors.

Remediation Plan

Immediate Action: Immediately update the "Find And Replace content for WordPress" plugin to the latest patched version (greater than version 1). If a patch is not yet available or the plugin is not critical, disable and delete it. As a best practice, review all installed plugins and themes, removing any that are no longer needed to reduce the overall attack surface.

Proactive Monitoring: Monitor web server access logs for an unusual number of POST requests to /wp-admin/admin-ajax.php with the action parameter set to far_admin_ajax_fun, especially from non-administrative users. Implement a file integrity monitoring system to alert on unexpected changes to website content and files. Use a Web Application Firewall (WAF) to inspect traffic for common XSS payloads and block malicious requests.

Compensating Controls: If patching cannot be performed immediately, disable the plugin as the primary compensating control. If the plugin must remain active, implement a stringent Web Application Firewall (WAF) rule to block requests to the vulnerable AJAX action from unauthorized users. Additionally, enforce the principle of least privilege by regularly reviewing user roles and disabling public user registration if not required for business operations.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of October 16, 2025, there are no confirmed reports of this vulnerability being actively exploited in widespread campaigns. However, due to the ease of exploitation, proof-of-concept (PoC) code is publicly available. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, but this status could change rapidly as threat actors begin to incorporate it into their toolkits.

Analyst Recommendation

Given the high severity (CVSS 7.2) and the public availability of exploit code, immediate action is strongly recommended. Organizations must prioritize patching this vulnerability on all public-facing WordPress instances to prevent potential website compromise and reputational damage. Although not currently on the CISA KEV list, its simplicity makes it an attractive target for opportunistic attackers. A full audit of all installed plugins should be conducted to identify and remediate other potentially vulnerable components.

Executive Summary:
A high-severity privilege escalation vulnerability exists in the "WPBifröst – Instant Passwordless Temporary Login Links" WordPress plugin. This flaw allows any authenticated user, regardless of their permission level, to generate a temporary login link for any account, including an administrator. Successful exploitation could result in a complete compromise of the affected WordPress site.

Vulnerability Details

CVE-ID: CVE-2025-10299

Affected Software: WPBifröst – Instant Passwordless Temporary Login Links plugin for WordPress

Affected Versions: All versions up to, and including, 1

Vulnerability: The vulnerability is a Broken Access Control issue caused by a missing capability check. The plugin's ctl_create_link AJAX function, which is responsible for generating passwordless login links, fails to verify that the user initiating the request has the necessary administrative permissions. A low-privileged authenticated attacker, such as a subscriber, can send a direct request to this AJAX endpoint to create a one-time login link for a high-privileged user (e.g., an administrator). The attacker can then use this link to gain full administrative access to the WordPress site.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 8.8. A successful exploit would grant an attacker complete administrative control over the website. This could lead to severe business consequences, including theft of sensitive user data, financial information, and intellectual property; website defacement causing significant reputational damage; and the use of the compromised server to host malware or launch further attacks against other systems.

Remediation Plan

Immediate Action: Immediately update the "WPBifröst – Instant Passwordless Temporary Login Links" plugin to the latest patched version provided by the vendor. If the plugin is not essential for business operations, the recommended course of action is to deactivate and delete it entirely to eliminate the attack surface.

Proactive Monitoring: Security teams should review web server access logs for POST requests to /wp-admin/admin-ajax.php containing the parameter action=ctl_create_link. Monitor for such requests originating from non-administrative users. Additionally, audit WordPress security logs for unexpected administrator logins, unusual session activity, or the creation of new, unauthorized administrative accounts.

Compensating Controls: If patching is not immediately feasible, implement a Web Application Firewall (WAF) rule to block or alert on requests to the vulnerable AJAX action (ctl_create_link) from users who are not in the administrator role. Restricting new user registrations or enforcing the principle of least privilege for all user accounts can also help reduce the initial attack surface.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of October 15, 2025, there are no confirmed reports of this vulnerability being actively exploited in the wild. However, given the simplicity of exploitation (requiring only a low-privileged account) and the high impact, it is highly probable that proof-of-concept exploits will be publicly released, leading to an increased risk of opportunistic attacks.

Analyst Recommendation
Due to the high CVSS score of 8.8 and the ease of exploitation, this vulnerability poses a critical risk to affected organizations. We strongly recommend that administrators take immediate action to apply the vendor-supplied patch by updating the plugin. If the plugin's functionality is not critical, it should be removed immediately. Although this CVE is not currently listed on the CISA KEV catalog, its severity warrants urgent attention to prevent a full site compromise.

Executive Summary:
A critical authentication bypass vulnerability has been identified in the OwnID Passwordless Login plugin for WordPress. This flaw allows an unauthenticated attacker to bypass security checks and gain unauthorized access to user accounts, including administrative accounts. Successful exploitation could lead to a full compromise of the affected WordPress site.

Vulnerability Details

CVE-ID: CVE-2025-10294

Affected Software: The OwnID Passwordless Login plugin for WordPress

Affected Versions: All versions up to, and including, 1.3.4

Vulnerability: The vulnerability exists because the plugin fails to properly validate authentication tokens or session data during the login process. An unauthenticated attacker can craft a malicious request to the plugin's authentication endpoint, likely by manipulating the ownid_share parameter or related data, to impersonate any user on the WordPress site. This bypasses the passwordless login mechanism entirely, granting the attacker access to the targeted account without any user interaction or valid credentials.

Business Impact

This vulnerability is rated as critical with a CVSS score of 9.8. A successful exploit grants an attacker complete control over any user account on the website, which could include administrator accounts. The potential business impact is severe and includes theft of sensitive user data, unauthorized content modification or website defacement, installation of malware or backdoors, and significant reputational damage. The ease of exploitation combined with the high impact poses a direct and immediate threat to any organization using the affected plugin.

Remediation Plan

Immediate Action: Immediately update the OwnID Passwordless Login plugin for WordPress to the latest version available (newer than 1.3.4) which contains the security patch for this vulnerability. After patching, review administrator and user access logs for any signs of suspicious login activity that may have occurred prior to the update.

Proactive Monitoring: System administrators should actively monitor web server access logs and WordPress security logs for unusual or anomalous login attempts. Specifically, look for direct POST requests to plugin-specific endpoints from unknown IP addresses or patterns that deviate from normal login flows. Implementing security information and event management (SIEM) rules to alert on multiple failed login attempts followed by a sudden success from the same source can help detect exploitation.

Compensating Controls: If immediate patching is not feasible, consider temporarily disabling the OwnID Passwordless Login plugin until it can be updated. Alternatively, implement a Web Application Firewall (WAF) with rules specifically designed to block malicious requests targeting the vulnerable plugin endpoints. Restricting access to the WordPress login page to trusted IP addresses can also serve as a temporary mitigating control.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Oct 15, 2025, there are no known public proof-of-concept exploits for this vulnerability, and it is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. However, due to the critical severity and the straightforward nature of authentication bypass flaws, it is highly probable that threat actors will develop exploits in the near future.

Analyst Recommendation
Given the critical CVSS score of 9.8, this vulnerability requires immediate attention. Organizations are strongly advised to apply the vendor-supplied patch to all affected WordPress instances without delay. The risk of a full site compromise is extremely high. Prioritize this update above other routine maintenance and audit logs for any potential signs of compromise.

Executive Summary:
A high-severity vulnerability has been identified in the Keyy Two Factor Authentication plugin for WordPress, which allows for privilege escalation. An unauthenticated attacker could exploit this flaw to bypass security controls and take over user accounts, including those with administrative privileges, leading to a full compromise of the affected website.

Vulnerability Details

CVE-ID: CVE-2025-10293

Affected Software: WordPress Multiple Products

Affected Versions: All versions up to, and including, 1 of the Keyy Two Factor Authentication plugin.

Vulnerability: The Keyy Two Factor Authentication plugin contains a critical flaw in its authentication mechanism. An attacker can manipulate the authentication process to bypass the second-factor requirement and impersonate any user on the WordPress site. This is achievable by intercepting and modifying the authentication handshake or by exploiting a weakness in how the plugin validates the user session, allowing the attacker to escalate their privileges to that of the targeted account, such as an administrator.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 8.8, posing a significant risk to the organization. Successful exploitation could lead to a complete compromise of the corporate website. Potential consequences include theft of sensitive data (customer information, intellectual property), unauthorized content modification, website defacement, and the use of the compromised server to launch further attacks or distribute malware, resulting in severe reputational damage and potential financial loss.

Remediation Plan

Immediate Action: Immediately update the "Keyy Two Factor Authentication" plugin to the latest patched version provided by the vendor. If this plugin is no longer business-critical or has been abandoned, it should be deactivated and completely removed from the WordPress installation to eliminate the attack surface.

Proactive Monitoring: Monitor WordPress authentication logs for unusual or suspicious login patterns, such as multiple failed login attempts followed by a success, or logins for administrative accounts from unexpected IP addresses or geographic locations. Regularly audit user accounts for unauthorized privilege changes or the creation of new, unknown administrative users.

Compensating Controls: If immediate patching is not feasible, disable the vulnerable plugin immediately and revert to standard WordPress password authentication or implement a different, secure two-factor authentication solution. Deploy a Web Application Firewall (WAF) with rules designed to detect and block account takeover attempts. Restrict access to the WordPress administrative dashboard (/wp-admin) to trusted IP addresses only.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of October 15, 2025, there are no known public proof-of-concept exploits or active malicious campaigns targeting this vulnerability. However, vulnerabilities in WordPress plugins are frequently and rapidly exploited by threat actors once details become public.

Analyst Recommendation

Given the high CVSS score of 8.8 and the potential for a complete site compromise, this vulnerability should be treated as a critical priority. Although it is not currently listed on the CISA KEV catalog, organizations are strongly advised to apply the recommended remediation actions immediately. All WordPress sites using the "Keyy Two Factor Authentication" plugin must be identified and patched or have the plugin removed without delay to prevent potential exploitation.

Executive Summary:
A critical vulnerability has been identified in the BBOT unarchive module, impacting multiple products. This flaw allows an attacker to gain complete control over an affected system by tricking it into extracting a specially crafted malicious archive file, which can lead to a full system compromise, data theft, or service disruption.

Vulnerability Details

CVE-ID: CVE-2025-10284

Affected Software: Unknown Multiple Products

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability exists within BBOT's unarchive module, which is responsible for extracting compressed files (e.g., .zip, .tar). An attacker can create a malicious archive containing files with manipulated path information, such as directory traversal sequences ("../"). When the vulnerable module processes this archive, it fails to properly sanitize these paths, allowing the attacker to write a file to an arbitrary location on the server's filesystem. By overwriting critical system files or planting a malicious script (e.g., a web shell) in an executable directory, an attacker can achieve remote code execution and gain full control over the affected system.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.6, indicating a high risk to the organization. Successful exploitation could lead to a complete compromise of the affected system's confidentiality, integrity, and availability. Potential consequences include the theft of sensitive corporate or customer data, deployment of ransomware, disruption of critical business operations, and the use of the compromised system as a pivot point to launch further attacks against the internal network. The financial and reputational damage from such an incident could be substantial.

Remediation Plan

Immediate Action: The primary remediation is to apply vendor-supplied patches immediately. Organizations must identify all products using the vulnerable BBOT module and update them to the latest, non-vulnerable version as a top priority.

Proactive Monitoring: Security teams should actively monitor for signs of exploitation. This includes scrutinizing logs for any errors or suspicious activity related to file extraction, monitoring for unexpected file creation in sensitive system directories (e.g., /var/www/html, /etc/, /bin/), and analyzing network traffic for unusual outbound connections that could indicate a command-and-control channel.

Compensating Controls: If immediate patching is not feasible, implement the following compensating controls:

• Restrict or disable the functionality that processes externally supplied archive files.
• Use a Web Application Firewall (WAF) with rules designed to detect and block directory traversal patterns in file uploads.
• Run the affected application in a sandboxed or containerized environment with strict, read-only permissions for most of the filesystem to limit the impact of an arbitrary file write.
• Implement File Integrity Monitoring (FIM) on critical application and system directories to alert on unauthorized file modifications.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of October 9, 2025, there are no known public exploits or active exploitation campaigns targeting this vulnerability. However, due to the critical severity and the straightforward nature of arbitrary file write vulnerabilities, it is highly probable that proof-of-concept exploits will be developed and weaponized by threat actors in the near future.

Analyst Recommendation

Given the critical CVSS score of 9.6, this vulnerability represents a severe and immediate threat to the organization. Although it is not currently listed on the CISA KEV catalog, its potential for enabling complete system compromise makes it a prime candidate for future inclusion. We strongly recommend that organizations prioritize the identification of all affected assets and apply the necessary patches immediately. If patching is delayed for any reason, compensating controls must be implemented without delay to mitigate the significant risk of exploitation.

Executive Summary:
A critical remote code execution vulnerability has been identified in the BBOT security tool's gitdumper module. An attacker can craft a malicious git repository which, when processed by the tool, allows them to execute arbitrary commands and gain complete control of the underlying system. Due to the high severity score, this vulnerability poses a significant risk of system compromise, data theft, and further network intrusion.

Vulnerability Details

CVE-ID: CVE-2025-10283

Affected Software: Unknown Multiple Products

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability exists within the gitdumper module of the BBOT tool, which may be integrated into various products. The module is designed to interact with git repositories. An attacker can host a malicious git repository containing specially crafted elements, such as malicious git hooks (e.g., post-checkout) or a manipulated .git/config file. When the vulnerable gitdumper module clones or interacts with this repository, it improperly handles these elements, leading to the execution of commands embedded by the attacker on the server running the BBOT tool. Successful exploitation requires the tool to be triggered to scan or interact with the attacker-controlled repository.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.6, indicating a high potential for widespread and damaging impact. Successful exploitation results in Remote Code Execution (RCE), granting an attacker full control over the affected server. The potential consequences include theft of sensitive data, deployment of ransomware, disruption of critical services, and using the compromised system as a pivot point to launch further attacks against the internal network. The "Multiple Products" classification suggests the attack surface may be broad and difficult to identify across the enterprise without a specific vendor advisory.

Remediation Plan

Immediate Action: Organizations must identify all instances of the affected products within their environment and immediately apply the patches provided by the vendor to update to the latest version. After patching, review system and application access logs for any signs of compromise or unusual activity preceding the update.

Proactive Monitoring: Security teams should monitor for indicators of exploitation. This includes inspecting network logs for outbound connections to unusual or untrusted git repository hosting services from servers running the affected software. Monitor for unexpected child processes being spawned by the BBOT tool or the user account it runs under. SIEM alerts should be configured to detect anomalous command-line executions on these systems.

Compensating Controls: If immediate patching is not feasible, implement compensating controls to reduce risk. Restrict outbound network access from the servers running the affected software, specifically blocking connections to public code repositories on ports 22, 443, and 9418. Run the BBOT tool within a sandboxed or containerized environment with minimal privileges and strict process execution policies to limit the impact of a potential compromise.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Oct 9, 2025, there are no known public proof-of-concept exploits or active exploitation campaigns targeting this vulnerability. However, given the critical severity and the straightforward nature of the attack vector, it is highly probable that a functional exploit will be developed and released by security researchers or malicious actors in the near future.

Analyst Recommendation

Due to the critical severity (CVSS 9.6) and the risk of remote code execution, this vulnerability represents a significant threat to the organization. It is our strong recommendation that all affected systems be identified and patched immediately. Although this CVE is not currently listed on the CISA KEV catalog, its high impact score makes it a prime candidate for future inclusion and a high-value target for attackers. Treat this vulnerability with the highest priority and expedite remediation efforts to prevent a potential system compromise.

---METADATA---
VENDOR: MLflow
PRODUCT: MLflow
AFFECTED_VERSIONS: Version 2
---END_METADATA---

Description Summary:
A vulnerability in MLflow version 2 could lead to unauthorized access or data manipulation within the machine learning lifecycle platform.

Executive Summary:
MLflow version 2 is affected by a High-severity vulnerability that could allow attackers to compromise machine learning experiments and data.

Vulnerability Details

CVE-ID: CVE-2025-10279

Affected Software: MLflow

Affected Versions: Version 2

Vulnerability: This vulnerability affects MLflow, an open-source platform for the machine learning lifecycle. With a CVSS score of 7.0, the flaw likely involves insecure deserialization, path traversal, or improper access control within the MLflow tracking server or UI.

Business Impact

The compromise of an MLflow instance can lead to the loss or corruption of machine learning models, training parameters, and sensitive datasets. This impacts the integrity of AI-driven decision-making and can result in significant intellectual property theft.

Remediation Plan

Immediate Action: Update MLflow to the latest patched version immediately to address the identified security flaw.

Proactive Monitoring: Audit the MLflow tracking server for unauthorized experiment creation or unexpected modifications to existing model artifacts.

Compensating Controls: Deploy MLflow behind an authentication proxy (like Nginx with OIDC) to ensure that only authorized users can interact with the API and UI.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of February 3, 2026, there is no public information indicating active exploitation. MLflow is a critical tool in the MLOps pipeline, making it a high-value target for industrial espionage.

Analyst Recommendation

Organizations relying on MLflow for their AI workflows must prioritize this update. Applying the latest patch is essential to maintaining the confidentiality and integrity of the machine learning research and deployment pipeline.

Executive Summary:
A high-severity vulnerability has been identified in the Spirit Framework plugin for WordPress, which could allow an unauthenticated attacker to read sensitive files from the underlying server. Successful exploitation could lead to the exposure of confidential information, such as website configuration details and system credentials, posing a significant risk to data security and system integrity. Organizations using the affected plugin are urged to take immediate action to mitigate this threat.

Vulnerability Details

CVE-ID: CVE-2025-10269

Affected Software: WordPress Spirit Framework plugin

Affected Versions: All versions up to, and including, 1

Vulnerability: The Spirit Framework plugin is vulnerable to Local File Inclusion (LFI). This flaw exists because the application does not properly validate user-supplied input when including files. An unauthenticated attacker can exploit this by manipulating a URL parameter to specify a path to a sensitive file on the server, causing the application to read and display the contents of that file. For example, an attacker could potentially access files like wp-config.php to steal database credentials or /etc/passwd to enumerate system users.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 7.5. Exploitation could lead to a significant data breach, exposing sensitive business and customer information. Specific risks include the theft of database credentials, API keys, and other secrets stored on the server, which could enable an attacker to gain further unauthorized access, compromise the entire website, or pivot to other systems on the network. The potential consequences include reputational damage, regulatory fines, and the financial cost associated with incident response and recovery.

Remediation Plan

Immediate Action:

• Immediately update the Spirit Framework plugin and any themes relying on it to the latest patched version provided by the vendor.
• If the plugin or theme is no longer required for business operations, it should be deactivated and completely removed from the WordPress installation to eliminate the attack surface.
• Review WordPress security settings to ensure they align with best practices for file permissions and user access control.

Proactive Monitoring:

• Monitor web server access logs for suspicious requests containing directory traversal patterns (e.g., ../, ..%2f) or absolute file paths in URL parameters.
• Implement file integrity monitoring on critical WordPress core files, including wp-config.php, to detect any unauthorized access or changes.
• Review network traffic for unusual outbound data flows which could indicate data exfiltration.

Compensating Controls:

• Deploy a Web Application Firewall (WAF) with rules specifically designed to detect and block LFI and directory traversal attack patterns.
• Harden the web server's file system permissions to restrict the web server user's read access to only necessary directories, preventing it from accessing sensitive system files outside the web root.
• Disable PHP functions that are commonly abused in LFI attacks, such as file_get_contents and include, if they are not essential for the application's functionality.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of September 12, 2025, proof-of-concept (PoC) exploit code is publicly available for this vulnerability. Local File Inclusion vulnerabilities in WordPress plugins are trivial to exploit and are frequently targeted by automated scanning tools shortly after disclosure. While there are no confirmed reports of widespread active exploitation at this time, the availability of a public PoC significantly increases the likelihood of attacks in the near future.

Analyst Recommendation

Given the high severity (CVSS 7.5) and the public availability of exploit code, immediate remediation is strongly recommended. Organizations must prioritize patching all websites using the vulnerable Spirit Framework plugin. Although this CVE is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, the ease of exploitation makes it a prime target for opportunistic attackers. All affected assets should be identified and patched or have compensating controls applied within the next 72 hours to prevent potential compromise.

Executive Summary:
A critical SQL Injection vulnerability, identified as CVE-2025-10266, has been discovered in NUP Pro software developed by NewType Infortech. This flaw allows a remote, unauthenticated attacker to gain complete control over the application's database. Successful exploitation could result in a severe data breach, including the theft, modification, or deletion of sensitive organizational and customer information.

Vulnerability Details

CVE-ID: CVE-2025-10266

Affected Software: NUP Pro (Multiple Products)

Affected Versions: See vendor advisory for specific affected versions.

Vulnerability: The vulnerability is a classic SQL Injection that exists because the application does not properly sanitize or validate user-supplied input before constructing a SQL query. An unauthenticated remote attacker can send specially crafted data to an exposed application endpoint (e.g., a web form, API endpoint, or URL parameter). This malicious input is then directly incorporated into a database query, allowing the attacker's SQL commands to be executed with the same privileges as the application's database user, leading to a full compromise of the database.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.8. Successful exploitation could lead to a severe data breach and significant business disruption. The potential consequences include the theft of confidential data (such as customer personally identifiable information (PII), financial records, and intellectual property), unauthorized modification or deletion of critical data leading to service unavailability and loss of data integrity, and reputational damage. A breach of this nature could also result in significant regulatory fines and legal liabilities.

Remediation Plan

Immediate Action:

• Identify all instances of the affected NUP Pro software within the environment.
• Apply the security patches or update to the latest version as recommended by the vendor, NewType Infortech, immediately.
• After patching, review application and database access logs for any signs of past or ongoing exploitation attempts, such as unusual queries or error messages.

Proactive Monitoring:

• Log Analysis: Scrutinize application and database logs for suspicious queries containing SQL keywords like UNION, SELECT, --, ', or ; in user input fields.
• Network Traffic: Monitor for anomalous outbound traffic from the database server, which could be an indicator of data exfiltration.
• WAF/IDS/IPS: Implement and tune Web Application Firewall (WAF) or Intrusion Detection/Prevention System (IDS/IPS) signatures that specifically target SQL injection patterns.

Compensating Controls:

• Web Application Firewall (WAF): If immediate patching is not feasible, deploy a WAF in front of the affected application and configure it with strict rules to block SQL injection attack patterns.
• Principle of Least Privilege: Ensure the database account used by the application has the minimum necessary permissions to function, preventing it from performing high-privilege actions like dropping tables or accessing the underlying operating system.
• Network Segmentation: Restrict network access to the database server so that it can only be reached from the application server, limiting the attack surface.

Exploitation Status

Public Exploit Available: False (as of Sep 12, 2025)

Analyst Notes:
As of the publication date, Sep 12, 2025, there are no known public exploits for this vulnerability. However, given the critical severity (CVSS 9.8) and the ease of exploitation for unauthenticated SQL injection flaws, it is highly probable that a functional exploit will be developed and used by threat actors in the near future. Organizations should assume that active exploitation is imminent.

Analyst Recommendation
This vulnerability represents a critical risk to the organization and must be addressed with the highest priority. The potential for a complete database compromise by an unauthenticated attacker necessitates immediate action. While this CVE is not currently on the CISA Known Exploited Vulnerabilities (KEV) catalog, its critical nature makes it a prime candidate for future inclusion. All system owners must prioritize the deployment of the vendor-supplied updates or, if patching is not possible, implement the recommended compensating controls without delay to prevent a potentially catastrophic data breach.

Executive Summary:
A critical vulnerability, identified as CVE-2025-10265, has been discovered in certain Digiever Network Video Recorder (NVR) models. This flaw allows a remote, unauthenticated attacker to take complete control of the affected device, potentially leading to the compromise of surveillance footage, system shutdown, or further attacks on the internal network.

Vulnerability Details

CVE-ID: CVE-2025-10265

Affected Software: Digiever Network Video Recorders (NVRs)

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability is an OS Command Injection flaw that can be exploited by an unauthenticated attacker over the network. By sending a specially crafted request to the device, an attacker can inject and execute arbitrary operating system commands with the privileges of the NVR's web service. This allows the attacker to gain a remote shell on the system, granting them full control over the device and its functions.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.8, posing a significant and immediate risk to the organization. Successful exploitation could lead to severe consequences, including the theft, modification, or deletion of sensitive video surveillance data, compromising physical security. An attacker could also disable the NVR, creating a surveillance blackout, or use the compromised device as a pivot point to launch further attacks against other systems on the internal network.

Remediation Plan

Immediate Action: Immediately apply the latest firmware updates provided by the vendor to all affected Digiever NVR models. Before and after patching, closely monitor device logs for any signs of compromise or unusual activity. Review historical access logs for indicators of exploitation attempts that may have occurred prior to remediation.

Proactive Monitoring: Implement enhanced monitoring for affected devices. Look for unusual outbound network traffic from the NVRs, unexpected processes or services running on the devices, and anomalous patterns in web server access logs that may indicate command injection attempts (e.g., requests containing shell metacharacters like ;, |, &&).

Compensating Controls: If immediate patching is not feasible, implement the following controls to mitigate risk:

• Isolate the NVRs from the public internet.
• Segment the NVRs onto a dedicated network VLAN with strict firewall rules, allowing access only from trusted security management workstations.
• Deploy an Intrusion Prevention System (IPS) with signatures capable of detecting and blocking OS command injection attacks.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Sep 12, 2025, there are no known public exploits or active exploitation campaigns targeting this vulnerability. However, due to the critical severity and the common nature of command injection flaws, proof-of-concept exploits are likely to be developed and published quickly. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog.

Analyst Recommendation

Given the critical CVSS score of 9.8 and the potential for complete system compromise by an unauthenticated attacker, this vulnerability requires immediate attention. We strongly recommend that all affected Digiever NVRs be patched immediately. If patching cannot be performed right away, the compensating controls listed above, particularly network isolation, must be implemented as a matter of urgency to reduce the attack surface and prevent exploitation.

Executive Summary:
A critical vulnerability has been identified in multiple Digiever Network Video Recorder (NVR) models. This flaw allows an unauthenticated attacker on the network to remotely access a system configuration file, which likely contains sensitive information such as administrator credentials, leading to a complete takeover of the device and the associated surveillance system.

Vulnerability Details

CVE-ID: CVE-2025-10264

Affected Software: Multiple Digiever Network Video Recorder (NVR) models

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability is an Exposure of Sensitive Information that allows an unauthenticated remote attacker to access critical system configuration files. An attacker can exploit this by sending a specially crafted request to the device, bypassing all authentication mechanisms. The exposed configuration file contains sensitive data, including administrative credentials and network settings, in a plaintext or easily decipherable format, which can be used to gain full administrative control over the NVR.

Business Impact

This vulnerability is rated as critical with a CVSS score of 10.0. A successful exploit could lead to a complete compromise of an organization's physical security monitoring capabilities. Potential consequences include attackers viewing, manipulating, or deleting live and recorded video footage, effectively blinding security operations. Furthermore, a compromised NVR can be used as a pivot point to launch further attacks against the internal corporate network, posing a significant risk to the broader IT infrastructure. The breach of surveillance data could also lead to severe reputational damage and regulatory penalties.

Remediation Plan

Immediate Action: Immediately apply the latest firmware updates provided by Digiever to all affected NVR models as this is the primary method to resolve the vulnerability. Before and after patching, review system and access logs for any evidence of unauthorized access to configuration files or suspicious login activity.

Proactive Monitoring: Monitor network traffic to and from the NVRs for unusual patterns, such as large data transfers or connections to unknown IP addresses. In system logs, search for anomalous requests for system configuration files or repeated failed login attempts followed by a successful login from an unfamiliar source.

Compensating Controls: If immediate patching is not feasible, implement the following controls:

• Isolate the NVRs on a segmented network, separate from critical business systems and user networks.
• Restrict all access to the NVR's management interface to a limited set of authorized IP addresses using a firewall or Access Control Lists (ACLs).
• Ensure the NVRs are not directly exposed to the public internet. If remote access is required, it must be secured behind a Virtual Private Network (VPN).

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of September 12, 2025, there is no known publicly available exploit code for this vulnerability. However, given the critical severity (CVSS 10.0) and the low complexity of the attack, it is highly probable that threat actors will develop and deploy exploits rapidly. Organizations should assume active exploitation is imminent.

Analyst Recommendation

Given the critical CVSS score of 10.0, this vulnerability represents a severe and immediate threat to the organization. We strongly recommend that all affected Digiever NVRs be patched immediately. Although this vulnerability is not currently on the CISA Known Exploited Vulnerabilities (KEV) catalog, its characteristics make it a prime candidate for future inclusion. Due to the high likelihood of exploitation, patching should be treated as an emergency action. If patching cannot be performed immediately, the compensating controls listed above must be implemented without delay to mitigate the risk of compromise.

Executive Summary:
A critical remote code execution vulnerability has been discovered in Samba, a widely used software suite. An unauthenticated attacker on the same network can send a malicious network packet to take complete control of the affected server, allowing for data theft, service disruption, or further attacks on the internal network. Due to the ease of exploitation and maximum possible impact, this vulnerability is rated with the highest possible severity score.

Vulnerability Details

CVE-ID: CVE-2025-10230

Affected Software: A flaw was found in Multiple Products

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability is a command injection flaw within Samba's Windows Internet Name Service (WINS) server component. An unauthenticated attacker on the local network can send a specially crafted NetBIOS name registration request. The Samba server fails to properly sanitize the NetBIOS name from this packet before passing it to a back-end shell script for processing, allowing the attacker to inject and execute arbitrary system commands with the privileges of the Samba service, which is often root.

Business Impact

This vulnerability represents a critical risk to the organization, reflected by its CVSS score of 10.0. Successful exploitation grants an attacker complete control over the affected server, resulting in a total loss of confidentiality, integrity, and availability. Potential consequences include unauthorized access to and exfiltration of sensitive data, deployment of ransomware, manipulation or destruction of critical files, and using the compromised server as a beachhead to launch further attacks against the internal network infrastructure.

Remediation Plan

Immediate Action: The primary remediation is to apply security patches immediately. Update A flaw was found in Multiple Products to the latest version. After patching, monitor for any signs of post-exploitation activity and review historical access and system logs for indicators of compromise.

Proactive Monitoring: Security teams should monitor network traffic for malformed or unusual NetBIOS name registration packets on UDP port 137. In system logs, look for unexpected commands being executed or suspicious child processes being spawned by the Samba daemon (nmbd). Enable and centralize Samba's logs, paying close attention to WINS registration entries containing shell metacharacters (e.g., ;, $, |, `).

Compensating Controls: If immediate patching is not feasible, implement the following controls to reduce the risk of exploitation:

• Disable the WINS server functionality within the Samba configuration (smb.conf) if it is not essential for business operations.
• Implement strict network segmentation and firewall rules to restrict access to NetBIOS ports (UDP/137, UDP/138, TCP/139, TCP/445) from untrusted network segments.
• Deploy an Intrusion Prevention System (IPS) with updated signatures capable of detecting and blocking exploit attempts targeting this vulnerability.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of November 7, 2025, multiple proof-of-concept (PoC) exploits have been made publicly available. Due to the simplicity of the command injection vector, exploitation is considered trivial. While there are no widespread, confirmed reports of active exploitation by threat actors yet, this is expected to change rapidly given the vulnerability's severity and the availability of public exploits.

Analyst Recommendation

This vulnerability is of the highest criticality and requires immediate attention. All organizations using affected products must prioritize the deployment of the vendor-supplied patch across all vulnerable systems without delay. Although this CVE is not yet listed on the CISA KEV catalog, its CVSS 10.0 score and the availability of public exploits make it a prime candidate for future inclusion and a high-value target for attackers. If patching cannot be performed immediately, the compensating controls listed above must be implemented as an urgent temporary measure.

---METADATA---
VENDOR: Rolantis Information Technologies
PRODUCT: Agentis
AFFECTED_VERSIONS: Agentis: before 4.44
---END_METADATA---

Description Summary:
Rolantis Information Technologies Agentis is susceptible to a session fixation vulnerability that allows unauthorized attackers to hijack valid user sessions.

Executive Summary:
A high-severity session fixation vulnerability in Rolantis Information Technologies Agentis allows attackers to hijack user sessions, leading to unauthorized account access.

Vulnerability Details

CVE-ID: CVE-2025-10228

Affected Software: Rolantis Information Technologies Agentis

Affected Versions: Agentis: before 4.44

Vulnerability: The application fails to properly regenerate session identifiers after a successful authentication event. This allows an attacker to pre-set a session ID and subsequently hijack the session of an authenticated user, bypassing standard login security controls.

Business Impact

With a CVSS score of 8.8, this flaw represents a major threat to user account security. Successful exploitation allows for complete account takeover, enabling attackers to access sensitive corporate data, perform unauthorized transactions, and impersonate legitimate users within the Agentis platform.

Remediation Plan

Immediate Action: Upgrade Agentis to version 4.44 or later, which addresses the session management flaw.

Proactive Monitoring: Monitor for anomalous session activity, such as a single session ID associated with multiple IP addresses or abnormal login geographic patterns.

Compensating Controls: Enforce short session timeouts and require re-authentication for sensitive actions to limit the window of opportunity for an attacker holding a hijacked session.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of June 7, 2026, public information confirms the existence of exploit methods for this vulnerability. The risk of session hijacking remains high until the patch is applied.

Analyst Recommendation

Session fixation is a critical security oversight that undermines the entire authentication process. Organizations should prioritize updating to version 4.44 to ensure session tokens are securely handled and regenerated upon authentication.

Executive Summary:
A critical vulnerability has been identified in AxxonSoft Axxon One, stemming from a vulnerable third-party component within its PostgreSQL backend. This flaw allows a remote, unauthenticated attacker to escalate privileges and execute arbitrary code, potentially leading to a complete compromise of the affected video management system and the underlying server. Due to the critical severity (CVSS 9.8), immediate remediation is required to prevent system takeover and data breaches.

Vulnerability Details

CVE-ID: CVE-2025-10226

Affected Software: AxxonSoft Axxon One

Affected Versions: 2.0.8 and earlier

Vulnerability: The vulnerability, classified as CWE-1395 (Dependency on Vulnerable Third-Party Component), exists in the PostgreSQL backend used by AxxonSoft Axxon One. The software incorporates a version of PostgreSQL that contains a known, critical vulnerability. A remote attacker can exploit this underlying flaw in the database component to escalate privileges and achieve remote code execution on the server hosting the Axxon One software, without requiring prior authentication.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.8. Successful exploitation could lead to a complete compromise of the Axxon One video management system. The potential business impact includes the theft of sensitive video surveillance data, manipulation or deletion of recordings, and disabling of security monitoring capabilities. Furthermore, an attacker could use the compromised server as a foothold to pivot and launch further attacks against the internal corporate network, significantly escalating the scope and impact of the breach.

Remediation Plan

Immediate Action: Apply the vendor-supplied security updates to all AxxonSoft Axxon One installations immediately to upgrade the vulnerable PostgreSQL component to a patched version. After patching, review system and database access logs for any signs of compromise that may have occurred prior to the update.

Proactive Monitoring: Monitor network traffic for unusual connections to the PostgreSQL database port (typically TCP 5432) from untrusted sources. Scrutinize Axxon One application logs and server system logs for unexpected processes, errors, or privilege escalation events. Implement alerts for high-volume or malformed database queries that could indicate an exploitation attempt.

Compensating Controls: If immediate patching is not feasible, implement network segmentation to restrict access to the PostgreSQL port from all but the necessary application servers. Deploy an Intrusion Prevention System (IPS) with signatures capable of detecting and blocking known PostgreSQL exploits. Ensure host-based security solutions are enabled and configured to detect anomalous process execution on the server.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Sep 10, 2025, there are no known public exploits specifically targeting this CVE in Axxon One. However, the vulnerability is within a third-party component (PostgreSQL), and exploits for the underlying database flaw may already exist. Threat actors are likely to adapt these existing exploits to target Axxon One systems, making the development of a functional exploit highly probable.

Analyst Recommendation

Given the critical CVSS score of 9.8, this vulnerability represents a severe and immediate risk to the organization. We strongly recommend that all affected AxxonSoft Axxon One systems be patched on an emergency basis. Although this CVE is not currently listed on the CISA KEV catalog, its high severity and the potential for complete system compromise make it a high-priority target for threat actors. Prioritize the deployment of vendor patches to prevent a potentially devastating security incident.

Executive Summary:
A critical vulnerability has been identified in AxxonSoft Axxon One VMS, stemming from its use of unmaintained third-party components. This weakness could allow a remote attacker to execute arbitrary code, potentially leading to a complete compromise of the affected video management system. Given the critical severity, immediate patching is required to prevent unauthorized access and protect sensitive security infrastructure.

Vulnerability Details

CVE-ID: CVE-2025-10220

Affected Software: AxxonSoft Axxon One VMS

Affected Versions: 2.0.0 through 2.0.4 on Windows

Vulnerability: The vulnerability, categorized as CWE-1104 (Use of Unmaintained Third Party Components), exists within the NuGet dependency components of the AxxonSoft Axxon One VMS software. Because these components are no longer maintained, they contain known, unpatched security flaws. A remote, unauthenticated attacker can exploit one of these underlying flaws by sending specially crafted data to the VMS server, triggering a condition that allows for arbitrary code execution with the privileges of the VMS service account.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.8. A successful exploit would grant an attacker complete control over the affected Video Management System (VMS) server. The potential consequences include theft or manipulation of sensitive video surveillance data, disruption of physical security monitoring, and using the compromised server as a pivot point for further attacks into the corporate network. This could lead to significant data breaches, operational downtime, reputational damage, and potential compromise of physical security controls.

Remediation Plan

Immediate Action: Update AxxonSoft Axxon One VMS to the latest available version that addresses this vulnerability, as per the vendor's security advisory. After patching, it is crucial to monitor for any signs of post-remediation exploitation attempts and review historical access logs for indicators of a prior compromise.

Proactive Monitoring: Implement enhanced monitoring on affected VMS servers. Security teams should look for unusual outbound network connections, unexpected processes spawned by the VMS application, and anomalous access patterns in application and system event logs. Monitor for network traffic that matches signatures of known exploits for common NuGet package vulnerabilities.

Compensating Controls: If immediate patching is not feasible, apply compensating controls to reduce the risk. Isolate the VMS servers from the general corporate network using network segmentation and enforce strict firewall rules to only allow access from trusted management endpoints. Deploy an Intrusion Prevention System (IPS) with up-to-date signatures to detect and block potential exploit traffic.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of the publication date, Sep 10, 2025, there are no known public proof-of-concept exploits or active attacks targeting this specific CVE. However, the vulnerability is rooted in unmaintained components, meaning that exploits for the underlying flaws may already exist and could be easily adapted by threat actors.

Analyst Recommendation

Given the critical CVSS score of 9.8 and the risk of complete system compromise, organizations must treat this vulnerability with the highest priority. We strongly recommend applying the vendor-provided patches to all affected AxxonSoft Axxon One VMS installations immediately. Although this vulnerability is not currently listed on the CISA KEV (Known Exploited Vulnerabilities) catalog, its high severity makes it an attractive target for attackers, and immediate remediation is the most effective course of action to prevent exploitation.

Executive Summary:
A high-severity path traversal vulnerability has been identified in Relative's Digilent WaveForms software. This flaw could allow a remote attacker to access, modify, or delete sensitive files on the server and potentially execute malicious code, leading to a full system compromise. Organizations are urged to apply the vendor-provided security updates immediately to mitigate the risk of data breaches and operational disruption.

Vulnerability Details

CVE-ID: CVE-2025-10203

Affected Software: Relative Digilent WaveForms

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability is a relative path traversal (also known as "dot-dot-slash") attack. It exists because the application fails to properly validate or sanitize user-supplied input that is used to construct file paths. An unauthenticated remote attacker can exploit this by crafting a malicious request containing "dot-dot-slash" (../) sequences to navigate outside of the intended directory and access arbitrary files on the system. Successful exploitation could allow an attacker to read sensitive configuration files, overwrite critical system files, or upload and execute a malicious script, resulting in arbitrary code execution with the privileges of the application's user account.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 7.8. A successful exploit could lead to a complete compromise of the affected system. The primary business impacts include the potential for a significant data breach, leading to the theft of confidential company information, customer data, or intellectual property. Furthermore, arbitrary code execution could lead to the installation of ransomware, disruption of critical business operations, and reputational damage. The compromised system could also be used as a pivot point to launch further attacks against the internal network.

Remediation Plan

Immediate Action: The primary remediation is to apply the security updates provided by the vendor across all affected systems immediately. Before deployment, patches should be tested in a non-production environment to ensure compatibility. After patching, review system access logs and application logs for any signs of compromise that may have occurred prior to remediation.

Proactive Monitoring: System administrators should actively monitor application and server logs for requests containing path traversal sequences (e.g., ../, ..\). Monitor for unusual file access patterns, unexpected process execution from the application's service account, or the creation of unauthorized files in system or web directories. Network monitoring should be configured to detect and alert on suspicious outbound connections from the affected servers, which could indicate a successful compromise.

Compensating Controls: If immediate patching is not feasible, consider implementing the following controls:

• Deploy a Web Application Firewall (WAF) with rules specifically designed to detect and block path traversal attempts.
• Enforce the principle of least privilege by ensuring the application's service account has the minimum necessary file system permissions, preventing it from writing to or reading from sensitive directories.
• Use host-based intrusion detection systems (HIDS) to monitor for and prevent unauthorized file modifications.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of the publication date of September 15, 2025, there are no known public proof-of-concept exploits or active exploitation of this vulnerability in the wild. However, given the high severity and the nature of path traversal flaws, it is highly likely that threat actors will reverse-engineer the patch to develop exploits. Organizations should assume exploitation is imminent.

Analyst Recommendation

Given the high CVSS score of 7.8 and the potential for complete system compromise via arbitrary code execution, this vulnerability poses a significant risk to the organization. Although not currently listed on the CISA KEV catalog, its severity makes it a prime target for future exploitation. We strongly recommend that all system owners prioritize the immediate testing and deployment of the vendor-supplied security patches to all affected systems to prevent potential exploitation.

Executive Summary:
A high-severity vulnerability, identified as CVE-2025-10201, has been discovered in Google Chrome's Mojo component affecting multiple platforms. This flaw allows a remote attacker to execute arbitrary code on a user's system by tricking them into visiting a specially crafted malicious website. Successful exploitation could lead to a complete system compromise, resulting in data theft, malware installation, or further network intrusion.

Vulnerability Details

CVE-ID: CVE-2025-10201

Affected Software: Google Multiple Products

Affected Versions: Google Chrome on Android, Linux, and ChromeOS versions prior to 140

Vulnerability: This vulnerability is an inappropriate implementation flaw within Mojo, Google's core inter-process communication (IPC) library. An attacker can exploit this by creating a malicious webpage that sends malformed data through the Mojo IPC channels. This triggers a memory corruption or logic error that can be leveraged to escape the browser's security sandbox and execute arbitrary code on the underlying operating system with the privileges of the logged-in user.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 8.8. Successful exploitation could have a significant business impact, leading to remote code execution on employee workstations or devices. Potential consequences include the theft of sensitive corporate data, deployment of ransomware, installation of spyware to capture credentials, and using the compromised system as a beachhead to launch further attacks against the internal network. Given the widespread use of Google Chrome, this vulnerability presents a large attack surface and a critical risk to data confidentiality, integrity, and system availability.

Remediation Plan

Immediate Action: The primary remediation is to apply vendor-supplied security updates immediately. All instances of Google Chrome on affected platforms must be updated to version 140 or later. Concurrently, security teams should actively monitor for any signs of exploitation, such as unusual browser process behavior, and review network and endpoint logs for indicators of compromise.

Proactive Monitoring: Security teams should monitor for anomalies that could indicate exploitation. This includes observing browser processes for unexpected child processes, unusual network connections to unknown domains, and alerts from Endpoint Detection and Response (EDR) solutions related to sandbox escapes or memory corruption exploits. Reviewing DNS and web proxy logs for traffic to suspicious or newly registered domains is also recommended.

Compensating Controls: If immediate patching is not feasible, the following controls can help reduce risk:

• Enforce strict web filtering policies to block access to uncategorized or known malicious websites.
• Utilize application control solutions to prevent the execution of unauthorized executables that could be downloaded post-exploitation.
• Ensure EDR and antivirus signatures and behavioral detection engines are fully updated.
• Reinforce user awareness training regarding phishing and the risks of navigating to untrusted websites.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of September 11, 2025, there is no known publicly available exploit code for this vulnerability. However, high-severity browser vulnerabilities are prime targets for exploit development by both security researchers and malicious actors. Organizations should assume that an exploit will become available and act accordingly.

Analyst Recommendation

Given the high severity (CVSS 8.8) of this vulnerability and its potential for remote code execution, we strongly recommend that organizations treat this as a critical priority. The risk of system compromise is significant. Although CVE-2025-10201 is not currently on the CISA KEV list, its status could change without warning. All system administrators should prioritize the immediate deployment of Google Chrome version 140 or later across all managed endpoints to mitigate this threat.

Executive Summary:
A high-severity vulnerability has been discovered in the Google Chrome web browser that could allow an attacker to execute arbitrary code on a user's computer. Successful exploitation requires an attacker to lure a victim to a specially crafted malicious website, which could lead to a full system compromise, data theft, or malware installation.

Vulnerability Details

CVE-ID: CVE-2025-10200

Affected Software: Google Chrome on Desktop

Affected Versions: Google Chrome on Desktop prior to version 140

Vulnerability: This vulnerability is a "Use-after-free" (UAF) memory corruption flaw within the Serviceworker component of Google Chrome. A UAF occurs when a program attempts to access a memory location after it has been deallocated or "freed." An attacker can exploit this by creating a malicious webpage with specific code that triggers this condition in the Serviceworker API, causing the browser to mishandle memory. Successful exploitation can lead to a browser crash (denial of service) or, more critically, allow the attacker to execute arbitrary code on the victim's system, initially within the context of the browser's security sandbox.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 8.8. A successful exploit could have a significant business impact by allowing an attacker to compromise employee workstations. Potential consequences include the theft of sensitive corporate data, intellectual property, or user credentials stored on the system. Furthermore, an attacker could install persistent malware, such as ransomware or spyware, or use the compromised machine as a beachhead to move laterally and attack other systems on the corporate network. Given the widespread use of Google Chrome in enterprise environments, the attack surface is extensive.

Remediation Plan

Immediate Action: The primary remediation is to apply vendor-supplied security updates immediately. All instances of Google Chrome on Desktop should be updated to version 140 or later. Following the update, security teams should monitor for any signs of exploitation attempts and review web proxy and endpoint security logs for anomalous activity related to browser processes.

Proactive Monitoring: Security teams should monitor for signs of compromise, including:

• Unusual network connections originating from chrome.exe processes.
• Unexpected child processes being spawned by the browser.
• Endpoint Detection and Response (EDR) alerts for memory corruption, code injection, or sandbox escape techniques.
• Reviewing web filter logs for traffic to suspicious or newly registered domains.

Compensating Controls: If immediate patching is not feasible, the following controls can help mitigate risk:

• Utilize web filtering solutions to block access to untrusted and malicious websites.
• Ensure endpoint security software (Antivirus/EDR) is up-to-date and configured to detect and block browser-based exploits.
• Enforce the principle of least privilege, ensuring users do not run browsers with administrative rights.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of September 10, 2025, there is no known public proof-of-concept exploit code, and the vulnerability is not reported to be actively exploited in the wild. However, high-severity vulnerabilities in widely used browsers are prime targets for threat actors, and exploit development is likely. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog.

Analyst Recommendation

Given the high CVSS score of 8.8 and the potential for remote code execution, this vulnerability poses a significant risk to the organization. We strongly recommend that all system administrators prioritize the immediate deployment of Google Chrome version 140 or newer to all corporate workstations. Although there is no evidence of active exploitation at this time, the risk profile of this vulnerability warrants urgent attention to prevent future compromise.

---METADATA---
VENDOR: TecCom
PRODUCT: TecConnect
AFFECTED_VERSIONS: 4.1
CONFIDENCE: high
MISSING: patch, exploit_status
---END_METADATA---

Description Summary:
A blind XML External Entity (XXE) injection in the OpenMessaging webservice of TecCom TecConnect 4.1 allows unauthenticated attackers to exfiltrate arbitrary files.

Executive Summary:
An unauthenticated blind XXE vulnerability in TecCom TecConnect 4.1 poses a critical risk of arbitrary file exfiltration and potential system compromise.

Vulnerability Details

CVE-ID: CVE-2025-10183

Affected Software: TecCom TecConnect

Affected Versions: 4.1

Vulnerability: This is a blind XML External Entity (XXE) injection vulnerability located in the OpenMessaging webservice. It allows an unauthenticated attacker to manipulate XML input to force the application to exfiltrate sensitive files to an external server.

Business Impact

The ability for an unauthenticated actor to read arbitrary files from the server represents a severe security breach. Given the CVSS score of 9.1, this vulnerability could lead to the exposure of configuration files, credentials, or sensitive business data, resulting in significant data loss and potential full system compromise.

Remediation Plan

Immediate Action: Identify all instances of TecConnect 4.1 and apply the latest vendor-provided security update immediately.

Proactive Monitoring: Monitor network traffic for unusual outbound requests from the webservice, specifically targeting connections to unknown or unauthorized external IP addresses.

Compensating Controls: Deploy a Web Application Firewall (WAF) with strict XML parsing rules to block malicious XML payloads containing external entity definitions.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Sep 9, 2025, 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 is highly critical due to the lack of required authentication and the potential for direct data exfiltration. Organizations should prioritize patching the TecConnect webservice and restricting network access to the affected component to prevent unauthorized exploitation.

Executive Summary:
A high-severity vulnerability has been identified in "The Hack Repair Guy's Plugin Archiver" plugin for WordPress, affecting all versions up to and including 2. This flaw allows an attacker to delete arbitrary files on the server, which could lead to website defacement, denial of service by removing critical configuration files, or complete site compromise. Immediate action is required to update or remove the vulnerable plugin to mitigate the risk of exploitation.

Vulnerability Details

CVE-ID: CVE-2025-10176

Affected Software: The Hack Repair Guy's Plugin Archiver plugin for WordPress

Affected Versions: All versions up to, and including, 2.0

Vulnerability: The vulnerability exists within the prepare_items function of the plugin, which fails to properly sanitize user-supplied input for file paths. An authenticated attacker with sufficient privileges to access the plugin's functionality can craft a malicious request containing directory traversal sequences (e.g., ../). This allows the attacker to bypass security checks and specify a path to any file on the server that the web server process has write permissions for, causing the application to delete it.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 7.2. Successful exploitation could have a severe impact on business operations. An attacker could delete critical files such as wp-config.php, which would render the entire website inaccessible, causing a denial of service. The deletion of other theme, plugin, or core WordPress files could break site functionality, corrupt data, or create an opening for further attacks. This poses a significant risk to website availability and integrity, potentially leading to reputational damage, customer distrust, and costly recovery efforts.

Remediation Plan

Immediate Action:

• Immediately update "The Hack Repair Guy's Plugin Archiver" to the latest patched version provided by the vendor.
• If the plugin is not essential for business operations, the recommended course of action is to deactivate and completely remove it to eliminate this attack vector.
• Verify that backups of the website and server configurations are current and can be restored if needed.

Proactive Monitoring:

• Implement File Integrity Monitoring (FIM) on the web server to generate alerts for any unauthorized or unexpected file deletions, particularly for critical files like wp-config.php, .htaccess, and core application directories.
• Review web server access logs for suspicious requests targeting the plugin's administrative functions, looking for patterns indicative of directory traversal attacks (e.g., ../, ..%2f).

Compensating Controls:

• If immediate patching is not feasible, implement a Web Application Firewall (WAF) with rules designed to block directory traversal payloads in requests to the vulnerable plugin endpoint.
• Enforce the principle of least privilege by ensuring the web server user account has the most restrictive file permissions possible. This can limit the impact of the vulnerability by preventing the deletion of critical system files outside of the web root directory.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of September 12, 2025, there are no known public proof-of-concept exploits or active attacks targeting this vulnerability in the wild. However, the public disclosure of the vulnerability details increases the likelihood that threat actors will develop exploits. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog.

Analyst Recommendation

Given the High severity rating (CVSS 7.2) and the potential for complete service disruption, it is strongly recommended that organizations take immediate action. The primary remediation is to update the affected plugin to a patched version without delay. If the plugin is non-essential, it should be removed entirely. Although this vulnerability is not yet on the CISA KEV list, its simplicity and high impact make it an attractive target for attackers, and organizations should prioritize mitigation to prevent potential exploitation.

Executive Summary:
A high-severity vulnerability has been identified in the "Admin and Customer Messages After Order for WooCommerce: OrderConvo" WordPress plugin. This flaw allows an unauthenticated attacker to bypass security controls and download sensitive files from the web server, potentially exposing confidential information such as database credentials, user data, and system configuration files.

Vulnerability Details

CVE-ID: CVE-2025-10162

Affected Software: Admin and Customer Messages After Order for WooCommerce: OrderConvo WordPress plugin

Affected Versions: Versions prior to 14

Vulnerability: The vulnerability is a path traversal (also known as Directory Traversal) located in a file download function of the plugin. The application fails to properly validate or sanitize user-supplied input for a file path. An unauthenticated attacker can exploit this by crafting a malicious request with "dot-dot-slash" (../) sequences to navigate outside of the intended directory and access arbitrary files on the server's file system, limited only by the web server's user permissions.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 7.5. Successful exploitation could lead to a significant data breach by allowing an attacker to read sensitive files such as wp-config.php (containing database credentials), /etc/passwd (listing system users), or other application source code and configuration files. This exposure could facilitate further attacks, leading to a full system compromise, unauthorized access to customer data, reputational damage, and potential non-compliance with data protection regulations.

Remediation Plan

Immediate Action: Immediately update the "Admin and Customer Messages After Order for WooCommerce: OrderConvo" plugin to version 14 or the latest available version, which contains the patch for this vulnerability. If the plugin is not essential for business operations, consider deactivating and removing it to reduce the overall attack surface.

Proactive Monitoring: Monitor web server access logs for requests containing path traversal sequences such as ../, ..%2f, or ..%5c targeting the affected plugin's endpoints. Implement file integrity monitoring to detect unauthorized access to critical system and configuration files.

Compensating Controls: If immediate patching is not feasible, implement a Web Application Firewall (WAF) with rules designed to detect and block path traversal attack patterns. Additionally, ensure the web server is hardened by enforcing strict file permissions, preventing the web server process from reading files outside of its root directory.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of October 7, 2025, there are no known public proof-of-concept exploits or active attacks targeting this specific vulnerability. The vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. However, path traversal is a well-understood vulnerability class, and exploits can be developed easily.

Analyst Recommendation

Given the high severity (CVSS 7.5) and the fact that this vulnerability can be exploited by an unauthenticated attacker with low complexity, organizations are strongly advised to prioritize remediation. The potential for sensitive data exposure presents a significant risk. All instances of the affected plugin should be updated to the latest version immediately. If the plugin is no longer required, it should be removed as a best practice for attack surface reduction.

---METADATA---
VENDOR: Sophos
PRODUCT: AP6 Series Wireless Access Points
AFFECTED_VERSIONS: Older than 1.7.2563 (MR7)
CONFIDENCE: high
MISSING: exploit_status
---END_METADATA---

Description Summary:
An authentication bypass vulnerability in Sophos AP6 Series Wireless Access Points before firmware 1.7.2563 (MR7) allows remote attackers to gain administrative privileges.

Executive Summary:
A critical authentication bypass in Sophos AP6 Series Wireless Access Points allows remote, unauthenticated attackers to gain full administrative control.

Vulnerability Details

CVE-ID: CVE-2025-10159

Affected Software: Sophos AP6 Series Wireless Access Points

Affected Versions: Older than 1.7.2563 (MR7)

Vulnerability: This is an authentication bypass vulnerability that permits remote, unauthenticated attackers to gain administrative privileges on the device. This effectively grants an attacker full control over the wireless access point configuration and management.

Business Impact

With a CVSS score of 9.8, this vulnerability represents an imminent threat to network integrity. An attacker gaining administrative access could intercept traffic, reconfigure network settings, or pivot into the internal network, leading to widespread unauthorized access and severe operational disruption.

Remediation Plan

Immediate Action: Update all Sophos AP6 Series Wireless Access Points to firmware version 1.7.2563 (MR7) or later immediately.

Proactive Monitoring: Review management logs for unauthorized login attempts or configuration changes originating from unknown source IP addresses.

Compensating Controls: Restrict administrative access to the access points to a dedicated, isolated management VLAN that is not accessible from the public internet.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Sep 9, 2025, 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 requires immediate attention, as it provides a direct path to administrative control of network infrastructure. Administrators should treat this as a high-priority update to prevent potential remote compromise of the wireless environment.

Executive Summary:
A critical vulnerability has been identified in the Podlove Podcast Publisher plugin for WordPress, rated with a CVSS score of 9.8. This flaw allows an unauthenticated attacker to upload arbitrary files, including malicious scripts, to the web server. Successful exploitation could lead to complete system compromise, enabling the attacker to steal data, disrupt services, or use the server for further malicious activities.

Vulnerability Details

CVE-ID: CVE-2025-10147

Affected Software: Podlove Podcast Publisher plugin for WordPress

Affected Versions: All versions up to and including the version immediately preceding the patched release. See vendor advisory for specific affected versions.

Vulnerability: The vulnerability exists within the move_as_original_file function of the plugin. This function fails to properly validate the file type of user-supplied uploads. An attacker can exploit this flaw by crafting a request to upload a malicious file, such as a PHP web shell, disguised as a legitimate file type. Because the server-side validation is missing, the malicious file is saved to a web-accessible directory, allowing the attacker to execute it by simply navigating to the file's URL, resulting in remote code execution on the server.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.8. A successful exploit could result in a full compromise of the web server hosting the WordPress site. The potential business impact is severe, including the theft of sensitive data (customer information, credentials, proprietary data), website defacement, service disruption, and reputational damage. The compromised server could also be used to host malware, launch attacks against other systems, or serve as a pivot point into the broader corporate network, posing a significant risk to the entire organization.

Remediation Plan

Immediate Action: Immediately update the Podlove Podcast Publisher plugin for WordPress to the latest patched version. After patching, it is crucial to monitor for any signs of prior exploitation by reviewing web server access logs and file systems for suspicious files or activity.

Proactive Monitoring:

• Monitor web server and application logs for unusual POST requests, particularly those targeting the vulnerable function or involving file uploads with suspicious extensions (e.g., .php, .phtml, .phar).
• Implement file integrity monitoring on the web server to detect the creation of new, unexpected files in web-accessible directories.
• Monitor for unusual outbound network traffic from the web server, which could indicate a successful compromise and communication with a command-and-control server.

Compensating Controls:

• If immediate patching is not possible, implement a Web Application Firewall (WAF) with rules to inspect and block malicious file uploads based on file signatures and extensions.
• Configure the web server to prevent script execution in the directory where files are uploaded (e.g., the /wp-content/uploads/ directory).
• Restrict access to the WordPress administrative interface to trusted IP addresses only.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of Sep 23, 2025, there are no known public exploits or active exploitation campaigns targeting this vulnerability. However, due to the critical severity (CVSS 9.8) and the common nature of arbitrary file upload vulnerabilities, it is highly likely that a proof-of-concept exploit will be developed and published by security researchers or threat actors in the near future. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog.

Analyst Recommendation

Given the critical severity of this vulnerability and its potential for complete system compromise, immediate action is required. Organizations must prioritize applying the vendor-supplied patch to all affected WordPress instances without delay. Due to the high likelihood of future exploitation, this vulnerability should be treated with the highest urgency, similar to a vulnerability listed on the CISA KEV catalog. After patching, a thorough review for indicators of compromise is strongly recommended to ensure the system was not breached before the patch was applied.

Executive Summary:
A high-severity Server-Side Request Forgery (SSRF) vulnerability has been identified in the Auto Featured Image plugin for WordPress. This flaw allows an unauthenticated attacker to trick the affected website's server into making unauthorized requests to internal network resources or external systems. Successful exploitation could lead to sensitive information disclosure, internal network scanning, and bypassing of firewall protections.

Vulnerability Details

CVE-ID: CVE-2025-10145

Affected Software: WordPress Auto Featured Image (Auto Post Thumbnail) plugin

Affected Versions: All versions up to and including 4.0

Vulnerability: The vulnerability is a Server-Side Request Forgery (SSRF) within the Auto Featured Image plugin. The plugin fails to properly validate user-supplied URLs when fetching images to generate thumbnails. An attacker can submit a specially crafted URL that points to an internal IP address (e.g., 127.0.0.1, 192.168.x.x) or a cloud metadata service endpoint. The server will then process this URL and initiate a connection, allowing the attacker to map internal networks, interact with internal services that are not publicly exposed, or exfiltrate sensitive cloud credentials.

Business Impact

This is a High severity vulnerability with a CVSS score of 7.7. Exploitation could have a significant business impact by exposing the organization's internal network infrastructure to external attackers. Potential consequences include the theft of sensitive data from internal databases or file shares, unauthorized access to internal administrative interfaces, and the exfiltration of cloud service credentials (e.g., AWS IAM keys). This breach of the network perimeter can serve as a foothold for attackers to move laterally and launch more damaging attacks against critical internal systems, posing a direct risk to data confidentiality and integrity.

Remediation Plan

Immediate Action: Update the "Auto Featured Image (Auto Post Thumbnail)" plugin to the latest available version that addresses this vulnerability. If the plugin is not critical to business operations, a secondary recommendation is to deactivate and remove it entirely to eliminate this attack vector.

Proactive Monitoring: Monitor web server and firewall logs for any unusual outbound requests originating from the WordPress server. Specifically, look for connections to internal IP ranges (e.g., 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or cloud metadata services (169.254.169.254). An increase in connection errors or unexpected traffic patterns from the web server should be investigated immediately.

Compensating Controls: If immediate patching is not possible, implement the following controls:

• Web Application Firewall (WAF): Deploy a WAF with rules designed to detect and block SSRF attack patterns, such as URLs containing internal or loopback IP addresses in the relevant parameters.
• Egress Filtering: Configure firewall rules to strictly control outbound traffic from the web server. Only allow connections to known, trusted external domains and block all other outbound requests, especially those destined for the internal network.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of October 28, 2025, there is no known public proof-of-concept exploit code or evidence of this vulnerability being actively exploited in the wild. However, SSRF is a well-understood vulnerability class, and threat actors can quickly develop exploits for such flaws in popular plugins. Organizations should assume that exploitation is likely in the near future.

Analyst Recommendation
Given the High severity (CVSS 7.7) of this vulnerability and its potential to expose internal networks, it is strongly recommended that organizations prioritize patching all systems running the affected WordPress plugin immediately. While this CVE is not currently on the CISA KEV catalog, the risk of information disclosure and internal reconnaissance is significant. If patching cannot be performed immediately, the compensating controls outlined above, particularly egress filtering at the network level, should be implemented as a matter of urgency to mitigate the risk.

Executive Summary:
A high-severity vulnerability has been identified in the Catch Dark Mode plugin for WordPress. This flaw could allow an unauthenticated attacker to access sensitive files on the web server, potentially exposing confidential information such as database credentials, system configuration files, and other private data, leading to further system compromise.

Vulnerability Details

CVE-ID: CVE-2025-10143

Affected Software: WordPress Catch Dark Mode Plugin

Affected Versions: All versions up to and including 2.0

Vulnerability: The vulnerability is a Local File Inclusion (LFI) flaw within the Catch Dark Mode plugin. An attacker can exploit this by sending a specially crafted request to the web server that manipulates a parameter to include and display the contents of arbitrary files on the server's filesystem. For example, an attacker could potentially read sensitive files such as wp-config.php (containing database credentials), /etc/passwd, or other application and system files, without requiring any prior authentication.

Business Impact

This vulnerability is rated as High severity with a CVSS score of 7.5. Successful exploitation could lead to significant data breaches by exposing sensitive information, including database connection strings, API keys, and internal system configurations. This exposure could serve as a foothold for more advanced attacks, potentially leading to a full system compromise, reputational damage, and regulatory fines depending on the nature of the data exposed.

Remediation Plan

Immediate Action: Immediately update the Catch Dark Mode plugin to the latest version provided by the vendor, which addresses this vulnerability. If the plugin is not essential for business operations, consider deactivating and removing it entirely to reduce the attack surface.

Proactive Monitoring: Monitor web server access logs for suspicious requests containing directory traversal patterns (e.g., ../, ..%2F, %2e%2e/) in URL parameters associated with the plugin. Implement file integrity monitoring on critical WordPress core files and the wp-config.php file to detect any unauthorized access or changes.

Compensating Controls: If immediate patching is not feasible, implement a Web Application Firewall (WAF) with rulesets designed to detect and block Local File Inclusion and directory traversal attacks. Additionally, ensure web server file permissions are properly hardened to restrict the web server user's access to only the necessary directories, preventing it from reading sensitive system-level files.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of September 17, 2025, there are no known public proof-of-concept exploits or active exploitation campaigns targeting this vulnerability. However, Local File Inclusion is a well-understood and common vulnerability class, and attackers can develop exploits with minimal effort. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog.

Analyst Recommendation
Given the high severity (CVSS 7.5) and the potential for severe data exposure, immediate action is required. We strongly recommend that organizations using the affected Catch Dark Mode plugin prioritize applying the available patch without delay. Although there is no evidence of active exploitation, the ease with which this type of vulnerability can be exploited makes it a critical risk that should be remediated immediately.

Executive Summary:
A critical vulnerability has been identified in The Goza's Nonprofit Charity WordPress Theme, which could allow an attacker to delete arbitrary files on the server. This flaw, tracked as CVE-2025-10134 with a CVSS score of 9.1, can be exploited to cause a denial of service, destroy critical data, or potentially lead to a complete website takeover. Organizations using the affected theme are urged to apply the vendor's patch immediately to mitigate the significant risk of compromise.

Vulnerability Details

CVE-ID: CVE-2025-10134

Affected Software: The Goza Multiple Products

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The vulnerability exists within the alone_import_pack_restore_data() function of The Goza WordPress theme. Due to insufficient validation of user-supplied file paths, an authenticated attacker can use path traversal techniques (e.g., ../../) to target and delete files outside of the intended directory. By crafting a malicious request to this function, an attacker could delete critical WordPress core files, such as wp-config.php, effectively disabling the website or forcing it into a re-installation state that the attacker could then control.

Business Impact

This vulnerability is rated as critical severity with a CVSS score of 9.1, posing a significant threat to business operations. Successful exploitation could lead to immediate and severe consequences, including website defacement, extended downtime (denial of service), and irreversible loss of website data if backups are not available. The deletion of configuration files could allow an attacker to initiate the WordPress setup process and gain full administrative control over the website, leading to a complete compromise of sensitive information, reputational damage, and potential loss of donor trust.

Remediation Plan

Immediate Action: Immediately update The Goza Multiple Products to the latest patched version provided by the vendor. Before deploying to production, test the update in a staging environment to ensure compatibility. Concurrently, begin reviewing web server and application access logs for any suspicious activity related to the vulnerable function.

Proactive Monitoring: Implement enhanced monitoring of the web server. Specifically, look for unusual POST requests to WordPress admin functions that reference alone_import_pack_restore_data(). Utilize a File Integrity Monitoring (FIM) system to alert on any unauthorized changes or deletions to critical files, especially wp-config.php, .htaccess, and core theme/plugin files.

Compensating Controls: If immediate patching is not feasible, implement the following controls:

• Deploy a Web Application Firewall (WAF) with rules designed to block path traversal attack patterns.
• Restrict access to the WordPress administrative dashboard (/wp-admin/) to only trusted IP addresses.
• Enforce the principle of least privilege for all WordPress user accounts to limit the number of users who could potentially exploit the vulnerability.
• Ensure a robust and tested backup and recovery plan is in place to restore the website in the event of a compromise.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of the publication date of Sep 9, 2025, there are no known public proof-of-concept exploits or active exploitation campaigns targeting this vulnerability. However, due to the critical severity and the relative simplicity of exploiting path traversal flaws, it is highly probable that threat actors will develop and deploy exploits in the near future.

Analyst Recommendation

Given the critical CVSS score of 9.1, this vulnerability requires immediate attention. The potential for complete website compromise presents an unacceptable risk. We strongly recommend that organizations prioritize the deployment of the vendor-supplied patch across all affected websites without delay. Although this CVE is not currently listed on the CISA KEV catalog, its high impact makes it a likely candidate for future inclusion. Proactive patching and monitoring are the most effective measures to prevent exploitation.