A flaw was found in ose-openshift-apiserver
Description
A flaw was found in ose-openshift-apiserver
AI Analyst Comment
Remediation
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Search and filter 24021 vulnerabilities with AI analyst insights
A flaw was found in ose-openshift-apiserver
A flaw was found in ose-openshift-apiserver
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The JAY Login & Register plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.4.01. This is due to incorrec...
The JAY Login & Register plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.4.01. This is due to incorrect authentication checking in the 'jay_login_register_process_switch_back' function with the 'jay_login_register_process_switch_back' cookie value. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the user id.
Description Summary:
The JAY Login & Register WordPress plugin contains an authentication bypass vulnerability allowing unauthenticated attackers to log in as any user, including administrators, via malicious cookie manipulation.
Executive Summary:
A critical authentication bypass vulnerability in the JAY Login & Register plugin allows unauthenticated attackers to hijack administrative accounts, posing a severe risk of total site compromise.
Vulnerability Details
CVE-ID: CVE-2025-14440
Affected Software: jayarsiech JAY Login & Register
Affected Versions: 0 through 2.4.01
Vulnerability: This flaw is caused by insufficient validation of the jay_login_register_process_switch_back cookie within the jay_login_register_process_switch_back function, which permits unauthenticated actors to assume the identity of any registered user.
Business Impact
The ability for an unauthenticated attacker to gain administrative access constitutes a critical security failure, leading to potential data exfiltration, unauthorized content modification, and full site takeover. Given the CVSS score of 9.8, the impact is classified as critical, as it bypasses all standard login protections and directly compromises the integrity and confidentiality of the entire WordPress environment.
Remediation Plan
Immediate Action: Since a specific patch version is not explicitly defined in the provided data, users must immediately deactivate or remove the JAY Login & Register plugin until a verified secure version is released by the developer.
Proactive Monitoring: Security teams should audit WordPress user logs for unexpected administrative logins or account switches that do not correlate with legitimate user activity.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block suspicious cookie-based requests targeting the identified vulnerable plugin endpoints.
Exploitation Status
Public Exploit Available: Yes — a public proof-of-concept exists on GitHub (Nxploited/CVE-2025-14440).
Analyst Notes: As of Dec 13, 2025, there is no public information indicating active exploitation in the wild, though the existence of a public proof-of-concept repository significantly lowers the barrier for attackers to weaponize this vulnerability.
Analyst Recommendation
The severity of this vulnerability cannot be overstated, as it provides a direct path to administrative control without requiring credentials. Organizations currently utilizing this plugin must prioritize its immediate removal from their production environment to prevent unauthorized access, as the flaw is easily automatable and poses an imminent threat to system security.
Update The JAY Login Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
The Hummingbird Performance plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3
The Hummingbird Performance plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3
Description Summary:
The Hummingbird Performance plugin for WordPress is vulnerable to sensitive information exposure, allowing unauthenticated attackers to steal credentials such as Cloudflare API keys via the request function.
Executive Summary:
The Hummingbird Performance plugin for WordPress contains a critical sensitive information exposure vulnerability that allows unauthenticated attackers to compromise sensitive credentials.
Vulnerability Details
CVE-ID: CVE-2025-14437
Affected Software: WPMU DEV Hummingbird Performance
Affected Versions: 0 through 3.18.0
Vulnerability: The plugin improperly handles sensitive information within its request function, which allows unauthenticated attackers to extract data including Cloudflare API credentials.
Business Impact
The exposure of API credentials, specifically for infrastructure services like Cloudflare, poses a significant risk to the integrity and security of the entire web environment. An attacker obtaining these credentials could potentially modify DNS records, bypass security controls, or gain unauthorized access to backend infrastructure. With a CVSS score of 7.5, this high severity vulnerability necessitates immediate remediation to prevent potential data breaches or service takeovers.
Remediation Plan
Immediate Action: Update the Hummingbird Performance plugin to the latest version available beyond 3.18.0 to incorporate the necessary security fixes.
Proactive Monitoring: Review application and server logs for unauthorized access attempts or unusual patterns originating from the plugin directory.
Compensating Controls: If an immediate update is not feasible, consider disabling the plugin or utilizing a Web Application Firewall to block requests targeting the vulnerable request function.
Exploitation Status
Public Exploit Available: No (Nuclei detection templates exist, but no weaponized exploit, Metasploit module, or ExploitDB entry is confirmed).
Analyst Notes: As of December 20, 2025, there is no public information indicating active exploitation or a published proof-of-concept for this vulnerability. The presence of a detection template indicates that security researchers are actively monitoring for this flaw, increasing the likelihood that automated scanning will occur.
Analyst Recommendation
Given the ease of exploitation for unauthenticated actors and the potential for severe credential compromise, organizations should prioritize updating this plugin immediately. Ensure that all API keys potentially exposed by this vulnerability are rotated as a precautionary measure once the patch is applied.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The Brevo for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘user_connection_id’ parameter in all versions up...
The Brevo for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘user_connection_id’ parameter in all versions up to, and including, 4
Description Summary:
The Brevo for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the user_connection_id parameter due to insufficient input sanitization and output escaping.
Executive Summary:
An unauthenticated stored cross-site scripting vulnerability in the Brevo for WooCommerce plugin allows attackers to inject malicious scripts into web pages, potentially leading to unauthorized actions.
Vulnerability Details
CVE-ID: CVE-2025-14436
Affected Software: Brevo Brevo for WooCommerce
Affected Versions: 0 through 4.0.49
Vulnerability: This vulnerability is a stored cross-site scripting (XSS) flaw occurring within the user_connection_id parameter. Because the plugin fails to properly sanitize input or escape output, unauthenticated attackers can inject arbitrary web scripts that execute whenever an administrator or user views the compromised page.
Business Impact
Successful exploitation of this vulnerability allows an attacker to execute arbitrary JavaScript in the context of an affected user session. This can result in session hijacking, unauthorized administrative actions, or the redirection of users to malicious external websites, severely impacting the integrity and security of the WordPress instance. With a CVSS score of 7.2, this represents a high-severity risk that demands immediate attention to prevent potential site compromise.
Remediation Plan
Immediate Action: Update the Brevo for WooCommerce plugin to the latest version available from the WordPress repository (version 4.0.50 or higher).
Proactive Monitoring: Monitor site access logs for unusual patterns or attempts to POST data to the plugin's endpoints that include script tags or obfuscated JavaScript payloads.
Compensating Controls: Deploy a Web Application Firewall (WAF) to filter and block malicious XSS payloads targeting the WooCommerce plugin environment until the update is applied.
Exploitation Status
Public Exploit Available: No (exploit_available: unknown)
Analyst Notes: As of January 10, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's reliance on improper input sanitization makes it a straightforward target for automated exploitation if the vulnerable endpoint is exposed to the public internet.
Analyst Recommendation
Given the unauthenticated nature of this vulnerability and the potential for full script execution within the administrative context, organizations must prioritize patching. Administrators should confirm that the plugin is updated to the latest version immediately to eliminate the injection vector and secure the WordPress site against potential cross-site scripting attacks.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in THEMELOGI Navian navian allow...
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in THEMELOGI Navian navian allows PHP Local File Inclusion.This issue affects Navian: from n/a through <= 1.5.4.
Description Summary:
The THEMELOGI Navian theme for WordPress is vulnerable to local file inclusion due to improper control of filenames used in include or require statements.
Executive Summary:
The THEMELOGI Navian theme is vulnerable to local file inclusion, which allows unauthenticated attackers to potentially read sensitive files or achieve remote code execution.
Vulnerability Details
CVE-ID: CVE-2025-14431
Affected Software: THEMELOGI Navian
Affected Versions: 0 through 1.5.4
Vulnerability: This is a local file inclusion vulnerability (CWE-98) occurring within the theme's PHP file handling logic. The flaw allows an unauthenticated attacker to manipulate file paths provided to include or require statements, leading to unauthorized file access or potential execution of arbitrary code.
Business Impact
A successful exploit allows an attacker to read arbitrary files from the server, which may include sensitive configuration files, credentials, or source code. Given the CVSS score of 9.8, this vulnerability poses a critical risk to data confidentiality, integrity, and system availability. If compromised, the entire web application and its underlying server environment could be fully controlled by an external actor.
Remediation Plan
Immediate Action: Currently, there is no official patch released for this vulnerability. Administrators should immediately deactivate or uninstall the Navian theme until an update is provided by the vendor.
Proactive Monitoring: Review web server access logs for requests containing suspicious directory traversal patterns, such as multiple dot-dot-slash sequences, targeting the theme directory.
Compensating Controls: Implement a Web Application Firewall (WAF) rule to block incoming requests that attempt to pass file paths or directory traversal characters to theme-specific parameters.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of January 8, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the vulnerability is highly dangerous, the absence of a confirmed exploit does not reduce the necessity for immediate defensive action.
Analyst Recommendation
The critical nature of this local file inclusion vulnerability requires immediate attention. Because no patch is currently available, the only effective way to eliminate this risk is to remove the vulnerable theme from the production environment. Organizations should prioritize migrating to a secure alternative or waiting for a confirmed fix from THEMELOGI before re-enabling the software.
Update Improper Control of Filename for Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeMove Brook - Agency Busi...
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeMove Brook - Agency Business Creative brook allows PHP Local File Inclusion.This issue affects Brook - Agency Business Creative: from n/a through <= 2.8.9.
Description Summary:
A local file inclusion vulnerability in the ThemeMove Brook WordPress theme allows unauthenticated attackers to include arbitrary local files via improper control of filename parameters.
Executive Summary:
The ThemeMove Brook WordPress theme contains a critical local file inclusion vulnerability that permits unauthenticated attackers to access or execute arbitrary files on the server.
Vulnerability Details
CVE-ID: CVE-2025-14430
Affected Software: ThemeMove Brook - Agency Business Creative
Affected Versions: 0 through 2.9.0
Vulnerability: This vulnerability is identified as a local file inclusion flaw (CWE-98) where the theme fails to properly sanitize input before passing it to include or require statements. An unauthenticated attacker can leverage this to read sensitive files or potentially execute malicious code on the host server.
Business Impact
The ability for an unauthenticated user to perform local file inclusion poses a severe risk to the confidentiality, integrity, and availability of the affected system. With a CVSS score of 9.8, this flaw could lead to full system compromise, including the exposure of database credentials, configuration files, and the execution of unauthorized commands.
Remediation Plan
Immediate Action: Review the ThemeMove official support channels for the release of a security patch and update the Brook theme to the latest version immediately upon availability.
Proactive Monitoring: Monitor server access logs for suspicious requests containing path traversal patterns such as "../" or attempts to include non-PHP files through the theme directory.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block directory traversal attempts and suspicious file inclusion requests targeting the WordPress themes directory.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of Jan 8, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the CVSS score is 9.8, indicating extreme severity, the actual exploitability depends on the specific implementation of the theme's file inclusion logic.
Analyst Recommendation
Given the critical nature of this vulnerability and the potential for full remote code execution, administrators should prioritize this issue. If a patch is not yet available, consider temporarily disabling the Brook theme or restricting access to the affected site components until a secure version is deployed.
Update Improper Control of Filename for Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeMove AeroLand aeroland a...
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeMove AeroLand aeroland allows PHP Local File Inclusion.This issue affects AeroLand: from n/a through <= 1.6.6.
Description Summary:
A Local File Inclusion vulnerability in the ThemeMove AeroLand WordPress theme allows unauthenticated attackers to include arbitrary files via improper filename control.
Executive Summary:
The ThemeMove AeroLand WordPress theme is vulnerable to a Local File Inclusion flaw that could allow an unauthenticated attacker to execute arbitrary code or access sensitive files.
Vulnerability Details
CVE-ID: CVE-2025-14429
Affected Software: ThemeMove AeroLand
Affected Versions: 0 through 1.6.6
Vulnerability: This is a PHP Local File Inclusion vulnerability (CWE-98) occurring due to improper validation of filenames used in include or require statements. The vulnerability is exploitable by an unauthenticated attacker via a network-based vector.
Business Impact
The ability for an unauthenticated user to perform Local File Inclusion represents a critical security risk. A successful exploit can lead to unauthorized access to sensitive configuration files, potential remote code execution, and full compromise of the affected WordPress site. Given the CVSS score of 9.8, this flaw presents a severe threat to data confidentiality, integrity, and system availability.
Remediation Plan
Immediate Action: Since a specific patch version is not currently identified in the enrichment data, users should immediately audit their use of the AeroLand theme and check the official ThemeMove portal for updates. If no update is available, consider switching to an alternative, well-maintained theme until a fix is released.
Proactive Monitoring: Security teams should review web server access logs for suspicious patterns, such as directory traversal sequences (e.g., ../) or requests targeting sensitive system files like wp-config.php.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block directory traversal attempts and common Local File Inclusion attack signatures.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of Jan 8, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While currently unexploited, the nature of the flaw makes it highly dangerous if a weaponized exploit is released.
Analyst Recommendation
Organizations utilizing the AeroLand theme must treat this vulnerability with extreme urgency. Given the potential for total system compromise, administrators should prioritize the identification and removal of vulnerable instances. If immediate patching is not possible, implementing strict WAF filtering and limiting file system permissions for the web server user are essential steps to mitigate the risk of exploitation.
Update Improper Control of Filename for Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
GIMP JP2 File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability
GIMP JP2 File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability
Description Summary:
A heap-based buffer overflow in GIMP allows remote attackers to execute arbitrary code via a specially crafted JP2 file, requiring user interaction to open the malicious file.
Executive Summary:
A heap-based buffer overflow vulnerability in GIMP version 3.0.6 creates a critical risk of remote code execution if a user opens a malicious JP2 image file.
Vulnerability Details
CVE-ID: CVE-2025-14425
Affected Software: GIMP GIMP
Affected Versions: 3.0.6
Vulnerability: This vulnerability is a heap-based buffer overflow (CWE-122) triggered during the parsing of JP2 files. It occurs due to insufficient validation of user-supplied data lengths before memory copying, which can be exploited by an unauthenticated attacker if the victim opens a malicious file.
Business Impact
The vulnerability carries a CVSS score of 7.8, indicating a high severity level. Successful exploitation allows for arbitrary code execution in the context of the user running the application, which could lead to full system compromise, data theft, or lateral movement within the network. Because the attack vector relies on file parsing, any business process involving the handling of external images is at significant risk.
Remediation Plan
Immediate Action: Update GIMP to the latest version, which includes the fix committed in the upstream repository (commit cd1c88a0364ad1444c06536731972a99bd8643fd).
Proactive Monitoring: Monitor file integrity and application logs for abnormal crashes or unexpected process behavior when the GIMP application handles image files.
Compensating Controls: Implement endpoint protection software that can detect and block malicious file execution and restrict users from opening untrusted JP2 files from unknown sources.
Exploitation Status
Public Exploit Available: No (exploit_available: unknown)
Analyst Notes: As of December 24, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the vulnerability requires user interaction, the potential for remote code execution makes it a high-priority item for remediation.
Analyst Recommendation
Given the severity of potential remote code execution, users and administrators should prioritize upgrading their GIMP installations to the patched version immediately. Organizations should also provide user awareness training regarding the risks of opening image files from untrusted or unverified sources to reduce the attack surface.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
GIMP XCF File Parsing Use-After-Free Remote Code Execution Vulnerability
GIMP XCF File Parsing Use-After-Free Remote Code Execution Vulnerability
Description Summary:
A use after free vulnerability in GIMP allows remote attackers to achieve arbitrary code execution via a specially crafted XCF file.
Executive Summary:
A critical use after free vulnerability in GIMP version 3.0.6 allows for remote code execution when a user opens a malicious XCF file.
Vulnerability Details
CVE-ID: CVE-2025-14424
Affected Software: GIMP
Affected Versions: 3.0.6
Vulnerability: The vulnerability is a use after free flaw occurring during the parsing of XCF files, caused by a failure to validate object existence before performing operations. An attacker can trigger this by convincing a user to open a malicious file, leading to code execution in the context of the current process.
Business Impact
Successful exploitation of this vulnerability allows an attacker to execute arbitrary code with the privileges of the user running GIMP. Given the CVSS score of 7.8, this poses a high risk to organizational security, as it could lead to full system compromise, data theft, or the installation of persistent malware on the affected workstation.
Remediation Plan
Immediate Action: Upgrade GIMP to the latest version as specified by the vendor advisory to incorporate the fix found in commit 5cc55d078b7fba995cef77d195fac325ee288ddd.
Proactive Monitoring: Monitor workstation file system activity and process execution logs for unusual behavior originating from the GIMP application.
Compensating Controls: Implement endpoint protection solutions that scan incoming files for malicious patterns and restrict the ability of standard users to execute unknown or untrusted software.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of December 24, 2025, there is no public information indicating active exploitation or a public proof of concept for this vulnerability. While the vulnerability is not currently being exploited, the ability to achieve code execution via file parsing makes it a significant target for weaponization.
Analyst Recommendation
Organizations should prioritize patching GIMP installations to remediate this use after free vulnerability immediately. Because the attack requires user interaction, user awareness training regarding the risks of opening untrusted files remains a critical secondary defense layer against this class of exploit.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
GIMP LBM File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability
GIMP LBM File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability
Description Summary:
A stack-based buffer overflow vulnerability in GIMP allows remote attackers to achieve arbitrary code execution via the parsing of malicious LBM files.
Executive Summary:
A critical stack-based buffer overflow vulnerability in GIMP 3.0.6 could allow a remote attacker to execute arbitrary code on a victim machine through a specially crafted LBM file.
Vulnerability Details
CVE-ID: CVE-2025-14423
Affected Software: GIMP
Affected Versions: GIMP 3.0.6
Vulnerability: The vulnerability exists due to improper validation of user-supplied data length when parsing LBM files, leading to a stack-based buffer overflow. An unauthenticated attacker can exploit this flaw by enticing a user to open a malicious LBM file, resulting in code execution within the context of the application.
Business Impact
Successful exploitation of this vulnerability allows an attacker to execute arbitrary code with the privileges of the user running GIMP. Given the CVSS score of 7.8, this represents a high-severity risk that could lead to full system compromise, unauthorized data access, or the deployment of persistent malware within the corporate environment.
Remediation Plan
Immediate Action: Update GIMP to the latest version that incorporates the fix provided in the GitLab commit 481cdbbb97746be1145ec3a633c567a68633c521.
Proactive Monitoring: Monitor system logs for unusual application crashes or unexpected child processes spawned by the GIMP process, which may indicate attempted exploitation.
Compensating Controls: Implement file-type restrictions or sandbox environments for users who must open untrusted image files, effectively containing the potential impact of a successful overflow exploit.
Exploitation Status
Public Exploit Available: No (exploit_available: unknown)
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While exploitation requires user interaction, the potential for remote code execution makes this a significant threat for workstations that handle diverse image formats.
Analyst Recommendation
Organizations should prioritize updating GIMP installations to the patched version as soon as it becomes available. Users should be cautioned against opening LBM files from untrusted or unverified sources until the patch is successfully deployed across the environment.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
GIMP PNM File Parsing Integer Overflow Remote Code Execution Vulnerability
GIMP PNM File Parsing Integer Overflow Remote Code Execution Vulnerability
Description Summary:
A remote code execution vulnerability exists in GIMP due to an integer overflow during the parsing of PNM files, which can be triggered by processing a malicious file.
Executive Summary:
An integer overflow vulnerability in GIMP version 3.0.6 allows remote attackers to execute arbitrary code when a user opens a specially crafted PNM file.
Vulnerability Details
CVE-ID: CVE-2025-14422
Affected Software: GIMP
Affected Versions: 3.0.6
Vulnerability: The flaw is an integer overflow (CWE-190) occurring during the parsing of PNM image files. It requires user interaction, specifically the opening of a malicious file, and allows an attacker to execute code within the context of the user process.
Business Impact
The ability for an attacker to achieve remote code execution poses a severe risk to organizational security. Successful exploitation could lead to total system compromise, unauthorized data exfiltration, or the installation of persistent malware, justifying the CVSS score of 7.8.
Remediation Plan
Immediate Action: Users should avoid opening untrusted or unknown PNM files until a vendor-provided security update or patch is officially released and applied.
Proactive Monitoring: Security teams should monitor endpoint activity for suspicious GIMP process behaviors, such as unexpected child process spawning or unauthorized network connections originating from the application.
Compensating Controls: Deploy host-based intrusion detection systems and endpoint protection tools configured to scan incoming files for anomalies, which may help identify malicious PNM structures before they are processed by the application.
Exploitation Status
Public Exploit Available: No — no confirmed public exploit exists in the provided data.
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While exploitation requires user interaction, the potential for remote code execution makes this a significant risk if users frequently handle untrusted image files.
Analyst Recommendation
Given the potential for remote code execution, this vulnerability represents a high-severity threat to any environment utilizing GIMP 3.0.6. Administrators must prioritize restricting the opening of untrusted files and should closely track the GIMP project repository for an official fix, applying it immediately upon release to remediate the underlying memory safety issue.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
pdfforge PDF Architect CBZ File Parsing Directory Traversal Remote Code Execution Vulnerability
pdfforge PDF Architect CBZ File Parsing Directory Traversal Remote Code Execution Vulnerability
Description Summary:
A directory traversal vulnerability in pdfforge PDF Architect allows remote attackers to achieve arbitrary code execution by tricking a user into opening a malicious CBZ file.
Executive Summary:
A critical directory traversal vulnerability in pdfforge PDF Architect allows remote attackers to execute arbitrary code on the host system through maliciously crafted CBZ files.
Vulnerability Details
CVE-ID: CVE-2025-14420
Affected Software: pdfforge PDF Architect
Affected Versions: 9.1.74.23030
Vulnerability: The software fails to properly validate user supplied paths during the parsing of CBZ files, leading to a path traversal vulnerability. An unauthenticated attacker can leverage this flaw to execute arbitrary code in the context of the current user, provided the user is enticed to open a malicious file.
Business Impact
The ability for an attacker to execute arbitrary code on a user workstation presents a severe risk of full system compromise, including data theft, malware installation, and lateral movement within the corporate network. With a CVSS score of 7.8, this high severity vulnerability poses a significant threat to operational integrity and sensitive information confidentiality.
Remediation Plan
Immediate Action: Since a specific patch is not yet confirmed, users should avoid opening unsolicited or untrusted CBZ files and monitor vendor communications for an emergency security update.
Proactive Monitoring: Security teams should monitor endpoint logs for suspicious file system activity or unexpected child processes spawned by the PDF Architect application.
Compensating Controls: Deploy endpoint detection and response (EDR) solutions to identify and block suspicious file execution patterns associated with document parsing software.
Exploitation Status
Public Exploit Available: No (exploit_available: false)
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the vulnerability requires user interaction to trigger, the potential for remote code execution makes it a high priority for organizations utilizing this software.
Analyst Recommendation
Given the severity of potential remote code execution, organizations should prioritize restricting the use of untrusted CBZ files within the environment. Administrators must remain vigilant for official patch releases from pdfforge and apply them immediately upon availability to neutralize this risk.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
pdfforge PDF Architect PDF File Parsing Memory Corruption Remote Code Execution Vulnerability
pdfforge PDF Architect PDF File Parsing Memory Corruption Remote Code Execution Vulnerability
Description Summary:
A memory corruption vulnerability in pdfforge PDF Architect allows remote attackers to execute arbitrary code via a specially crafted PDF file.
Executive Summary:
A memory corruption vulnerability in pdfforge PDF Architect poses a critical risk of remote code execution if a user opens a malicious PDF file.
Vulnerability Details
CVE-ID: CVE-2025-14419
Affected Software: pdfforge PDF Architect
Affected Versions: pdfforge PDF Architect: 9.1.74.23030
Vulnerability: The vulnerability stems from improper restriction of operations within memory buffer bounds during PDF file parsing. An unauthenticated attacker can exploit this by inducing a user to open a malicious PDF file, leading to memory corruption and potential code execution in the context of the application.
Business Impact
Successful exploitation of this flaw allows an attacker to execute arbitrary code on the victim's system, potentially leading to a complete compromise of the host. Given the CVSS score of 7.8, this vulnerability represents a high risk to organizational data integrity and system confidentiality. Unauthorized code execution could facilitate lateral movement within the network or the deployment of additional malicious payloads.
Remediation Plan
Immediate Action: Update pdfforge PDF Architect to the latest version as recommended by the vendor to remediate the memory corruption flaw.
Proactive Monitoring: Monitor endpoint activity for unusual process spawning originating from PDF reader applications and review application logs for signs of application crashes or unexpected memory errors.
Compensating Controls: Implement endpoint protection solutions that can detect and block the execution of files originating from untrusted sources, and utilize file integrity monitoring to detect unauthorized modifications.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw requires user interaction, specifically the opening of a malicious file, to trigger the memory corruption condition.
Analyst Recommendation
This vulnerability presents a significant risk due to the potential for remote code execution. Administrators should prioritize identifying all instances of the affected PDF Architect software and applying vendor-supplied patches immediately. User awareness training regarding the risks of opening unsolicited PDF files remains an essential secondary defense against this class of vulnerability.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
pdfforge PDF Architect Launch Insufficient UI Warning Remote Code Execution Vulnerability
pdfforge PDF Architect Launch Insufficient UI Warning Remote Code Execution Vulnerability
Description Summary:
A vulnerability in pdfforge PDF Architect allows local attackers to achieve remote code execution through the Launch action by failing to display necessary warnings for unsafe script execution.
Executive Summary:
A critical remote code execution vulnerability in pdfforge PDF Architect, triggered via user interaction, poses a significant risk of full system compromise.
Vulnerability Details
CVE-ID: CVE-2025-14417
Affected Software: pdfforge PDF Architect
Affected Versions: 9.1.74.23030
Vulnerability: The flaw resides in the Launch action implementation, which fails to provide adequate user warnings before executing dangerous scripts. An attacker can exploit this by enticing a user to open a malicious file or visit a compromised webpage, leading to code execution in the context of the current user.
Business Impact
The ability for an attacker to execute arbitrary code with the privileges of the logged-in user represents a severe risk to organizational data and system integrity. Given the CVSS score of 7.8, this vulnerability is classified as High, as it could facilitate unauthorized data access, malware installation, or persistent lateral movement within the network.
Remediation Plan
Immediate Action: Update pdfforge PDF Architect to the latest version provided by the vendor to remediate the unsafe Launch action implementation.
Proactive Monitoring: Review endpoint process execution logs for suspicious child processes spawned by the PDF Architect application.
Compensating Controls: Restrict user access to untrusted websites and implement robust email filtering to prevent the delivery of malicious files that could trigger this vulnerability.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the vulnerability requires user interaction, its potential for full code execution makes it a high-priority item for patching.
Analyst Recommendation
Organizations utilizing pdfforge PDF Architect should prioritize identifying all instances of version 9.1.74.23030 and applying the vendor-supplied security update immediately. Due to the nature of the flaw, which allows for remote code execution, failing to patch leaves endpoints vulnerable to exploitation via common social engineering tactics.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
Soda PDF Desktop Word File Insufficient UI Warning Remote Code Execution Vulnerability
Soda PDF Desktop Word File Insufficient UI Warning Remote Code Execution Vulnerability
Description Summary:
Soda PDF Desktop contains a remote code execution vulnerability due to insufficient UI warnings when handling Word files, allowing attackers to execute code via malicious files or web pages.
Executive Summary:
A remote code execution vulnerability in Soda PDF Desktop requires user interaction to compromise systems and achieve arbitrary code execution.
Vulnerability Details
CVE-ID: CVE-2025-14414
Affected Software: Soda PDF Desktop
Affected Versions: Soda PDF Desktop: 14.0.509.23030
Vulnerability: The software fails to provide adequate UI warnings when processing Word files, which allows for the execution of dangerous scripts. An attacker can leverage this flaw to execute code in the context of the current user, provided the user is tricked into opening a malicious file or visiting a compromised page.
Business Impact
The ability for an attacker to execute arbitrary code on a user workstation poses a significant risk to organizational data integrity and confidentiality. Given the CVSS score of 7.8, this vulnerability is classified as High severity because successful exploitation could lead to full system compromise, unauthorized data access, or the deployment of secondary malware within the corporate environment.
Remediation Plan
Immediate Action: Update Soda PDF Desktop to the latest version provided by the vendor to resolve the insufficient UI warning flaw.
Proactive Monitoring: Review endpoint security logs for unusual process execution chains originating from the Soda PDF application, particularly those involving script interpreters.
Compensating Controls: Use email filtering and endpoint protection software to scan incoming attachments and block files that exhibit suspicious script-based behaviors or originate from untrusted sources.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The requirement for user interaction, specifically the opening of a malicious file, serves as a natural barrier to widespread automated exploitation.
Analyst Recommendation
This vulnerability represents a high-risk entry point for attackers to gain a foothold on local systems. Organizations should prioritize patching Soda PDF Desktop installations immediately to ensure that UI warning mechanisms are correctly implemented and that users are protected from inadvertent script execution.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
Soda PDF Desktop CBZ File Parsing Directory Traversal Remote Code Execution Vulnerability
Soda PDF Desktop CBZ File Parsing Directory Traversal Remote Code Execution Vulnerability
Description Summary:
A directory traversal vulnerability in Soda PDF Desktop allows remote attackers to execute arbitrary code via malicious CBZ files.
Executive Summary:
A directory traversal vulnerability in Soda PDF Desktop enables remote code execution when a user opens a specially crafted CBZ file, posing a significant risk to system integrity.
Vulnerability Details
CVE-ID: CVE-2025-14413
Affected Software: Soda PDF Desktop
Affected Versions: Soda PDF Desktop: 14.0.509.23030
Vulnerability: The software fails to properly validate user supplied paths during the parsing of CBZ files, leading to a path traversal vulnerability. An unauthenticated attacker can leverage this flaw to achieve remote code execution in the context of the current user, provided the user is enticed to open a malicious file.
Business Impact
The exploitation of this vulnerability allows for full code execution, which may result in complete system compromise, unauthorized data access, and the potential for lateral movement within the network. With a CVSS score of 7.8, this flaw represents a high-severity risk that could lead to significant operational disruption and loss of confidentiality or integrity.
Remediation Plan
Immediate Action: Users should immediately contact the vendor or monitor the official support portal for the release of a security patch addressing ZDI-25-1086.
Proactive Monitoring: Security teams should monitor endpoint activity for suspicious file execution patterns originating from PDF processing software and review logs for unusual file system access.
Compensating Controls: Organizations should implement restrictive endpoint policies to prevent the execution of untrusted files and utilize security software capable of detecting malicious archive contents.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the vulnerability requires user interaction, the impact of arbitrary code execution makes it a high priority for remediation once a fix is made available.
Analyst Recommendation
Given the potential for remote code execution, this vulnerability poses a severe threat to end-user workstations. Organizations should prioritize the identification of affected installations and restrict the opening of untrusted or externally sourced CBZ files until a vendor-supplied patch is successfully applied.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
Soda PDF Desktop XLS File Insufficient UI Warning Remote Code Execution Vulnerability
Soda PDF Desktop XLS File Insufficient UI Warning Remote Code Execution Vulnerability
Description Summary:
Soda PDF Desktop contains a vulnerability in XLS file handling where insufficient UI warnings allow remote attackers to execute arbitrary code.
Executive Summary:
A critical remote code execution vulnerability in Soda PDF Desktop allows attackers to execute arbitrary code through malicious XLS files, requiring user interaction.
Vulnerability Details
CVE-ID: CVE-2025-14412
Affected Software: Soda PDF Desktop
Affected Versions: 14.0.509.23030
Vulnerability: The vulnerability stems from an insufficient UI warning when processing XLS files, categorized as CWE-356. Attackers can leverage this flaw to execute arbitrary code in the context of the current user, provided the user is enticed to open a malicious file.
Business Impact
This vulnerability poses a significant risk to organizational integrity and confidentiality. Successful exploitation allows an attacker to gain full control over the user session, potentially leading to unauthorized data access, installation of malware, or further lateral movement within the network. Given the CVSS score of 7.8, this is classified as a high-severity issue that necessitates prompt remediation to prevent potential system compromise.
Remediation Plan
Immediate Action: Update Soda PDF Desktop to the latest available version provided by the vendor to patch the XLS file handling flaw.
Proactive Monitoring: Review endpoint security logs for unusual process execution patterns originating from Soda PDF Desktop.
Compensating Controls: Implement file integrity monitoring and ensure that email security gateways are configured to scan and block suspicious XLS attachments from untrusted sources.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's requirement for user interaction, specifically the opening of a malicious file, serves as the primary barrier to exploitation.
Analyst Recommendation
The risk associated with this vulnerability is significant due to the potential for full code execution upon user interaction. Organizations utilizing Soda PDF Desktop should prioritize updating the software to the version specified by the vendor. Until an update is applied, users should exercise extreme caution when opening unsolicited or suspicious XLS files.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
Soda PDF Desktop PDF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability
Soda PDF Desktop PDF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability
Description Summary:
Soda PDF Desktop contains an out-of-bounds write vulnerability in its PDF parsing engine that can lead to remote code execution when a user opens a maliciously crafted PDF file.
Executive Summary:
A critical out-of-bounds write vulnerability in Soda PDF Desktop allows remote attackers to achieve arbitrary code execution on target systems through malicious file interaction.
Vulnerability Details
CVE-ID: CVE-2025-14409
Affected Software: Soda PDF Desktop
Affected Versions: Soda PDF Desktop: 14.0.506.23016
Vulnerability: The software fails to properly validate user-supplied data during the parsing of PDF files, resulting in an out-of-bounds write vulnerability (CWE-787). This flaw can be triggered by an unauthenticated attacker if a victim is coerced into opening a specially crafted malicious PDF file.
Business Impact
The ability for an attacker to execute arbitrary code with the privileges of the current user presents a significant risk to organizational data integrity and system confidentiality. Successful exploitation could lead to full system compromise, the installation of malware, or unauthorized access to sensitive documents processed within the application. Given the CVSS score of 7.8, this vulnerability represents a high-severity risk that requires immediate attention, especially for users who frequently interact with untrusted PDF documents.
Remediation Plan
Immediate Action: Users should restrict the opening of PDF files from untrusted sources and monitor official vendor channels for the release of a security patch addressing this out-of-bounds write flaw.
Proactive Monitoring: Security teams should monitor endpoint logs for suspicious process spawning behavior originating from the Soda PDF Desktop application or unexpected crashes during file parsing.
Compensating Controls: Deploy endpoint protection solutions capable of detecting malicious file execution and ensure that PDF software is run with the least privilege necessary to limit potential damage from an exploitation event.
Exploitation Status
Public Exploit Available: No — exploit_available (false).
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The requirement for user interaction, specifically opening a malicious file, serves as a primary vector for this memory corruption flaw.
Analyst Recommendation
While this vulnerability requires user interaction to facilitate exploitation, the potential for remote code execution makes it a high-priority concern. Organizations should ensure that users are educated on the risks of opening unsolicited PDF files and maintain high vigilance for vendor-provided updates. Once a patch is released by the vendor, it should be deployed across all installations immediately to eliminate the underlying memory corruption risk.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
Soda PDF Desktop Uncontrolled Search Path Element Local Privilege Escalation Vulnerability
Soda PDF Desktop Uncontrolled Search Path Element Local Privilege Escalation Vulnerability
Description Summary:
Soda PDF Desktop contains an uncontrolled search path element vulnerability that allows a local attacker to escalate privileges to SYSTEM level.
Executive Summary:
A high-severity local privilege escalation vulnerability in Soda PDF Desktop allows authenticated local attackers to achieve full SYSTEM compromise.
Vulnerability Details
CVE-ID: CVE-2025-14406
Affected Software: Soda PDF Desktop
Affected Versions: Soda PDF Desktop: 14.0.437.22898
Vulnerability: The application is vulnerable to an uncontrolled search path element flaw (CWE-427) within its OpenSSL configuration, where it attempts to load a configuration file from an insecure directory. An attacker with low-privileged access can leverage this to execute arbitrary code in the context of the SYSTEM account.
Business Impact
Successful exploitation of this vulnerability results in full system compromise, as the attacker gains SYSTEM-level privileges. Given the CVSS score of 7.8, this represents a significant risk to organizational assets, potentially facilitating lateral movement, data exfiltration, or the deployment of ransomware across the local machine.
Remediation Plan
Immediate Action: Consult the vendor advisory and the Zero Day Initiative entry (ZDI-25-1079) to identify the specific patch version and update the software immediately.
Proactive Monitoring: Monitor system logs for unauthorized attempts to place or modify configuration files in application directories and audit process creation events for unusual child processes spawned by the Soda PDF service.
Compensating Controls: Restrict local user permissions to prevent unauthorized file system write access in directories used by the application and ensure the principle of least privilege is strictly enforced for all standard users.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to its ability to elevate a standard user to the highest level of system authority.
Analyst Recommendation
This vulnerability presents a critical risk to endpoints where Soda PDF Desktop is installed because it provides a direct path to full system takeover. Organizations should prioritize updating the software as soon as the vendor provides a patch and restrict local user access to the application installation paths to minimize the attack surface until remediation is complete.
Update to patched version immediately. Review user permissions and access controls.
PDFsam Enhanced Launch Insufficient UI Warning Remote Code Execution Vulnerability
PDFsam Enhanced Launch Insufficient UI Warning Remote Code Execution Vulnerability
Description Summary:
PDFsam Enhanced suffers from an insufficient UI warning vulnerability in the Launch action, which allows attackers to achieve remote code execution via malicious files or web pages.
Executive Summary:
A critical remote code execution vulnerability in PDFsam Enhanced allows attackers to execute arbitrary code on the host system if a user interacts with a malicious file or page.
Vulnerability Details
CVE-ID: CVE-2025-14403
Affected Software: PDFsam Enhanced
Affected Versions: 7.0.76.15222
Vulnerability: The application fails to issue appropriate warnings when executing dangerous scripts through the Launch action. This flaw allows an unauthenticated attacker to execute code in the context of the current user, provided the user interacts with a malicious file or visits a compromised webpage.
Business Impact
Successful exploitation of this vulnerability grants an attacker the ability to execute arbitrary code on the victim's machine. Given the CVSS score of 7.8, this poses a high risk of total system compromise, including data exfiltration, unauthorized access to sensitive files, and potential movement within the local network.
Remediation Plan
Immediate Action: Users should update PDFsam Enhanced to the latest available version provided by the vendor to resolve the unsafe Launch action behavior.
Proactive Monitoring: Security teams should monitor endpoint logs for suspicious process execution patterns originating from PDFsam Enhanced.
Compensating Controls: Restrict users from opening unsolicited PDF files from untrusted sources and utilize endpoint protection software to detect and block malicious script execution.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's exploitability is dependent on social engineering or user interaction to trigger the malicious file or page.
Analyst Recommendation
The vulnerability represents a significant security risk due to the potential for full system compromise. Organizations running the affected version of PDFsam Enhanced must prioritize updating their installations. If an update cannot be applied immediately, ensure that users are trained to avoid opening untrusted PDF documents and maintain strict endpoint security controls to mitigate the risk of code execution.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
PDFsam Enhanced App Out-Of-Bounds Read Remote Code Execution Vulnerability
PDFsam Enhanced App Out-Of-Bounds Read Remote Code Execution Vulnerability
Description Summary:
A remote code execution vulnerability in PDFsam Enhanced exists due to an out-of-bounds read flaw when processing App objects.
Executive Summary:
PDFsam Enhanced is vulnerable to remote code execution that can be triggered by a user interacting with a malicious file or page, posing a significant risk to system integrity.
Vulnerability Details
CVE-ID: CVE-2025-14401
Affected Software: PDFsam Enhanced
Affected Versions: PDFsam Enhanced: 7.0.76.15222
Vulnerability: The vulnerability is an out-of-bounds read error occurring during the parsing of App objects. An attacker can leverage this flaw to execute arbitrary code in the context of the application process, provided the victim is enticed into opening a malicious file or visiting a compromised webpage.
Business Impact
The potential for remote code execution represents a critical threat to organizational security, potentially allowing attackers to gain full control over the affected host. Given the CVSS score of 7.8, this vulnerability is categorized as High severity, which could lead to unauthorized data access, malware installation, or persistent system compromise.
Remediation Plan
Immediate Action: Organizations should restrict the opening of untrusted PDF files and monitor for vendor-provided security updates. If an update is released, prioritize its deployment across all workstations running the affected software.
Proactive Monitoring: Security teams should monitor endpoint logs for suspicious process execution chains or unexpected network traffic originating from the PDFsam Enhanced application.
Compensating Controls: Deploy endpoint detection and response (EDR) solutions to identify and block malicious child processes spawned by PDF readers.
Exploitation Status
Public Exploit Available: No (the referenced ZDI advisory provides technical detail but does not constitute a functional public exploit).
Analyst Notes: As of December 25, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to its potential for code execution, though it requires user interaction to trigger.
Analyst Recommendation
Given the capability for remote code execution, this vulnerability warrants immediate attention despite the requirement for user interaction. Administrators must track the vendor advisory for patch availability and ensure that users are educated on the risks associated with opening unsolicited or untrusted PDF documents.
Apply security patches immediately for internet-facing systems. Monitor for exploitation attempts and review access logs.
The Postem Ipsum plugin for WordPress is vulnerable to unauthorized modification of data to Privilege Escalation due to a missing capability check on...
The Postem Ipsum plugin for WordPress is vulnerable to unauthorized modification of data to Privilege Escalation due to a missing capability check on the postem_ipsum_generate_users() function in all versions up to, and including, 3
Description Summary:
The Postem Ipsum WordPress plugin is vulnerable to privilege escalation due to a missing capability check in the postem_ipsum_generate_users() function, allowing authenticated users to gain admin rights.
Executive Summary:
The Postem Ipsum plugin for WordPress contains a critical privilege escalation vulnerability that allows authenticated attackers to create arbitrary administrator accounts.
Vulnerability Details
CVE-ID: CVE-2025-14397
Affected Software: Francisco Palacios Postem Ipsum
Affected Versions: 0 through 3.0.1
Vulnerability: This vulnerability is caused by a missing authorization check (CWE-862) within the postem_ipsum_generate_users() function. Any authenticated user, including those with minimal Subscriber-level access, can trigger this function to create new accounts with full administrative privileges.
Business Impact
The ability for a low-privileged user to escalate their permissions to an administrator constitutes a complete compromise of the WordPress site. An attacker gaining administrative access can modify site content, exfiltrate sensitive data, install malicious backdoors, or perform further attacks against site visitors. Given the CVSS score of 8.8, this flaw represents a high-severity risk that could lead to total loss of system integrity and confidentiality.
Remediation Plan
Immediate Action: As no patched version is currently confirmed, administrators should immediately deactivate and uninstall the Postem Ipsum plugin until a security update is released by the developer.
Proactive Monitoring: Monitor WordPress user management logs for the creation of unauthorized administrator accounts or suspicious activity originating from accounts with standard user roles.
Compensating Controls: Implement a Web Application Firewall (WAF) rule to block access to the administrative functions of the plugin if it must remain active, though removal is the only guaranteed mitigation.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of December 15, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the ease with which an attacker can bypass the intended access control model to gain full control of the application.
Analyst Recommendation
This vulnerability presents a severe risk to the security of your WordPress installation by enabling unauthorized administrative access. Because the plugin lacks a verified security patch at this time, the most effective way to eliminate this risk is to remove the software entirely. Security teams should prioritize the audit of all installed plugins to ensure this component is identified and addressed immediately.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The Video Merchant plugin for WordPress is vulnerable to Cross-Site Request Forgery in version <= 5
The Video Merchant plugin for WordPress is vulnerable to Cross-Site Request Forgery in version <= 5
Description Summary:
The Video Merchant plugin for WordPress is vulnerable to Cross-Site Request Forgery, allowing unauthenticated attackers to achieve remote code execution via arbitrary file uploads.
Executive Summary:
A critical vulnerability in the Video Merchant WordPress plugin allows unauthenticated attackers to execute arbitrary code on the server by tricking an administrator into performing a malicious action.
Vulnerability Details
CVE-ID: CVE-2025-14390
Affected Software: WordPress Video Merchant
Affected Versions: 0 through 5.0.4
Vulnerability: This flaw is a Cross-Site Request Forgery (CSRF) vulnerability stemming from missing nonce validation within the video_merchant_add_video_file function. Unauthenticated attackers can leverage this to upload malicious files, leading to remote code execution when a site administrator is coerced into clicking a forged link.
Business Impact
The potential for remote code execution poses a severe risk to the confidentiality, integrity, and availability of the entire WordPress environment. Given the high CVSS score of 8.8, successful exploitation could result in full site compromise, unauthorized data access, and the deployment of persistent backdoors, leading to significant reputational and operational damage.
Remediation Plan
Immediate Action: As no specific patch version is currently confirmed, administrators should immediately deactivate and remove the Video Merchant plugin from their WordPress installations until a secure update is released by the vendor.
Proactive Monitoring: Review web server access logs for anomalous requests targeting the video_merchant_add_video_file function, and monitor the file system for unexpected script uploads in the plugin directory.
Compensating Controls: Implement a Web Application Firewall (WAF) with rules configured to block suspicious file upload attempts and restrict access to administrative functions.
Exploitation Status
Public Exploit Available: exploit_available (unknown)
Analyst Notes: As of December 12, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's requirement for user interaction via CSRF slightly mitigates its reach, but the total impact of remote code execution makes it a high priority for removal.
Analyst Recommendation
Due to the severity of remote code execution, organizations must prioritize the removal of the Video Merchant plugin from their production environments immediately. Do not rely on configuration changes alone; complete deactivation is the only reliable method to mitigate this risk until the developer provides a verified security patch.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The PhastPress plugin for WordPress is vulnerable to Unauthenticated Arbitrary File Read via null byte injection in all versions up to, and including,...
The PhastPress plugin for WordPress is vulnerable to Unauthenticated Arbitrary File Read via null byte injection in all versions up to, and including, 3.7. This is due to a discrepancy between the extension validation in `getExtensionForURL()` which operates on URL-decoded paths, and `appendNormalized()` which strips everything after a null byte before constructing the filesystem path. This makes it possible for unauthenticated attackers to read arbitrary files from the webroot, including wp-config.php, by appending a double URL-encoded null byte (%2500) followed by an allowed extension (.txt) to the file path.
Description Summary:
The PhastPress plugin for WordPress is vulnerable to unauthenticated arbitrary file read via null byte injection, allowing attackers to access sensitive files like wp-config.php.
Executive Summary:
The PhastPress plugin for WordPress contains a critical arbitrary file read vulnerability that allows unauthenticated attackers to exfiltrate sensitive configuration data from the host server.
Vulnerability Details
CVE-ID: CVE-2025-14388
Affected Software: kiboit PhastPress
Affected Versions: 0 through 3.7
Vulnerability: This is an improper neutralization of null byte vulnerability (CWE-158) occurring in the getExtensionForURL and appendNormalized functions. Unauthenticated attackers can bypass extension validation by using a double URL encoded null byte to read arbitrary files within the webroot.
Business Impact
The ability for an unauthenticated attacker to read arbitrary files, such as wp-config.php, poses a catastrophic risk to business operations. This exposure typically leads to the compromise of database credentials, API keys, and administrative access tokens, which can result in total site takeover and long-term data breach. With a CVSS score of 9.8, this vulnerability represents the highest level of urgency for remediation.
Remediation Plan
Immediate Action: Update the PhastPress plugin to the latest version as soon as a patch is available. If no patch is currently available, deactivate and remove the plugin from the WordPress environment until a secure version is released.
Proactive Monitoring: Review server access logs for requests containing encoded null byte sequences or attempts to access sensitive configuration files like wp-config.php.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block requests containing null bytes or suspicious path traversal patterns to mitigate the risk of exploitation.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of Dec 23, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's reliance on a simple parameter manipulation makes it highly susceptible to automated scanning and exploitation once the technique becomes public knowledge.
Analyst Recommendation
Given the critical CVSS severity and the unauthenticated nature of this vulnerability, immediate action is required. Organizations should prioritize patching this plugin to prevent full compromise of the underlying WordPress environment. If an update is not immediately available, the risk must be mitigated by disabling the plugin to prevent unauthorized access to sensitive system files.
Update The PhastPress plugin for WordPress is vulnerable to Unauthenticated Arbitrary File Read via null byte injection in all versions up Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
The Search Atlas SEO – Premier SEO Plugin for One-Click WP Publishing & Integrated AI Optimization plugin for WordPress is vulnerable to authenticatio...
The Search Atlas SEO – Premier SEO Plugin for One-Click WP Publishing & Integrated AI Optimization plugin for WordPress is vulnerable to authentication bypass due to a missing capability check on the 'generate_sso_url' and 'validate_sso_token' functions in versions 2
Description Summary:
The Search Atlas SEO plugin for WordPress suffers from an authentication bypass vulnerability due to missing capability checks, allowing authenticated users to hijack administrator accounts.
Executive Summary:
The Search Atlas SEO plugin for WordPress is vulnerable to an authentication bypass flaw that allows low-privileged users to compromise administrative accounts.
Vulnerability Details
CVE-ID: CVE-2025-14386
Affected Software: Shahrukh LinkGraph Search Atlas SEO – Premier SEO Plugin for One-Click WP Publishing & Integrated AI Optimization
Affected Versions: 2.4.4 through 2.5.12
Vulnerability: This vulnerability is caused by a missing authorization check (CWE-862) within the generate_sso_url and validate_sso_token functions. Any authenticated user with Subscriber-level access or higher can exploit this flaw to extract a nonce token and gain full administrative access.
Business Impact
This vulnerability carries a high CVSS score of 8.8, reflecting the severe impact of a total account takeover. An attacker who gains administrative access can modify site content, inject malicious scripts, distribute malware to visitors, or fully exfiltrate sensitive site data, resulting in significant reputational damage and operational downtime for the business.
Remediation Plan
Immediate Action: There is currently no confirmed patch available; immediately deactivate and remove the Search Atlas SEO plugin from your WordPress installation until a secure version is released by the vendor.
Proactive Monitoring: Monitor WordPress user logs and database records for unexpected privilege escalations or unusual administrative login activity originating from accounts typically assigned the Subscriber role.
Compensating Controls: Deploy a Web Application Firewall (WAF) with custom rules to block unauthorized access attempts to the specific admin functions identified in the plugin source code.
Exploitation Status
Public Exploit Available: No (exploit_available: false).
Analyst Notes: As of January 30, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While exploitation is not currently observed in the wild, the technical requirements for an attacker are minimal, as they only require a standard subscriber account to initiate the attack.
Analyst Recommendation
Given the critical nature of an administrative authentication bypass, this vulnerability poses a severe risk to WordPress environments. Organizations should prioritize the immediate removal of the affected plugin to prevent unauthorized access. Monitor the vendor's official plugin page for security updates and only restore the service once the developer has confirmed a verified fix has been implemented.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The Booking Calendar plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'dates_to_check' parameter in all versions up to, an...
The Booking Calendar plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'dates_to_check' parameter in all versions up to, and including, 10
Description Summary:
The Booking Calendar plugin for WordPress is susceptible to unauthenticated time-based blind SQL injection via the dates_to_check parameter due to improper input sanitization.
Executive Summary:
A critical SQL injection vulnerability in the Booking Calendar plugin for WordPress allows unauthenticated attackers to extract sensitive database information.
Vulnerability Details
CVE-ID: CVE-2025-14383
Affected Software: wpdevelop Booking Calendar
Affected Versions: 0 through 10.14.8
Vulnerability: The vulnerability is a time-based blind SQL injection (CWE-89) located in the dates_to_check parameter. It allows unauthenticated attackers to manipulate SQL queries and potentially exfiltrate data from the underlying database.
Business Impact
Successful exploitation of this vulnerability can lead to the unauthorized disclosure of sensitive information stored within the WordPress database. Given the CVSS score of 7.5, this high-severity flaw poses a significant risk to data confidentiality, potentially resulting in regulatory non-compliance and reputational damage.
Remediation Plan
Immediate Action: Update the Booking Calendar plugin to the latest version, which includes the necessary escaping and SQL preparation to address the flaw.
Proactive Monitoring: Monitor database query logs for anomalous or high-latency requests that may indicate time-based blind SQL injection attempts.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block malicious SQL injection patterns targeting the dates_to_check parameter.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of December 17, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While exploitation is technically straightforward due to the lack of required authentication, no verified weaponized exploit is currently available in public repositories.
Analyst Recommendation
Organizations utilizing the Booking Calendar plugin must prioritize upgrading to a version beyond 10.14.8 immediately. Because this vulnerability is exploitable by unauthenticated attackers and does not require complex prerequisites, it represents a direct threat to the integrity of the application data. Failure to patch creates a clear pathway for unauthorized data exfiltration.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
The Demo Importer Plus plugin for WordPress is vulnerable to unauthorized modification of data, loss of data, and privilege escalation due to a missin...
The Demo Importer Plus plugin for WordPress is vulnerable to unauthorized modification of data, loss of data, and privilege escalation due to a missing capability check on the Ajax::handle_request() function in all versions up to, and including, 2
Description Summary:
The Demo Importer Plus WordPress plugin suffers from a missing capability check, allowing authenticated attackers to perform unauthorized site resets and elevate their privileges to Administrator.
Executive Summary:
The Demo Importer Plus plugin for WordPress contains a critical authorization flaw that enables authenticated subscribers to perform a full site reset and escalate their privileges to Administrator.
Vulnerability Details
CVE-ID: CVE-2025-14364
Affected Software: kraftplugins Demo Importer Plus
Affected Versions: 0 through 2.0.8
Vulnerability: This vulnerability stems from a missing capability check on the Ajax::handle_request() function, which allows any authenticated user with Subscriber-level access or higher to execute administrative actions. By invoking this function, an attacker can drop database tables and trigger the wp_install() process to grant themselves full administrative control.
Business Impact
The ability for a low-privileged user to achieve full administrative access poses an extreme risk to the integrity and availability of the WordPress environment. With a CVSS score of 8.8, this flaw facilitates complete site compromise, leading to total data loss, unauthorized administrative control, and potential long-term persistence by the attacker.
Remediation Plan
Immediate Action: There is no currently patched version available; administrators should immediately deactivate and remove the Demo Importer Plus plugin from their WordPress environment until a secure update is released.
Proactive Monitoring: Monitor WordPress user logs for suspicious administrative account creation and audit database activity for unexpected table drops or re-installation patterns.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block unauthorized Ajax requests targeting administrative endpoints in third-party plugins.
Exploitation Status
Public Exploit Available: Yes, a public proof-of-concept repository exists on GitHub (Nxploited/CVE-2025-14364).
Analyst Notes: As of December 20, 2025, there is no public information indicating active exploitation in the wild. The vulnerability is highly exploitable due to the trivial nature of the missing authorization check, which requires no specialized knowledge to trigger once an attacker has registered a basic subscriber account.
Analyst Recommendation
Given the severity of this privilege escalation flaw, organizations must prioritize the removal of the vulnerable plugin. The potential for total site takeover and data destruction makes this an urgent security concern for all WordPress administrators utilizing this software.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
Missing Authorization vulnerability in Kaira Blockons blockons allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Bloc...
Missing Authorization vulnerability in Kaira Blockons blockons allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Blockons: from n/a through <= 1.2.15.
Description Summary:
The Blockons WordPress plugin contains a missing authorization vulnerability, allowing unauthenticated attackers to access restricted functionality due to improper ACL enforcement.
Executive Summary:
A missing authorization vulnerability in the Blockons plugin for WordPress allows unauthenticated attackers to access unauthorized functionality, posing a significant risk to site integrity.
Vulnerability Details
CVE-ID: CVE-2025-14360
Affected Software: Kaira Blockons
Affected Versions: 0 through 1.2.19
Vulnerability: The plugin fails to perform adequate capability checks on specific functions, allowing an unauthenticated attacker to invoke restricted actions via the web interface.
Business Impact
Successful exploitation allows unauthorized users to perform actions that should be restricted to administrators or privileged users. Given the high CVSS score of 9.8, the potential for unauthorized data exposure or administrative manipulation is severe, potentially leading to a full site compromise if sensitive functions are accessed.
Remediation Plan
Immediate Action: As no patched version is currently available, administrators should deactivate and uninstall the Blockons plugin until a security update is released by Kaira.
Proactive Monitoring: Review web server and WordPress access logs for anomalous requests directed at plugin-specific API endpoints or unusual administrative actions originating from non-privileged accounts.
Compensating Controls: Implement a Web Application Firewall (WAF) rule to block unauthorized access attempts to known plugin endpoints if the plugin must remain active for critical business operations.
Exploitation Status
Public Exploit Available: No (exploit_available: unknown)
Analyst Notes: As of Jan 8, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently exploitable due to the lack of server-side authorization checks for sensitive functions.
Analyst Recommendation
Due to the critical nature of this authorization flaw and the current lack of a vendor-provided patch, immediate removal of the plugin is the only effective mitigation. Organizations should prioritize identifying alternative solutions or waiting for official confirmation from the vendor that a secure version has been released.
Update Missing Authorization vulnerability in Kaira Blockons blockons allows Accessing Functionality Not Properly Constrained by Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in brandexponents Oshine oshin a...
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in brandexponents Oshine oshin allows PHP Local File Inclusion.This issue affects Oshine: from n/a through <= 7.2.7.
Description Summary:
The Oshine WordPress theme is vulnerable to Local File Inclusion, allowing unauthenticated attackers to include arbitrary files via improper control of filenames in PHP include statements.
Executive Summary:
A critical Local File Inclusion vulnerability in the brandexponents Oshine theme allows unauthenticated attackers to potentially achieve remote code execution and full system compromise.
Vulnerability Details
CVE-ID: CVE-2025-14359
Affected Software: brandexponents Oshine
Affected Versions: n/a up to (excluding) 7.3.0
Vulnerability: This is a PHP Local File Inclusion flaw (CWE-98) occurring within the theme code. It allows an unauthenticated attacker to manipulate file inclusion paths, resulting in unauthorized file access or potential execution of malicious scripts.
Business Impact
The severity of this vulnerability is underscored by its CVSS score of 9.8, indicating a critical risk to the confidentiality, integrity, and availability of the affected environment. Successful exploitation could lead to full site takeover, unauthorized access to sensitive configuration files, and potential remote code execution, posing significant reputational and operational risks to the organization.
Remediation Plan
Immediate Action: Update the Oshine WordPress theme to version 7.3.0 or the latest available release immediately to patch the vulnerable file inclusion mechanism.
Proactive Monitoring: Review web server and application logs for suspicious directory traversal patterns, such as sequences involving dots and slashes, or requests targeting sensitive system files like wp-config.php.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block common Local File Inclusion payloads and directory traversal attempts until the theme update can be applied.
Exploitation Status
Public Exploit Available: No (exploit_available: unknown).
Analyst Notes: As of Jan 8, 2026, there is no public information indicating active exploitation or a published proof-of-concept for this vulnerability. While the vulnerability is critical due to the lack of authentication required, no confirmed exploit code is available in the analyzed data sources.
Analyst Recommendation
Given the critical nature of this vulnerability and the potential for total system compromise, organizations using the Oshine theme must prioritize this update above non-critical maintenance tasks. Failure to patch allows attackers a straightforward path to execute arbitrary code, making immediate remediation essential for maintaining the security posture of the WordPress installation.
Update Improper Control of Filename for Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
Missing Authorization vulnerability in sizam REHub Framework rehub-framework allows Accessing Functionality Not Properly Constrained by ACLs.This issu...
Missing Authorization vulnerability in sizam REHub Framework rehub-framework allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects REHub Framework: from n/a through <= 19.9.5.
Description Summary:
The REHub Framework WordPress plugin is vulnerable to missing authorization, enabling unauthenticated attackers to access restricted functions due to improper access control checks.
Executive Summary:
A critical missing authorization vulnerability in the REHub Framework plugin allows unauthenticated attackers to bypass access controls, potentially leading to unauthorized system actions.
Vulnerability Details
CVE-ID: CVE-2025-14358
Affected Software: sizam REHub Framework
Affected Versions: 0 through 19.9.5
Vulnerability: The plugin fails to validate user capabilities, allowing unauthenticated requests to perform actions intended only for authorized administrative users.
Business Impact
The CVSS score of 9.8 reflects the high risk of unauthorized access. Exploitation can lead to significant business disruption, including the unauthorized modification of site settings or the compromise of sensitive administrative functions, negatively impacting the operational integrity of the host website.
Remediation Plan
Immediate Action: Update the REHub Framework plugin to version 19.9.9.6 or later immediately to resolve the authorization bypass.
Proactive Monitoring: Monitor site activity logs for unauthorized administrative changes or suspicious requests that coincide with the plugin's functionality.
Compensating Controls: Deploy a WAF with virtual patching capabilities to intercept and block malicious requests targeting the vulnerable plugin components.
Exploitation Status
Public Exploit Available: No (exploit_available: unknown)
Analyst Notes: As of Jan 8, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is fundamentally exploitable due to the absence of proper authorization checks for privileged operations.
Analyst Recommendation
The availability of a patched version necessitates an immediate update to version 19.9.9.6. Security teams should prioritize this update across all affected WordPress environments to close the authorization gap and prevent potential unauthorized exploitation.
Update Missing Authorization vulnerability in sizam REHub Framework Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
The ZIP Code Based Content Protection plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 1
The ZIP Code Based Content Protection plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 1
Description Summary:
The ZIP Code Based Content Protection plugin for WordPress contains an unauthenticated SQL injection vulnerability via the zipcode parameter, allowing unauthorized database information extraction.
Executive Summary:
A critical SQL injection vulnerability in the Presstigers ZIP Code Based Content Protection plugin for WordPress allows unauthenticated attackers to extract sensitive database information.
Vulnerability Details
CVE-ID: CVE-2025-14353
Affected Software: Presstigers ZIP Code Based Content Protection
Affected Versions: 0 through 1.0.2
Vulnerability: This vulnerability is a SQL injection flaw (CWE-89) located in the zipcode parameter, caused by insufficient input sanitization and lack of prepared statements. It permits unauthenticated remote attackers to execute arbitrary SQL queries against the underlying database.
Business Impact
The ability for an unauthenticated attacker to inject SQL queries poses a severe risk to data confidentiality, as it enables the unauthorized exfiltration of sensitive information from the WordPress database. With a CVSS score of 7.5, this high-severity flaw could lead to significant data breaches, regulatory non-compliance, and loss of intellectual property if left unaddressed.
Remediation Plan
Immediate Action: Since a specific patched version is not explicitly identified in the provided data, administrators should immediately deactivate and remove the ZIP Code Based Content Protection plugin until a secure update is confirmed by the vendor.
Proactive Monitoring: Review database access logs and query execution logs for anomalous activity or unexpected syntax patterns originating from public-facing endpoints.
Compensating Controls: Deploy a Web Application Firewall (WAF) with updated SQL injection protection rules to block malicious requests targeting the zipcode parameter.
Exploitation Status
Public Exploit Available: No (no confirmed public exploit in the available data).
Analyst Notes: As of March 8, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to its unauthenticated nature and the relative ease of automating SQL injection attacks.
Analyst Recommendation
Given the high CVSS score and the potential for unauthenticated database compromise, organizations must treat this vulnerability with urgency. Administrators should prioritize the removal of the affected plugin from all production environments immediately, as no confirmed patch is currently available to mitigate the underlying code flaw.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
Privilege Defined With Unsafe Actions, Missing Authentication for Critical Function vulnerability in Universal Software Inc
Privilege Defined With Unsafe Actions, Missing Authentication for Critical Function vulnerability in Universal Software Inc
Description Summary:
Universal Software Inc products are affected by a vulnerability involving improper privilege definition and missing authentication for critical functions, potentially allowing unauthorized access.
Executive Summary:
This high-severity vulnerability in Universal Software Inc products poses a significant risk of unauthorized access and privilege escalation due to missing authentication controls.
Vulnerability Details
CVE-ID: CVE-2025-14349
Affected Software: Universal Software Inc Multiple Products
Affected Versions: See vendor advisory for affected versions
Vulnerability: The software fails to implement necessary authentication checks for critical functions and utilizes unsafe privilege definitions. This allows an attacker to interact with sensitive system functions without proper authorization.
Business Impact
With a CVSS score of 8.8, this vulnerability carries a high risk of system compromise. Successful exploitation could allow an attacker to perform administrative actions, leading to full unauthorized control, potential data manipulation, and severe disruption to business operations.
Remediation Plan
Immediate Action: Contact Universal Software Inc support or consult their official security portal to identify if your specific product version is impacted and apply the necessary security patches.
Proactive Monitoring: Review application and system access logs for anomalous activity, specifically looking for unauthorized execution of administrative functions.
Compensating Controls: Implement strict network access control lists (ACLs) to limit exposure of the affected software to trusted internal segments only.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of June 4, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Given the high CVSS score, organizations should prioritize this vulnerability for immediate investigation. Administrators must verify their current software versions against the vendor’s guidance and apply available patches immediately to prevent unauthorized access to critical systems.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
WHILL Model C2 Electric Wheelchairs and Model F Power Chairs do not enforce authentication for Bluetooth connections. An attacker within range can pai...
WHILL Model C2 Electric Wheelchairs and Model F Power Chairs do not enforce authentication for Bluetooth connections. An attacker within range can pair with the device and issue movement commands, override speed restrictions, and manipulate configuration profiles without any credentials or user interaction.
Description Summary:
WHILL Model C2 and Model F wheelchairs fail to enforce Bluetooth authentication, allowing unauthorized attackers within range to remotely control device movement and configuration settings.
Executive Summary:
A critical authentication bypass in WHILL Model C2 and Model F power chairs allows unauthenticated attackers to gain full control over device movement and configuration.
Vulnerability Details
CVE-ID: CVE-2025-14346
Affected Software: WHILL Model C2 Electric Wheelchair and Model F Power Chair
Affected Versions: All versions
Vulnerability: This vulnerability involves a missing authentication mechanism for critical functions (CWE-306) within the Bluetooth interface. An unauthenticated attacker within wireless range can pair with the device to issue arbitrary movement commands, override safety speed limits, and alter device profiles.
Business Impact
This vulnerability presents a severe physical safety risk to users, as the lack of authentication allows for the unauthorized manipulation of medical mobility hardware. With a CVSS score of 9.8, the potential for malicious control over critical device functions necessitates immediate attention to mitigate the risk of injury or device misuse.
Remediation Plan
Immediate Action: Consult the official CISA ICS medical advisory (ICSMA-25-364-01) and the manufacturer for specific firmware updates or safety guidance, as no specific patch version is currently identified.
Proactive Monitoring: Users and caregivers should monitor for unexpected Bluetooth pairing requests or erratic device behavior that may indicate unauthorized connection attempts.
Compensating Controls: If a software patch is unavailable, minimize the risk by ensuring the device is stored in secure environments and disabling Bluetooth functionality if the specific model configuration allows for such a modification.
Exploitation Status
Public Exploit Available: exploit_available (unknown)
Analyst Notes: As of Jan 5, 2026, there is no public information indicating active exploitation or a published proof-of-concept for this vulnerability. While the flaw is highly accessible due to the nature of Bluetooth, there is no confirmed evidence of weaponized exploitation at this time.
Analyst Recommendation
The severity of this vulnerability is extreme due to the direct impact on physical safety and the total loss of control over the affected hardware. Users are urged to prioritize communication with WHILL to identify and apply any available safety updates or operational mitigations provided by the vendor.
Update WHILL Model Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
The Multi Uploader for Gravity Forms plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'pl...
The Multi Uploader for Gravity Forms plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'plupload_ajax_delete_file' function in all versions up to, and including, 1.1.7. This makes it possible for unauthenticated attackers to delete arbitrary files on the server.
Description Summary:
The Multi Uploader for Gravity Forms plugin for WordPress is vulnerable to arbitrary file deletion via path traversal in the plupload_ajax_delete_file function, allowing unauthenticated file removal.
Executive Summary:
An unauthenticated arbitrary file deletion vulnerability in the Multi Uploader for Gravity Forms plugin poses a critical risk of complete system compromise.
Vulnerability Details
CVE-ID: CVE-2025-14344
Affected Software: sh1zen Multi Uploader for Gravity Forms
Affected Versions: 0 through 1.1.7
Vulnerability: The vulnerability is a path traversal flaw (CWE-22) located in the plupload_ajax_delete_file function, which lacks sufficient validation of file paths. This allows any unauthenticated attacker to delete arbitrary files on the hosting server.
Business Impact
The ability for an unauthenticated attacker to delete arbitrary files on a web server represents a critical business risk, potentially leading to total service disruption, loss of data, or the deletion of critical configuration files required for system operation. With a CVSS score of 9.8, this vulnerability is classified as critical due to the high impact on availability and the lack of required authentication.
Remediation Plan
Immediate Action: Administrators should immediately deactivate or remove the Multi Uploader for Gravity Forms plugin until a vendor-supplied patch is confirmed and applied.
Proactive Monitoring: Review server access logs for anomalous requests targeting the plupload_ajax_delete_file endpoint, specifically looking for path traversal patterns such as directory climbing sequences.
Compensating Controls: Implement a Web Application Firewall (WAF) rule to block requests containing directory traversal characters (e.g., ../) directed at the plugin's AJAX endpoints.
Exploitation Status
Public Exploit Available: exploit_available (unknown).
Analyst Notes: As of Dec 15, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous because it allows unauthenticated actors to interact directly with the server filesystem, bypassing standard access controls.
Analyst Recommendation
This vulnerability is highly severe and requires immediate attention to prevent unauthorized file deletion. Given the lack of a clear patch version in the provided data, the most secure course of action is to stop using the plugin immediately. Administrators must prioritize the removal or containment of this software to protect the integrity and availability of the underlying server environment.
Update The Multi Uploader for Gravity Forms plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Dokuzsoft Technology Ltd
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Dokuzsoft Technology Ltd
Description Summary:
A reflected cross-site scripting (XSS) vulnerability in Dokuzsoft Technology E-Commerce Product allows unauthenticated attackers to execute malicious scripts in a user's browser.
Executive Summary:
Dokuzsoft Technology E-Commerce Product contains a reflected cross-site scripting vulnerability that could allow unauthenticated attackers to execute arbitrary scripts in the context of a victim session.
Vulnerability Details
CVE-ID: CVE-2025-14343
Affected Software: Dokuzsoft Technology E-Commerce Product
Affected Versions: 0 through 10122025
Vulnerability: This is a reflected cross-site scripting (XSS) vulnerability (CWE-79) triggered by improper input sanitization during web page generation. An unauthenticated attacker can leverage this flaw to inject malicious scripts into the application, which are then executed within the browser of a victim who clicks a crafted link.
Business Impact
Successful exploitation of this vulnerability can lead to session hijacking, unauthorized actions performed on behalf of a user, or the theft of sensitive information displayed on the affected web page. Given the CVSS score of 7.6, this is a high-severity issue that poses a significant risk to user trust and data confidentiality, particularly if administrative users are targeted.
Remediation Plan
Immediate Action: Review the official security notifications from USOM (TR-26-0083) to determine if a patch has been released for your specific deployment. If no patch is available, restrict access to the web application and implement strict input validation on all user-supplied parameters.
Proactive Monitoring: Monitor web server access logs for anomalous URL patterns containing script tags or suspicious JavaScript event handlers. Review logs for high volumes of traffic originating from unexpected sources that target web parameters.
Compensating Controls: Deploy a Web Application Firewall (WAF) with updated rulesets to detect and block common XSS injection patterns. Configure Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser.
Exploitation Status
Public Exploit Available: No — exploit_available (unknown).
Analyst Notes: As of February 28, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability relies on user interaction, which slightly reduces the risk of automated mass exploitation.
Analyst Recommendation
This reflected XSS vulnerability represents a significant risk to application integrity and user security. Security teams should prioritize identifying whether their version of the Dokuzsoft E-Commerce Product falls within the vulnerable range and apply any available vendor updates immediately. In the absence of a vendor patch, utilize WAF rules to mitigate potential injection attempts until a formal resolution is implemented.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Improperly controlled modification of Dynamically-Determined object attributes, Allocation of resources without limits or throttling vulnerability in...
Improperly controlled modification of Dynamically-Determined object attributes, Allocation of resources without limits or throttling vulnerability in DivvyDrive Information Technologies Inc
Description Summary:
DivvyDrive is vulnerable to improper modification of dynamically determined object attributes and unrestricted resource allocation, allowing potential flooding and excessive consumption.
Executive Summary:
An improper object attribute modification and resource allocation vulnerability in DivvyDrive exposes organizations to potential unauthorized modifications and denial of service conditions.
Vulnerability Details
CVE-ID: CVE-2025-14341
Affected Software: DivvyDrive Information Technologies Inc DivvyDrive
Affected Versions: DivvyDrive 4.8.2.19 up to (excluding) 4.8.3.2
Vulnerability: This issue encompasses CWE-915 (Improperly controlled modification of Dynamically-Determined object attributes) and CWE-770 (Allocation of resources without limits or throttling). The attack vector is network-based with low attack complexity, requiring user interaction and no attacker privileges.
Business Impact
A successful exploit of these vulnerabilities can lead to integrity violations through unauthorized attribute modifications, as well as availability impacts via resource exhaustion and flooding. Given the CVSS score of 8.3, this high severity flaw poses a significant risk to operational continuity and data integrity, potentially resulting in system downtime and unauthorized data state changes.
Remediation Plan
Immediate Action: Update DivvyDrive to version 4.8.3.2 or later as soon as patches are made available by the vendor.
Proactive Monitoring: Monitor system resource utilization, network traffic patterns, and application logs for unusual flooding activity or unauthorized attribute modification attempts.
Compensating Controls: Implement Web Application Firewall (WAF) rules to inspect and filter suspicious requests targeting object modification endpoints, alongside rate limiting to mitigate potential resource exhaustion.
Exploitation Status
Public Exploit Available: false
Analyst Notes: As of May 9, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The CISA SSVC assessment lists exploitation as none, but the high CVSS vector requires treating the underlying architecture with heightened scrutiny.
Analyst Recommendation
Security teams must treat CVE-2025-14341 with high priority due to its severe CVSS rating of 8.3 and potential for significant operational disruption. Administrators should verify vendor advisory channels for the immediate deployment of version 4.8.3.2 or higher to secure the affected DivvyDrive deployments.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Memory safety bugs present in Firefox ESR 140
Memory safety bugs present in Firefox ESR 140
Description Summary:
Mozilla Firefox and Thunderbird contain memory safety bugs that could allow an attacker to trigger memory corruption and achieve arbitrary code execution.
Executive Summary:
Critical memory safety vulnerabilities in Mozilla Firefox and Thunderbird could allow remote attackers to execute arbitrary code via memory corruption.
Vulnerability Details
CVE-ID: CVE-2025-14333
Affected Software: Mozilla Firefox and Mozilla Thunderbird
Affected Versions: Firefox 140.5, 145; Thunderbird 140.5, 145
Vulnerability: These memory safety bugs involve potential memory corruption within the browser engine, which could be exploited by an unauthenticated remote attacker to run arbitrary code. The vulnerability is triggered through standard browser interactions where the attacker presumes the ability to manipulate memory state to bypass security controls.
Business Impact
The potential for arbitrary code execution poses a severe risk to organizational security, as it could lead to full system compromise, data theft, or the installation of persistent malware. With a CVSS score of 8.1, these vulnerabilities are categorized as High severity, reflecting the significant danger posed by flaws that enable remote code execution on end-user workstations.
Remediation Plan
Immediate Action: Update Mozilla Firefox and Mozilla Thunderbird to version 140.6 or 146 immediately to apply the necessary memory safety patches.
Proactive Monitoring: Review endpoint security logs for signs of anomalous process crashes or unexpected binary execution associated with browser components.
Compensating Controls: Ensure that browser-based security policies, such as disabling unnecessary plugins or enforcing sandboxing, are strictly configured to limit the reach of potential exploits.
Exploitation Status
Public Exploit Available: No — there is no confirmed public exploit available.
Analyst Notes: As of December 10, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the bugs are inherently dangerous due to their potential for arbitrary code execution, they remain largely theoretical in terms of public weaponization at this time.
Analyst Recommendation
Given the severity of memory corruption flaws, organizations must prioritize patching these browser versions across their environments. Failure to update allows for a critical attack vector that bypasses standard perimeter defenses, necessitating immediate deployment of the vendor-supplied security releases to maintain a secure posture.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Privilege escalation in the Netmonitor component
Privilege escalation in the Netmonitor component
Description Summary:
A privilege escalation vulnerability exists in the Netmonitor component of Mozilla Firefox and Thunderbird, potentially allowing an attacker to gain elevated permissions.
Executive Summary:
A critical privilege escalation flaw in the Netmonitor component of Mozilla Firefox and Thunderbird exposes users to potential security compromises and requires immediate updates.
Vulnerability Details
CVE-ID: CVE-2025-14329
Affected Software: Mozilla Firefox and Mozilla Thunderbird
Affected Versions: Versions prior to 140.6 and 146
Vulnerability: This is a privilege escalation vulnerability within the Netmonitor component. Based on the CVSS vector (PR:N, UI:R), the attack is unauthenticated but requires user interaction to exploit.
Business Impact
The vulnerability carries a CVSS score of 8.8, indicating a high severity risk that could lead to full system compromise if exploited. Successful exploitation allows an attacker to gain unauthorized privileges, potentially resulting in data exfiltration, the installation of malicious software, or unauthorized control over the affected application.
Remediation Plan
Immediate Action: Update Mozilla Firefox and Thunderbird to version 146 or the ESR version 140.6 immediately to apply the necessary security patches.
Proactive Monitoring: Review browser and application logs for unusual Netmonitor activity or unexpected privilege changes within the application environment.
Compensating Controls: Ensure that users operate with the principle of least privilege, limiting the potential impact of an application-level compromise on the underlying operating system.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of December 10, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's requirement for user interaction provides a slight barrier to entry, but the potential for total impact makes patching essential.
Analyst Recommendation
Given the high CVSS score and the nature of privilege escalation, this vulnerability poses a significant risk to organizational endpoints. Security teams should prioritize the deployment of the Mozilla updates across all managed devices. Failure to patch these applications leaves users vulnerable to potential code execution and system-wide security breaches.
Update to patched version immediately. Review user permissions and access controls.
Privilege escalation in the Netmonitor component
Privilege escalation in the Netmonitor component
Description Summary:
A privilege escalation vulnerability exists in the Netmonitor component of Mozilla Firefox and Thunderbird, potentially allowing an attacker to gain elevated control.
Executive Summary:
A critical privilege escalation vulnerability in the Netmonitor component of Mozilla Firefox and Thunderbird exposes users to potential system compromise.
Vulnerability Details
CVE-ID: CVE-2025-14328
Affected Software: Mozilla Firefox and Mozilla Thunderbird
Affected Versions: Versions prior to 140.6 and 146
Vulnerability: The vulnerability exists within the Netmonitor component of the affected applications. Based on the CVSS vector (AV:N/AC:L/PR:N/UI:R), this flaw can be triggered by an unauthenticated attacker through user interaction.
Business Impact
The vulnerability carries a CVSS score of 8.8, indicating a high level of risk to organizational security. Successful exploitation could lead to unauthorized privilege escalation, allowing an attacker to bypass security boundaries, access sensitive data, or perform actions with the permissions of the affected user, potentially resulting in significant reputational damage and data loss.
Remediation Plan
Immediate Action: Update Mozilla Firefox and Mozilla Thunderbird to version 140.6 or 146, or the latest available stable release, to apply the necessary security fixes.
Proactive Monitoring: Monitor endpoint security logs for unusual process execution patterns or unauthorized attempts to access sensitive system files following browser updates.
Compensating Controls: Ensure that endpoint protection software is active and configured to block malicious scripts, and enforce the principle of least privilege for all local user accounts to limit the potential impact of successful escalation.
Exploitation Status
Public Exploit Available: No (exploit_available: false)
Analyst Notes: As of December 10, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the vulnerability is highly severe, the requirement for user interaction provides a slight barrier to immediate exploitation.
Analyst Recommendation
Given the high CVSS score and the critical nature of privilege escalation flaws in web browsers, immediate remediation is required. Organizations should prioritize patching all instances of Firefox and Thunderbird across their infrastructure to eliminate this exposure and prevent potential exploitation by malicious actors.
Update to patched version immediately. Review user permissions and access controls.
Spoofing issue in the Downloads Panel component
Spoofing issue in the Downloads Panel component
Description Summary:
A spoofing vulnerability exists in the Downloads Panel component of Mozilla Firefox and Thunderbird, potentially allowing attackers to deceive users regarding file origin or safety.
Executive Summary:
A high-severity spoofing vulnerability in the Downloads Panel of Mozilla Firefox and Thunderbird allows unauthenticated attackers to manipulate interface elements to deceive users.
Vulnerability Details
CVE-ID: CVE-2025-14327
Affected Software: Mozilla Firefox and Mozilla Thunderbird
Affected Versions: Versions prior to 140.7 or 146
Vulnerability: The flaw resides in the Downloads Panel, which fails to properly validate or render content, allowing an unauthenticated remote attacker to spoof information. This vulnerability is triggered via network interaction with the affected software.
Business Impact
The ability to spoof information within the browser or email client interface poses a significant risk to user security and organizational integrity. By deceiving users about the nature of downloaded files, attackers may facilitate social engineering campaigns, leading to the execution of malicious software or the compromise of sensitive credentials. With a CVSS score of 7.5, this vulnerability represents a high risk that could lead to unauthorized system access or data loss if successfully exploited.
Remediation Plan
Immediate Action: Update Mozilla Firefox and Mozilla Thunderbird to version 146 or the ESR version 140.7 immediately to incorporate the vendor security patches.
Proactive Monitoring: Review security logs for unusual activity related to browser or email client interactions and monitor for reports of suspicious file download prompts.
Compensating Controls: Implement endpoint security solutions and email filtering gateways to detect and block malicious payloads that may be delivered via spoofed download notifications.
Exploitation Status
Public Exploit Available: No (exploit_available: false)
Analyst Notes: As of December 11, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is inherently exploitable by any remote user who can induce a target to interact with the malicious content, making it a critical item for patch management cycles.
Analyst Recommendation
Given the high CVSS score and the potential for wide-scale social engineering, organizations must prioritize the deployment of the provided patches. Administrators should ensure that all instances of Firefox and Thunderbird are updated to the fixed versions across the enterprise to eliminate the risk of interface spoofing and subsequent user deception.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Privilege escalation in the DOM: Notifications component
Privilege escalation in the DOM: Notifications component
Description Summary:
A privilege escalation vulnerability exists in the Notifications component of the DOM in Mozilla Firefox and Thunderbird, potentially allowing an attacker to gain elevated privileges.
Executive Summary:
A critical privilege escalation vulnerability in Mozilla Firefox and Thunderbird could allow an attacker to bypass security controls and gain unauthorized elevated access.
Vulnerability Details
CVE-ID: CVE-2025-14323
Affected Software: Mozilla Firefox and Mozilla Thunderbird
Affected Versions: Versions prior to 146, 115.31 (ESR), and 140.6 (ESR)
Vulnerability: The flaw resides in the DOM Notifications component, which fails to properly enforce privilege boundaries. Exploitation requires user interaction via a network-based vector, allowing an unauthenticated remote attacker to gain elevated privileges within the application context.
Business Impact
Successful exploitation of this vulnerability can lead to a complete compromise of the affected client application, potentially resulting in unauthorized data access or the execution of arbitrary code within the user session. Given the CVSS score of 8.8, this vulnerability represents a significant risk to organizational endpoints, necessitating immediate attention to prevent potential system-wide security breaches.
Remediation Plan
Immediate Action: Update Mozilla Firefox and Thunderbird to version 146 or higher, or the applicable Extended Support Release (ESR) versions 115.31 or 140.6, to apply the necessary security patches.
Proactive Monitoring: Monitor endpoint security logs for unusual process execution or attempts to access restricted system resources originating from the browser or email client.
Compensating Controls: While no direct virtual patch exists, enforcing strict browser security policies and limiting user permissions on local workstations can reduce the potential blast radius of an exploited client-side application.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of December 10, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is considered highly exploitable due to the nature of DOM-based components, requiring only standard user interaction to trigger.
Analyst Recommendation
Organizations must prioritize the deployment of the provided security updates across all managed instances of Firefox and Thunderbird. Because this vulnerability allows for privilege escalation, delay in patching increases the risk of successful weaponization by threat actors who may target vulnerable browsers for initial access or lateral movement.
Update to patched version immediately. Review user permissions and access controls.
Sandbox escape due to incorrect boundary conditions in the Graphics: CanvasWebGL component
Sandbox escape due to incorrect boundary conditions in the Graphics: CanvasWebGL component
Description Summary:
A sandbox escape vulnerability exists in the Graphics: CanvasWebGL component of Mozilla Firefox and Thunderbird, potentially allowing attackers to bypass security restrictions.
Executive Summary:
A critical sandbox escape vulnerability in Mozilla Firefox and Thunderbird allows remote attackers to bypass security boundaries, creating a significant risk of system compromise.
Vulnerability Details
CVE-ID: CVE-2025-14322
Affected Software: Mozilla Firefox and Mozilla Thunderbird
Affected Versions: Firefox before 146, Firefox ESR before 115.31, Firefox ESR before 140.6, Thunderbird before 146, and Thunderbird before 140.6.
Vulnerability: The flaw is an incorrect boundary condition in the Graphics: CanvasWebGL component. This vulnerability is remotely exploitable and does not require authentication, though it does require user interaction to trigger.
Business Impact
Successful exploitation of this sandbox escape allows an attacker to break out of the browser security sandbox, potentially leading to unauthorized execution of code on the underlying host operating system. Given the CVSS score of 8.0, this represents a high-severity risk that could lead to full system compromise, data exfiltration, or the installation of persistent malicious software.
Remediation Plan
Immediate Action: Update all instances of Mozilla Firefox and Thunderbird to the versions specified in the vendor security advisories (MFSA 2025-92 through 2025-96) to apply the necessary security patches.
Proactive Monitoring: Monitor endpoint security logs for unusual process execution patterns or unexpected child processes originating from the browser or email client.
Compensating Controls: Ensure that systems are running with the principle of least privilege, as this limits the potential impact of a successful sandbox escape if the user account does not have administrative rights.
Exploitation Status
Public Exploit Available: No (exploit_available: unknown)
Analyst Notes: As of December 10, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. While the vulnerability is complex due to the requirement for user interaction, the potential for sandbox escape makes it a high-priority target for remediation.
Analyst Recommendation
The severity of this flaw necessitates immediate attention. IT administrators should prioritize the deployment of the latest updates for Firefox and Thunderbird across all managed workstations to eliminate the sandbox escape vector. Failure to update leaves the host environment vulnerable to potential remote code execution attacks initiated through web or email content.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Tegsoft Management and Information Services Trad...
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Tegsoft Management and Information Services Trade Limited Company Online Support Application allows Reflected XSS. This issue affects Online Support Application: from V3 through 31122025.
Description Summary:
A reflected cross-site scripting (XSS) vulnerability in the Tegsoft Online Support Application allows attackers to execute arbitrary scripts in a user's browser.
Executive Summary:
The Tegsoft Online Support Application is vulnerable to reflected XSS, which could allow attackers to execute malicious scripts against users of the platform.
Vulnerability Details
CVE-ID: CVE-2025-14320
Affected Software: Tegsoft Online Support Application
Affected Versions: V3 through 31122025
Vulnerability: The application fails to properly neutralize user-supplied input during web page generation, leading to a reflected XSS vulnerability. This allows an attacker to inject malicious JavaScript into a URL or request, which is then executed in the context of the victim's session.
Business Impact
A CVSS score of 9.8 indicates a critical risk, as XSS can be used to hijack user sessions, steal sensitive session cookies, or redirect users to malicious sites. This compromise can lead to full account takeover and unauthorized access to support data, resulting in significant reputational and operational harm.
Remediation Plan
Immediate Action: Consult the vendor for the latest security release or patch addressing input neutralization in the Online Support Application.
Proactive Monitoring: Monitor web server logs for suspicious URL parameters containing script tags or encoded characters typical of XSS payloads.
Compensating Controls: Deploy a Web Application Firewall (WAF) configured with rules to detect and block common cross-site scripting attack patterns.
Exploitation Status
Public Exploit Available: Not specified
Analyst Notes: As of May 4, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
Reflected XSS is a common but dangerous vector. Users of the Tegsoft Online Support Application should restrict access to the affected web interfaces until a patch is applied and verify that all user inputs are properly sanitized by the application framework.
Update Infor Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
The AhaChat Messenger Marketing WordPress plugin through 1
The AhaChat Messenger Marketing WordPress plugin through 1
Description Summary:
The AhaChat Messenger Marketing WordPress plugin is vulnerable to reflected Cross-Site Scripting (XSS) due to insufficient input sanitization, allowing attackers to target high-privilege users.
Executive Summary:
A reflected Cross-Site Scripting vulnerability in the AhaChat Messenger Marketing plugin for WordPress exposes administrators to potential account compromise and unauthorized actions.
Vulnerability Details
CVE-ID: CVE-2025-14316
Affected Software: AhaChat Messenger Marketing WordPress Plugin
Affected Versions: 0 through 1.1
Vulnerability: This flaw is a Reflected Cross-Site Scripting (CWE-79) vulnerability where a parameter is output to the page without proper sanitization or escaping. The vulnerability can be triggered by an unauthenticated attacker, potentially allowing the execution of malicious scripts in the context of a high-privilege user session, such as an administrator.
Business Impact
The ability for an attacker to execute arbitrary scripts in an administrator's browser poses a significant risk of account takeover, unauthorized configuration changes, and the exfiltration of sensitive site data. With a CVSS score of 7.1, this vulnerability is classified as High severity, necessitating immediate attention to prevent potential site defacement or full administrative compromise.
Remediation Plan
Immediate Action: There is currently no confirmed patch available; administrators should deactivate and remove the AhaChat Messenger Marketing plugin from their WordPress environment until an official security update is released by the vendor.
Proactive Monitoring: Monitor server logs for unusual HTTP requests containing script tags or suspicious URL parameters directed at the WordPress dashboard.
Compensating Controls: Deploy a Web Application Firewall (WAF) configured with aggressive XSS filtering rules to inspect incoming traffic for malicious payloads targeting the plugin's endpoints.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of January 27, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The flaw is inherently dangerous due to its ability to bypass authentication requirements and target administrative sessions.
Analyst Recommendation
Given the High severity rating and the existence of a proof-of-concept, users must prioritize the removal or containment of the AhaChat Messenger Marketing plugin. Administrators should conduct a thorough audit of their WordPress installations to ensure no remnants of this plugin remain, as the risk of administrative account compromise outweighs the operational benefits of the tool until a secure version is provided.
Update WordPress plugin/theme to the latest version. Review WordPress security settings and remove if no longer needed.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Roxnor PopupKit popup-builder-block allows Blind...
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Roxnor PopupKit popup-builder-block allows Blind SQL Injection
Description Summary:
Roxnor PopupKit contains a blind SQL injection vulnerability in the popup-builder-block component that allows authenticated attackers to extract data from the database.
Executive Summary:
A blind SQL injection vulnerability in Roxnor PopupKit version 2.1.5 and earlier poses a high risk of sensitive data exposure for affected WordPress environments.
Vulnerability Details
CVE-ID: CVE-2025-14314
Affected Software: Roxnor PopupKit
Affected Versions: 0 through 2.1.5
Vulnerability: The plugin fails to properly sanitize user-supplied input within the popup-builder-block component, leading to a blind SQL injection. The CVSS vector (PR:L) indicates that an authenticated user with low privileges can trigger this flaw to perform unauthorized database operations.
Business Impact
Successful exploitation of this vulnerability allows an attacker to perform blind SQL injection, potentially leading to the unauthorized exfiltration of sensitive information from the underlying database. With a CVSS score of 8.5, this high-severity flaw represents a significant risk to data confidentiality and integrity, which could result in severe regulatory non-compliance and reputational damage.
Remediation Plan
Immediate Action: Since no specific patch version is currently confirmed, administrators should monitor the official Roxnor repository for updates and disable the PopupKit plugin if it is not business-critical.
Proactive Monitoring: Security teams should monitor database logs for anomalous query patterns, specifically those containing SQL syntax or unusual function calls originating from the application layer.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection patterns targeting WordPress plugins.
Exploitation Status
Public Exploit Available: No — there is no confirmed public exploit in the available data.
Analyst Notes: As of December 19, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw's requirement for low-privileged authentication slightly limits the attack surface, but the potential for blind data extraction remains a serious concern.
Analyst Recommendation
Given the high CVSS score of 8.5, organizations using Roxnor PopupKit must treat this vulnerability with urgency. Until a vendor-supplied patch is released and applied, administrators should restrict access to the affected features or deactivate the plugin to prevent potential exploitation by authenticated users.
Apply vendor patches immediately. Review database access controls and enable query logging.
NULL Pointer Dereference vulnerability in ravynsoft ravynos
NULL Pointer Dereference vulnerability in ravynsoft ravynos
Description Summary:
A NULL pointer dereference vulnerability in ravynsoft ravynos allows for potential denial of service via unauthenticated network access.
Executive Summary:
A NULL pointer dereference vulnerability in ravynsoft ravynos poses a significant denial of service risk to affected systems.
Vulnerability Details
CVE-ID: CVE-2025-14309
Affected Software: ravynsoft ravynos
Affected Versions: ravynsoft ravynos: 0 through 0.5.2
Vulnerability: The software contains a NULL pointer dereference flaw (CWE-476) that can be triggered by an unauthenticated remote attacker, resulting in a crash of the affected service.
Business Impact
The vulnerability carries a CVSS score of 7.5, indicating a high severity due to the ease of exploitation and the potential for service disruption. Successful exploitation results in a denial of service, which can lead to system downtime, operational impairment, and loss of availability for critical business functions.
Remediation Plan
Immediate Action: Review the official project repository for the fix commit 7b52bea467b8a65e24e1beae56df73bff95a95cd and apply the necessary code changes or update to the next stable release once provided by the vendor.
Proactive Monitoring: Monitor system logs for unexpected service crashes or recurring application errors that may indicate exploitation attempts.
Compensating Controls: Implement network-level filtering or rate limiting to restrict access to the vulnerable service, reducing the exposure to external unauthenticated traffic.
Exploitation Status
Public Exploit Available: No — there is no confirmed public exploit in the available data.
Analyst Notes: As of December 11, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is considered inherently exploitable due to the lack of required authentication, but no weaponized code has been identified.
Analyst Recommendation
Given the high CVSS score and the potential for unauthenticated denial of service, administrators should prioritize this issue. While a specific versioned patch is not yet explicitly documented beyond the fix commit, ensuring the environment is updated to the latest available source code is essential to mitigate the risk of service interruption.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
ListCheck
ListCheck
Description Summary:
A local privilege escalation vulnerability in Acer ListCheck.exe allows authenticated local attackers to replace the executable with a malicious file, resulting in arbitrary code execution as the system.
Executive Summary:
The Acer ListCheck.exe utility contains a local privilege escalation vulnerability that enables authenticated attackers to execute malicious code with system level privileges.
Vulnerability Details
CVE-ID: CVE-2025-14305
Affected Software: Acer ListCheck.exe
Affected Versions: 0 through 4.0.0.1
Vulnerability: The vulnerability stems from incorrect authorization (CWE-863), where a local authenticated attacker can replace the legitimate ListCheck.exe file with a malicious version. Because the system subsequently executes this file, the attacker gains elevated privileges.
Business Impact
This vulnerability poses a significant risk to system integrity and security. By successfully exploiting this flaw, a local attacker can move from a standard user account to full system control, potentially compromising sensitive data, installing persistent backdoors, or disabling security software. Given the CVSS score of 7.8, this is classified as a High severity issue that requires immediate attention to prevent unauthorized administrative access.
Remediation Plan
Immediate Action: As the software is no longer maintained, the recommended remediation is to delete the ListCheck.exe program from all systems immediately.
Proactive Monitoring: Security teams should monitor for unauthorized file modifications in directories where legacy tools are stored and review system logs for unexpected execution of binaries.
Compensating Controls: Implement strict file system permissions and host based intrusion detection systems to prevent non-privileged users from modifying or replacing critical executable files.
Exploitation Status
Public Exploit Available: No.
Analyst Notes: As of December 18, 2025, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently exploitable by any user with local access who can modify the specific directory where the application resides.
Analyst Recommendation
Because Acer has confirmed that ListCheck.exe is no longer maintained, no security patch will be released for this product. Organizations should prioritize the identification and removal of this utility from all company assets to eliminate the risk of privilege escalation. Failure to remove the software leaves the system permanently susceptible to this local attack vector.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
The Integration Opvius AI for WooCommerce plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.3.0. This is du...
The Integration Opvius AI for WooCommerce plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.3.0. This is due to the `process_table_bulk_actions()` function processing user-supplied file paths without authentication checks, nonce verification, or path validation. This makes it possible for unauthenticated attackers to delete or download arbitrary files on the server via the `wsaw-log[]` POST parameter, which can be leveraged to delete critical files like `wp-config.php` or read sensitive configuration files.
Description Summary:
The Integration Opvius AI for WooCommerce plugin for WordPress is vulnerable to unauthenticated path traversal, allowing arbitrary file deletion or disclosure via the wsaw-log[] parameter.
Executive Summary:
An unauthenticated path traversal vulnerability in the Integration Opvius AI for WooCommerce plugin enables attackers to remotely delete or read sensitive server files, posing a critical security risk.
Vulnerability Details
CVE-ID: CVE-2025-14301
Affected Software: Woosa Integration Opvius AI for WooCommerce
Affected Versions: 0 through 1.3.0
Vulnerability: The vulnerability exists in the process_table_bulk_actions() function, which fails to perform authentication checks or path validation on user-supplied input. This allows unauthenticated attackers to manipulate the wsaw-log[] POST parameter to perform path traversal attacks, leading to unauthorized file access or deletion.
Business Impact
The ability to read or delete arbitrary files, such as wp-config.php, can lead to complete site takeover, database credential theft, and permanent data loss. Given the CVSS score of 9.8, this vulnerability is classified as critical, as it requires no user interaction or authentication to achieve full system compromise.
Remediation Plan
Immediate Action: Since a specific patched version is not confirmed in the provided data, administrators should immediately deactivate and uninstall the Integration Opvius AI for WooCommerce plugin until a fix is verified.
Proactive Monitoring: Review web server access logs for suspicious POST requests containing path traversal sequences or attempts to access restricted configuration files.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block directory traversal attempts and restrict access to the underlying vulnerable plugin endpoints.
Exploitation Status
Public Exploit Available: Unknown.
Analyst Notes: As of Jan 14, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is highly exploitable due to the total lack of authentication controls and the ability to target sensitive system files.
Analyst Recommendation
This vulnerability presents a severe risk to the integrity and availability of the hosting environment. Because the flaw allows unauthenticated attackers to execute destructive actions on the server, immediate removal of the affected plugin is the only effective way to eliminate the attack surface until the vendor releases a verified security update.
Update The Integration Opvius AI for WooCommerce plugin for WordPress is vulnerable to Path Traversal in all versions up Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
A command injection vulnerability exists in mlflow/mlflow versions before v3
A command injection vulnerability exists in mlflow/mlflow versions before v3
Description Summary:
A command injection vulnerability in MLflow versions before 3.7.0 allows local attackers to execute arbitrary system commands via malicious container image names.
Executive Summary:
A critical command injection vulnerability in MLflow allows authenticated local attackers to execute arbitrary code on the host system, posing a significant risk to CI/CD and deployment environments.
Vulnerability Details
CVE-ID: CVE-2025-14287
Affected Software: MLflow
Affected Versions: Versions before 3.7.0
Vulnerability: The vulnerability exists in the mlflow/sagemaker/__init__.py file, where user-supplied container image names are passed directly into os.system() shell commands without sanitization. An attacker with local access can exploit this by providing a malicious string through the --container parameter of the MLflow CLI.
Business Impact
The ability to execute arbitrary commands on a system running MLflow can lead to full system compromise, data theft, and unauthorized manipulation of machine learning models. Given the CVSS score of 7.5, this high-severity flaw threatens the integrity of CI/CD pipelines and cloud deployment infrastructures, potentially allowing attackers to pivot deeper into the corporate network.
Remediation Plan
Immediate Action: Update MLflow to version 3.8.0rc0 or later to include the necessary input sanitization fixes.
Proactive Monitoring: Audit logs for the MLflow CLI, specifically monitoring for unusual characters or shell syntax within the --container parameter inputs.
Compensating Controls: Restrict access to the MLflow CLI to authorized users only and implement strict input validation at the application layer if an immediate update is not feasible.
Exploitation Status
Public Exploit Available: Yes, a public proof-of-concept exists as documented in the Huntr security bounty report.
Analyst Notes: As of March 18, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is highly exploitable due to the direct usage of unsanitized user input in a system execution function.
Analyst Recommendation
This vulnerability presents a clear path for arbitrary command execution, which could result in a total compromise of the affected MLflow environment. It is imperative that security teams verify their MLflow deployment versions immediately and apply the 3.8.0rc0 patch to mitigate this risk. Priority should be given to protecting systems used within CI/CD pipelines and cloud-based production environments.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
MLFlow versions up to and including 3
MLFlow versions up to and including 3
Description Summary:
MLFlow versions up to 3.4.0 are vulnerable to DNS rebinding attacks due to missing Origin header validation in the REST server, allowing unauthorized operations against experiment endpoints.
Executive Summary:
A critical security vulnerability in MLFlow allows unauthenticated attackers to bypass Same-Origin Policy protections through DNS rebinding, enabling unauthorized manipulation or exfiltration of experiment data.
Vulnerability Details
CVE-ID: CVE-2025-14279
Affected Software: MLFlow
Affected Versions: Up to (excluding) 3.5.0
Vulnerability: The vulnerability is caused by a failure to validate the Origin header in the MLFlow REST server, which exposes the system to DNS rebinding attacks. This flaw allows an unauthenticated attacker to execute unauthorized REST API calls, including querying, updating, or deleting sensitive experiment data.
Business Impact
The exploitation of this vulnerability could lead to the complete compromise of machine learning experiment data, including the destruction or unauthorized modification of proprietary models and datasets. Given the CVSS score of 8.1, the risk of data exfiltration and integrity loss is significant, potentially resulting in severe operational disruption and loss of intellectual property.
Remediation Plan
Immediate Action: Update the MLFlow installation to version 3.5.0 or later to implement the required Origin header validation.
Proactive Monitoring: Review web server access logs for anomalous requests originating from unexpected domains or patterns indicative of DNS rebinding attempts.
Compensating Controls: Deploy a Web Application Firewall (WAF) or configure reverse proxy rules to strictly validate the Host and Origin headers of incoming requests until the patch can be applied.
Exploitation Status
Public Exploit Available: No (exploit_available: unknown)
Analyst Notes: As of January 13, 2026, there is no public information indicating active exploitation or a published proof-of-concept for this vulnerability. The vulnerability requires user interaction via a malicious website, but the lack of origin validation makes it a highly accessible attack vector for remote actors.
Analyst Recommendation
The vulnerability represents a high risk to data integrity and confidentiality within MLFlow environments. Organizations should prioritize the update to version 3.5.0 immediately to remediate the underlying lack of origin validation. If patching is not immediately feasible, network-level controls to restrict access to the REST interface are strongly advised.
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Description Summary:
A Server-Side Request Forgery vulnerability in the OpenShift API server allows authenticated users to perform internal network enumeration and denial of service attacks.
Executive Summary:
A Server-Side Request Forgery vulnerability in Red Hat OpenShift Container Platform 4 allows authenticated attackers to perform unauthorized network discovery and denial of service.
Vulnerability Details
CVE-ID: CVE-2025-14443
Affected Software: Red Hat OpenShift Container Platform
Affected Versions: Red Hat OpenShift Container Platform 4
Vulnerability: This vulnerability is a Server-Side Request Forgery (CWE-918) caused by insufficient validation of IP addresses and network ranges when processing user-supplied image references. The flaw requires an authenticated user with low privileges to trigger the request.
Business Impact
The ability to perform internal network enumeration and service discovery exposes sensitive internal infrastructure that is typically hidden from external actors. This information disclosure, combined with the potential for denial of service, poses a significant risk to the availability and security posture of the platform. The CVSS score of 8.5 (High) reflects the critical nature of these impacts in a containerized environment.
Remediation Plan
Immediate Action: Review official Red Hat security advisories for the release of patches addressing this issue and apply them to all affected OpenShift clusters immediately.
Proactive Monitoring: Monitor API server access logs for anomalous requests involving image references and unexpected outbound connection attempts from the control plane to internal subnets.
Compensating Controls: Implement strict network egress policies and service mesh configurations to restrict the API server's ability to communicate with sensitive internal endpoints that do not require such access.
Exploitation Status
Public Exploit Available: Yes, a public proof-of-concept exists as documented in the linked GitHub repository.
Analyst Notes: As of December 18, 2025, there is no public information indicating active exploitation in the wild; however, a public proof-of-concept is available via the referenced research write-up. The flaw is inherently dangerous due to the elevated privileges and visibility inherent in the API server's network location.
Analyst Recommendation
Given the High severity rating and the availability of a public proof-of-concept, organizations should prioritize the identification and patching of all OpenShift instances. Administrators should verify their current version status against official Red Hat guidance and apply updates as soon as they become available to prevent potential internal reconnaissance and service disruption.