Top 100 Recent CVEs

CVE-2025-64310 9.8
Published: 2025-11-21T03:16:10.857

What it does:

The EPSON WebConfig and Epson Web Control for SEIKO EPSON Projector Products are vulnerable to brute force attacks because they do not limit the number of authentication attempts, allowing an attacker to repeatedly try different passwords to gain access to an administrative user's account.

Why it's a problem:

This vulnerability is a problem because it enables attackers to guess or crack administrative passwords through relentless guessing, potentially leading to unauthorized access and control of the projector products, which could result in data breaches, malicious configuration changes, or other harmful activities.

Steps to mitigate:

  • Implement rate limiting or account lockout policies for authentication attempts
  • Use strong, unique passwords for administrative accounts
  • Enable multi-factor authentication (MFA) to add an extra layer of security
  • Regularly update and patch EPSON WebConfig and Epson Web Control software to the latest version
  • Monitor system logs for suspicious authentication activity.
CVE-2025-64762 0
Published: 2025-11-21T02:15:44.077

What it does:

The AuthKit library for Next.js has a vulnerability that allows authenticated responses to be cached by CDNs, potentially including sensitive session tokens, when using authkit-nextjs version 2.11.0 or below.

Why it's a problem:

This vulnerability is a problem because it can result in session tokens being served to multiple users, allowing unauthorized access to sensitive information and potentially leading to security breaches.

Steps to mitigate:

  • Update authkit-nextjs to version 2.11.1 or later, which applies anti-caching headers to all responses behind authentication
  • Avoid enabling CDN caching for authenticated paths in Next.js applications, especially when deployed on platforms like Vercel
  • Manually set anti-caching headers on authenticated responses as a temporary workaround until the update to authkit-nextjs 2.11.1 or later can be applied.
CVE-2025-64755 0
Published: 2025-11-21T02:15:43.917

What it does:

The CVE-2025-64755 vulnerability allows an attacker to bypass the read-only validation in Claude Code, an agentic coding tool, and write to arbitrary files on the host system due to an error in sed command parsing.

Why it's a problem:

This vulnerability is a problem because it enables unauthorized modifications to files on the host system, potentially leading to data corruption, system compromise, or malicious activity.

Steps to mitigate:

  • Update Claude Code to version 2.0.31 or later
  • [Ensure all dependencies and related tools are updated to the latest versions]
  • [Monitor system logs for suspicious file modifications and access attempts]
CVE-2025-64751 0
Published: 2025-11-21T02:15:43.747

What it does:

The CVE-2025-64751 vulnerability affects OpenFGA, an authorization engine, and allows for improper policy enforcement when specific calls are made, potentially leading to unauthorized access or data exposure.

Why it's a problem:

This vulnerability is a problem because it can compromise the security and integrity of systems that rely on OpenFGA for permission management, potentially allowing malicious actors to bypass restrictions and access sensitive data or perform unauthorized actions.

Steps to mitigate:

  • Update OpenFGA to version 1.11.1 or later
  • Verify that your Helm chart version is outside the vulnerable range (openfga-0.1.34 to openfga-0.2.48)
  • Ensure your Docker version is updated to a version outside the vulnerable range (v.1.4.0 to v.1.11.0)
CVE-2025-62426 6.5
Published: 2025-11-21T02:15:43.570

What it does:

The CVE-2025-62426 vulnerability affects the vLLM inference and serving engine, allowing an attacker to send a specially crafted request to the /v1/chat/completions and /tokenize endpoints, which can cause the API server to become unresponsive for an extended period.

Why it's a problem:

This vulnerability is a problem because it enables a denial-of-service (DoS) attack, where an attacker can intentionally overload the API server, delaying or blocking all other requests and potentially disrupting critical services that rely on the vLLM engine.

Steps to mitigate:

  • Update vLLM to version 0.11.1 or later
  • [Verify that the /v1/chat/completions and /tokenize endpoints are properly validated and sanitized to prevent malicious requests]
  • Implement rate limiting and IP blocking to prevent repeated DoS attacks from the same source.
CVE-2025-62372 0
Published: 2025-11-21T02:15:43.393

What it does:

The CVE-2025-62372 vulnerability allows attackers to crash the vLLM engine, which serves large language models, by sending specially crafted multimodal embedding inputs with incorrect shapes, even if the model is not intended to support such inputs.

Why it's a problem:

This vulnerability is a problem because it can be used to disrupt the service of the vLLM engine, potentially leading to downtime and affecting users who rely on it, by exploiting a flaw in the engine's input validation.

Steps to mitigate:

  • Update vLLM engine to version 0.11.1 or later
  • Verify that the model is configured to only accept supported input shapes
  • Monitor the engine for suspicious activity and crashes to detect potential exploitation attempts.
CVE-2025-62164 8.8
Published: 2025-11-21T02:15:43.193

What it does:

The CVE-2025-62164 vulnerability is a memory corruption issue in the vLLM inference and serving engine that can cause a crash or potentially allow remote code execution when processing user-supplied prompt embeddings.

Why it's a problem:

This vulnerability is a problem because it can be exploited by attackers to crash the vLLM server, disrupting service, or potentially execute malicious code on the server, leading to unauthorized access or data breaches.

Steps to mitigate:

  • Update vLLM to version 0.11.1 or later
  • [Validate user-supplied prompt embeddings to prevent malicious input]
  • [Enable sparse tensor integrity checks in PyTorch to prevent bypassing internal bounds checks]
  • [Monitor server logs for signs of denial-of-service or remote code execution attempts]
CVE-2025-13485 7.3
Published: 2025-11-21T00:15:49.060

What it does:

The CVE-2025-13485 vulnerability allows an attacker to inject malicious SQL code into the itsourcecode Online File Management System 1.0 by manipulating the "Username" argument in the /ajax.php?action=login file, which can be done remotely.

Why it's a problem:

This vulnerability is a problem because it enables attackers to access and manipulate sensitive data in the system's database, potentially leading to unauthorized data breaches, modification, or deletion, which can have serious consequences for the security and integrity of the system.

Steps to mitigate:

  • Update the itsourcecode Online File Management System to a patched version
  • [Implement input validation and sanitization for user inputs]
  • [Use prepared statements to prevent SQL injection]
  • [Limit remote access to the system
  • [Monitor system logs for suspicious activity]
CVE-2025-64660 5.7
Published: 2025-11-20T23:15:56.943

What it does:

The CVE-2025-64660 vulnerability allows an authorized attacker to bypass a security feature in GitHub Copilot and Visual Studio Code over a network, due to improper access control.

Why it's a problem:

This vulnerability is a problem because it enables attackers to gain unauthorized access to sensitive information or systems, potentially leading to data breaches, unauthorized modifications, or other malicious activities, even if they already have some level of authorized access.

Steps to mitigate:

  • Update GitHub Copilot and Visual Studio Code to the latest versions
  • [Check network security settings to ensure proper access controls are in place]
  • Implement additional security measures, such as multi-factor authentication and intrusion detection systems
  • Monitor system logs for suspicious activity
  • Limit network access to authorized personnel only.
CVE-2025-64655 8.8
Published: 2025-11-20T23:15:56.750

What it does:

The CVE-2025-64655 vulnerability allows an unauthorized attacker to gain elevated privileges over a network by exploiting improper authorization in Dynamics OmniChannel SDK Storage Containers.

Why it's a problem:

This vulnerability is a problem because it enables attackers to access sensitive information and perform actions that they should not be allowed to, potentially leading to data breaches, system compromise, and other malicious activities, especially given its high severity score of 8.8.

Steps to mitigate:

  • Update Dynamics OmniChannel SDK to the latest version
  • [Apply security patches from the vendor]
  • Implement network segmentation to limit access to Storage Containers
  • Monitor network activity for suspicious behavior
  • Restrict access to authorized personnel only.
CVE-2025-62459 8.3
Published: 2025-11-20T23:15:56.563

What it does:

The Microsoft Defender Portal Spoofing Vulnerability (CVE-2025-62459) allows an attacker to trick users into interacting with a fake Microsoft Defender portal, potentially leading to unauthorized access or malicious activities.

Why it's a problem:

This vulnerability is a problem because it can be used to deceive users into revealing sensitive information, installing malware, or performing unintended actions, which can compromise the security of their systems and data.

Steps to mitigate:

  • Verify the authenticity of the Microsoft Defender portal
  • [Update Microsoft Defender to the latest version]
  • [Be cautious of suspicious links or prompts]
  • [Enable two-factor authentication for an additional layer of security]
  • [Regularly monitor system activity for signs of unauthorized access]
CVE-2025-62207 8.6
Published: 2025-11-20T23:15:55.350

What it does:

The Azure Monitor Elevation of Privilege Vulnerability allows an attacker to gain elevated access and permissions within the Azure Monitor system, potentially giving them control over sensitive data and operations.

Why it's a problem:

This vulnerability is a problem because it could enable unauthorized users to access, modify, or delete critical system resources, leading to data breaches, service disruptions, or other malicious activities, ultimately compromising the security and integrity of the affected systems.

Steps to mitigate:

  • Update Azure Monitor to the latest patched version
  • Implement least privilege access controls to limit user permissions
  • Monitor system logs for suspicious activity and anomalies
  • Apply additional security measures such as multi-factor authentication to prevent unauthorized access.
CVE-2025-59245 9.8
Published: 2025-11-20T23:15:52.253

What it does:

The CVE-2025-59245 vulnerability allows an attacker to gain elevated privileges on Microsoft SharePoint Online, potentially giving them unauthorized access to sensitive information and capabilities.

Why it's a problem:

This vulnerability is a problem because it enables attackers to bypass normal security restrictions, allowing them to perform malicious actions such as accessing confidential data, modifying system settings, or taking control of user accounts, which can lead to significant data breaches and security compromises.

Steps to mitigate:

  • Apply the latest security patches from Microsoft
  • [Implement least privilege access principles for all SharePoint users]
  • [Monitor SharePoint Online for suspicious activity and anomalies
  • [Configure auditing and logging to detect potential exploitation attempts]
CVE-2025-49752 10.0
Published: 2025-11-20T23:15:51.780

What it does:

The Azure Bastion Elevation of Privilege Vulnerability allows an attacker to gain higher-level access and control within an Azure Bastion environment, potentially enabling them to perform actions that would normally be restricted.

Why it's a problem:

This vulnerability is a problem because it could allow unauthorized users to gain administrative access, compromising the security and integrity of the Azure Bastion and connected resources, leading to potential data breaches, system compromises, and other malicious activities.

Steps to mitigate:

  • Update Azure Bastion to the latest version
  • [Apply the security patch provided by Microsoft]
  • Implement least privilege access principles to limit user permissions
  • Monitor Azure Bastion logs for suspicious activity
  • Contact Microsoft support for further guidance and recommendations.
CVE-2025-36072 8.8
Published: 2025-11-20T23:15:51.527

What it does:

The CVE-2025-36072 vulnerability in IBM webMethods Integration allows an authenticated user to execute arbitrary code on the system by exploiting the deserialization of untrusted object graphs data.

Why it's a problem:

This vulnerability is a problem because it enables an attacker with authenticated access to take control of the system, potentially leading to data breaches, malware installation, or other malicious activities, which can have severe consequences for the security and integrity of the system.

Steps to mitigate:

  • Update IBM webMethods Integration to the latest version beyond the affected ranges (10.11_Core_Fix22, 10.15_Core_Fix22, 11.1_Core_Fix6)
  • Implement strict access controls to limit authenticated user privileges
  • Monitor system activity for suspicious behavior and signs of exploitation
  • Apply security patches and fixes as soon as they are available from the vendor.
CVE-2025-13484 2.4
Published: 2025-11-20T23:15:50.723

What it does:

This vulnerability allows an attacker to inject malicious code into the Campcodes Complete Online Beauty Parlor Management System, specifically through the "Name" argument in the /admin/customer-list.php file, leading to a cross-site scripting (XSS) attack that can be initiated remotely.

Why it's a problem:

This vulnerability is a problem because it enables attackers to execute malicious scripts on the system, potentially stealing sensitive data, hijacking user sessions, or taking control of the system, which can compromise the security and integrity of the beauty parlor management system and its users.

Steps to mitigate:

  • Update the Campcodes Complete Online Beauty Parlor Management System to a patched version
  • [Implement input validation and sanitization for the "Name" argument in the /admin/customer-list.php file
  • [Use a Web Application Firewall (WAF) to detect and prevent XSS attacks
  • [Limit access to the /admin/customer-list.php file to authorized personnel only
  • [Monitor system logs for suspicious activity and signs of XSS attacks].
CVE-2025-61138 0
Published: 2025-11-20T22:16:01.610

What it does:

The Qlik Sense Enterprise version v14.212.13 has a vulnerability that allows unauthorized access to sensitive information through the /dev-hub/ directory, potentially exposing internal data.

Why it's a problem:

This vulnerability is a problem because it could allow attackers to gain access to confidential information, which could be used for malicious purposes, compromising the security and integrity of the system and its data.

Steps to mitigate:

  • Update Qlik Sense Enterprise to the latest version
  • [Apply security patches to fix the information leak vulnerability]
  • [Restrict access to the /dev-hub/ directory by configuring proper access controls and permissions]
  • [Monitor system logs for suspicious activity related to the /dev-hub/ directory]
CVE-2025-36160 5.3
Published: 2025-11-20T22:15:57.530

What it does:

The IBM Concert vulnerability (CVE-2025-36160) allows sensitive server information to be disclosed through HTTP response headers, potentially revealing details about the system.

Why it's a problem:

This vulnerability is a problem because it could provide attackers with valuable information to plan and execute further attacks against the system, compromising its security and potentially leading to unauthorized access or data breaches.

Steps to mitigate:

  • Update IBM Concert to a version later than 2.0.0
  • Configure the server to remove sensitive information from HTTP response headers
  • Implement a web application firewall (WAF) to filter and monitor incoming traffic
  • Regularly review and update server configurations to ensure security best practices are followed.
CVE-2025-36159 6.2
Published: 2025-11-20T22:15:57.340

What it does:

This vulnerability in IBM Concert versions 1.0.0 through 2.0.0 allows a local user to manipulate log files, making it possible to impersonate other users or conceal their own identity by altering the logs.

Why it's a problem:

This vulnerability is a problem because it enables malicious users to disguise their actions, making it difficult to track and identify security breaches or other malicious activities, which can lead to further unauthorized access or damage.

Steps to mitigate:

  • Update IBM Concert to a version later than 2.0.0 if available
  • Implement strict access controls to limit who can modify log files
  • Monitor log files regularly for suspicious activity and discrepancies
  • Consider using additional logging and auditing tools to enhance security and detection capabilities.
CVE-2025-36158 5.1
Published: 2025-11-20T22:15:57.153

What it does:

The IBM Concert vulnerability allows a local user with specific permissions to access sensitive information from files by exploiting uncontrolled recursive directory copying in versions 1.0.0 through 2.0.0.

Why it's a problem:

This vulnerability is a problem because it enables unauthorized access to sensitive information, potentially leading to data breaches or other security issues, even if the attacker only has local access and specific permissions.

Steps to mitigate:

  • Update IBM Concert to a version later than 2.0.0
  • $ Restrict local user permissions to minimize access
  • $ Monitor system logs for suspicious directory copying activity
  • $ Implement additional access controls to sensitive files and directories.
CVE-2025-36153 6.1
Published: 2025-11-20T22:15:56.970

What it does:

This vulnerability allows an attacker to embed arbitrary JavaScript code into the IBM Concert Web UI, altering its intended functionality and potentially leading to the disclosure of sensitive credentials within a trusted session.

Why it's a problem:

This vulnerability is a problem because it enables unauthenticated attackers to manipulate the Web UI, potentially stealing credentials and gaining unauthorized access to sensitive information, which could compromise the security and integrity of the system.

Steps to mitigate:

  • Update IBM Concert to a version later than 2.0.0
  • [Apply security patches provided by IBM]
  • [Implement Web Application Firewall (WAF) rules to detect and prevent cross-site scripting attacks]
  • [Limit access to the IBM Concert Web UI to trusted users and networks
  • [Monitor system logs for suspicious activity and signs of potential exploitation].
CVE-2025-13087 6.2
Published: 2025-11-20T22:15:54.310

What it does:

This vulnerability allows an attacker to execute arbitrary code with root privileges on Opto22 Groov Manage REST API, affecting GRV-EPIC and groov RIO Products, by injecting malicious commands through a POST request.

Why it's a problem:

This vulnerability is a problem because it enables an attacker with administrative privileges to gain complete control over the affected system, potentially leading to unauthorized access, data breaches, and disruption of critical operations.

Steps to mitigate:

  • Update Opto22 Groov Manage software to the latest version
  • [Apply security patches provided by the vendor]
  • Implement network segmentation to limit access to the vulnerable API
  • [Use intrusion detection and prevention systems to monitor for suspicious activity]
  • Restrict administrative privileges to trusted personnel only.
CVE-2025-64770 6.8
Published: 2025-11-20T21:16:06.753

What it does:

This vulnerability allows unauthorized access to camera configuration information through Open Network Video Interface Forum (ONVIF) services without requiring authentication.

Why it's a problem:

This is a problem because it enables attackers to gain access to sensitive camera settings and potentially manipulate them, which could lead to unauthorized surveillance, data breaches, or disruption of camera functionality.

Steps to mitigate:

  • Enable authentication for ONVIF services
  • Implement firewall rules to restrict access to ONVIF ports
  • Update affected products to the latest firmware or software version
  • Limit camera access to trusted networks or IPs
  • Monitor camera systems for suspicious activity
CVE-2025-63807 0
Published: 2025-11-20T21:16:06.617

What it does:

This vulnerability allows attackers to perform brute-force attacks on verification codes in the university-bbs (Blogin) system without authentication, due to a weak verification code generation mechanism and lack of rate limiting, potentially leading to account takeover via password reset or other authentication bypass methods.

Why it's a problem:

This vulnerability is a problem because it enables unauthorized users to gain access to accounts, potentially leading to sensitive information theft, data tampering, or other malicious activities, which can have serious consequences for the security and integrity of the system and its users.

Steps to mitigate:

  • Implement a stronger verification code generation mechanism
  • [Enforce rate limiting on verification code attempts]
  • [Update university-bbs (Blogin) to a version that addresses this vulnerability, if available]
  • [Use additional authentication methods, such as two-factor authentication, to prevent account takeover
  • [Monitor system logs for suspicious activity and respond promptly to potential security incidents].
CVE-2025-63685 0
Published: 2025-11-20T21:16:06.370

What it does:

The Quark Cloud Drive v3.23.2 application is vulnerable to DLL Hijacking, which allows an attacker to load and execute a malicious DLL file when the program starts, by placing it in the application's startup directory.

Why it's a problem:

This vulnerability is a problem because it enables an attacker to run malicious code on a user's system, potentially leading to data theft, system compromise, or other harmful activities, simply by tricking the user into launching the application.

Steps to mitigate:

  • Update Quark Cloud Drive to a version later than v3.23.2
  • [Avoid running the application from untrusted directories]
  • [Monitor system activity for suspicious behavior]
  • [Use antivirus software to scan for malicious DLL files]
CVE-2025-62674 6.8
Published: 2025-11-20T21:16:05.957

What it does:

The CVE-2025-62674 vulnerability allows unauthorized access to Real Time Streaming Protocol (RTSP) services without requiring authentication, potentially giving attackers access to sensitive camera configuration information.

Why it's a problem:

This vulnerability is a problem because it could allow malicious individuals to gain unauthorized access to camera settings and configuration data, which could be used for malicious purposes such as spying, data theft, or disrupting camera functionality.

Steps to mitigate:

  • Implement authentication for RTSP services
  • Configure cameras to use secure communication protocols
  • Limit access to RTSP services to trusted networks and IP addresses
  • Regularly update camera firmware and software to ensure latest security patches are applied.
CVE-2025-25613 0
Published: 2025-11-20T21:16:02.310

What it does:

The FS Inc S3150-8T2F switch transmits cookies containing usernames and passwords in cleartext using simple base64 encoding during every POST request to the server for its web-based administrative application, for all versions before 2.2.0D Build 135103.

Why it's a problem:

This vulnerability is a problem because it allows unauthorized access to sensitive information, such as usernames and passwords, which can be easily decoded from the base64 encoding, potentially leading to unauthorized control of the switch and the network it manages.

Steps to mitigate:

  • Update the switch to version 2.2.0D Build 135103 or later
  • [Use a secure connection, such as HTTPS, to encrypt data transmitted to and from the switch]
  • [Change passwords and usernames for all administrative accounts after updating the switch]
  • [Limit access to the switch's administrative interface to trusted networks or IPs only]
CVE-2025-55124 0
Published: 2025-11-20T20:16:23.677

What it does:

The CVE-2025-55124 vulnerability allows an attacker to inject malicious code into the Revive Adserver's banner-zone.php script, which can lead to a reflected Cross-Site Scripting (XSS) attack, enabling the execution of unauthorized code on a user's browser.

Why it's a problem:

This vulnerability is a problem because it can be exploited by attackers to steal user data, take control of user sessions, or redirect users to malicious websites, ultimately compromising the security and privacy of users interacting with the affected Revive Adserver.

Steps to mitigate:

  • Update Revive Adserver to the latest version
  • [patch the banner-zone.php script to properly neutralize user input]
  • implement a Web Application Firewall (WAF) to detect and prevent XSS attacks
  • use a reputable XSS filtering solution to protect user browsers.
CVE-2025-55123 0
Published: 2025-11-20T20:16:23.547

What it does:

The CVE-2025-55123 vulnerability allows manager accounts in Revive Adserver versions 5.5.2, 6.0.1, and earlier to create malicious input that can launch Cross-Site Scripting (XSS) attacks on their own advertiser users.

Why it's a problem:

This vulnerability is a problem because it enables attackers to inject malicious code into the websites or applications of advertiser users, potentially leading to unauthorized access, data theft, or other malicious activities.

Steps to mitigate:

  • Update Revive Adserver to the latest version
  • [apply security patches to fix the input neutralization issue]
  • implement additional security measures such as input validation and sanitization to prevent XSS attacks
  • monitor user activity for suspicious behavior
  • restrict manager account privileges to minimize potential damage.
CVE-2025-52671 0
Published: 2025-11-20T20:16:23.410

What it does:

The CVE-2025-52671 vulnerability allows non-admin users to access debug information in SQL error messages in Revive Adserver versions 5.5.2, 6.0.1, and earlier, revealing details about the software, PHP, and database versions being used.

Why it's a problem:

This vulnerability is a problem because it discloses sensitive information about the system's configuration, which could be used by attackers to plan and launch targeted attacks, potentially leading to further exploitation and compromise of the system.

Steps to mitigate:

  • Update Revive Adserver to the latest version
  • [check and disable debug mode in SQL error messages]
  • implement access controls to restrict non-admin users from viewing error messages
  • monitor system logs for suspicious activity.
CVE-2025-52670 0
Published: 2025-11-20T20:16:23.280

What it does:

The CVE-2025-52670 vulnerability allows users to delete banners owned by other accounts in Revive Adserver versions 5.5.2, 6.0.1, and earlier, due to a missing authorization check.

Why it's a problem:

This vulnerability is a problem because it enables unauthorized users to manipulate and delete advertisements that belong to other accounts, potentially disrupting ad campaigns, causing financial losses, and compromising the integrity of the ad serving system.

Steps to mitigate:

  • Update to the latest version of Revive Adserver
  • [apply security patches to earlier versions if available]
  • restrict user permissions to prevent unauthorized access to banners
  • monitor ad server activity for suspicious deletion of banners
  • implement additional authorization checks to prevent unauthorized banner deletion.
CVE-2025-52669 0
Published: 2025-11-20T20:16:23.140

What it does:

The CVE-2025-52669 vulnerability allows non-admin users to access the contact name and email address of other users in the Revive Adserver system, specifically in versions 5.5.2, 6.0.1, and earlier.

Why it's a problem:

This vulnerability is a problem because it compromises user privacy by exposing sensitive contact information to unauthorized individuals, potentially leading to spam, phishing attacks, or other malicious activities.

Steps to mitigate:

  • Update Revive Adserver to the latest version
  • [check user management system settings to ensure proper access controls]
  • implement additional security measures to protect user data, such as encryption and secure authentication protocols.
CVE-2025-52668 0
Published: 2025-11-20T20:16:22.987

What it does:

The CVE-2025-52668 vulnerability allows an attacker to inject malicious code into the stats-conversions.php script in Revive Adserver versions 5.5.2, 6.0.1, and earlier, potentially leading to information disclosure and session hijacking through a stored XSS (Cross-Site Scripting) attack.

Why it's a problem:

This vulnerability is a problem because it enables attackers to steal sensitive information, hijack user sessions, and potentially gain unauthorized access to the affected system, compromising the security and privacy of users.

Steps to mitigate:

  • Update Revive Adserver to the latest version
  • [patch the stats-conversions.php script to properly neutralize user input]
  • implement a Web Application Firewall (WAF) to detect and prevent XSS attacks
  • use a reputable security plugin to scan for vulnerabilities and monitor system activity.
CVE-2025-52667 0
Published: 2025-11-20T20:16:22.830

What it does:

The CVE-2025-52667 vulnerability allows a stored XSS (Cross-Site Scripting) attack to occur in Revive Adserver versions 6.0.1, 5.5.2, and earlier, due to a missing JSON Content-Type header in a script, which can be exploited by a logged-in manager user.

Why it's a problem:

This vulnerability is a problem because it enables an attacker to inject malicious code into the system, potentially leading to unauthorized access, data theft, or disruption of service, by exploiting the trust given to a logged-in manager user.

Steps to mitigate:

  • Update to a patched version of Revive Adserver
  • [Apply a JSON Content-Type header to the vulnerable script]
  • Implement additional security measures such as input validation and output encoding to prevent XSS attacks
  • Limit access to manager user accounts and monitor their activity
  • Consider using a Web Application Firewall (WAF) to detect and prevent XSS attacks.
CVE-2025-52666 0
Published: 2025-11-20T20:16:22.687

What it does:

The CVE-2025-52666 vulnerability allows an attacker to exploit improper neutralization of format characters in the settings of Revive Adserver versions 5.5.2, 6.0.1, and earlier, potentially causing a fatal PHP error that disables the admin user console.

Why it's a problem:

This vulnerability is a problem because it can be used to disable administrative access to the Revive Adserver, potentially allowing an attacker to disrupt or take control of the system, and causing significant disruption to advertising services.

Steps to mitigate:

  • Update to the latest version of Revive Adserver
  • [apply security patches to fix the format character neutralization issue]
  • restrict access to the admin console to trusted users and networks
  • monitor server logs for signs of attempted exploitation.
CVE-2025-48987 0
Published: 2025-11-20T20:16:22.550

What it does:

The CVE-2025-48987 vulnerability allows an attacker to inject malicious code into the Revive Adserver, specifically versions 5.5.2, 6.0.1, and earlier, through improper neutralization of user input, leading to a potential reflected Cross-Site Scripting (XSS) attack.

Why it's a problem:

This vulnerability is a problem because it enables attackers to execute malicious scripts on a user's browser, potentially stealing sensitive information, hijacking user sessions, or performing unauthorized actions, which can compromise the security and integrity of the affected system and its users.

Steps to mitigate:

  • Update Revive Adserver to the latest version
  • [apply security patches to fix the input neutralization issue]
  • implement a Web Application Firewall (WAF) to detect and prevent XSS attacks
  • use input validation and sanitization to ensure user input is properly handled and cleaned.
CVE-2025-48986 0
Published: 2025-11-20T20:16:22.407

What it does:

The CVE-2025-48986 vulnerability allows an authorized user to bypass security measures in Revive Adserver versions 5.5.2, 6.0.1, and earlier, enabling them to change other users' email addresses and potentially take control of their accounts by exploiting the forgot password feature.

Why it's a problem:

This vulnerability is a problem because it can lead to unauthorized account takeovers, allowing attackers to access sensitive information, make changes to accounts, and potentially disrupt the entire system, compromising the security and integrity of the Revive Adserver platform.

Steps to mitigate:

  • Update Revive Adserver to the latest version
  • [_patch or fix the authorization bypass issue]
  • Implement additional security measures such as multi-factor authentication to prevent unauthorized account takeovers
  • Monitor user account activity for suspicious changes to email addresses or password resets.
CVE-2025-35029 3.5
Published: 2025-11-20T20:16:22.187

What it does:

This vulnerability allows an authenticated attacker to add malicious content to the 'Demographic Information' page in Medical Informatics Engineering Enterprise Health, which will be executed when someone else accesses the page.

Why it's a problem:

This is a problem because it enables attackers to inject arbitrary code, potentially leading to unauthorized actions, data theft, or disruption of the system, all of which can compromise the security and integrity of sensitive medical information.

Steps to mitigate:

  • Update Medical Informatics Engineering Enterprise Health to the latest version released after 2025-03-14
  • Ensure that all users with access to the 'Demographic Information' page have the least privileges necessary to perform their tasks
  • Monitor the system for any suspicious activity, especially after the vulnerability was disclosed on 2025-11-20.
CVE-2025-63700 0
Published: 2025-11-20T19:16:21.367

What it does:

This vulnerability allows attackers to bypass the OAuth authentication process in Clerk-js version 5.88.0 by manipulating the request during the One-Time Password (OTP) verification stage.

Why it's a problem:

This vulnerability is a problem because it enables unauthorized access to protected resources, potentially leading to data breaches, identity theft, or other malicious activities, by circumventing the intended authentication mechanism.

Steps to mitigate:

  • Update Clerk-js to a version newer than 5.88.0
  • [Implement additional authentication measures, such as multi-factor authentication, to provide an extra layer of security
  • [Monitor authentication logs for suspicious activity and respond promptly to potential security incidents]
  • [Consider temporarily disabling OTP verification until a patched version of Clerk-js is deployed]
CVE-2025-55128 0
Published: 2025-11-20T19:16:19.137

What it does:

This vulnerability allows an attacker with admin interface access to request an excessively large number of items per page on the "userlog-index.php" page, potentially overwhelming the system.

Why it's a problem:

This vulnerability is a problem because it could lead to a denial of service, where the system becomes unresponsive or crashes due to excessive resource consumption, disrupting normal operations and causing inconvenience to users.

Steps to mitigate:

  • Implement input validation to limit the number of items per page
  • Restrict access to the admin interface to trusted users
  • Monitor system resources for unusual consumption patterns
  • Update the "userlog-index.php" page to handle large requests more efficiently
  • Apply security patches or updates as soon as they become available.
CVE-2025-55127 0
Published: 2025-11-20T19:16:19.027

What it does:

This vulnerability allows an attacker to create a username with leading or trailing whitespace characters, making it appear similar to a legitimate username when displayed in the user interface.

Why it's a problem:

This vulnerability can cause confusion among users and administrators, potentially leading to mistaken identities, unauthorized access, or other security issues, as the username with whitespace may be virtually indistinguishable from its legitimate counterpart.

Steps to mitigate:

  • Validate and trim usernames to remove leading and trailing whitespace before creating new user accounts
  • Implement a username display mechanism that visibly indicates the presence of whitespace characters
  • Regularly review and update user account management policies to prevent similar vulnerabilities.
CVE-2025-55126 0
Published: 2025-11-20T19:16:18.880

What it does:

This vulnerability allows an attacker to store malicious code in the campaign names on advertiser-related pages, which can then be executed when a user interacts with the navigation box at the top of the page, potentially leading to cross-site scripting (XSS) attacks.

Why it's a problem:

This vulnerability is a problem because it enables attackers to inject malicious code into a website, potentially allowing them to steal user data, take control of user sessions, or perform other malicious actions, which can compromise the security and trust of the website and its users.

Steps to mitigate:

  • Validate and sanitize user-inputted campaign names
  • Implement proper output encoding to prevent XSS attacks
  • Regularly update and patch software to prevent similar vulnerabilities
  • Use a Web Application Firewall (WAF) to detect and prevent XSS attacks
  • Limit user privileges to prevent attackers from storing malicious code.
CVE-2025-10571 9.6
Published: 2025-11-20T19:16:11.527

What it does:

This vulnerability allows unauthorized access to ABB Ability Edgenius by bypassing the normal authentication process through an alternate path or channel, affecting versions 3.2.0.0 and 3.2.1.1.

Why it's a problem:

This vulnerability is a significant problem because it enables attackers to gain unauthorized access to the system without being detected, potentially leading to data theft, system compromise, or other malicious activities, especially given its high severity score of 9.6.

Steps to mitigate:

  • Update ABB Ability Edgenius to the latest version
  • [apply security patches provided by ABB]
  • [implement additional authentication measures such as multi-factor authentication]
  • [monitor system logs for suspicious activity]
  • [restrict access to the system to only necessary personnel]
CVE-2025-64524 3.3
Published: 2025-11-20T18:15:51.250

What it does:

The CVE-2025-64524 vulnerability is a heap-buffer-overflow issue in the rastertopclx filter of the cups-filters software, which can cause the program to crash when processing malicious input data, potentially leading to arbitrary code execution.

Why it's a problem:

This vulnerability is a problem because it can be exploited by attackers to trigger memory corruption, potentially allowing them to execute arbitrary code and gain unauthorized access to a system, which can lead to data theft, system compromise, or other malicious activities.

Steps to mitigate:

  • Update cups-filters to a version later than 2.0.1
  • [Apply the patch from commit 956283c]
  • Avoid using the rastertopclx filter with untrusted input data
  • Regularly monitor system logs for signs of exploitation.
CVE-2025-63889 0
Published: 2025-11-20T18:15:51.110

What it does:

The CVE-2025-63889 vulnerability allows attackers to read arbitrary files on a server by manipulating file paths in template values, specifically targeting the fetch function in ThinkPHP's Template.php file.

Why it's a problem:

This vulnerability is a problem because it enables unauthorized access to sensitive files on the server, potentially leading to data breaches, leakage of confidential information, or further exploitation of the system.

Steps to mitigate:

  • Update ThinkPHP to a version later than 5.0.24
  • [Validate and sanitize all user-input data, especially template values]
  • [Implement proper access controls and file system permissions to restrict access to sensitive files]
  • [Monitor server logs for suspicious activity and signs of exploitation]
CVE-2025-63888 0
Published: 2025-11-20T18:15:50.977

What it does:

The CVE-2025-63888 vulnerability allows an attacker to execute remote code on a server by exploiting a flaw in the read function of the ThinkPHP 5.0.24 library, specifically in the File.php file.

Why it's a problem:

This vulnerability is a problem because it enables attackers to run malicious code on the server, potentially leading to unauthorized access, data breaches, and system compromise, which can have severe consequences for the security and integrity of the affected system.

Steps to mitigate:

  • Update ThinkPHP to a version later than 5.0.24
  • [Patch the vulnerable File.php file]
  • Implement a web application firewall (WAF) to detect and block malicious requests
  • Restrict access to the affected server and monitor for suspicious activity
  • Apply general security best practices, such as input validation and secure coding guidelines.
CVE-2025-64428 0
Published: 2025-11-20T17:15:53.197

What it does:

This vulnerability allows attackers to perform JNDI (Java Naming and Directory Interface) injection attacks on Dataease, an open source data visualization analysis tool, by exploiting the iiop, corbaname, and iiopname schemes, even after a blacklist was added in version 2.10.14.

Why it's a problem:

This vulnerability is a problem because it enables attackers to potentially execute malicious code, access sensitive data, or take control of the system, compromising the security and integrity of the Dataease application and its associated data.

Steps to mitigate:

  • Update Dataease to version 2.10.17 or later
  • Avoid using versions prior to 2.10.17
  • Implement additional security measures to detect and prevent JNDI injection attacks, such as input validation and secure configuration of the JNDI interface.
CVE-2025-64185 0
Published: 2025-11-20T17:15:53.017

What it does:

The Open OnDemand HPC portal creates world-writable locations in the GEM_PATH in versions prior to 4.0.8 and 3.1.16, allowing unauthorized access and modifications.

Why it's a problem:

This vulnerability is a problem because it enables malicious users to write and execute arbitrary code, potentially leading to data breaches, system compromises, and other security threats.

Steps to mitigate:

  • Update Open OnDemand to version 4.0.8 or 3.1.16 or later
  • Verify that the GEM_PATH is not world-writable
  • Monitor system logs for suspicious activity related to the GEM_PATH
  • Limit access to the GEM_PATH to authorized users only
CVE-2025-64027 0
Published: 2025-11-20T17:15:52.873

What it does:

The CVE-2025-64027 vulnerability allows an attacker to inject arbitrary HTML or JavaScript code into the Snipe-IT application when an invalid CSV file is uploaded, causing the code to execute in the browser of any authenticated admin who views the import page.

Why it's a problem:

This vulnerability is a problem because it enables an attacker to execute malicious code on the admin's browser, potentially allowing them to steal sensitive information, perform unauthorized actions, or take control of the admin's session.

Steps to mitigate:

  • Update Snipe-IT to a version later than v8.3.4 (build 20218)
  • Implement input validation and sanitization for CSV imports
  • Restrict access to the import page to authorized personnel only
  • Monitor the application for suspicious activity and update security protocols accordingly.
CVE-2025-63848 0
Published: 2025-11-20T17:15:52.733

What it does:

This vulnerability allows attackers to execute arbitrary code on a website by storing malicious code in a SWISH Prolog web IDE notebook, which can then be executed when the notebook is accessed.

Why it's a problem:

This vulnerability is a problem because it enables attackers to inject malicious code into a website, potentially leading to unauthorized access, data theft, or other malicious activities, compromising the security and integrity of the website and its users.

Steps to mitigate:

  • Update SWISH Prolog to a version later than 2.2.0
  • Validate and sanitize user input in web IDE notebooks
  • Implement a Web Application Firewall (WAF) to detect and prevent XSS attacks
  • Regularly monitor website activity for suspicious behavior
  • Restrict access to web IDE notebooks to authorized users only
CVE-2025-62724 4.3
Published: 2025-11-20T17:15:51.333

What it does:

This vulnerability allows users to exploit a "Time of Check to Time of Use" (TOCTOU) attack when downloading zip files, potentially accessing files outside of the allowed list in Open OnDemand, an open-source HPC portal.

Why it's a problem:

This vulnerability is a problem because it could allow unauthorized access to sensitive files, even though they are still protected by UNIX permissions, which could lead to data breaches or other security issues, particularly in sites that rely on file browser allowlists.

Steps to mitigate:

  • Update Open OnDemand to version 4.0.8 or 3.1.16
  • [Verify that UNIX permissions are properly set to restrict access to sensitive files]
  • Monitor file access logs for suspicious activity
  • [Review and update allowlists to ensure they are current and restrictive].
CVE-2025-62709 6.8
Published: 2025-11-20T17:15:51.087

What it does:

The CVE-2025-62709 vulnerability in ClipBucket v5 allows an attacker to manipulate the server URL by supplying a fake Host header, which can be used to generate password-reset links with the attacker's domain, potentially leading to account takeover.

Why it's a problem:

This vulnerability is a problem because it enables attackers to trick victims into revealing their activation codes, allowing the attackers to reset the victims' passwords and gain unauthorized access to their accounts, compromising the security and privacy of the users.

Steps to mitigate:

  • Update ClipBucket to version 5.5.2#162 or later
  • [Verify that the base_url configuration is set to prevent dynamic building of the server URL]
  • [Use a web application firewall (WAF) to filter and validate incoming HTTP Host headers]
  • [Educate users to be cautious when following password-reset links and to verify the authenticity of the link before entering their activation code]
CVE-2025-52410 0
Published: 2025-11-20T17:15:50.760

What it does:

The Institute-of-Current-Students v1.0 has a vulnerability that allows an attacker to inject malicious SQL code into the database through the `myds` parameter in the `mydetailsstudent.php` endpoint, potentially giving them access to sensitive information.

Why it's a problem:

This vulnerability is a problem because it could allow unauthorized users to extract or modify sensitive data, disrupt the application's functionality, or even gain control of the entire system, leading to serious security breaches and data losses.

Steps to mitigate:

  • Validate and sanitize all user input
  • [use prepared statements with parameterized queries to prevent SQL injection]
  • [implement a Web Application Firewall (WAF) to detect and block suspicious traffic]
  • [update the Institute-of-Current-Students application to the latest version with patched vulnerabilities]
  • [conduct regular security audits and penetration testing to identify and address potential vulnerabilities].
CVE-2025-13437 0
Published: 2025-11-20T17:15:49.453

What it does:

The CVE-2025-13437 vulnerability occurs when the zx CLI is invoked with a specific option, causing it to create a symlink to an external directory. Due to a logic error, the function returns the wrong path, leading to the deletion of the target directory instead of the intended symlink.

Why it's a problem:

This vulnerability is a problem because it can result in the unintentional deletion of external directories, specifically the node_modules directory, which can cause significant disruptions to projects and systems that rely on those directories.

Steps to mitigate:

  • Avoid using the --prefer-local option with zx until a patch is available
  • Verify the integrity of external directories before invoking zx
  • Use a temporary or isolated environment to test zx invocations
  • Regularly back up important directories to prevent data loss.
CVE-2025-12121 0
Published: 2025-11-20T17:15:48.787

What it does:

The CVE-2025-12121 vulnerability in Lite XL versions 2.1.8 and prior allows an attacker to execute arbitrary commands on a system by exploiting the system.exec function, which constructs shell commands without proper sanitization, potentially through project directory launching, drag-and-drop file handling, or the "open in system" command.

Why it's a problem:

This vulnerability is a problem because it enables an attacker to run arbitrary commands with the same privileges as the Lite XL process, potentially leading to unauthorized access, data theft, or system compromise if an attacker can influence the input to the system.exec function.

Steps to mitigate:

  • Update Lite XL to a version later than 2.1.8
  • [Verify input validation and sanitization for any user-provided data]
  • [Implement strict access controls and privilege separation for the Lite XL process
  • [Monitor system logs for suspicious activity related to the Lite XL process]
CVE-2025-12120 0
Published: 2025-11-20T17:15:48.640

What it does:

The Lite XL software automatically runs a file called .lite_project.lua when opening a project directory, without asking for user confirmation, allowing it to execute Lua code embedded in the file.

Why it's a problem:

This behavior is a problem because it enables the potential execution of malicious Lua code if a user opens a tampered project directory, which could lead to unauthorized actions being performed with the same privileges as the Lite XL application.

Steps to mitigate:

  • Update Lite XL to a version later than 2.1.8
  • Avoid opening project directories from untrusted sources
  • Manually review the contents of .lite_project.lua files before opening project directories
  • Use antivirus software to scan project directories for malicious code.
CVE-2025-62875 0
Published: 2025-11-20T16:16:00.540

What it does:

The CVE-2025-62875 vulnerability allows local users to crash the OpenSMTPD service due to an improper check for unusual or exceptional conditions.

Why it's a problem:

This vulnerability is a problem because it can be exploited by local users to intentionally disrupt the email service, causing denial-of-service and potentially leading to loss of important emails or system downtime.

Steps to mitigate:

  • Update openSUSE Tumbleweed to version 7.8.0p0-1.1 or later
  • Monitor system logs for unusual OpenSMTPD activity
  • Restrict local user access to the OpenSMTPD service to prevent potential exploitation.
CVE-2025-62731 0
Published: 2025-11-20T16:16:00.363

What it does:

The CVE-2025-62731 vulnerability allows an attacker to inject arbitrary HTML and JavaScript code into the SOPlanning website through the /feries endpoint, which is used to manage public holidays. This malicious code will be executed when multiple pages are opened.

Why it's a problem:

This vulnerability is a problem because it enables an attacker to perform Stored Cross-Site Scripting (XSS) attacks, potentially allowing them to steal user data, take control of user sessions, or perform other malicious actions. Although only administrators and users with special privileges can access this endpoint by default, it still poses a significant risk if an attacker gains access to these privileged accounts.

Steps to mitigate:

  • Update SOPlanning to version 1.55 or later
  • Restrict access to the /feries endpoint to only necessary personnel
  • Monitor user activity and website behavior for signs of malicious code execution.
CVE-2025-62730 0
Published: 2025-11-20T16:16:00.180

What it does:

The CVE-2025-62730 vulnerability in SOPlanning allows users with the "user_manage_team" role to modify permissions of other users, including assigning administrative permissions to themselves or others, effectively escalating their privileges to admin level.

Why it's a problem:

This vulnerability is a problem because it enables malicious authenticated attackers with the "user_manage_team" role to gain unauthorized administrative access, potentially leading to unauthorized data modifications, breaches, or other malicious activities.

Steps to mitigate:

  • Update SOPlanning to version 1.55 or later
  • Restrict the "user_manage_team" role to trusted users only
  • Monitor user activity for suspicious permission changes and administrative access attempts.
CVE-2025-62729 0
Published: 2025-11-20T16:15:59.997

What it does:

The CVE-2025-62729 vulnerability allows an attacker with an account to inject arbitrary HTML and JavaScript code into the SOPlanning website through the /status endpoint, which can then be executed when multiple pages are opened.

Why it's a problem:

This vulnerability is a problem because it enables malicious users to embed malicious code into the website, potentially leading to unauthorized actions, data theft, or other harmful activities when other users access the affected pages.

Steps to mitigate:

  • Update SOPlanning to version 1.55 or later
  • Restrict access to the /status endpoint to trusted users only
  • Monitor website activity for suspicious code injections and executions.
CVE-2025-62297 0
Published: 2025-11-20T16:15:59.753

What it does:

The CVE-2025-62297 vulnerability allows an attacker with medium privileges to inject arbitrary HTML and JavaScript code into the SOPlanning website through the /projets endpoint, which will be executed when the edited page is opened.

Why it's a problem:

This vulnerability is a problem because it enables malicious attackers to execute arbitrary code on the website, potentially leading to unauthorized access, data theft, or other malicious activities, by exploiting the Stored XSS vulnerability.

Steps to mitigate:

  • Update SOPlanning to version 1.55 or later
  • Restrict access to the /projets endpoint to trusted users
  • Implement additional security measures, such as input validation and output encoding, to prevent XSS attacks.
CVE-2025-62296 0
Published: 2025-11-20T16:15:59.583

What it does:

The CVE-2025-62296 vulnerability allows an attacker with medium privileges to inject arbitrary HTML and JavaScript code into the SOPlanning website through the /taches endpoint, which is then rendered and executed when the editor is opened.

Why it's a problem:

This vulnerability is a problem because it enables malicious attackers to execute arbitrary code on the website, potentially leading to unauthorized access, data theft, or other malicious activities, by exploiting the trust that users have in the website.

Steps to mitigate:

  • Update SOPlanning to version 1.55 or later
  • Restrict access to the /taches endpoint to trusted users only
  • Monitor website activity for suspicious code injections and executions.
CVE-2025-62295 0
Published: 2025-11-20T16:15:59.410

What it does:

The CVE-2025-62295 vulnerability allows an attacker to inject arbitrary HTML and JavaScript code into the SOPlanning website through the /groupe_form endpoint, which is then rendered and executed when the editor is opened.

Why it's a problem:

This vulnerability is a problem because it enables malicious attackers with medium privileges to perform Stored Cross-Site Scripting (XSS) attacks, potentially leading to unauthorized access, data theft, or other malicious activities on the website.

Steps to mitigate:

  • Update SOPlanning to version 1.55 or later
  • Restrict access to the /groupe_form endpoint to trusted users
  • Implement additional security measures, such as input validation and output encoding, to prevent malicious code injection.
CVE-2025-62294 0
Published: 2025-11-20T16:15:59.243

What it does:

The SOPlanning vulnerability allows an attacker to predict and brute-force password recovery tokens, enabling them to take over any account.

Why it's a problem:

This vulnerability is a problem because it allows malicious attackers to gain unauthorized access to user accounts, potentially leading to data theft, tampering, or other malicious activities, all due to the weak password recovery token generation mechanism.

Steps to mitigate:

  • Update SOPlanning to version 1.55 or later
  • Use alternative authentication methods until the update is applied
  • Monitor account activity for suspicious behavior
  • Consider implementing additional security measures, such as two-factor authentication, to prevent unauthorized access.
CVE-2025-62293 0
Published: 2025-11-20T16:15:59.060

What it does:

The CVE-2025-62293 vulnerability in SOPlanning allows an authenticated attacker to add, edit, and delete any project status due to a lack of permission checks in the Project Status functionality, specifically in the /status endpoint.

Why it's a problem:

This vulnerability is a problem because it enables unauthorized modifications to project statuses, which can lead to data inconsistency, disruption of project workflows, and potential security breaches by allowing attackers to manipulate project information.

Steps to mitigate:

  • Update SOPlanning to version 1.55 or later
  • [Verify that all users have the necessary permissions and access controls in place]
  • Regularly monitor project status changes for suspicious activity
  • Limit user access to the /status endpoint to only those who require it.
CVE-2025-60738 0
Published: 2025-11-20T16:15:58.927

What it does:

The CVE-2025-60738 vulnerability allows a remote attacker to execute arbitrary code on the Ilevia EVE X1 Server Firmware due to a lack of secure filtering on IP parameters in the ping.php component.

Why it's a problem:

This vulnerability is a problem because it enables attackers to remotely take control of the server, potentially leading to unauthorized access, data theft, or disruption of service, which can have serious consequences for the security and integrity of the system.

Steps to mitigate:

  • Update Ilevia EVE X1 Server Firmware to a version later than v4.7.18.0.eden
  • Update Logic Version to a version later than v6.00 - 2025_07_21
  • Implement network segmentation to limit access to the server
  • Use a web application firewall (WAF) to filter incoming traffic
  • Monitor server logs for suspicious activity
CVE-2025-60737 0
Published: 2025-11-20T16:15:58.800

What it does:

This vulnerability allows a remote attacker to execute arbitrary code on the Ilevia EVE X1 Server by exploiting a Cross Site Scripting (XSS) flaw in the /index.php component, affecting firmware versions 4.7.18.0.eden and earlier, with Logic Version 6.00 or earlier.

Why it's a problem:

This vulnerability is a problem because it enables attackers to inject malicious code into the server, potentially leading to unauthorized access, data theft, or disruption of service, which can have serious consequences for the security and integrity of the system.

Steps to mitigate:

  • Update firmware to version 4.7.18.0.eden or later
  • [Apply Logic Version 6.00 or later patch]
  • [Implement web application firewall (WAF) rules to detect and prevent XSS attacks]
  • [Limit remote access to the server
  • [Monitor system logs for suspicious activity]
CVE-2025-36161 5.9
Published: 2025-11-20T16:15:58.330

What it does:

The IBM Concert vulnerability (CVE-2025-36161) allows a remote attacker to obtain sensitive information by exploiting the lack of HTTP Strict-Transport-Security (HSTS) enforcement, making it possible to intercept data using man-in-the-middle techniques.

Why it's a problem:

This vulnerability is a problem because it enables attackers to access sensitive information, potentially leading to data breaches, eavesdropping, and other malicious activities, which can compromise the security and confidentiality of the affected system.

Steps to mitigate:

  • Enable HTTP Strict-Transport-Security (HSTS) in IBM Concert
  • [Upgrade to a version of IBM Concert that has HSTS enabled by default]
  • Implement additional security measures, such as SSL/TLS encryption and secure communication protocols, to protect against man-in-the-middle attacks.
CVE-2025-34320 0
Published: 2025-11-20T16:15:57.583

What it does:

The BASIS BBj vulnerability allows an attacker to access arbitrary system files on the server by exploiting a weakness in the Jetty-served web endpoint, which fails to properly validate input path segments, enabling unauthenticated directory traversal.

Why it's a problem:

This vulnerability is a problem because it can lead to the exposure of sensitive information, including account credentials used for BBj Enterprise Manager, which can be used to gain administrative access and execute system commands, potentially allowing access to other confidential files on the host.

Steps to mitigate:

  • Update BASIS BBj to version 25.00 or later
  • [Limit access to the BBj service account to minimize potential damage]
  • [Monitor system files and configuration artifacts for suspicious activity]
  • [Change administrative passwords and consider rotating credentials as a precautionary measure]
CVE-2025-13425 0
Published: 2025-11-20T16:15:56.793

What it does:

This vulnerability causes a bug in the filesystem traversal fallback path, leading to an application crash (denial of service) when it encounters an empty directory, due to an "index out of range" error.

Why it's a problem:

This vulnerability is a problem because it can be exploited to deliberately crash an application, resulting in a denial of service, which means that users cannot access the application or its services, potentially causing disruption and loss of productivity.

Steps to mitigate:

  • Update the OSV-SCALIBR application to the latest version
  • [patch the fs/diriterate/diriterate.go file to handle empty directories correctly]
  • [implement error handling to prevent the application from crashing when encountering empty directories]
  • monitor application logs for signs of denial of service attacks.
CVE-2024-31405 0
Published: 2025-11-20T16:15:55.880

What it does:

This CVE (CVE-2024-31405) has been voluntarily withdrawn and does not pose a known security risk.

Why it's a problem:

There is no identified problem or vulnerability associated with this CVE, as it was withdrawn.

Steps to mitigate:

  • No action required
  • Monitor future CVE publications for relevant security updates
  • Continue with standard cybersecurity best practices
CVE-2025-65226 0
Published: 2025-11-20T15:17:40.577

What it does:

The CVE-2025-65226 vulnerability allows an attacker to overflow a buffer by manipulating the deviceId parameter in the /goform/saveParentControlInfo endpoint of the Tenda AC21 router, version V16.03.08.16.

Why it's a problem:

This vulnerability is a problem because it could potentially allow an attacker to execute arbitrary code on the router, leading to unauthorized access, data theft, or disruption of network services.

Steps to mitigate:

  • Update the Tenda AC21 router to a version later than V16.03.08.16
  • [Apply patches or fixes provided by the manufacturer]
  • Change the deviceId parameter to a validated and sanitized input to prevent buffer overflow
  • [Implement network segmentation and isolation to limit the attack surface]
  • Monitor network traffic for suspicious activity and adjust firewall rules accordingly.
CVE-2025-65223 0
Published: 2025-11-20T15:17:40.440

What it does:

The CVE-2025-65223 vulnerability allows an attacker to overflow a buffer by manipulating the "urls" parameter in the "/goform/saveParentControlInfo" endpoint of the Tenda AC21 router, version V16.03.08.16, potentially leading to arbitrary code execution.

Why it's a problem:

This vulnerability is a problem because it could enable an attacker to gain control of the router, allowing them to intercept sensitive information, disrupt network traffic, or use the router as a launching point for further attacks on the network.

Steps to mitigate:

  • Update the Tenda AC21 router to the latest firmware version
  • [Verify that the router's parental control feature is not exposed to the internet]
  • [Implement network segmentation to limit the spread of potential attacks]
  • [Use a firewall to restrict access to the router's administrative interface]
  • [Monitor network traffic for suspicious activity]
CVE-2025-65222 0
Published: 2025-11-20T15:17:40.297

What it does:

The CVE-2025-65222 vulnerability allows an attacker to overflow a buffer by manipulating the rebootTime parameter in the /goform/SetSysAutoRebbotCfg endpoint of Tenda AC21 devices running firmware version V16.03.08.16, potentially leading to arbitrary code execution.

Why it's a problem:

This vulnerability is a problem because it could be exploited by an attacker to gain control over the affected device, leading to unauthorized access, data theft, or disruption of network services, which can compromise the security and integrity of the network.

Steps to mitigate:

  • Update Tenda AC21 firmware to a version later than V16.03.08.16]
  • [Limit access to the /goform/SetSysAutoRebbotCfg endpoint]
  • [Implement network segmentation to isolate vulnerable devices]
  • [Monitor network traffic for suspicious activity related to the vulnerability.
CVE-2025-65221 0
Published: 2025-11-20T15:17:40.160

What it does:

The CVE-2025-65221 vulnerability allows an attacker to overflow a buffer by manipulating the "list" parameter in the /goform/setPptpUserList endpoint of Tenda AC21 devices running firmware version V16.03.08.16, potentially enabling them to execute arbitrary code.

Why it's a problem:

This vulnerability is a problem because it could allow unauthorized access and control of the affected device, leading to potential data theft, disruption of service, or other malicious activities, compromising the security and integrity of the network.

Steps to mitigate:

  • Update Tenda AC21 firmware to a version later than V16.03.08.16
  • [Apply patches or fixes provided by the manufacturer]
  • [Limit access to the /goform/setPptpUserList endpoint through firewall rules or access controls]
  • [Monitor network traffic for suspicious activity related to the vulnerability]
CVE-2025-65220 0
Published: 2025-11-20T15:17:40.010

What it does:

The CVE-2025-65220 vulnerability allows an attacker to exploit a buffer overflow in the Tenda AC21 router's SetVirtualServerCfg function, specifically through the 'list' parameter, potentially enabling them to execute malicious code or crash the system.

Why it's a problem:

This vulnerability is a problem because it could allow unauthorized access to the router, giving attackers the ability to modify settings, intercept sensitive information, or disrupt network services, which could lead to significant security breaches and data loss.

Steps to mitigate:

  • Update the Tenda AC21 firmware to a version later than V16.03.08.16
  • [Limit access to the router's administrative interface]
  • Implement network segmentation to reduce the attack surface
  • Regularly monitor network traffic for suspicious activity
  • Change default passwords and use strong authentication methods.
CVE-2025-64984 6.1
Published: 2025-11-20T15:17:39.420

What it does:

This vulnerability allows an attacker to carry out a reflected Cross-Site Scripting (XSS) attack using phishing techniques on certain Kaspersky products, including Kaspersky Endpoint Security for Linux, Kaspersky Industrial CyberSecurity for Linux Nodes, and Kaspersky Endpoint Security for Mac, with outdated anti-virus databases.

Why it's a problem:

This vulnerability is a problem because it enables attackers to trick users into performing unintended actions, potentially leading to unauthorized access, data theft, or malware installation, which can compromise the security of the affected systems and put sensitive information at risk.

Steps to mitigate:

  • Update anti-virus databases to version 18.11.2025 or later
  • Ensure Kaspersky Endpoint Security for Mac is updated to a version with anti-virus databases from 18.11.2025 or later
  • Avoid clicking on suspicious links or providing sensitive information in response to phishing emails
  • Regularly check for updates to Kaspersky products and install them promptly.
CVE-2025-62346 6.8
Published: 2025-11-20T15:17:38.673

What it does:

The CVE-2025-62346 vulnerability allows an attacker to trick a user's web browser into performing an unwanted action on a trusted website, specifically on one endpoint of the HCL Glovius Cloud, without the user's knowledge or consent.

Why it's a problem:

This vulnerability is a problem because it enables attackers to exploit the trust between a user and a website, potentially leading to unauthorized actions, data breaches, or other malicious activities, all while appearing to come from the legitimate user.

Steps to mitigate:

  • Implement proper CSRF tokens and validation on all endpoints
  • Use double-submit cookie patterns or similar techniques to prevent CSRF attacks
  • Keep HCL Glovius Cloud and all related components up to date with the latest security patches
  • Use web application firewalls (WAFs) to detect and prevent CSRF attacks
  • Educate users about the risks of CSRF and how to identify suspicious activity.
CVE-2025-60799 0
Published: 2025-11-20T15:17:38.533

What it does:

The CVE-2025-60799 vulnerability in phpPgAdmin 7.13.0 and earlier allows attackers to manipulate session variables by sending user-controlled parameters, potentially storing arbitrary SQL queries in the session, which can lead to unauthorized access or malicious actions.

Why it's a problem:

This vulnerability is a problem because it enables attackers to exploit the application's lack of proper validation and access control checks, potentially resulting in session poisoning, stored cross-site scripting, or unauthorized access to sensitive session data, compromising the security and integrity of the application and its users.

Steps to mitigate:

  • Update phpPgAdmin to a version later than 7.13.0
  • Implement proper input validation and access control checks for user-controlled parameters
  • Use a web application firewall (WAF) to detect and prevent malicious requests
  • Regularly monitor session data for suspicious activity
  • Limit access to sensitive session data to authorized personnel only
CVE-2025-60798 0
Published: 2025-11-20T15:17:38.393

What it does:

The CVE-2025-60798 vulnerability allows an attacker to inject malicious SQL code into the phpPgAdmin application by manipulating user-controlled input, potentially enabling them to execute arbitrary SQL commands and access sensitive database information.

Why it's a problem:

This vulnerability is a problem because it can lead to a complete database compromise, giving an attacker unauthorized access to sensitive data, allowing them to modify or delete data, and potentially disrupting the entire system.

Steps to mitigate:

  • Update phpPgAdmin to a version later than 7.13.0
  • Validate and sanitize all user-controlled input to prevent SQL injection
  • Implement a Web Application Firewall (WAF) to detect and prevent SQL injection attacks
  • Limit database privileges to the minimum required for the application to function
  • Monitor database activity for suspicious queries and behavior.
CVE-2025-60797 0
Published: 2025-11-20T15:17:38.250

What it does:

The CVE-2025-60797 vulnerability allows an attacker to inject malicious SQL code into the phpPgAdmin application through the $_REQUEST['query'] parameter, enabling them to execute arbitrary SQL commands.

Why it's a problem:

This vulnerability is a problem because it can lead to a complete database compromise, allowing attackers to steal sensitive data, modify database structures, or escalate their privileges, potentially gaining full control over the database.

Steps to mitigate:

  • Update phpPgAdmin to a version later than 7.13.0
  • Validate and sanitize all user-supplied input to prevent SQL injection
  • Implement parameterized queries or prepared statements to separate code from user input
  • Limit database privileges to the minimum required for the application
  • Monitor database activity for suspicious queries and behavior.
CVE-2025-60796 0
Published: 2025-11-20T15:17:38.100

What it does:

The CVE-2025-60796 vulnerability allows an attacker to inject malicious JavaScript code into the phpPgAdmin application, which is then executed in the user's browser, due to improper encoding or sanitization of user-supplied input.

Why it's a problem:

This vulnerability is a problem because it enables attackers to execute arbitrary JavaScript code in victims' browsers, potentially leading to session hijacking, credential theft, or other malicious actions, compromising the security and privacy of users.

Steps to mitigate:

  • Update phpPgAdmin to a version later than 7.13.0
  • Validate and sanitize all user-supplied input
  • Implement a Web Application Firewall (WAF) to detect and prevent XSS attacks
  • Use a browser extension that provides XSS protection
  • Limit access to phpPgAdmin to trusted users and networks only
CVE-2025-60794 0
Published: 2025-11-20T15:17:37.937

What it does:

The CVE-2025-60794 vulnerability allows session tokens and passwords to be stored in memory without being properly cleared, making them accessible through memory dumps, debugging tools, or other memory access techniques.

Why it's a problem:

This vulnerability is a problem because it creates an opportunity for attackers to extract sensitive data, such as session tokens and passwords, which could lead to session hijacking and unauthorized access to sensitive information.

Steps to mitigate:

  • Update couch-auth to a version that properly clears sensitive data from memory
  • Use a secure method to store and manage session tokens and passwords
  • Implement memory protection mechanisms, such as memory encryption or secure memory allocation, to prevent unauthorized access to sensitive data
  • Monitor system logs and memory dumps for signs of potential data extraction attempts.
CVE-2025-5092 6.4
Published: 2025-11-20T15:17:37.650

What it does:

This vulnerability allows attackers with Contributor-level access or higher to inject malicious scripts into WordPress pages using a flawed library called lightGallery, which is bundled with various plugins and themes. This happens because the library doesn't properly clean and secure user-inputted data.

Why it's a problem:

This is a problem because it enables attackers to execute arbitrary web scripts whenever a user visits an infected page, potentially leading to unauthorized actions, data theft, or further malicious activities on the affected WordPress site.

Steps to mitigate:

  • Update affected plugins and themes to versions that use lightGallery 2.8.4 or later
  • [Verify that all user input is properly sanitized and escaped in your WordPress environment]
  • Restrict Contributor-level access and above to trusted users only
  • Regularly monitor your WordPress site for suspicious activity and update all components to ensure you have the latest security patches.
CVE-2025-41076 0
Published: 2025-11-20T15:17:29.427

What it does:

The CVE-2025-41076 vulnerability allows an external user to send a malformed session cookie to the LimeSurvey system, causing a 500 error and exposing internal backend information, including the framework, database engine, table names, and primary keys.

Why it's a problem:

This vulnerability is a problem because it provides an attacker with valuable information about the internal architecture of the application, making it easier for them to plan and execute further attacks, potentially leading to unauthorized access or data breaches.

Steps to mitigate:

  • Update LimeSurvey to a version later than 6.13.0
  • [validate and sanitize user-input session cookies]
  • [implement error handling to display generic error messages instead of sensitive backend information]
  • [restrict access to the survey system to trusted users and networks
  • [monitor system logs for suspicious activity and malformed session cookies].
CVE-2025-41075 0
Published: 2025-11-20T15:17:29.263

What it does:

The CVE-2025-41075 vulnerability in LimeSurvey 6.13.0 causes infinite HTTP redirects when the /optin endpoint is accessed directly, leading to a potential Denial of Service (DoS) attack by exhausting server or client resources.

Why it's a problem:

This vulnerability is a problem because it can cause service degradation or browser instability due to the system's inability to break the redirect loop, ultimately disrupting the normal functioning of the system and potentially causing resource exhaustion.

Steps to mitigate:

  • Update LimeSurvey to a version patched for this vulnerability
  • Implement rate limiting on HTTP redirects to prevent excessive resource usage
  • Configure the server to detect and break infinite redirect loops
  • Monitor system resources for signs of exhaustion and take proactive measures to prevent DoS attacks.
CVE-2025-41074 0
Published: 2025-11-20T15:17:29.067

What it does:

The CVE-2025-41074 vulnerability in LimeSurvey 6.13.0 causes infinite HTTP redirects when the /optout endpoint is accessed directly, leading to a potential Denial of Service (DoS) attack by exhausting server or client resources.

Why it's a problem:

This vulnerability is a problem because it can cause service degradation or browser instability due to the system's inability to break the redirect loop, potentially disrupting normal operations and impacting user experience.

Steps to mitigate:

  • Update LimeSurvey to a version that fixes the vulnerability
  • [Apply a web application firewall (WAF) rule to detect and prevent infinite redirect loops]
  • [Implement rate limiting on the /optout endpoint to prevent abuse
  • [Monitor server and client resources for signs of exhaustion and adjust configurations as needed]
CVE-2025-40605 0
Published: 2025-11-20T15:17:28.917

What it does:

This vulnerability allows an attacker to manipulate file system paths on an Email Security appliance by using special sequences of characters (like "../") to access files and directories that are normally restricted.

Why it's a problem:

This is a problem because it could allow unauthorized access to sensitive files and directories, potentially leading to data theft, system compromise, or other malicious activities.

Steps to mitigate:

  • Update the Email Security appliance to the latest version
  • [Apply patches or fixes provided by the vendor]
  • Restrict access to the appliance to only trusted users and networks
  • Monitor system logs for suspicious activity
  • Implement additional security measures such as intrusion detection and prevention systems.
CVE-2025-40604 0
Published: 2025-11-20T15:17:28.750

What it does:

The SonicWall Email Security appliance has a vulnerability that allows attackers to download and load code without verifying its integrity, specifically by modifying root filesystem images without checking their signatures, which can lead to arbitrary code execution.

Why it's a problem:

This vulnerability is a problem because it enables attackers with access to the appliance's VMDK or datastore to modify system files, potentially allowing them to gain persistent and unauthorized control over the system, which can lead to data breaches, malware infections, and other security threats.

Steps to mitigate:

  • Update SonicWall Email Security appliance to the latest version
  • [Apply security patches to the appliance]
  • [Restrict access to VMDK and datastore to authorized personnel only]
  • [Monitor system logs for suspicious activity]
  • [Implement additional security measures such as intrusion detection and prevention systems]
CVE-2025-40601 0
Published: 2025-11-20T15:17:28.570

What it does:

This vulnerability allows a remote attacker to overflow a buffer in the SonicOS SSLVPN service, causing a Denial of Service (DoS) that can crash an impacted firewall.

Why it's a problem:

This vulnerability is a problem because it enables an unauthenticated attacker to disrupt the normal functioning of a firewall, potentially leaving a network vulnerable to further attacks and causing downtime.

Steps to mitigate:

  • Update SonicOS to the latest version
  • "Apply the patch provided by the vendor
  • Contact the vendor for guidance on temporary workaround measures
  • Implement network segmentation to limit the attack surface
  • Monitor network traffic for signs of exploitation.
CVE-2025-13469 2.4
Published: 2025-11-20T15:17:26.853

What it does:

This vulnerability allows an attacker to manipulate the "manualInstructions" argument in the Payment Instructions Setting Handler of the Public Knowledge Project's Open Journal Systems (OJS) and Open Monograph Press (OMP), leading to a cross-site scripting (XSS) attack, which can be initiated remotely.

Why it's a problem:

This vulnerability is a problem because it enables attackers to inject malicious code into the system, potentially allowing them to steal user data, take control of user sessions, or perform other malicious actions, compromising the security and integrity of the affected systems.

Steps to mitigate:

  • Upgrade to a patched version of OJS and OMP
  • [Verify that the Payment Instructions Setting Handler is properly configured and validated]
  • Implement additional security measures such as input validation and output encoding to prevent XSS attacks
  • Monitor system logs for suspicious activity and signs of exploitation.
CVE-2025-13468 5.4
Published: 2025-11-20T15:17:26.627

What it does:

The CVE-2025-13468 vulnerability allows an attacker to manipulate the ID argument in the delete functions of the Alumni Management System, potentially bypassing authorization and allowing unauthorized deletion of forum posts, careers, comments, galleries, and events.

Why it's a problem:

This vulnerability is a problem because it enables remote attackers to modify or delete sensitive data without proper authorization, which can lead to data loss, disruption of services, and potential security breaches.

Steps to mitigate:

  • Update to a patched version of the Alumni Management System
  • [Apply proper input validation and authorization checks to the delete functions in admin_class.php
  • [Implement remote access controls and monitoring to detect and prevent potential attacks
  • [Notify administrators and users of the potential vulnerability and provide guidance on secure usage].
CVE-2025-13451 7.3
Published: 2025-11-20T15:17:26.403

What it does:

This vulnerability allows an attacker to inject malicious SQL code into the Online Shop Project 1.0 database by manipulating the "Search" argument in the /action.php file, potentially leading to unauthorized data access or modification.

Why it's a problem:

This vulnerability is a problem because it enables remote attackers to exploit the database, potentially stealing sensitive information, modifying data, or disrupting the application's functionality, which can lead to significant security breaches and data losses.

Steps to mitigate:

  • Update the Online Shop Project to a patched version
  • [Implement input validation and sanitization for the "Search" argument in the /action.php file]
  • [Use prepared statements or parameterized queries to prevent SQL injection]
  • [Limit database privileges to the minimum required for the application
  • [Monitor the application for suspicious activity and keep backups of critical data].
CVE-2025-13450 3.5
Published: 2025-11-20T15:17:26.180

What it does:

The CVE-2025-13450 vulnerability allows an attacker to perform a cross-site scripting (XSS) attack by manipulating the "f_name" argument in the /shop/register.php file of the SourceCodester Online Shop Project 1.0, which can be initiated remotely.

Why it's a problem:

This vulnerability is a problem because it enables attackers to inject malicious code into the website, potentially allowing them to steal user data, take control of user sessions, or perform other malicious actions, which can compromise the security and trust of the online shop.

Steps to mitigate:

  • Update the SourceCodester Online Shop Project to a patched version
  • [Implement input validation and sanitization for the "f_name" field in the register.php file]
  • [Use a Web Application Firewall (WAF) to detect and prevent XSS attacks
  • [Keep software and plugins up-to-date to prevent exploitation of known vulnerabilities].
CVE-2025-13449 7.3
Published: 2025-11-20T15:17:25.953

What it does:

This vulnerability allows an attacker to inject malicious SQL code into the Online Shop Project 1.0's login system by manipulating the password field, potentially giving them unauthorized access to the database.

Why it's a problem:

This vulnerability is a problem because it could allow attackers to remotely access sensitive data, modify database records, or even take control of the entire system, compromising user accounts and confidential information.

Steps to mitigate:

  • Update the Online Shop Project to a patched version
  • [Implement input validation and sanitization on the password field]
  • [Use prepared statements to prevent SQL injection]
  • [Limit database privileges to the minimum required]
  • [Monitor the system for suspicious activity and update incident response plans]
CVE-2025-13446 8.8
Published: 2025-11-20T15:17:25.713

What it does:

This vulnerability allows an attacker to overflow a buffer on the stack by manipulating the timeZone/time argument in the /goform/SetSysTimeCfg file of the Tenda AC21 router, which can be done remotely.

Why it's a problem:

This vulnerability is a problem because it can be exploited by an attacker to potentially execute arbitrary code, gain unauthorized access, or cause the router to crash, compromising the security and stability of the network.

Steps to mitigate:

  • Update the Tenda AC21 firmware to the latest version
  • [patch the /goform/SetSysTimeCfg file to prevent buffer overflow]
  • change the router's configuration to limit remote access to the /goform/SetSysTimeCfg file
  • use a firewall to block unauthorized access to the router
  • monitor network traffic for suspicious activity.
CVE-2025-13445 8.8
Published: 2025-11-20T15:17:25.480

What it does:

The CVE-2025-13445 vulnerability is a stack-based buffer overflow flaw in the Tenda AC21 router, specifically in the /goform/SetIpMacBind file, which can be exploited by manipulating the argument list, allowing for remote execution of the attack.

Why it's a problem:

This vulnerability is a problem because it can be executed remotely, meaning an attacker can exploit it from anywhere, and the exploit has already been published, making it easily accessible to potential attackers, which could lead to unauthorized access, data theft, or other malicious activities.

Steps to mitigate:

  • Update the Tenda AC21 router to the latest firmware version
  • [Disable remote access to the router until a patch is available]
  • [Implement a firewall to block unauthorized access to the router]
  • Monitor network traffic for suspicious activity
  • Change default passwords and credentials to prevent exploitation.
CVE-2025-13443 5.4
Published: 2025-11-20T15:17:25.267

What it does:

This vulnerability allows an attacker to manipulate the "ids" argument in the delete function of the /member/readHistory/delete file in macrozheng mall versions up to 1.0.3, bypassing access controls and potentially deleting unauthorized data.

Why it's a problem:

This vulnerability is a problem because it enables remote exploitation, allowing attackers to access and manipulate sensitive data without proper authorization, which can lead to data loss, unauthorized modifications, and other security breaches.

Steps to mitigate:

  • Update macrozheng mall to a version later than 1.0.3>
  • Restrict access to the /member/readHistory/delete file to authorized users only>
  • Implement additional access controls and validation for the "ids" argument in the delete function
  • Monitor the system for suspicious activity and potential exploitation attempts.
CVE-2025-13442 7.3
Published: 2025-11-20T15:17:25.057

What it does:

This vulnerability allows an attacker to inject commands into the system of UTT 进取 750W devices with firmware up to 3.2.2-191225 by manipulating the "policyNames" argument in the /goform/formPdbUpConfig function, which can be done remotely.

Why it's a problem:

This vulnerability is a problem because it enables remote attackers to execute arbitrary commands on the device, potentially leading to unauthorized access, data theft, or disruption of service, and the fact that the exploit has been publicly disclosed increases the risk of attack.

Steps to mitigate:

  • Update firmware to a version later than 3.2.2-191225 if available
  • [Disallow remote access to the /goform/formPdbUpConfig function until a patch is available]
  • [Implement network segmentation to limit the spread of a potential attack]
  • [Monitor device logs for suspicious activity and sign of command injection attempts]
CVE-2025-13435 5.6
Published: 2025-11-20T15:17:24.840

What it does:

The CVE-2025-13435 vulnerability allows an attacker to manipulate the "filename" argument in the HttpClient Module of Dreampie Resty, leading to a path traversal attack, which can be performed remotely.

Why it's a problem:

This vulnerability is a problem because it enables an attacker to access and potentially modify sensitive files on the system by traversing the directory path, which could lead to data breaches, unauthorized access, or other malicious activities, and the fact that the exploit has been publicly disclosed makes it more likely to be used by attackers.

Steps to mitigate:

  • Update Dreampie Resty to a version later than 1.3.1.SNAPSHOT]
  • [Implement additional security measures to restrict remote access to the HttpClient Module]
  • [Monitor system logs for suspicious activity and signs of potential path traversal attacks]
  • [Consider implementing a web application firewall (WAF) to detect and prevent such attacks.