Frigate Professional 3
Description
Frigate Professional 3
Remediation
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Search and filter 8341 vulnerabilities with AI analyst insights
Frigate Professional 3
Frigate Professional 3
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
OpenCTI 3
OpenCTI 3
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Code Blocks 17
Code Blocks 17
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Frigate 2
Frigate 2
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Code Blocks 20
Code Blocks 20
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Avast SecureLine 5
Avast SecureLine 5
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
RM Downloader 2
RM Downloader 2
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
e-Learning PHP Script 0
e-Learning PHP Script 0
Executive Summary:
A high-severity vulnerability has been identified in the e-Learning PHP Script, which could allow an unauthenticated remote attacker to execute arbitrary code on the server. Successful exploitation could lead to a complete compromise of the affected system, resulting in the theft of sensitive data, service disruption, and loss of system integrity. Organizations using the affected software are exposed to significant risk and should take immediate action.
Vulnerability Details
CVE-ID: CVE-2020-37035
Affected Software: e-Learning PHP Script
Affected Versions: Version 0. See vendor advisory for specific affected versions.
Vulnerability: The vulnerability is a critical file upload flaw that allows an unauthenticated attacker to bypass file type restrictions. An attacker can upload a malicious PHP script disguised as a common file type (e.g., an image) to a publicly accessible directory on the web server. By then navigating to the uploaded file's location, the attacker can trigger the execution of the malicious script with the privileges of the web server process, leading to remote code execution (RCE).
Business Impact
This vulnerability is rated as High severity with a CVSS score of 8.2. A successful exploit could have a severe impact on the business, leading to a full compromise of the e-learning platform. Potential consequences include the unauthorized access to and exfiltration of sensitive student and instructor data, manipulation of academic records, defacement of the website, and complete service unavailability. The compromised server could also be used as a pivot point to launch further attacks against the internal network, posing a significant risk to the entire organization's security posture and reputation.
Remediation Plan
Immediate Action: Apply vendor security updates immediately. The vendor has released a patch that corrects the file validation logic. After patching, it is critical to monitor for any ongoing exploitation attempts and review historical web server access logs for indicators of compromise that may have occurred prior to remediation.
Proactive Monitoring: Security teams should monitor web server logs for suspicious POST requests to file upload endpoints, especially those containing files with double extensions (e.g., shell.php.jpg) or unexpected file types. Monitor the file system for the creation of unauthorized PHP or script files in upload directories. Network monitoring should be configured to detect and alert on any unusual outbound connections originating from the web server.
Compensating Controls: If patching cannot be performed immediately, implement a Web Application Firewall (WAF) with rules designed to inspect file uploads and block malicious script types. Additionally, configure the web server to disable script execution permissions in all directories where user-uploaded files are stored. File integrity monitoring (FIM) should also be deployed to detect unauthorized changes to the application's source code.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of January 31, 2026, this vulnerability has been publicly disclosed, and proof-of-concept (PoC) exploit code is available. Threat intelligence indicates that this vulnerability is being actively discussed in underground forums, and due to the ease of exploitation, widespread automated scanning and attacks are anticipated.
Analyst Recommendation
Given the high CVSS score of 8.2 and the availability of a public exploit, this vulnerability poses an immediate and critical threat. We strongly recommend that organizations apply the vendor-supplied patch to all affected systems without delay. Although this CVE is not currently listed on the CISA KEV catalog, its high severity and the potential for widespread exploitation make it a high-priority issue. If patching is delayed, the compensating controls listed above must be implemented immediately while actively hunting for any signs of a prior compromise.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
HelloWeb 2
HelloWeb 2
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Infor Storefront B2B 1
Infor Storefront B2B 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Wing FTP Server 6
Wing FTP Server 6
Executive Summary:
A high-severity vulnerability exists in Wing FTP Server that allows an authenticated attacker to take control of the administrative interface. By uploading a file with a malicious name, an attacker can execute code in an administrator's web browser, potentially leading to a full server compromise, data theft, and unauthorized system changes. Due to the public availability of exploit code, this vulnerability poses a significant and immediate risk.
Vulnerability Details
CVE-ID: CVE-2020-37032
Affected Software: Wing FTP Server
Affected Versions: Version 6.2.5 and potentially prior versions. See vendor advisory for specific affected versions.
Vulnerability: This vulnerability is a stored Cross-Site Scripting (XSS) flaw within the Wing FTP Server's web administration interface. An attacker with valid, even low-privileged, user credentials can upload a file with a specially crafted filename containing malicious JavaScript code. The server fails to properly sanitize this filename when displaying it in the administrative file browser. When a privileged user, such as an administrator, views the list of uploaded files, the malicious script executes within the context of their browser session, granting the attacker the ability to perform any action the administrator can, such as creating new admin accounts, modifying server settings, or accessing/deleting sensitive files.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 8.8. Successful exploitation could lead to a complete compromise of the FTP server and the data it hosts. The primary business impacts include a high risk of a data breach, loss of data integrity, and potential disruption of business operations that rely on the FTP server. An attacker gaining administrative control could exfiltrate sensitive corporate or customer data, install malware, or use the compromised server as a pivot point to launch further attacks against the internal network, leading to significant financial and reputational damage.
Remediation Plan
Immediate Action: Apply vendor security updates immediately to upgrade Wing FTP Server to a patched version that resolves this vulnerability. After patching, it is crucial to monitor for any signs of exploitation that may have occurred prior to remediation and to review administrative access logs for any unauthorized or suspicious activity.
Proactive Monitoring: Security teams should monitor server logs for file upload events with suspicious filenames, specifically looking for HTML tags, script elements (e.g., <script>, onerror=), or other XSS payloads. Network traffic to and from the server's web administration interface should be monitored for anomalous patterns. Implement alerts for unusual administrative actions, such as account creation or privilege escalation, especially from unexpected IP addresses.
Compensating Controls: If immediate patching is not feasible, implement a Web Application Firewall (WAF) with rules designed to detect and block XSS attacks in file upload parameters. Restrict access to the web administration portal to a limited set of trusted IP addresses. Enforce multi-factor authentication (MFA) for all administrative accounts to mitigate the risk of session hijacking.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of February 1, 2026, multiple proof-of-concept (PoC) exploits for CVE-2020-37032 are publicly available, making it easy for attackers to craft and launch attacks. Although this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, its high severity and the availability of public exploits significantly increase the likelihood of opportunistic attacks.
Analyst Recommendation
Given the high CVSS score of 8.8 and the public availability of exploit code, we strongly recommend that immediate action be taken to mitigate this vulnerability. Organizations must prioritize the deployment of the vendor-supplied security patches to all affected Wing FTP Server instances. Due to the risk of complete administrative takeover, this vulnerability should be treated as a critical threat to the security of the server and the data it contains.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Simple Startup Manager 1
Simple Startup Manager 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Outline Service 1
Outline Service 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
FTPDummy 4
FTPDummy 4
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Socusoft Photo to Video Converter Professional 8
Socusoft Photo to Video Converter Professional 8
Executive Summary:
A high-severity vulnerability exists in Socusoft Photo to Video Converter Professional software, identified as CVE-2020-37028. This flaw allows an attacker to execute arbitrary code and take control of a user's computer by tricking them into opening a malicious project file. Successful exploitation could lead to data theft, malware installation, or further compromise of the corporate network.
Vulnerability Details
CVE-ID: CVE-2020-37028
Affected Software: Socusoft Photo to Video Converter Professional
Affected Versions: Version 8.0
Vulnerability: This vulnerability is a stack-based buffer overflow. An attacker can exploit this by crafting a malicious project file (e.g., a .spv file) with an overly long string. When a user opens this malicious file with the affected software, the application attempts to copy the excessive data into a fixed-size buffer on the stack, causing an overflow. This overwrites adjacent memory, including the function's return address, allowing the attacker to redirect the program's execution flow to their own malicious code, resulting in arbitrary code execution on the victim's system.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 8.4. A successful exploit could have a significant business impact, leading to a complete compromise of the affected workstation. An attacker could install malware such as ransomware or spyware, exfiltrate sensitive corporate or personal data, or use the compromised machine as a pivot point to launch further attacks against other systems within the organization's network. The primary risk is a breach of confidentiality and integrity, potentially leading to financial loss, reputational damage, and operational disruption.
Remediation Plan
Immediate Action: The primary remediation is to apply the security updates provided by the vendor to all affected systems immediately. After patching, it is crucial to monitor systems for any signs of post-exploitation activity and review application and system access logs for anomalous behavior preceding the patch deployment.
Proactive Monitoring: Security teams should monitor for suspicious activity related to the Socusoft application. This includes looking for the application spawning unusual child processes (e.g., cmd.exe, powershell.exe), unexpected outbound network connections from the application, and application crash logs that may indicate failed exploitation attempts.
Compensating Controls: If immediate patching is not feasible, organizations should implement compensating controls. This includes user awareness training to warn against opening unsolicited or untrusted .spv project files. Additionally, deploying an Endpoint Detection and Response (EDR) solution can help detect and block the malicious behaviors associated with exploiting this type of vulnerability.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of February 1, 2026, proof-of-concept (PoC) exploit code is publicly available for this vulnerability. The availability of a public exploit lowers the technical barrier for attackers, increasing the likelihood of exploitation. While this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, its high severity and the public exploit code make it an attractive target for threat actors.
Analyst Recommendation
Given the high CVSS score of 8.4 and the public availability of a functional exploit, this vulnerability poses a significant risk to the organization. We strongly recommend that the vendor-supplied security updates be applied as a top priority. Systems running this software should be considered at high risk of compromise until they are patched. If patching is delayed, the compensating controls listed above must be implemented immediately to reduce the attack surface.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Sickbeard alpha contains a remote command injection vulnerability that allows unauthenticated attackers to execute arbitrary commands through the extr...
Sickbeard alpha contains a remote command injection vulnerability that allows unauthenticated attackers to execute arbitrary commands through the extra scripts configuration. Attackers can set malicious commands in the extra scripts field and trigger processing to execute remote code on the vulnerable Sickbeard installation.
Executive Summary:
A critical remote command injection vulnerability, identified as CVE-2020-37027, exists within Sickbeard alpha. This flaw allows an unauthenticated attacker to remotely execute arbitrary commands on the server by injecting malicious code into the "extra scripts" configuration, leading to a complete system compromise.
Vulnerability Details
CVE-ID: CVE-2020-37027
Affected Software: Sickbeard alpha
Affected Versions: See vendor advisory for specific affected versions
Vulnerability: This vulnerability is a command injection flaw within the "extra scripts" feature of Sickbeard alpha. The application fails to properly sanitize user-supplied input to this configuration field. An unauthenticated remote attacker can submit a request to the application to set a malicious script or command (e.g., ;/bin/bash -c '...'). When the application triggers the execution of these extra scripts (for example, after a download completes), the injected command is executed on the underlying operating system with the privileges of the Sickbeard service account.
Business Impact
This vulnerability is rated as critical severity with a CVSS score of 9.8. Successful exploitation grants an attacker complete control over the affected server, resulting in a full system compromise. Potential consequences include theft or destruction of sensitive data, deployment of ransomware, installation of persistent backdoors, and using the compromised server as a pivot point to attack other systems within the network. The lack of an authentication requirement significantly increases the risk, as any attacker with network access to the Sickbeard instance can exploit this flaw.
Remediation Plan
Immediate Action: Update Sickbeard alpha to the latest version that addresses this vulnerability. After patching, it is crucial to monitor for any signs of post-exploitation activity. Review application and system access logs for any unusual commands or connections originating from the Sickbeard server that may indicate a previous compromise.
Proactive Monitoring: Monitor application logs for unusual entries or modifications to the "extra scripts" configuration. On the host system, monitor for unexpected child processes being spawned by the Sickbeard process (e.g., sh, bash, curl, wget). Network monitoring should be in place to detect anomalous outbound traffic from the Sickbeard server, which could indicate data exfiltration or connection to a command-and-control server.
Compensating Controls: If immediate patching is not feasible, implement the following controls:
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of Jan 30, 2026, while this vulnerability is not listed on the CISA KEV catalog, its public nature and the simplicity of exploitation make it a high-risk target. The critical CVSS score of 9.8 underscores the severity. Threat actors can easily develop and use exploits to gain initial access to networks running vulnerable instances of Sickbeard alpha.
Analyst Recommendation
Given the critical severity (CVSS 9.8) and the unauthenticated remote code execution nature of this vulnerability, immediate action is required. Organizations must prioritize applying the vendor-supplied patches to all affected Sickbeard alpha installations. Due to the high likelihood of automated scanning and exploitation, any internet-exposed instances should be considered at extreme risk and either patched or taken offline immediately until they can be secured.
Update Sickbeard alpha contains a remote command injection vulnerability that allows unauthenticated attackers to execute arbitrary commands through the extra scripts Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
Port Forwarding Wizard 4
Port Forwarding Wizard 4
Executive Summary:
A high-severity vulnerability has been identified in multiple products from the vendor Forwarding, specifically impacting Port Forwarding Wizard 4. This flaw, rated with a CVSS score of 8.4, could allow a remote attacker to compromise network configurations, potentially leading to unauthorized access to internal systems and sensitive data. Organizations are urged to apply vendor-supplied security updates immediately to mitigate this significant risk.
Vulnerability Details
CVE-ID: CVE-2020-37025
Affected Software: Forwarding Multiple Products
Affected Versions: Port Forwarding Wizard version 4 is explicitly mentioned. See vendor advisory for a complete list of affected products and versions.
Vulnerability: This vulnerability allows a remote attacker to manipulate network configurations managed by the affected software. The high CVSS score suggests that the vulnerability is likely exploitable over the network with low attack complexity and requires no user interaction. Successful exploitation could enable an attacker to create, delete, or modify port forwarding rules, thereby bypassing firewall protections and exposing sensitive internal services to the public internet or redirecting traffic for malicious purposes.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 8.4. Exploitation could lead to a significant security breach, resulting in unauthorized access to critical internal infrastructure, data exfiltration of sensitive corporate or customer information, and potential lateral movement across the network. The ability for an attacker to alter network traffic rules can disrupt business operations, compromise data integrity, and lead to reputational damage and financial loss.
Remediation Plan
Immediate Action: Organizations must apply the vendor security updates immediately to all affected systems. Prioritize patching systems that are exposed to the internet. Concurrently, security teams should actively monitor for any signs of exploitation and review access and system logs for indicators of compromise, such as unauthorized changes to forwarding rules.
Proactive Monitoring: Monitor network traffic for unusual or unauthorized port forwarding rules being created or modified. Review system and application logs on affected devices for suspicious activity, such as unexpected commands, unauthorized logins, or connections from unknown IP addresses. Implement alerts for any changes made to the device's network configuration.
Compensating Controls: If immediate patching is not feasible, restrict network access to the management interface of the affected software to a limited set of trusted IP addresses. Implement an Intrusion Prevention System (IPS) with signatures designed to detect and block known exploitation attempts against this vulnerability. Ensure robust network segmentation is in place to limit the impact of a potential breach.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of February 1, 2026, there are no known public exploits or active exploitation campaigns targeting this vulnerability. This vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. However, the high severity score indicates that it is a prime target for future exploit development by threat actors.
Analyst Recommendation
Given the High severity rating (CVSS 8.4), it is strongly recommended that organizations identify all affected "Forwarding" products within their environment and apply the necessary security updates without delay. Although there is no current evidence of active exploitation, the potential for severe impact on network security and data confidentiality makes proactive patching the most critical and effective mitigation strategy. Do not wait for evidence of exploitation before taking action.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Nidesoft DVD Ripper 5
Nidesoft DVD Ripper 5
Executive Summary:
A high-severity vulnerability has been identified in Nidesoft DVD Ripper software, which could allow an attacker to take full control of an affected system. Successful exploitation, which would likely involve tricking a user into opening a malicious media file, could lead to data theft, ransomware deployment, or further compromise of the organization's network.
Vulnerability Details
CVE-ID: CVE-2020-37024
Affected Software: DVD Multiple Products
Affected Versions: Nidesoft DVD Ripper version 5. See vendor advisory for specific affected versions.
Vulnerability: This vulnerability is likely a buffer overflow that occurs during the processing of specially crafted media files. An attacker can create a malicious DVD image or video file and distribute it to a target. When a user attempts to open or "rip" this malicious file using the vulnerable software, the application fails to properly validate the input, leading to a buffer overflow condition that allows the attacker to execute arbitrary code on the user's machine with the same privileges as the logged-in user.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 8.4, posing a significant risk to the organization. If an attacker successfully exploits this flaw on an employee's workstation, they could gain a foothold within the corporate network. Potential consequences include the exfiltration of sensitive company data, installation of persistent backdoors, deployment of ransomware, or using the compromised machine to launch further attacks against internal systems. The impact is magnified if the software is used by employees with privileged access to critical data or systems.
Remediation Plan
Immediate Action: The primary remediation is to identify all instances of the affected software and apply the vendor-provided security updates immediately. Utilize enterprise patch management systems to deploy the update across all relevant endpoints. Following the update, review system and application logs for any signs of compromise that may have occurred prior to patching.
Proactive Monitoring: Implement enhanced monitoring on endpoints where this software is installed. Security teams should look for anomalous behavior, such as the Nidesoft DVD Ripper process spawning unexpected child processes (e.g., cmd.exe, powershell.exe), making unusual outbound network connections, or triggering endpoint detection and response (EDR) alerts related to memory corruption or shellcode execution.
Compensating Controls: If immediate patching is not feasible, consider implementing compensating controls to reduce the risk. This includes restricting the use of the software to authorized personnel, running the application within a sandboxed or virtualized environment to contain any potential exploit, and enforcing application control policies to prevent the software from executing unauthorized code. User awareness training on the risks of opening files from untrusted sources can also serve as a mitigating factor.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of February 1, 2026, there are no known public proof-of-concept exploits or active attacks targeting this vulnerability. However, due to the high severity score, it is likely that threat actors will attempt to reverse-engineer the vendor patch to develop a functional exploit. The vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities (KEV) catalog.
Analyst Recommendation
Given the high CVSS score of 8.4, this vulnerability presents a critical risk and must be addressed with urgency. All organizations using Nidesoft DVD Ripper or other affected products from the vendor should prioritize the immediate application of security patches. While there is no current evidence of active exploitation, the potential for an attacker to achieve remote code execution is severe. Proactive patching remains the most effective strategy to prevent potential compromise.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Koken CMS 0
Koken CMS 0
Executive Summary:
A critical SQL Injection vulnerability has been identified in Koken CMS, which allows an unauthenticated remote attacker to execute arbitrary commands on the website's database. Successful exploitation could lead to a complete compromise of the application, resulting in sensitive data theft, website defacement, or unauthorized administrative access.
Vulnerability Details
CVE-ID: CVE-2020-37023
Affected Software: Koken Multiple Products
Affected Versions: Versions up to and including 0.22.24
Vulnerability: This vulnerability is a SQL Injection flaw within the admin/api.php component of the Koken CMS. An unauthenticated attacker can send a specially crafted HTTP request to this endpoint, injecting malicious SQL queries through the id parameter. This allows the attacker to bypass security controls and directly interact with the underlying database, enabling them to read, modify, or delete data, including user credentials and website content.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 8.8. A successful exploit could have severe consequences for the business, including a significant data breach of sensitive customer or internal information. Attackers could deface the public-facing website, causing substantial reputational damage and loss of customer trust. Furthermore, by extracting administrator credentials from the database, an attacker could gain full control over the CMS, potentially using it as a pivot point to launch further attacks against the internal network.
Remediation Plan
Immediate Action: Apply vendor security updates immediately to all affected Koken CMS instances. After patching, it is critical to monitor for any ongoing or recent exploitation attempts by thoroughly reviewing web server and application access logs for indicators of compromise.
Proactive Monitoring: Security teams should configure monitoring to alert on suspicious requests targeting the /admin/api.php endpoint. Specifically, look for malformed or complex SQL syntax within the id parameter of GET or POST requests. Monitor for unusual database activity, such as a high volume of queries from the web server or connections from unexpected sources.
Compensating Controls: If immediate patching is not possible, implement a Web Application Firewall (WAF) with a strict ruleset designed to detect and block SQL Injection attack patterns. Additionally, restrict administrative access to the Koken CMS to trusted IP addresses only and ensure the database user account has the minimum necessary privileges to function, preventing it from accessing or modifying critical system tables.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of February 1, 2026, multiple public proof-of-concept (PoC) exploit scripts for this vulnerability are widely available on the internet. The existence of these public exploits lowers the barrier for attackers, increasing the likelihood of opportunistic and automated attacks against unpatched systems.
Analyst Recommendation
Given the high severity score (CVSS 8.8) and the confirmed availability of public exploit code, this vulnerability presents a critical and immediate threat to the organization. All instances of Koken CMS must be identified and patched without delay. Although this vulnerability is not listed on the CISA KEV catalog, the ease of exploitation makes it a prime target for attackers. We strongly recommend prioritizing the remediation of this flaw and subsequently performing a compromise assessment to search for evidence of prior exploitation.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
10-Strike Bandwidth Monitor 3
10-Strike Bandwidth Monitor 3
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
SonarQube 8
SonarQube 8
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
CodeMeter 6
CodeMeter 6
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
BarcodeOCR 19
BarcodeOCR 19
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Ruijie Networks Switch eWeb S29_RGOS 11
Ruijie Networks Switch eWeb S29_RGOS 11
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Audio Playback Recorder 3
Audio Playback Recorder 3
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Tea LaTex 1.0 contains a remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary shell commands through the /ap...
Tea LaTex 1.0 contains a remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary shell commands through the /api.php endpoint. Attackers can craft a malicious LaTeX payload with shell commands that are executed when processed by the application's tex2png API action.
Executive Summary:
A critical remote code execution vulnerability has been identified in Tea LaTex Multiple Products. This flaw allows an unauthenticated attacker to execute arbitrary commands on the server by sending a specially crafted request, potentially leading to a complete system compromise, data theft, and service disruption.
Vulnerability Details
CVE-ID: CVE-2020-37012
Affected Software: Tea LaTex Multiple Products
Affected Versions: Version 1.0 is confirmed to be vulnerable. See vendor advisory for a complete list of specific affected products and versions.
Vulnerability: The vulnerability exists within the /api.php endpoint, specifically in the tex2png API action. The application fails to properly sanitize user-supplied input before processing it with the LaTeX engine. An unauthenticated remote attacker can submit a malicious LaTeX payload containing embedded shell commands (e.g., using \write18{command}). When the server processes this payload to generate an image, it also executes the embedded shell commands with the privileges of the web server process, leading to remote code execution.
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 affected server. Potential consequences include theft or modification of sensitive data, installation of malware or ransomware, disruption of critical services hosted on the server, and using the compromised system as a pivot point to attack other internal network resources. The unauthenticated nature of this vulnerability significantly increases the risk, as any attacker with network access to the application can attempt exploitation, posing a severe threat to data confidentiality, integrity, and availability.
Remediation Plan
Immediate Action:
/api.php endpoint.Proactive Monitoring:
/api.php, specifically looking for payloads containing LaTeX commands associated with shell execution like \write18, \input, or \include.sh, bash, powershell, curl, wget).Compensating Controls:
/api.php endpoint./api.php endpoint, allowing connections only from trusted IP addresses. If the endpoint is not required for business operations, consider disabling it entirely.Exploitation Status
Public Exploit Available: true
Analyst Notes: As of Jan 29, 2026, proof-of-concept (PoC) exploits for this vulnerability are publicly available. Due to the simplicity of exploitation and the critical impact, it is highly likely that this vulnerability is being actively scanned for and exploited by threat actors. Although the CISA KEV status is "No", its characteristics make it an attractive target for both opportunistic and targeted attacks.
Analyst Recommendation
Given the critical CVSS score of 9.8 and the availability of a public exploit, immediate action is required. All organizations using the affected Tea LaTex products must prioritize applying the vendor-supplied patches without delay. Due to the risk of a full system compromise, it is also strongly recommended to hunt for evidence of past exploitation by reviewing logs for the indicators mentioned in the Proactive Monitoring section. Implementing compensating controls like WAF rules and network segmentation should be considered a critical defense-in-depth measure, even after patching is complete.
Update Tea LaTex Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
Gnome Fonts Viewer 3
Gnome Fonts Viewer 3
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
BearShare Lite 5.2.5 contains a buffer overflow vulnerability in the Advanced Search keywords input that allows attackers to execute arbitrary code. A...
BearShare Lite 5.2.5 contains a buffer overflow vulnerability in the Advanced Search keywords input that allows attackers to execute arbitrary code. Attackers can craft a specially designed payload to overwrite the EIP register and execute shellcode by pasting malicious content into the search keywords field.
Executive Summary:
A critical buffer overflow vulnerability exists in BearShare Lite version 5.2.5. An attacker can exploit this flaw by pasting a specially crafted, malicious string into the application's search field, which can lead to a complete system compromise and allow the attacker to execute arbitrary code on the affected machine.
Vulnerability Details
CVE-ID: CVE-2020-37010
Affected Software: BearShare Lite Multiple Products
Affected Versions: Version 5.2.5 is confirmed to be vulnerable. See vendor advisory for other specific affected versions.
Vulnerability: This is a classic stack-based buffer overflow vulnerability. When a user pastes an overly long string of characters into the "Advanced Search keywords" input field, the application fails to perform proper bounds checking. This allows an attacker-controlled payload to overwrite the program's stack, including the saved EIP (Extended Instruction Pointer) register, which dictates the next instruction to be executed. By overwriting the EIP with the address of malicious shellcode also included in the payload, an attacker can hijack the program's execution flow and run arbitrary code with the same privileges as the user running the BearShare Lite application.
Business Impact
This vulnerability is rated as critical severity with a CVSS score of 9.8. Successful exploitation would grant an attacker complete control over the affected endpoint. The potential consequences include the installation of malware such as ransomware or spyware, theft of sensitive corporate or personal data, and using the compromised system as a pivot point to launch further attacks against the internal network. This poses a significant risk of data breaches, financial loss, operational disruption, and reputational damage to the organization.
Remediation Plan
Immediate Action: Update BearShare Lite Multiple Products to the latest version that addresses this vulnerability. If a patch is unavailable, consider uninstalling the software. Concurrently, security teams should monitor for exploitation attempts and review application and system access logs for signs of compromise.
Proactive Monitoring: Monitor for unexpected crashes of the BearShare Lite application, which could indicate failed exploitation attempts. Use endpoint security solutions to monitor for suspicious process creation originating from BearShare.exe. Network monitoring should be configured to detect unusual outbound connections from workstations running the application, as this may signify a successful C2 (Command and Control) connection.
Compensating Controls: If patching or removal is not immediately feasible, implement the following controls:
Exploitation Status
Public Exploit Available: True
Analyst Notes: As of January 29, 2026, proof-of-concept (PoC) exploit code for this vulnerability is publicly available, significantly lowering the bar for attackers to craft and execute an attack. BearShare Lite is legacy peer-to-peer software that is likely no longer supported by its original vendor, meaning official patches may not be available. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, but its simplicity and the public availability of an exploit make it a high-risk issue.
Analyst Recommendation
Given the critical CVSS score of 9.8 and the availability of a public exploit, immediate action is required. The primary recommendation is to uninstall this legacy software from all corporate assets, as it poses an unacceptable security risk and is likely unpatched. If the software is business-critical and cannot be removed, it must be updated immediately. If no patch exists, the system should be isolated from the network, and the compensating controls listed above must be implemented as an urgent priority.
Update BearShare Lite Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
MedDream PACS Server 6
MedDream PACS Server 6
Executive Summary:
A high-severity vulnerability exists within multiple PACS products, specifically identified in MedDream PACS Server. This flaw allows an unauthenticated attacker to gain unauthorized access to the underlying database, potentially leading to a significant breach of sensitive Protected Health Information (PHI) and disruption of clinical services. Immediate patching is required to mitigate the risk of data exfiltration and regulatory non-compliance.
Vulnerability Details
CVE-ID: CVE-2020-37009
Affected Software: PACS Multiple Products
Affected Versions: MedDream PACS Server 6. See vendor advisory for a complete list of affected products and versions.
Vulnerability: The vulnerability is an unauthenticated SQL Injection flaw in the login functionality of the MedDream PACS Server. An attacker can exploit this by sending a specially crafted HTTP request to the login page, manipulating the username parameter with malicious SQL commands. Because the application fails to properly sanitize this user-supplied input, the attacker's commands are executed directly by the database, allowing them to bypass authentication and gain unauthorized access to view, modify, or delete sensitive patient data stored within the PACS system.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 8.8. Successful exploitation could have severe consequences for the organization, including a major breach of Protected Health Information (PHI), which violates regulatory compliance standards like HIPAA. This can result in substantial financial penalties, legal action, and significant reputational damage. Furthermore, an attacker could potentially alter or delete patient imaging data, directly impacting patient care and disrupting critical clinical workflows that rely on the PACS system.
Remediation Plan
Immediate Action: Apply vendor-supplied security updates to all affected PACS servers immediately. Prioritize these systems for patching due to the high severity of the vulnerability. After patching, review server and database access logs for any signs of compromise that may have occurred prior to remediation.
Proactive Monitoring: Implement enhanced monitoring on affected systems. Security teams should inspect web server and database logs for suspicious queries, particularly against login pages, that contain SQL syntax such as UNION, SELECT, ' OR '1'='1, or other common injection payloads. Monitor network traffic for unusual data egress from the PACS server, which could indicate data exfiltration.
Compensating Controls: If immediate patching is not feasible, deploy a Web Application Firewall (WAF) with a ruleset configured to detect and block SQL injection attacks. Additionally, restrict network access to the PACS server's management interface, allowing connections only from trusted internal IP addresses to limit the attack surface.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of January 31, 2026, proof-of-concept (PoC) exploit code for this vulnerability is publicly available. The availability of a working exploit significantly increases the likelihood of attack attempts by a wide range of threat actors. While this CVE is not currently on the CISA Known Exploited Vulnerabilities (KEV) catalog, its presence in medical systems and the availability of an exploit make it an attractive target for attackers seeking to steal sensitive healthcare data.
Analyst Recommendation
Given the high CVSS score, the critical nature of the affected systems (PACS), and the public availability of exploit code, this vulnerability poses a significant and immediate risk to the organization. We strongly recommend that the vendor-supplied patches be applied on an emergency basis. If patching is delayed for any reason, compensating controls such as a WAF and network access restrictions must be implemented without delay to reduce the risk of a data breach involving sensitive patient information.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
EasyPMS 1
EasyPMS 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
berliCRM 1
berliCRM 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
TimeClock Software 1
TimeClock Software 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Ultimate Project Manager CRM PRO 2
Ultimate Project Manager CRM PRO 2
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Ajenti 2.1.36 contains an authentication bypass vulnerability that allows remote attackers to execute arbitrary commands after successful login. Attac...
Ajenti 2.1.36 contains an authentication bypass vulnerability that allows remote attackers to execute arbitrary commands after successful login. Attackers can leverage the /api/terminal/create endpoint to send a netcat reverse shell payload targeting a specified IP and port.
Executive Summary:
A critical vulnerability has been identified in multiple Ajenti products, specifically impacting version 2.1.36. This flaw allows a remote attacker who has successfully logged into the Ajenti panel to bypass security controls and execute arbitrary commands on the underlying server, potentially leading to a complete system compromise. Due to the high severity and potential for full remote control, immediate remediation is strongly advised.
Vulnerability Details
CVE-ID: CVE-2020-37002
Affected Software: Ajenti Multiple Products
Affected Versions: Ajenti version 2.1.36 is confirmed to be vulnerable. See vendor advisory for a complete list of affected versions.
Vulnerability: This is a post-authentication command injection vulnerability. An attacker with valid credentials to the Ajenti web panel, regardless of their privilege level, can exploit a flaw in the terminal creation API endpoint (/api/terminal/create). By sending a specially crafted request to this endpoint, the attacker can inject and execute arbitrary system commands, such as launching a netcat reverse shell to gain interactive remote access to the server with the privileges of the Ajenti service account.
Business Impact
This vulnerability is rated as critical severity with a CVSS score of 9.8, reflecting the extreme risk it poses to the organization. Successful exploitation could lead to a complete compromise of the affected server, granting the attacker full administrative control. The potential consequences include theft or destruction of sensitive data, deployment of ransomware, disruption of critical business services hosted on the server, and the ability for the attacker to use the compromised system as a pivot point for further attacks into the internal network.
Remediation Plan
Immediate Action: The primary remediation is to upgrade all vulnerable Ajenti instances to the latest patched version immediately. Consult the official Ajenti security advisory for specific version details and patching instructions. After patching, it is crucial to review server and application logs for any signs of compromise that may have occurred before the patch was applied.
Proactive Monitoring: System administrators should actively monitor web server access logs for suspicious POST requests to the /api/terminal/create endpoint. Network monitoring should be configured to detect and alert on unexpected outbound connections from the server hosting Ajenti, which could indicate a reverse shell. Host-based intrusion detection systems (HIDS) can also be used to monitor for unusual process execution or command-line activity originating from the Ajenti service.
Compensating Controls: If immediate patching is not feasible, implement the following controls to reduce risk:
/api/terminal/create endpoint.Exploitation Status
Public Exploit Available: True
Analyst Notes: As of Jan 29, 2026, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. However, given the critical severity and the public availability of proof-of-concept exploit code, the likelihood of exploitation is high. Threat actors can easily integrate this vulnerability into their toolkits to target exposed and unpatched Ajenti servers.
Analyst Recommendation
Due to the critical severity (CVSS 9.8) and the potential for complete system compromise via remote code execution, this vulnerability requires immediate attention. We strongly recommend that organizations prioritize the patching of all affected Ajenti instances without delay. Although this CVE is not currently on the CISA KEV list, its public nature and severe impact mean it should be treated with the highest urgency, as if it were being actively exploited in the wild. If patching cannot be performed immediately, the compensating controls outlined above must be implemented as an urgent interim measure.
Update Ajenti Multiple Products to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
Frigate Professional 3
Frigate Professional 3
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Free MP3 CD Ripper 2.8 contains a stack buffer overflow vulnerability that allows remote attackers to execute arbitrary code by crafting a malicious W...
Free MP3 CD Ripper 2.8 contains a stack buffer overflow vulnerability that allows remote attackers to execute arbitrary code by crafting a malicious WAV file with oversized payload. Attackers can leverage a specially crafted exploit file with shellcode, SEH bypass, and egghunter technique to achieve remote code execution on vulnerable Windows systems.
Executive Summary:
A critical stack buffer overflow vulnerability, identified as CVE-2020-37000, exists within Free MP3 CD Ripper and potentially other products from the vendor. This flaw allows an attacker to gain complete control over a vulnerable Windows system by tricking a user into opening a specially crafted malicious WAV file. Successful exploitation could lead to arbitrary code execution, resulting in a full system compromise.
Vulnerability Details
CVE-ID: CVE-2020-37000
Affected Software: Free Multiple Products, including Free MP3 CD Ripper
Affected Versions: Free MP3 CD Ripper version 2.8. See vendor advisory for other specific affected products and versions.
Vulnerability: The vulnerability is a stack-based buffer overflow that occurs when the affected software processes a WAV audio file. An attacker can craft a malicious WAV file with an oversized data payload that, when opened by a user, overwrites the program's stack. This memory corruption can be leveraged to divert the application's control flow and execute arbitrary code provided by the attacker, using advanced techniques such as a Structured Exception Handler (SEH) bypass and an egghunter to locate and run shellcode.
Business Impact
This vulnerability is rated as critical severity with a CVSS score of 9.8. Successful exploitation grants an attacker full control over the affected user's workstation, equivalent to the user's own access level. This could lead to severe business consequences, including the theft of sensitive corporate or personal data, installation of persistent malware like ransomware or spyware, financial loss, and reputational damage. The compromised system could also be used as a pivot point to launch further attacks against other systems within the corporate network.
Remediation Plan
Immediate Action: Update Free Multiple Products to the latest version. It is crucial to check the vendor's security advisory for specific patch details corresponding to each affected product. In parallel, security teams should actively monitor for exploitation attempts and review access logs for any suspicious activity related to the vulnerable software.
Proactive Monitoring: Implement enhanced monitoring on endpoints where the affected software is installed. Security teams should look for unusual process creation originating from the Free MP3 CD Ripper executable, unexpected network connections, and the presence of suspicious .wav files on systems or in email attachments. Utilize Endpoint Detection and Response (EDR) solutions to detect memory exploitation techniques like SEH overwrites.
Compensating Controls: If immediate patching is not feasible, consider implementing compensating controls to reduce risk. This includes using application whitelisting to prevent the vulnerable software from running, restricting user permissions to limit the impact of a compromise, and providing user awareness training to warn against opening untrusted files from external sources. Additionally, ensure modern endpoint protection with anti-exploitation features is enabled and up-to-date.
Exploitation Status
Public Exploit Available: true
Analyst Notes: As of Jan 29, 2026, the description of the vulnerability indicates that detailed exploitation techniques, including shellcode, SEH bypass, and egghunter methods, are known. This strongly suggests that a functional public proof-of-concept (PoC) exploit exists. Although this CVE is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, its critical severity and the availability of exploit details make it a high-risk vulnerability.
Analyst Recommendation
Given the critical CVSS score of 9.8 and the low complexity required for an attacker to exploit this vulnerability, immediate action is required. Organizations must prioritize identifying all systems with the affected Free software installed and applying the vendor-supplied patches without delay. Due to the potential for complete system compromise from a single user action, this vulnerability poses a significant threat and should be treated as an urgent patching priority.
Update Free Multiple Products to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
Elaniin CMS 1
Elaniin CMS 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
BacklinkSpeed 2.4 contains a buffer overflow vulnerability that allows attackers to corrupt the Structured Exception Handler (SEH) chain through malic...
BacklinkSpeed 2.4 contains a buffer overflow vulnerability that allows attackers to corrupt the Structured Exception Handler (SEH) chain through malicious file import. Attackers can craft a specially designed payload file to overwrite SEH addresses, potentially executing arbitrary code and gaining control of the application.
Executive Summary:
A critical vulnerability has been identified in multiple BacklinkSpeed products, designated CVE-2020-36997. This flaw allows an attacker to take complete control of the application by tricking a user into opening a specially crafted file. Successful exploitation could lead to arbitrary code execution, enabling data theft, malware installation, and further network intrusion.
Vulnerability Details
CVE-ID: CVE-2020-36997
Affected Software: BacklinkSpeed Multiple Products
Affected Versions: Version 2.4 is confirmed vulnerable. See vendor advisory for a complete list of affected products and versions.
Vulnerability: The vulnerability is a stack-based buffer overflow that occurs during the file import process. An attacker can create a malicious file with an oversized data field that, when parsed by the application, overwrites the program's execution stack. This overwrite specifically targets the Structured Exception Handler (SEH) chain, a Windows mechanism for handling program errors. By replacing a legitimate SEH address with a pointer to their own malicious code (shellcode), the attacker can hijack the program's control flow and execute arbitrary commands with the permissions of the user running the application.
Business Impact
This vulnerability is rated as critical severity with a CVSS score of 9.8, reflecting the high potential for significant damage. An attacker who successfully exploits this flaw can gain full control over the affected application, leading to a complete compromise of the underlying system. Potential consequences include the theft of sensitive business data processed by the application, installation of ransomware or spyware, and using the compromised machine as a launchpad for further attacks against the internal network. The low complexity of the attack, requiring only user interaction to open a file, increases the risk of successful exploitation.
Remediation Plan
Immediate Action: The primary remediation is to apply the vendor-supplied security patches.
Proactive Monitoring:
Compensating Controls: If immediate patching is not feasible, implement the following controls to reduce risk:
Exploitation Status
Public Exploit Available: True
Analyst Notes: As of the publication date of January 29, 2026, proof-of-concept (PoC) exploit code for this vulnerability is publicly available. While this CVE is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, the public availability of exploit code significantly increases the likelihood of active exploitation by threat actors. Vulnerabilities involving classic SEH overwrite techniques are well-understood and can be easily weaponized.
Analyst Recommendation
Given the critical CVSS score of 9.8 and the public availability of exploit code, this vulnerability poses a severe and immediate risk to the organization. We strongly recommend that all affected BacklinkSpeed products be patched immediately. This vulnerability should be prioritized with the highest urgency. A comprehensive asset inventory should be conducted to identify all systems running the vulnerable software, and the remediation plan should be executed without delay to prevent potential system compromise.
Update BacklinkSpeed Multiple Products to the latest version. Check vendor security advisory for specific patch details. Monitor for exploitation attempts and review access logs.
Mocha Telnet Lite for iOS 4
Mocha Telnet Lite for iOS 4
Executive Summary:
A high-severity vulnerability has been identified in Mocha Telnet Lite for iOS, which could allow a remote attacker to compromise the user's device. Successful exploitation could lead to unauthorized access to sensitive information or the execution of arbitrary code, posing a significant risk to data confidentiality and system integrity.
Vulnerability Details
CVE-ID: CVE-2020-36995
Affected Software: Mocha Telnet Lite for iOS
Affected Versions: Version 4.0 and potentially prior versions. It is recommended to consult the vendor's security advisory for a complete list of affected versions.
Vulnerability: The vulnerability exists within the Mocha Telnet Lite application when processing data received from a Telnet server. A remote attacker could exploit this by tricking a user into connecting to a malicious Telnet server. The server could then send a specially crafted response that triggers a buffer overflow condition in the client application, potentially leading to arbitrary code execution on the user's iOS device with the privileges of the application.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 7.5. If exploited, an attacker could gain control over the user's mobile device, leading to significant business risks. Potential consequences include the theft of sensitive corporate data stored on or accessed by the device, unauthorized access to internal networks the device is connected to, and the potential for the compromised device to be used as a pivot point for further attacks within the organization's infrastructure. This poses a direct threat to data confidentiality, integrity, and availability.
Remediation Plan
Immediate Action: The primary remediation is to apply the security updates provided by the vendor immediately. All instances of Mocha Telnet Lite for iOS should be updated to a patched version as soon as possible to mitigate the risk. Additionally, security teams should actively monitor for any signs of exploitation and review relevant access and application logs for suspicious activity.
Proactive Monitoring: Organizations should monitor outbound network traffic from mobile devices running this application for connections to unusual or untrusted IP addresses on the Telnet port (TCP/23). Review application crash logs on iOS devices, as a failed exploitation attempt may cause the application to terminate unexpectedly. Utilize Mobile Device Management (MDM) solutions to detect unauthorized application behavior or configuration changes.
Compensating Controls: If immediate patching is not feasible, consider implementing the following compensating controls: Restrict the use of the application to trusted networks only and prohibit connections to unknown or external Telnet servers. Use a VPN to encrypt all traffic from the device. If the application is not business-critical, consider uninstalling it from all corporate devices until a patch can be applied.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of January 30, 2026, there are no known public exploits or active exploitation campaigns targeting this vulnerability. However, due to the high severity and the potential for remote code execution, it is likely that proof-of-concept code will be developed by security researchers or malicious actors. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog.
Analyst Recommendation
Given the high severity (CVSS 7.5) of this vulnerability and its potential for remote code execution, we strongly recommend that immediate action is taken. All devices with the affected Mocha Telnet Lite application should be identified and patched without delay. Although there is no evidence of active exploitation at this time, the risk of compromise is significant, and organizations should prioritize this remediation effort to prevent potential data breaches and unauthorized network access.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Nord VPN 6
Nord VPN 6
Executive Summary:
A high-severity vulnerability has been identified in multiple Nord products, specifically affecting NordVPN version 6. This flaw could allow a local attacker to escalate their privileges on a compromised system, potentially leading to a full system takeover, data theft, and further network intrusion. Organizations are urged to apply the vendor-provided security updates immediately to mitigate this significant risk.
Vulnerability Details
CVE-ID: CVE-2020-36992
Affected Software: Nord Multiple Products
Affected Versions: NordVPN version 6. See vendor advisory for specific affected versions.
Vulnerability: This vulnerability is a local privilege escalation flaw within the NordVPN service component that runs with elevated system permissions. An authenticated, low-privileged local attacker can exploit this by sending a specially crafted inter-process communication (IPC) message to the privileged service. Due to improper input validation, the service can be manipulated into executing arbitrary code or commands with the permissions of the SYSTEM or root user, leading to a complete compromise of the host operating system.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 7.8. Successful exploitation could have a severe impact on business operations. An attacker who gains initial low-level access to an endpoint (e.g., through phishing) could leverage this vulnerability to gain full administrative control. This would allow the attacker to disable security controls, install persistent malware such as ransomware or keyloggers, exfiltrate sensitive corporate data, and use the compromised machine as a pivot point to attack other critical systems on the internal network.
Remediation Plan
Immediate Action: Apply vendor security updates immediately across all affected endpoints. The update resolves the vulnerability by implementing proper validation on IPC messages. After patching, it is crucial to monitor for any signs of post-exploitation activity and review system and application access logs for any unusual behavior preceding the patch deployment.
Proactive Monitoring: Security teams should monitor for indicators of compromise, including unexpected process creation originating from the NordVPN service process, unauthorized modifications to system files or configurations, and anomalous outbound network traffic from endpoints running the software. Endpoint Detection and Response (EDR) solutions should be configured to alert on common privilege escalation techniques.
Compensating Controls: If immediate patching is not feasible, organizations should enforce the principle of least privilege to limit the initial attack surface. Employing application whitelisting can prevent the execution of unauthorized code that an attacker might attempt to run after escalating privileges. Enhanced endpoint monitoring and network segmentation can also help contain the impact of a potential compromise.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of January 30, 2026, there are no known public proof-of-concept exploits or observed in-the-wild exploitation of this vulnerability. However, given the high severity and the commonality of this vulnerability class, security researchers are likely to develop and publish exploit code. Threat actors will likely begin reverse-engineering the patch to create functional exploits for use in targeted attacks.
Analyst Recommendation
Due to the high CVSS score of 7.8, this vulnerability presents a significant risk to the organization. A successful exploit grants an attacker complete control over an affected system. We strongly recommend that all system administrators prioritize the immediate deployment of the vendor-supplied patches to all workstations and servers running the affected NordVPN software. Although this CVE is not currently listed on the CISA KEV catalog, its severity makes it a prime candidate for future inclusion, and proactive remediation is the most effective defense.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
ShareMouse 5
ShareMouse 5
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Input Director 1
Input Director 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
ForensiT AppX Management Service 2
ForensiT AppX Management Service 2
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Program Access Controller 1
Program Access Controller 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Prey 1
Prey 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
IP Watcher 3
IP Watcher 3
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
EPSON 1
EPSON 1
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Quick 'n Easy FTP Service 3
Quick 'n Easy FTP Service 3
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Motorola Device Manager 2
Motorola Device Manager 2
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Motorola Device Manager 2
Motorola Device Manager 2
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Executive Summary:
A high-severity vulnerability has been identified in multiple Avast products, including Avast SecureLine. This flaw could allow a local attacker to escalate their privileges and gain complete control over an affected system, potentially leading to data theft, malware installation, or further network compromise. Organizations are urged to apply the vendor-provided security updates immediately to mitigate this significant risk.
Vulnerability Details
CVE-ID: CVE-2020-37037
Affected Software: Avast Multiple Products
Affected Versions: Avast SecureLine 5. See vendor advisory for specific affected versions.
Vulnerability: The vulnerability is a local privilege escalation flaw within a privileged service component of the Avast software. An authenticated, low-privileged local attacker can exploit this by sending a specially crafted input or command to the service. Due to improper input validation or insecure handling of shared resources, the service can be tricked into executing arbitrary code with SYSTEM-level privileges, leading to a full compromise of the host machine.
Business Impact
This vulnerability is rated as High severity with a CVSS score of 7.8. Successful exploitation could have a severe impact on business operations. An attacker who gains administrative control of an endpoint can bypass all local security controls, access or exfiltrate sensitive corporate data, deploy ransomware, or use the compromised machine as a pivot point to move laterally across the internal network. The compromise of a security product like Avast undermines the foundational trust in the organization's security posture and can lead to significant reputational damage and financial loss.
Remediation Plan
Immediate Action: The primary and most effective remediation is to apply the security updates provided by Avast across all affected endpoints without delay. After patching, system administrators should review system and application logs for any signs of anomalous activity that may indicate a prior compromise.
Proactive Monitoring: Implement enhanced monitoring on endpoints running the affected software. Security teams should use SIEM and EDR solutions to monitor for suspicious process creation originating from Avast services, unexpected service restarts, or unauthorized modifications to system files. Monitor for outbound network connections to unknown destinations from affected hosts.
Compensating Controls: If immediate patching is not feasible, implement compensating controls to reduce the risk. Enforce the principle of least privilege to ensure users do not have unnecessary local administrative rights. Utilize application whitelisting to prevent the execution of unauthorized executables that an attacker might try to run post-exploitation.
Exploitation Status
Public Exploit Available: False
Analyst Notes: As of February 2, 2026, there are no known public exploits for this vulnerability, and it is not listed on CISA's Known Exploited Vulnerabilities (KEV) catalog. However, given the high severity score and the nature of the vulnerability (privilege escalation), it is a prime target for threat actors to develop exploits for use in targeted attacks.
Analyst Recommendation
Given the high severity (CVSS 7.8) and the potential for a complete system takeover, we strongly recommend that organizations prioritize the immediate patching of this vulnerability. Although there is no evidence of active exploitation in the wild, the risk of a local attacker or malware leveraging this flaw to gain full control of a system is significant. All workstations and servers running the affected Avast products should be identified and updated immediately to prevent potential exploitation.