CVE Vulnerability Catalog

In PHPCSUtils from 1.0.0-alpha1 until 1.2.3, AbstractArrayDeclarationSniff::getActualArrayKey() evaluates attacker-controlled array-key expressions with eval(). This allows callback-form keys in untrusted PHP code scanned by an extending sniff to execute arbitrary commands on the scanning host.

In ConvertX before 0.18.0, the /delete/{id} endpoint uses HTTP GET for permanent deletion without CSRF protection. If an authenticated user visits attacker-controlled content, the browser sends the session cookie and deletes the targeted job.

In ConvertX before 0.18.0, the ImageMagick converter uses the unsanitized convert_to parameter to construct an output path. An authenticated user (or unauthenticated when access is allowed) can upload an extensionless image and supply directory traversal sequences in convert_to via /convert, writing output outside the intended directory.

In PraisonAI before praisonaiagents 1.6.62, searxng_search and the search_web SearxNG provider pass the LLM-controlled searxng_url parameter directly to requests.get without validating scheme, host, port, or resolved address. Prompt-injected content can direct the search tool to internal JSON services, distinguish open and closed internal ports, and attempt cloud-metadata requests.

IBM Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 for Linux, UNIX and Windows (including DB2 Connect Server) could allow a remote authenticated attacker to obtain sensitive information due to improper authorization when using the CREATE WRAPPER command.

A vulnerability was detected in KusalkaSilva Learning-Management-System up to commit ffeb873f8803f1e9664384ff75000c7da45466d2, affecting the mysql_query function in remove_announcements.php. Manipulating the ID argument results in missing authentication, and the attack can be performed remotely; the exploit is publicly available.

IBM Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 is vulnerable to privilege escalation when db2locssh is enabled with the db2 instance. The flaw allows an attacker to gain elevated privileges on the system.

IBM Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 for Linux, UNIX and Windows (including DB2 Connect Server) could allow a local attacker to gain elevated privileges due to improper privilege management.

A vulnerability in Temporal Server allows a connected peer cluster to modify local namespaces in the receiving cluster, which should not be replicated. The receiving cluster does not check if the namespace is global and overwrites its state, description, owner, retention, archival settings, cluster list, and active cluster if the task carries a higher failover version. An attacker controlling a registered peer's replies can change any local namespace without credentials on the receiving cluster, e.g., marking it Deprecated, causing new Workflow starts to fail.

A vulnerability in obsidian-tc, a Model Context Protocol server for Obsidian vaults, before version 1.3.1, does not validate Host or Origin headers or enable DNS-rebinding protection in the Streamable HTTP transport. With loopback configuration using auth.mode set to none, a malicious web page can send requests to the local MCP endpoint and gain unrestricted vault access via the http-local caller. Version 1.3.1 fixes the issue by enabling host, origin, and DNS-rebinding validation.

A vulnerability in Edimax BR-6208AC router version 1.32 affects unknown code in the file /goform/formAccept. Manipulating the submit-url argument results in command injection. The attack can be carried out remotely, and the exploit has been made public. The vendor was contacted but did not respond, and the product is no longer supported.

A Cross-Site Request Forgery (CSRF) vulnerability in the Patreon WordPress plugin (patreon-connect) up to version 1.10.0. It allows an attacker to force an authenticated user to perform unwanted actions in the context of their session.

A Cross-Site Request Forgery (CSRF) vulnerability in the Patreon WordPress plugin (patreon-connect) up to version 1.9.17. It allows an attacker to force an authenticated user to perform unwanted actions in the context of their session.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 may use cleartext transport for Amazon S3 connections by default. A network-positioned attacker could intercept data or credentials transmitted through an affected connection.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 do not consistently validate TLS certificate hostnames for certain outbound connections. A network-positioned attacker could exploit this weakness to intercept or modify communications with an affected service.

Progress MarkLogic Server 12.x releases before 12.1.0 may use cleartext transport for certain cluster-management communications. A network-positioned attacker could intercept or modify information transmitted through an affected connection.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 do not sufficiently verify the identity of a Kerberos authentication service in certain password-based authentication configurations. A network-positioned attacker could impersonate trusted authentication infrastructure, potentially resulting in unauthorized access or modification of protected data.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 assign overly permissive operating-system permissions to certain log files, which could allow a local user to read or alter log data. The corrected default permissions apply to newly created and rotated logs; existing logs retain their current permissions until remediated.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 enable XML external entity processing by default in multiple server paths, which could allow crafted XML to cause server-side requests or disclosure of local files.

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 contain an out-of-bounds write vulnerability in certain language-processing functionality. A remote authenticated attacker could exploit this vulnerability to cause server instability or limited modification of data.