CVE Vulnerability Catalog

The Post Export Import with Media plugin for WordPress up to version 1.13.1 is vulnerable to arbitrary file upload. The issue is caused by insufficient file extension validation in the import_media_file_secure function, where the extension allow-list can be bypassed by appending a trailing dot to the filename in a ZIP archive.

A security vulnerability was found in Sipeed PicoClaw up to version 0.2.9 in the IPAllowlist function of the file web/backend/middleware/access_control.go in the Launcher component. This leads to improper access controls and can be exploited remotely. The exploit has been publicly disclosed and may be used in attacks.

A vulnerability in Langroid framework prior to version 0.65.3 allows untrusted users to directly invoke tools via raw JSON payloads, even when tools are registered with `use=False, handle=True`.

In the Langroid framework, the ReadFileTool and WriteFileTool do not validate that the file path stays within the working directory (curr_dir). This allows an attacker to read and write files outside the allowed directory using path traversal sequences like ../.

In Langroid library prior to version 0.64.0, the SQLChatAgent component has an imperfect _validate_query defense layer that fails to block all dangerous SQL primitives. The blocklist misses PostgreSQL file-reading functions (pg_read_file, pg_stat_file) and SQL Server/SQLite constructs, allowing an attacker to read files from the database host.

The LoginPress Pro plugin for WordPress up to version 6.2.3 has an authentication bypass vulnerability in the Spotify Social Login addon. The loginpress_on_spotify_login() function trusts the unverified 'email' field from Spotify's API and uses it to log into an existing WordPress account without verifying email ownership.

The LoginPress Pro plugin for WordPress up to version 6.2.3 has an authentication bypass vulnerability via GitHub OAuth. The loginpress_on_github_login() function blindly trusts the first email from GitHub's API response without verifying it, allowing an attacker to log in as any WordPress user, including administrators.

The LoginPress Pro plugin for WordPress up to version 6.2.3 contains an authentication bypass vulnerability via unverified OAuth email. The loginpress_on_discord_login() function accepts the email field from Discord without checking the verified flag, allowing administrator account takeover.

In Vim prior to 9.2.0735, the C omni-completion script (ccomplete.vim) improperly interpolates the typeref: or typename: field from a tags file into a :vimgrep pattern executed via :execute. This allows injection of arbitrary Ex commands through a crafted .c file and invoking C omni-completion.

A vulnerability in Vim prior to 9.2.0736 allows arbitrary OS command execution when a victim opens a crafted PHP file and invokes omni-completion. The issue is due to improper escaping of class or trait names in the phpcomplete.vim script, enabling injection of Ex commands including :!.

A vulnerability in SiYuan before version 3.7.1 allows JavaScript injection via unsafe interpolation of the this.path value into innerHTML. A crafted asset link with a double quote can break out of the src attribute, inject an event handler, and execute code in the Electron renderer.

A vulnerability in SiYuan before version 3.7.1 allows an unauthenticated publish visitor to inject a UNION SELECT query into the block search endpoint. Attackers can read hidden documents by manipulating path values in POST requests.

SiYuan prior to 3.7.1 has a stored cross-site scripting (XSS) vulnerability in the HTML rendering via the Lute engine. The dangerous JavaScript scheme block does not check form action or SVG xlink:href attributes, allowing OS command execution in the Electron desktop renderer.

A vulnerability in SiYuan before version 3.7.1 allows reading files outside the snippets directory. The serveSnippets function improperly handles path traversal sequences like %2e%2e (..), enabling an authenticated attacker to read workspace secrets and the document database.

In New API, an LLM gateway and AI asset management system, the default SSRF protection configuration did not apply IP filtering to hostnames. With ApplyIPFilterForDomain disabled by default, URL validation checked domain allow/block rules but did not resolve hostnames to IP addresses, allowing authenticated users to configure Webhook, Bark, or Gotify notification URLs pointing to internal or metadata IP addresses.

Cotonti Siena 0.9.26 and earlier contains a cross-site request forgery vulnerability that allows unauthenticated attackers to modify administrator configuration by tricking a logged-in administrator into submitting a forged POST request to the admin.php config update handler, which never invokes the application's CSRF validation function. Attackers can disable the PFS module's file extension whitelist by setting pfsfilecheck to 0, enabling any user with PFS access to upload and execute arbitrary PHP files on the server.

An Improper Restriction of Communication Channel to Intended Endpoints vulnerability in Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause license exhaustion. Due to incorrect initialization, a process that should only communicate internally can be reached over the network via an open port, leading to unauthorized access to license management.

The SIP plugin in Junos OS on MX Series with SPC3 and SRX Series improperly validates the syntactic correctness of incoming SIP packets. An unauthenticated attacker can send a malformed INVITE packet, causing a flowd crash and restart, leading to a complete service outage.

An improper validation of specified quantity in input vulnerability in the TCP proxy plugin of Juniper Networks Junos OS on MX Series with SPC3 and SRX Series allows an unauthenticated, network-based attacker to cause a complete Denial of Service (DoS) by sending a TCP packet with a malformed header, crashing the flowd process.

A vulnerability in DeepSeek MCP Server allows an attacker to hijack user sessions by enumerating session IDs and reusing them in chat requests. The issue affects versions 1.4.2 through 1.7.0, where the global session store does not validate session ID authenticity.