CVE Vulnerability Catalog

The Conekta Payment Gateway WordPress plugin before version 6.2.2 does not verify the authenticity of incoming payment gateway webhook notifications, nor bind the confirmed payment to the targeted order or verify its amount. This allows unauthenticated attackers to mark arbitrary orders as paid without payment.

The FiboSearch WordPress plugin before version 1.34.1 does not consistently exclude password-protected products from its unauthenticated AJAX endpoints. This allows unauthenticated users to disclose and enumerate password-protected products and their metadata without entering the product password. Two endpoints are affected: the autocomplete search endpoint (dgwt_wcas_ajax_search) and the Details Panel endpoint (dgwt_wcas_result_details) when queried for taxonomy details.

The Post Grid, Slider & Carousel Ultimate WordPress plugin before version 1.8.1 does not sanitize and escape one of its custom post type settings before outputting it in an HTML attribute on the admin edit screen. This allows users with the Contributor role and above to inject JavaScript that executes in the session of any administrator who opens the affected item.

The Tutor LMS WordPress plugin before version 4.0.6 does not enforce per-object ownership checks on its course content type. This allows any user with the instructor role to read the content of private courses belonging to other instructors.

The AutomatorWP plugin for WordPress up to version 5.8.4 is vulnerable to authorization bypass due to improper verification of user permissions. Authenticated attackers with subscriber-level access or above can retrieve the site's Campaign Monitor mailing list catalog, including list IDs and names, which should be restricted to managers.

The AutomatorWP plugin for WordPress up to version 5.8.4 is vulnerable to authorization bypass due to improper verification of user permissions. Authenticated attackers with subscriber-level access or above can retrieve all ConvertKit form data configured by the site's manager, exposing integration details intended to be restricted to managers.

The Themify Builder plugin for WordPress up to version 7.8.0 is vulnerable to authorization bypass due to improper verification of user permissions. Unauthenticated attackers can modify the stored styling data (padding and margin properties) of arbitrary posts, including private and draft posts, by supplying a post ID and JSON payload.

The WPeMatico RSS Feed Fetcher plugin for WordPress up to version 2.8.24 is vulnerable to unauthorized data modification due to a missing capability check in the wpematico_import_settings function. Authenticated attackers with subscriber-level access or above can update arbitrary options on the WordPress site, potentially leading to privilege escalation.

The Tie::Hash::Regex module for Perl before version 2.0.0 throws an exception on unparseable lookup keys. The FETCH, EXISTS, and DELETE methods throw an exception when the key is an invalid regular expression, potentially causing application termination.

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

OliveTin before commit ebffd9f040f791208aee1db2e5a8aecd1e3e603d has a vulnerability that allows arguments whose names start with 'ot_' to bypass the filterToDefinedArgumentsOnly filter. These arguments are not type-checked, are set as environment variables and passed to executed commands, and are also available in the template context.

WeeChat versions 0.3.1 through 4.9.0 use non-constant-time string comparison functions (weechat_strcasecmp and strcmp) to verify password hashes and plaintext passwords in relay authentication. An attacker can exploit timing differences to extract the server-computed hash character by character, then authenticate without knowing the password. Version 4.9.1 fixes the issue.

WeeChat versions 4.3.0 through 4.9.0 have a vulnerability in the WebSocket permessage-deflate decompression function relay_websocket_inflate() in the relay module, which has no upper bound on output size. An authenticated relay user can send a small compressed WebSocket frame (~100 bytes) that decompresses to gigabytes, exhausting all server memory and crashing the entire WeeChat process.

FORT Validator versions through 1.6.7 contain an origin-validation error in RRDP processing: a delegated CA under the same TAL can reference a victim CA's public RRDP notification and snapshot URLs, causing FORT's URL-based download cache to report success after deleting the victim's local snapshot. This can silently remove the victim's VRPs and other signed objects from FORT's output, potentially enabling route hijacking or loss of reachability. Version 1.6.8 contains a patch that rejects cross-origin RRDP snapshot and delta URLs.

Recce before version 1.50.0, in OSS server deployments exposed to an untrusted network without authentication, is vulnerable to unauthenticated SQL execution through the query run API. When Recce is configured with a DuckDB-backed project, an attacker can use DuckDB filesystem primitives to read and write files accessible to the Recce server process.

Arc Enterprise prior to version 26.06.1 validates only the wire-format envelope (length, opcode) of inbound messages in the cluster replication receiver. The MsgReplicateSync payload is accepted without any application-layer authentication (no HMAC, signature, or per-message nonce). Transport-layer TLS/mTLS does not protect against application-layer tampering or replay. Fixed in 2026.06.1.

Arc Enterprise prior to version 26.06.1 accepts attacker-chosen file paths in manifest-registration proposals in the Raft FSM without validating them against the configured storage backend. The only check is that the path is non-empty; there is no parent-traversal rejection, allowlist, scheme restriction, or length bound. Fixed in 2026.06.1.

Arc versions prior to 26.06.1 register Go's net/http/pprof handlers at /debug/pprof/* and add /debug/pprof to PublicPrefixes, making these endpoints reachable without authentication. Version 26.06.1 contains a patch. Workarounds include blocking /debug/pprof* at a reverse proxy or restricting the API port to trusted networks.