CVE-2025-59151 Vulnerability Analysis & Exploit Details

CVE-2025-59151
Vulnerability Scoring

8.2
/10
Severe Risk

Cybersecurity professionals consider CVE-2025-59151 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-59151 Details

Status: Analyzed

Last updated: 🕓 18 Dec 2025, 16:21 UTC
Originally published on: 🕗 27 Oct 2025, 20:15 UTC

Time between publication and last update: 51 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

CVE-2025-59151 Vulnerability Summary

CVE-2025-59151: Pi-hole Admin Interface is a web interface for managing Pi-hole, a network-level advertisement and internet tracker blocking application. Pi-hole Admin Interface before 6.3 is vulnerable to Carriage Return Line Feed (CRLF) injection. When a request is made to a file ending with the .lp extension, the application performs a redirect without properly sanitizing the input. An attacker can inject carriage return and line feed characters (%0d%0a) to manipulate both the headers and the content of the HTTP response. This enables the injection of arbitrary HTTP response headers, potentially leading to session fixation, cache poisoning, and the weakening or bypassing of browser-based security mechanisms such as Content Security Policy or X-XSS-Protection. This vulnerability is fixed in 6.3.

Assessing the Risk of CVE-2025-59151

Access Complexity Graph

The exploitability of CVE-2025-59151 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-59151

With low attack complexity and no required privileges, CVE-2025-59151 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-59151, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-59151, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2025-59151 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2025-59151 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: Low
    CVE-2025-59151 may slightly degrade system performance without fully affecting service availability.

CVE-2025-59151 References

External References

CWE Common Weakness Enumeration

CWE-113

CAPEC Common Attack Pattern Enumeration and Classification

  • HTTP Request Splitting CAPEC-105 An adversary abuses the flexibility and discrepancies in the parsing and interpretation of HTTP Request messages by different intermediary HTTP agents (e.g., load balancer, reverse proxy, web caching proxies, application firewalls, etc.) to split a single HTTP request into multiple unauthorized and malicious HTTP requests to a back-end HTTP agent (e.g., web server). See CanPrecede relationships for possible consequences.
  • Accessing/Intercepting/Modifying HTTP Cookies CAPEC-31 This attack relies on the use of HTTP Cookies to store credentials, state information and other critical data on client systems. There are several different forms of this attack. The first form of this attack involves accessing HTTP Cookies to mine for potentially sensitive data contained therein. The second form involves intercepting this data as it is transmitted from client to server. This intercepted information is then used by the adversary to impersonate the remote user/session. The third form is when the cookie's content is modified by the adversary before it is sent back to the server. Here the adversary seeks to convince the target server to operate on this falsified information.
  • HTTP Response Splitting CAPEC-34 An adversary manipulates and injects malicious content, in the form of secret unauthorized HTTP responses, into a single HTTP response from a vulnerable or compromised back-end HTTP agent (e.g., web server) or into an already spoofed HTTP response from an adversary controlled domain/site. See CanPrecede relationships for possible consequences.
  • AJAX Footprinting CAPEC-85 This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.

Vulnerable Configurations

  • cpe:2.3:a:pi-hole:web_interface:-:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:-:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:0.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.0:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.3:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.4:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.4.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.4.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.4.3.1a:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.4.3.1a:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.4.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.4.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:1.4.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:1.4.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.1.0:beta:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.1.0:beta:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.1.0:alpha1:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.1.0:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.3:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.4:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.5:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:2.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:2.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:3.0:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:3.0.1a:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:3.0.1a:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:3.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:3.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:3.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:3.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:3.3:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:4.0:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:4.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:4.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:4.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:4.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:4.3:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:4.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:4.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:4.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:4.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.0:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.3:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.4:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.5:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.6:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.6:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.7:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.7:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.8:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.8:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.9:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.9:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.10:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.10:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.10.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.11:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.11:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.12:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.12:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.13:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.13:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.14:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.14:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.14.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.14.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.14.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.14.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.15:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.15:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.15.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.15.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.16:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.16:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.17:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.17:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.18:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.18:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.18.1:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.18.1:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.18.2:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.18.2:*:*:*:*:*:*:*
  • cpe:2.3:a:pi-hole:web_interface:5.18.3:*:*:*:*:*:*:*
    cpe:2.3:a:pi-hole:web_interface:5.18.3:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-59151: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-15166 – A vulnerability was found in itsourcecode Online Cake Ordering System 1.0. This affects an unknown function of the file /updatesupplier.php?action=...
  • CVE-2025-15165 – A vulnerability has been found in itsourcecode Online Cake Ordering System 1.0. The impacted element is an unknown function of the file /updatecust...
  • CVE-2025-15164 – A security flaw has been discovered in Tenda WH450 1.0.0.18. This affects an unknown part of the file /goform/SafeMacFilter. The manipulation of th...
  • CVE-2025-15163 – A vulnerability was identified in Tenda WH450 1.0.0.18. Affected by this issue is some unknown functionality of the file /goform/SafeEmailFilter. T...
  • CVE-2025-15067 – Unrestricted Upload of File with Dangerous Type vulnerability in Innorix Innorix WP allows Upload a Web Shell to a Web Server.This issue affects In...