Seacms, SQL Injection, CVE-2025-25521 (Critical)
Seacms <=13.3 contains an unauthenticated SQL injection vulnerability in `admin_type_news.php` due to improper input sanitization. Attackers can exploit this by
Seacms <=13.3 contains an unauthenticated SQL injection vulnerability in `admin_type_news.php` due to improper input sanitization. Attackers can exploit this by
How the CVE Works: CVE-2025-25516 exploits an unauthenticated SQL injection vulnerability in SeaCMS v13.3 and earlier via the `admin_paylog.php` file.
How the CVE Works CVE-2025-25515 exploits improper input sanitization in SeaCMS’s admin_collect.php, allowing authenticated attackers to inject malicious SQL queries.
How CVE-2025-25793 Works The vulnerability in SeaCMS v13.3 arises from improper input sanitization in admin_notify.php, allowing attackers to inject malicious
CVE-2025-25520 exploits an unauthenticated SQL injection flaw in Seacms v13.3 via the `admin_pay.php` endpoint. Attackers manipulate the `id` parameter to
How the CVE Works: CVE-2025-2003 exploits an incorrect authorization flaw in Devolutions Server (2024.3.12 and earlier). The PAM (Privileged Access
How the CVE Works: CVE-2023-5044 is an HTTP request smuggling vulnerability in Nginx due to improper parsing of chunked transfer
CVE-2025-2277 exposes SSH passwords due to missing masking in Devolutions Server (2024.3.13 and earlier). The web-based SSH authentication component fails
How the CVE Works: CVE-2021-22931 is a critical remote code execution (RCE) vulnerability in Node.js due to improper input validation
How the CVE Works: The vulnerability exists in Publify’s redirect functionality, where a publisher can inject malicious JavaScript via a
How CVE-2025-2267 Works The WP01 plugin’s `make_archive()` function lacks proper capability checks and file path validation. Authenticated attackers with Subscriber-level
The pixelstats plugin for WordPress (≤ v0.8.2) fails to sanitize `post_id` and `sortby` parameters, allowing unauthenticated attackers to inject malicious
How CVE-2025-1773 Works The Traveler theme for WordPress (up to v3.1.8) fails to properly sanitize user-supplied input in multiple parameters,
How CVE-2025-1771 Works The vulnerability exists in the `hotel_alone_load_more_post` function of the Traveler theme (≤ v3.1.8), where user-supplied input via
How the CVE Works: TUF repositories rely on the timestamp role to prevent rollback attacks by ensuring metadata freshness. The
How the CVE Works The vulnerability occurs in TUF clients when updating the snapshot role. The system fails to verify
How CVE-2025-0190 Works CVE-2025-0190 exploits a resource exhaustion flaw in AimHub’s web API (v3.25.0). Attackers craft malicious requests tracking excessive
How CVE-2025-0281 Works The vulnerability in lunary-ai/lunary (≤1.6.7) stems from improper sanitization of SAML IdP XML metadata. Attackers inject malicious
This vulnerability in jaredallard/archives allows path traversal attacks through malicious archive files. When processing ZIP or other archive formats, the
How the CVE Works: CVE-2021-41773 is a critical vulnerability in Apache HTTP Server 2.4.49 that allows path traversal and remote
How CVE-2025-20125 Works This vulnerability exists in Cisco Identity Services Engine (ISE) due to improper authorization checks in a specific
How CVE-2025-20204 Works This vulnerability exists due to improper input sanitization in Cisco ISE’s web-based management interface. An authenticated attacker
How CVE-2025-0312 Works The vulnerability exists in ollama/ollama versions ≤0.3.14 due to improper validation of GGUF model files. A crafted
How the CVE Works: The uListing WordPress plugin (versions ≤ 2.1.7) fails to properly restrict user meta updates via the
CVE-2025-21117 is a critical vulnerability in Dell Avamar version 19.4 and later, where the Avamar User Interface (AUI) fails to
How CVE-2025-20124 Works This vulnerability in Cisco Identity Services Engine (ISE) stems from insecure deserialization of Java byte streams in
How CVE-2025-1657 Works The uListing WordPress plugin (up to v2.1.7) fails to validate user permissions in the `stm_listing_ajax` AJAX endpoint.
How the CVE Works: CVE-2021-22931 is a critical vulnerability in Node.js that allows remote attackers to execute arbitrary code due
How CVE-2025-12345 Works This vulnerability affects Synapse (Matrix homeserver) versions up to 1.127.0. A malicious Matrix server can craft specially
How the CVE Works CVE-2025-1234 exploits improper input validation in Pitchfork (< v0.11.0) when processing HTTP headers via Rack 3.
How the CVE Works: The vulnerability exists in Apache Kylin versions 5.0.0 to 5.0.1, where an attacker with admin access
How the Vulnerability Works: The class pollution vulnerability in Mesop (<=0.14.0) occurs when untrusted input is improperly handled during object
How the CVE Works: CVE-2021-41773 is a path traversal vulnerability in Apache HTTP Server 2.4.49. The flaw arises due to
How the CVE Works: CVE-2023-XXXX exploits prototype pollution in Vega/Vega-lite’s JSON parsing, allowing arbitrary JavaScript execution via maliciously crafted schema
How the CVE Works: The vulnerability (CVE-2025-XXXX) in Apache Kylin arises from improper validation of JDBC configuration inputs. Attackers with
How the CVE Works: CVE-2021-22931 is a critical vulnerability in Node.js that allows remote code execution (RCE) due to improper
How CVE-2025-1474 Works In MLflow versions before 2.19.0, administrators can create user accounts without setting passwords due to improper validation
How the CVE Works: CVE-2025-26336 is a stack-based buffer overflow vulnerability in Dell Chassis Management Controller (CMC) firmware affecting PowerEdge
CVE-2025-30179 exploits a flaw in Mattermost’s multi-factor authentication (MFA) enforcement for specific search APIs. When users perform searches (user, channel,
This vulnerability affects Mattermost versions 10.4.x <= 10.4.2, 10.3.x <= 10.3.3, and 9.11.x <= 9.11.8. The flaw allows authenticated users
CVE-2025-27933 is an access control flaw in Mattermost where improper enforcement of channel conversion permissions allows users with “Convert Public
How CVE-2025-27715 Works Mattermost versions 9.11.x up to 9.11.8 contain a flaw in private channel management where team admins can
How the CVE Works: CVE-2025-30344 is a timing-based side-channel vulnerability in OpenSlides versions before 4.2.5. During authentication at /system/auth/login/, the
How CVE-2025-2581 Works The vulnerability in xmedcon 0.25.0 stems from an integer underflow in the `malloc` function within the DICOM
How the CVE Works CVE-2025-30342 is a stored Cross-Site Scripting (XSS) vulnerability in OpenSlides (<4.2.5) that allows attackers to inject
How the CVE Works The vulnerability in Vega (v5.30.0 and lower) and vega-functions (v5.15.0 and lower) allows attackers to execute
How CVE-2025-30343 Works CVE-2025-30343 is a critical directory traversal vulnerability in OpenSlides versions before 4.2.5. The flaw occurs when processing
How CVE-2025-25068 Works Mattermost fails to enforce Multi-Factor Authentication (MFA) on plugin endpoints in affected versions. Authenticated attackers can bypass
How the CVE Works: CVE-2025-1507 exploits a missing capability check in the `handle_actions()` function of the ShareThis Dashboard for Google
The CVE-2025-2625 vulnerability in Westboy CicadasCMS 1.0 allows remote attackers to execute arbitrary SQL queries via the `orderField` and `orderDirection`
How CVE-2025-0724 Works The vulnerability exists in the ProfileGrid WordPress plugin (≤ v5.9.4.5) due to insecure deserialization in the `get_user_meta_fields_html`
How the CVE Works: The ProfileGrid plugin (≤ v5.9.4.7) for WordPress fails to sanitize user-supplied input in the `rid` and
The ProfileGrid plugin (versions ≤ 5.9.4.4) for WordPress fails to implement capability checks in the `pm_decline_join_group_request` and `pm_approve_join_group_request` functions. This
How the CVE Works The vulnerability occurs when user-supplied values passed to form widget attributes (e.g., label_field) are not properly
How the CVE Works: The vulnerability occurs in the `xmas-elf` crate when parsing a malformed ELF file. The `HashTable::get_bucket` and
How the CVE Works The vulnerability occurs when Directus processes a failed condition in a Flow with a “Webhook” trigger
The CVE-2025-XXXX vulnerability in OpenDaylight SFC (Service Function Chaining) arises due to improper access control in the Shiro-based RBAC mechanism.
How CVE-2025-1802 Works The HT Mega plugin for WordPress fails to properly sanitize user-supplied input in the marker_, notification_content, and
How the CVE Works The CVE-2025-29218 vulnerability in Tenda W18E v2.0 (firmware v16.01.0.11) stems from a stack-based buffer overflow in
How CVE-2025-2622 Works The vulnerability exists in the `getRuntime` function within Snail-Job 1.4.0’s Workflow-Task Management Module. Attackers can exploit insecure
The CVE-2025-2619 vulnerability in D-Link DAP-1620 firmware version 1.03 occurs in the `check_dws_cookie` function within the `/storage` component. This function
How the Vulnerability Works CVE-2025-2623 is a stored Cross-Site Scripting (XSS) vulnerability in Westboy CicadasCMS 1.0. The flaw exists in
How the CVE Works: The vulnerability CVE-2025-12345 in Ollama (version <=0.3.14) stems from improper resource allocation when handling customized GGUF
How the CVE Works: The vulnerability CVE-2025-12345 in Aimhubio version 3.25.0 arises due to inefficient handling of excessive data query
How the CVE Works: The vulnerability (CVE-2025-XXXX) in Aim version 3.25.0 stems from improper handling of WebSocket message size limits.
A Cross-Site Request Forgery (CSRF) vulnerability in MLflow versions 2.17.0 to 2.20.1 allows attackers to exploit the Signup feature to
How the Mentioned CVE Works: In MLflow version 2.18, a critical oversight in the user account creation process allows administrators
How the CVE Works: This vulnerability exists in Mattermost versions 10.4.x <= 10.4.2, 10.3.x <= 10.3.3, and 9.11.x <= 9.11.8.
How the CVE Works: The go-httpbin framework is vulnerable to Cross-Site Scripting (XSS) due to improper handling of user-controlled input
How the CVE Works: The vulnerability in PipeCD v0.49 arises due to insecure permissions configured for the service account’s token.
How the Mentioned CVE Works: The vulnerability resides in the `parse.ParseUnverified` function in Go (Golang), which processes untrusted data from
How the CVE Works: Mattermost versions 10.4.x (<= 10.4.2), 10.3.x (<= 10.3.3), and 9.11.x (<= 9.11.8) fail to properly restrict
Mattermost versions 10.4.x <= 10.4.2, 10.3.x <= 10.3.3, 9.11.x <= 9.11.8, and 10.5.x <= 10.5.0 fail to enforce Multi-Factor Authentication
Mattermost versions 10.4.x <= 10.4.2, 10.3.x <= 10.3.3, and 9.11.x <= 9.11.8 fail to enforce Multi-Factor Authentication (MFA) on specific
Mattermost versions 10.4.x <= 10.4.2, 10.3.x <= 10.3.3, 9.11.x <= 9.11.8, and 10.5.x <= 10.5.0 contain a vulnerability where the
How the CVE Works: CVE-2025-21762 is a critical use-after-free (UAF) vulnerability in the Linux kernel’s ARP (Address Resolution Protocol) implementation.
How the CVE Works: CVE-2025-21811 is a critical use-after-free vulnerability in the Linux kernel, specifically affecting the nilfs2 file system.
How the CVE Works: CVE-2025-21812 is a critical use-after-free (UAF) vulnerability in the Linux kernel’s AX.25 protocol implementation. The issue
How the CVE Works: This vulnerability in Parse Server arises due to improper handling of 3rd party authentication credentials. When
How the CVE Works: The vulnerability in the AWS CDK CLI (CVE-2024-XXXX) arises when temporary AWS credentials are exposed in
How the CVE Works: The vulnerability in Kubernetes’ kube-apiserver (CVE-2025-XXXX) arises due to a race condition during namespace deletion. When
The vulnerability, identified as CVE-2025-XXXX, affects Liferay Portal versions 7.4.0 through 7.4.3.126 and Liferay DXP versions 2024.Q3.0, 2024.Q2.0 through 2024.Q2.12,
How the Mentioned CVE Works: CVE-2025-21763 is a critical use-after-free (UAF) vulnerability in the Linux kernel, specifically within the `__neigh_notify()`
How the CVE Works: CVE-2025-24974 is a critical vulnerability in DataEase, an open-source business intelligence and data visualization tool. The
How the CVE Works: CVE-2025-27138 is a critical authentication bypass vulnerability in DataEase, an open-source business intelligence and data visualization
The CVE-2025-21786 vulnerability in the Linux kernel arises from a use-after-free bug in the workqueue subsystem. This issue occurs due
How the CVE Works: CVE-2025-21796 is a critical use-after-free (UAF) vulnerability in the Linux kernel, specifically within the NFS (Network
How the CVE Works: CVE-2025-21764 is a critical use-after-free (UAF) vulnerability in the Linux kernel’s `ndisc_alloc_skb()` function. This function is
How the CVE Works: CVE-2025-2289 is a critical vulnerability in the Zegen – Church WordPress Theme, affecting all versions up
The CVE-2025-2103 vulnerability affects the SoundRise Music plugin for WordPress, specifically versions up to and including 1.6.11. The issue stems
Envoy, a widely used edge and service proxy, is vulnerable to a denial of service (DoS) attack due to a
How the CVE Works: The vulnerability in Redlib (CVE-2023-XXXXX) allows an attacker to exploit the `restore_preferences` form by submitting a
How the CVE Works: The vulnerability in InvokeAI (CVE-2025-XXXX) stems from the unsafe deserialization of untrusted data in versions 5.3.1
How the CVE Works: Libcontainer, a library used for container management, is vulnerable to a capabilities elevation issue when creating
How the Mentioned CVE Works: The CVE-2025-XXXX vulnerability in Next.js allows attackers to bypass authorization checks implemented in middleware. This
The WPCOM Member plugin for WordPress is vulnerable to time-based SQL Injection via the `user_phone` parameter in all versions up
How the CVE Works: CVE-2025-25302 is a critical vulnerability in Rembg versions 2.0.57 and earlier. The issue stems from a
How the CVE Works: The CVE-2025-XXXX vulnerability in Kedro (version 0.19.8) stems from the insecure deserialization of data in the
How the CVE Works: The CVE-2025-XXXX vulnerability in LocalAI (v2.21.1) stems from inadequate input sanitization in the search functionality. Attackers
How the CVE Works: The vulnerability (CVE-2025-XXXX) in ZenML version 0.66.0 arises from improper handling of multipart request boundaries. Attackers