Golang (golangorg/x/net), HTTP Proxy Bypass, CVE-2025-XXXX (Moderate)
How the Mentioned CVE Works: The vulnerability in the `golang.org/x/net` library arises due to improper handling of IPv6 Zone IDs […]
How the Mentioned CVE Works: The vulnerability in the `golang.org/x/net` library arises due to improper handling of IPv6 Zone IDs […]
How the Mentioned CVE Works: CVE-2025-XXXX affects Apache NiFi versions 1.13.0 through 2.2.0. The vulnerability arises when MongoDB components in
How the CVE Works: The vulnerability, CVE-2025-XXXX, is a Cross-site Scripting (XSS) issue in the Apache Felix HTTP Webconsole Plugin.
How the CVE Works: Plenti versions up to 0.7.16 are vulnerable to a code injection vulnerability due to improper handling
How the Mentioned CVE Works: The CVE-2025-XXXX vulnerability in Ruby SAML arises due to inconsistent XML namespace handling between the
The CVE-2025-XXXX vulnerability in SmallRye Fault Tolerance arises due to an out-of-memory (OOM) issue in the `smallrye-fault-tolerance` library. This flaw
How the CVE Works: The vulnerability in Apache Camel (CVE-2025-27636) stems from a flaw in the default incoming header filter.
How the Mentioned CVE Works: The CVE-2025-XXXX vulnerability in Ruby SAML arises due to differences in XML parsing between ReXML
How the Mentioned CVE Works: CVE-2025-25292 is a critical vulnerability in the `ruby-saml` library, which is a dependency of omniauth-saml.
How the CVE Works: The vulnerability (CVE-2025-XXXX) in GraphQL arises when a maliciously crafted GraphQL schema is loaded using `GraphQL::Schema.from_introspection`
How the CVE Works: The vulnerability, CVE-2025-001, arises in IBC-Go’s deserialization process of IBC acknowledgements. During JSON unmarshalling, non-deterministic behavior
The vulnerability CVE-2025-002 in the Cosmos SDK’s `x/group` module allows malicious actors to trigger errors in the `EndBlocker` function, leading
The Shortcode Cleaner Lite plugin for WordPress, up to and including version 1.0.9, contains a critical vulnerability (CVE-2025-1481) due to
The CVE-2025-1323 vulnerability affects the WP-Recall plugin for WordPress, specifically versions up to and including 16.26.10. This vulnerability arises due
How the CVE Works: The vulnerability in laravel-crud-wizard-free (CVE-2025-XXXX) arises due to improper file validation in versions below 3.4.17. The
The CVE-2025-27840 vulnerability affects Espressif ESP32 chips, which are widely used in IoT devices. This vulnerability allows attackers to execute
How the Mentioned CVE Works: CVE-2025-1234 is an out-of-bounds read vulnerability in the Ruby JSON parser. This vulnerability occurs when
How the Mentioned CVE Works: CVE-2025-2127 is a Cross-Site Scripting (XSS) vulnerability discovered in JoomlaUX JUX Real Estate 3.4.0, a
The Essential Blocks – Page Builder Gutenberg Blocks, Patterns & Templates plugin for WordPress is vulnerable to Stored Cross-Site Scripting
How the Mentioned CVE Works: The vulnerability arises in the Inter-Blockchain Communication (IBC) protocol’s deserialization process of acknowledgements. Specifically, the
How the CVE Works: CVE-2025-2126 is a critical SQL Injection vulnerability found in JoomlaUX JUX Real Estate 3.4.0 on Joomla.
How the Mentioned CVE Works: Rembg, a tool designed to remove image backgrounds, is vulnerable to Server-Side Request Forgery (SSRF)
How the CVE Works: The vulnerability in Pimcore arises from improper input sanitization in the `getRelationFilterCondition` method. This function processes
How the CVE Works: The vulnerability in Rembg 2.0.57 and earlier stems from a misconfigured Cross-Origin Resource Sharing (CORS) policy.
How the Mentioned CVE Works: CVE-2025-27591 is a privilege escalation vulnerability in the Below service (prior to version 0.9.0) due
How the CVE Works: CVE-2025-0469 is a critical vulnerability in the Forminator Forms plugin for WordPress, affecting versions up to
How the CVE Works: CVE-2025-2130 is a cross-site scripting (XSS) vulnerability found in OpenXE versions up to 1.12. The issue
How the Mentioned CVE Works: CVE-2025-2133 is a medium-severity Cross-Site Scripting (XSS) vulnerability found in FTCMS version 2.1. The vulnerability
How the CVE Works: CVE-2025-2132 is a critical SQL injection vulnerability found in FTCMS version 2.1. The flaw resides in
How the CVE Works: CVE-2025-2131 is a cross-site scripting (XSS) vulnerability found in XunRuiCMS versions up to 4.6.3. The issue
How the CVE Works: The vulnerability arises due to insufficient input validation in the customer account portal’s email section. When
How the CVE Works: This vulnerability arises in Babel when compiling regular expressions with named capturing groups. Babel generates a
How the Mentioned CVE Works: The vulnerability in Froxlor, identified as CVE-2023-XXXX, allows authenticated users (such as resellers or customers)
How the CVE Works: The vulnerability in Keras’ `Model.load_model` function allows arbitrary code execution even when `safe_mode=True` is enabled. This
How the Mentioned CVE Works: CVE-2025-1150 is a critical memory leak vulnerability found in GNU Binutils version 2.43. The issue
How the CVE Works: CVE-2025-22757 is a critical stored Cross-site Scripting (XSS) vulnerability in CodeBard Help Desk versions up to
How the CVE Works: The vulnerability lies in the HTTPRedirect binding of SimpleSAMLphp, specifically in versions prior to v5. The
How the CVE Works: The vulnerability in ASP.NET Core 9.0, 8.0, and 2.3 arises when the `RefreshSignInAsync` method is called
How the Mentioned CVE Works: CVE-2017-5638 is a critical vulnerability in Apache Struts 2, a popular framework for building Java
CVE-2025-0587 is a critical vulnerability in OpenHarmony v5.0.2 and prior versions that allows a local attacker to execute arbitrary code
The ThemeMakers PayPal Express Checkout plugin for WordPress, versions up to and including 1.1.9, is vulnerable to Stored Cross-Site Scripting
The CVE-2025-1717 vulnerability affects the Login Me Now plugin for WordPress, specifically versions up to and including 1.7.2. This critical
The Car Dealer Automotive WordPress Theme, a responsive theme for WordPress, is vulnerable to arbitrary file deletion due to insufficient
How the Mentioned CVE Works: CVE-2025-1690 is a critical vulnerability in the ThemeMakers Stripe Checkout plugin for WordPress, affecting versions
How the CVE Works: The vulnerability in Keras, identified as CVE-2025-XXXX, resides in the `Model.load_model` function. This function is designed
How the CVE Works: The vulnerability arises in Mockoon’s static file serving configuration, where the `filePath` variable is generated using
How the CVE Works: CVE-2025-1450 is a critical vulnerability in the Chaty plugin for WordPress, affecting versions up to and
How the CVE Works: The vulnerability in Umbraco CMS (CVE-2025-XXXX) allows restricted editor users to manipulate backoffice API URLs to
How the CVE Works: The vulnerability, CVE-2025-XXXX, in Umbraco CMS arises due to improper access control in the API endpoints
How the CVE Works: In a Kubernetes environment, Ratify is used to authenticate to a private Azure Container Registry (ACR)
How the CVE Works: The vulnerability in Rack::Static arises due to improper sanitization of user-supplied file paths. When serving static
This vulnerability in Apache Tomcat arises due to improper handling of path equivalence in the `file.Name` parameter, specifically involving internal
How the Mentioned CVE Works: Concrete CMS versions 9.0.0 through 9.3.9 are vulnerable to a stored Cross-Site Scripting (XSS) attack
How the CVE Works: CVE-2025-1296 affects Nomad Community and Enterprise editions, where sensitive information such as workload identity tokens and
How the CVE Works: The vulnerability in Vela Server (CVE-2025-XXXX) stems from insufficient verification of webhook payload data. Attackers can
How the CVE Works: This vulnerability in Keycloak (CVE-2025-XXXX) arises due to improper authorization in the Organization Mapper feature. The
How the Mentioned CVE Works: The vulnerability (CVE-2025-XXXX) in Keycloak arises due to the absence of an LDAP bind operation
This vulnerability in Apache Camel’s Bean component allows an attacker to bypass header filtering mechanisms under specific conditions. The issue
The Laravel framework versions 11.9.0 to 11.35.1 are vulnerable to reflected cross-site scripting (XSS) due to improper encoding of route
How the Mentioned CVE Works: The vulnerability arises from the improper use of the `explode()` function in PHP, which lacks
How the Mentioned CVE Works: The vulnerability, CVE-2025-XXXX, affects Laravel framework versions 11.9.0 to 11.35.1. It arises due to improper
How the CVE Works: The vulnerability arises in Ekuiper, an edge lightweight IoT data analytics/streaming software, where a user with
How the CVE Works: CVE-2025-24727 is a critical vulnerability in the CodePeople Contact Form Email plugin, affecting versions from n/a
How the CVE Works: CVE-2025-24782 is a critical vulnerability in the wpWax Post Grid, Slider & Carousel Ultimate plugin for
How the CVE Works: The vulnerability in LocalS3 arises due to improper handling of XML input in the bucket tagging
How the CVE Works: CVE-2025-24591 is a Missing Authorization vulnerability in NinjaTeam GDPR CCPA Compliance Support, affecting versions from n/a
How the Mentioned CVE Works: The vulnerability arises due to PickleScan’s inability to detect malicious pickle files embedded within PyTorch
How the CVE Works: CVE-2025-1340 is a critical vulnerability in TOTOLINK X18 routers, specifically affecting firmware version 9.1.0cu.2024_B20220329. The flaw
How the CVE Works: CVE-2025-1339 is a critical vulnerability in TOTOLINK X18 routers, specifically affecting firmware version 9.1.0cu.2024_B20220329. The flaw
How the Mentioned CVE Works: CVE-2017-5638 is a critical vulnerability in Apache Struts, a popular framework for building Java web
How the CVE Works: CVE-2025-27590 is a critical vulnerability in oxidized-web (Oxidized Web) versions before 0.15.0. The flaw resides in
How the CVE Works: CVE-2025-27419 is a critical Denial of Service (DoS) vulnerability in WeGIA, an open-source web management platform.
How the CVE Works: CVE-2025-0678 is a critical vulnerability in GRUB2, specifically within its squash4 filesystem module. When GRUB2 reads
How the CVE Works: The vulnerability in the protobuf crate arises due to uncontrolled recursion during the parsing of unknown
How the CVE Works: The vulnerability in @intlify/message-resolver (v9.1) and @intlify/vue-i18n-core (v9.2 or later) arises due to improper handling of
The vulnerability in `com.xwiki.confluencepro:application-confluence-migrator-pro-ui` (CVE-2025-XXXX) allows unauthorized access to the application’s homepage, exposing sensitive information to guests. This issue arises
How the CVE Works: The vulnerability in `ring::aead::quic::HeaderProtectionKey::new_mask()` arises due to integer overflow when overflow checking is enabled. In the
How the CVE Works: The vulnerability (CVE-2025-XXXX) in XWiki Confluence Migrator Pro (versions >= 1.0, < 1.2.0) allows unauthenticated remote
The vulnerability CVE-2025-24043 in Microsoft WinDbg arises from improper verification of cryptographic signatures in the SOS (Son of Strike) debugging
How the CVE Works: CVE-2025-1571 is a critical vulnerability in the Exclusive Addons for Elementor plugin for WordPress, affecting versions
How the Mentioned CVE Works: The vulnerability (CVE-2023-XXXX) in the OpenTelemetry.Api package versions 1.10.0 to 1.11.1 arises due to improper
How the CVE Works: This vulnerability exists in Jenkins versions 2.499 and earlier, including LTS 2.492.1 and earlier. The issue
How the CVE Works: The vulnerability CVE-2025-XXXX affects versions of the Ray package prior to 2.43.0. It involves the unintended
How the Mentioned CVE Works: The vulnerability in Envoy Gateway versions prior to 1.2.7 and 1.3.1 lies in the default
How the CVE Works: The vulnerability in Jenkins (CVE-2025-XXXX) arises due to the lack of POST request enforcement for the
How the CVE Works: CVE-2025-1505 is a critical vulnerability in the Advanced AJAX Product Filters plugin for WordPress, affecting versions
How the CVE Works: The vulnerability in Fleet arises due to improper validation of SAML responses. An attacker can craft
How the Mentioned CVE Works: The Jenkins Open Redirect vulnerability (CVE-2025-XXXX) arises due to improper validation of URLs in redirect
How the CVE Works: The vulnerability in NocoDB lies in the password reset functionality, specifically in the API endpoint /api/v1/db/auth/password/reset/:tokenId.
How the CVE Works: CVE-2025-24729 is a critical vulnerability in ElementInvader Addons for Elementor, a popular WordPress plugin. The issue
How the CVE Works: CVE-2025-1757 is a critical vulnerability in the WordPress Portfolio Builder – Portfolio Gallery plugin (versions up
How the Mentioned CVE Works: CVE-2025-21401 is a critical security vulnerability in Microsoft Edge (Chromium-based) that allows attackers to bypass
How the Mentioned CVE Works: CVE-2025-27501 is a critical Server-Side Request Forgery (SSRF) vulnerability in OpenZiti, a zero-trust application framework.
How the Mentioned CVE Works: CVE-2025-27500 is a critical vulnerability in OpenZiti, a zero-trust application platform. The vulnerability exists in
How the CVE Works: CVE-2025-1891 is a Cross-Site Request Forgery (CSRF) vulnerability found in ShishuoCMS version 1.1. The vulnerability arises
This vulnerability arises due to an oversight in the Jinja2 sandboxed environment’s interaction with the `|attr` filter. The flaw allows
How the CVE Works: CVE-2025-1892 is a cross-site scripting (XSS) vulnerability found in ShishuoCMS version 1.1. The issue resides in
How the Mentioned CVE Works: CVE-2025-1470 is a vulnerability in Eclipse OMR, affecting versions from the initial contribution up to
How the Mentioned CVE Works: The vulnerability in DGL (Deep Graph Library) arises from its implementation of an RPC server
How the Mentioned CVE Works: CVE-2025-1471 is a critical buffer overflow vulnerability found in Eclipse OMR versions 0.2.0 to 0.4.0.