CVE Vulnerability Catalog

The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_revision function in all versions up to, and including, 2.8.169. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). By placing post_type=attachment exclusively in the query string to bypass the consistency check, an attacker can convert an auto-draft GeoDirectory listing into a WordPress attachment with attacker-controlled file paths injected into attachment metadata, which the delete_revision handler then dereferences and unlinks without any post-type or path validation.

The firmware of the Pulsetto Vagus Nerve Stimulator accepts several undisclosed commands over its Bluetooth Low Energy (BLE) interface. These commands are sent without authentication or encryption, and are never issued by the companion mobile application, yet are fully processed by the device when it is powered on.

The InstaWP Connect – 1-click WP Staging & Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 0.1.3.6. The plugin stores its encrypted options file as options-{migrate_key}.txt in wp-content/instawpbackups/ without deploying an index.php or .htaccess to prevent directory listing, exposing the 40-character migrate_key on Apache servers with directory indexing enabled, which allows an attacker to derive the AES-256-CBC passphrase via SHA256(migrate_key), decrypt the options file to recover the api_signature. This makes it possible for unauthenticated attackers to get the database access details and api_signature. Exploitation requires the target WordPress site to be hosted on Apache with directory listing enabled and is time limited to the migration period.

electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. Prior to 3.15.120, electerm allows a malicious RDP server to write attacker-controlled content outside the selected save directory because the RDP clipboard download path in src/client/components/rdp/file-transfer.js passes the server-controlled CLIPRDR filename fileInfo.name to osResolve without sanitization. This issue is fixed in version 3.15.120.

electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. Prior to 3.15.186, electerm allows an authenticated WebSocket client to invoke unintended internal functions through client-controlled func values in upgrade-func in src/app/server/dispatch-center.js and handleFs in src/app/server/fs.js, exposing Upgrade and fsExport methods that can execute commands, open files, mutate the filesystem, or terminate the process. This issue is fixed in version 3.15.186.

electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. Prior to 3.15.120, electerm allows a malicious FTP or SFTP server to write attacker-controlled content outside the selected download directory because recursive transfers in src/client/components/file-transfer/transfer.jsx pass server-supplied file.name and folder.name values to resolve without sanitization. This issue is fixed in version 3.15.120.

electerm before version 3.15.120 allows a malicious FTP or SFTP server to execute arbitrary commands when a user downloads a crafted folder and invokes Properties and Calculate Size. This is because calcLocal inserts the server-controlled folder name into a du -sh shell command without safely escaping single quotes. The issue is fixed in version 3.15.120.

electerm before version 3.15.120 allows a malicious SFTP server to write attacker-controlled content outside the temporary directory. This is because the server-controlled filename used by editWithSystemEditor is interpolated into path.resolve without sanitization. The issue is fixed in version 3.15.120.

Claude Code Templates before version 1.29.4 contains a vulnerability in the Studio server launched by the --studio option. The server binds to all interfaces on port 3444, permits cross-origin requests, and requires no authentication. The POST /api/execute and /api/install-agent endpoints pass attacker-controlled data to child_process.spawn with shell execution enabled, allowing arbitrary OS command execution. The issue is fixed in version 1.29.4.

DSPy 3.3.0b1 contains a file exfiltration vulnerability in the Image and Audio output field adapters. An attacker with influence over language model outputs can read arbitrary local files by injecting a filesystem path into the url field of a parsed Image or Audio typed output. The JSONAdapter and ChatAdapter parse untrusted model completions through parse_value into TypeAdapter validation, which triggers encode_image or encode_audio to read and base64-encode any local file path, subsequently embedding the contents into outgoing messages to the attacker-controlled endpoint.

Taubyte Tau v1.1.10 contains a missing authorization vulnerability in the services/auth HTTP service that allows any authenticated user to read or permanently delete another tenant's project by supplying an arbitrary project ID to the GET and DELETE /projects/{id} endpoints. The GitHubTokenHTTPAuth middleware only validates that a caller presents a valid GitHub OAuth token without verifying ownership or access rights to the target project, enabling attackers with any valid GitHub token to invoke bare KV-store operations such as projects.Fetch and project.Delete against any project ID to achieve cross-tenant project takeover.

python-engineio before version 4.13.2 has two server configurations where the size of incoming messages is not checked before loading them into memory. An attacker can exploit this to cause unnecessary memory allocations in the server. This affects POST requests when using ASGI with long polling transport and WebSocket messages when using Aiohttp with WebSocket transport. Version 4.13.2 addresses this issue.

python-engineio before version 4.13.2 allows an attacker to cause the creation of unnecessary background threads in the server by exploiting the heartbeat mechanism, which launches a thread when a new connection is received and when the client sends a PONG packet. This issue primarily affects synchronous servers. Version 4.13.2 fixes this by launching the initial thread only after client authentication and ensuring only one thread per client.

MongoDB Server has an issue in Queryable Encryption maintenance operations that could allow an authenticated user with privileges on one encrypted collection to cause unauthorized modification or destruction of data belonging to a different collection. This is due to insufficient validation of certain internal metadata references before they are used to perform operations on other namespaces.

MongoDB Server has an issue in the query execution engine that could allow an authenticated user with read and write privileges to cause an internal reference to be used after the underlying memory has been freed, when running certain queries against time-series collections. This could result in a server crash or disclosure of freed memory contents within query results.

MongoDB Server has an issue in the aggregation framework that could allow an unauthenticated party to cause a mongos (router) process to terminate unexpectedly by submitting a specially formed aggregation command. This could result in a denial of service, disrupting client connections routed through the affected mongos instance.

A vulnerability in MongoDB Server's geospatial query processing allows an authenticated user with write privileges to store malformed geometry data that is later processed without proper validation. This can lead to out-of-bounds memory access, causing a server crash (denial of service) and potentially exposing a limited amount of server process memory.

A vulnerability in MongoDB Server's handling of timeseries collections allows an authenticated user with write privileges to cause internal data structure inconsistency through specific document insertions. Subsequent inserts into the affected bucket can lead to out-of-bounds memory access, potentially causing a server crash, memory exposure, or memory corruption.

A vulnerability in MongoDB Server's timeseries bucket lifecycle handling allows an authenticated user with write privileges to trigger a use-after-free condition. Subsequent operations could result in a server crash or potentially execution of unintended code.

A vulnerability in MongoDB Server's intra-cluster connection setup allows a party with suitable network access to influence the authentication mechanism used between replica set members. Under certain conditions, this could cause the cluster's shared internal credential to be transmitted in a less-protected form, potentially allowing its recovery. If recovered, the credential could be used to authenticate as the internal superuser.