Export limit exceeded: 55819 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429120 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (429120 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-110486 | 1 Eclipse | 1 Eclipse Mosquitto | 2026-11-18 | 9.8 Critical |
| In Eclipse Mosquitto versions 2.1 through 2.1.2, a listener configured with `protocol websockets` mishandles empty WebSocket data frames. `net__read_ws()` in `lib/net_ws.c` returns the number of framing bytes consumed (the 4 masking-key bytes) for a data frame with a zero-length payload, without writing any bytes to the caller’s buffer. The MQTT packet reader in `packet__read_single()` (`lib/packet_mosq.c`) trusts that return value as a payload byte count. A remote client can therefore advance the read position over an uninitialised heap allocation, causing the broker to process and forward uninitialised heap memory (information disclosure, including heap and libc pointers), and can underflow the unsigned `to_process` counter so that subsequent attacker-controlled frame data is written past the end of the allocation (heap out-of-bounds write). The out-of-bounds write is reachable from the CONNECT packet before any authentication check, so an unauthenticated client can corrupt the heap and crash the broker even when `allow_anonymous false` is set. Combining the disclosure and the write allows remote code execution as the broker’s user by any client able to establish a session. | ||||
| CVE-2025-59906 | 1 Wincrm | 1 Wincrm.exe | 2026-11-18 | N/A |
| This CVE identifier has been rejected or withdrawn by its CVE numbering authority. New CVEs are now being reserved. | ||||
| CVE-2025-59907 | 1 Wincrm | 1 Winsat.exe | 2026-11-18 | N/A |
| This CVE identifier has been rejected or withdrawn by its CVE numbering authority. New CVEs are now being reserved. | ||||
| CVE-2025-59908 | 1 Wincrm | 1 Wincrm | 2026-11-18 | N/A |
| This CVE identifier has been rejected or withdrawn by its CVE numbering authority. New CVEs are now being reserved. | ||||
| CVE-2025-59909 | 1 Wincrm | 1 Wincrm | 2026-11-18 | N/A |
| This CVE identifier has been rejected or withdrawn by its CVE numbering authority. New CVEs are now being reserved. | ||||
| CVE-2025-59910 | 1 Wincrm | 1 Wincrm | 2026-11-18 | N/A |
| This CVE identifier has been rejected or withdrawn by its CVE numbering authority. New CVEs are now being reserved. | ||||
| CVE-2025-59911 | 1 Wincrm | 1 Wincrm | 2026-11-18 | N/A |
| This CVE identifier has been rejected or withdrawn by its CVE numbering authority. New CVEs are now being reserved. | ||||
| CVE-2025-59912 | 1 Wincrm | 1 Wincrm | 2026-11-18 | N/A |
| This CVE identifier has been rejected or withdrawn by its CVE numbering authority. New CVEs are now being reserved. | ||||
| CVE-2026-116536 | 2 Smub, Wordpress-extensions | 2 Custom Twitter Feeds – A Tweets Widget Or X Feed Widget, Custom Twitter Feeds | 2026-11-18 | 7.2 High |
| The Custom Twitter Feeds – A Tweets Widget or X Feed Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'atts (JSON object, specifically the inner `feed` key)' parameter in all versions up to, and including, 2.11.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is first stored in the wp_ctf_feed_caches database table and later written into the ctf_cron_report WordPress option by the scheduled ctf_feed_update cron job, meaning execution is deferred until the cron runs and an administrator subsequently loads the Support page. | ||||
| CVE-2026-129322 | 2 Themeisle, Wordpress-extensions | 2 Orbit Fox: Duplicate Page, Menu Icons, Svg Support, Cookie Notice, Custom Fonts & More, Orbit Fox: Duplicate Page, Menu Icons, Svg Support, Cookie Notice, Custom Fonts & More | 2026-11-18 | 6.4 Medium |
| The Orbit Fox: Duplicate Page, Menu Icons, SVG Support, Cookie Notice, Custom Fonts & More plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title (post_title)' parameter in all versions up to, and including, 3.0.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit is further enabled by wptexturize deliberately skipping texturization of content inside <code> elements and the default WordPress kses allow-list preserving <code> tags and raw double quotes on save, allowing a crafted title attribute breakout payload to survive storage and the the_title filter chain intact. | ||||
| CVE-2026-11602 | 2 Fs-code, Wordpress-extensions | 2 Fs Poster - Wordpress Social Media Auto Poster & Scheduler [facebook, Instagram, Twitter, Pinterest], Fs Poster | 2026-11-18 | 5.3 Medium |
| The FS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest] plugin for WordPress is vulnerable to missing authorization to Unauthorized Social App Data Modification in all versions up to, and including, 8.0.1 This is due to missing authentication, nonce, and capability checks in the `standardFSApp()` function, which is registered on the `wp` action hook and executes on every frontend page load without any login or permission verification. This makes it possible for unauthenticated attackers to insert arbitrary social network app records into the database, or overwrite the OAuth `client_id` and `client_secret` of existing social network connections, by supplying attacker-controlled values via the `fsp_app_redirect` and `app` GET parameters. An attacker can target a specific existing social app record for credential overwrite by supplying matching `social_network` and `slug` values, requiring no knowledge of internal record IDs, which disrupts scheduled social media posts and forces administrators to re-authenticate their connected accounts. | ||||
| CVE-2026-124977 | 2 Wordpress-extensions, Wpdesk | 2 Flexible Pdf Invoices For Woocommerce & Wordpress, Flexible Pdf Invoices For Woocommerce & Wordpress | 2026-11-18 | 6.1 Medium |
| The Flexible PDF Invoices for WooCommerce & WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'billing_address.first_name / extensions.wpdesk-flexible-invoices-checkout._billing_vat_number' parameter in all versions up to, and including, 7.1.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Execution requires an administrator to open the invoice edit page for the attacker's order and interact with (e.g., type into or trigger a change/keyup event on) a field in the customer metabox, at which point the payload stored in billing fields such as first_name or _billing_vat_number is decoded from its entity-escaped input value and passed unsanitized to jQuery .html(). Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. | ||||
| CVE-2026-127132 | 2 Rubengc, Wordpress-extensions | 2 Gamipress – Gamification Plugin To Reward Points, Badges & Ranks In Wordpress, Now With Ai, Gamipress | 2026-11-18 | 6.5 Medium |
| The GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI plugin for WordPress is vulnerable to generic SQL Injection via the 'name-1[compare]' parameter in all versions up to, and including, 8.1.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires that an administrator has published at least one GamiPress achievement step triggered by a Forminator field-value submission event, as the GamiPress Forminator integration listener is the only path that routes a form submission's raw field array — including the attacker-controlled compare operator — into gamipress_query_logs(). | ||||
| CVE-2026-118519 | 2 Alexacrm, Wordpress-extensions | 2 Datapress (dataverse Integration), Datapress (dataverse Integration) | 2026-11-18 | 5.9 Medium |
| The DataPress (Dataverse Integration) plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.97 via the 'src' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Exploitation requires WP_DEBUG to be defined as true on the target site — not the default on production, but commonly enabled on staging, development, and misconfigured production environments. | ||||
| CVE-2026-12040 | 2 Fs-code, Wordpress-extensions | 2 Fs Poster - Wordpress Social Media Auto Poster & Scheduler [facebook, Instagram, Twitter, Pinterest], Fs Poster | 2026-11-18 | 6.4 Medium |
| The FS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest] plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 8.0.1 via the 'site_url' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. The Guzzle HTTP client is instantiated with TLS certificate verification disabled and redirect following enabled by default, allowing redirect-based SSRF bypasses and enabling internal port scanning via distinguishable server responses. | ||||
| CVE-2026-126009 | 2 Nomadcoder, Wordpress-extensions | 2 (simply) Guest Author Name, (simply) Guest Author Name | 2026-11-18 | 6.4 Medium |
| The (Simply) Guest Author Name plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the user Biographical Info (description) field in versions up to, and including, 4.42. The plugin unconditionally calls remove_filter('pre_user_description', 'wp_filter_kses') at plugin load (sfly-guest-author.php:17), which strips WordPress core's sanitization of the user description field for users who lack the unfiltered_html capability (Subscribers, Contributors, Authors). This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in their own profile Biographical Info that will execute whenever a user accesses a page rendering that author's description (such as an author archive or a single-post author bio in default WordPress themes like Twenty Seventeen and Twenty Fifteen). | ||||
| CVE-2026-127921 | 2 Scottopolis, Wordpress-extensions | 2 Apppresser – Mobile App Framework, Apppresser | 2026-11-18 | 7.5 High |
| The AppPresser – Mobile App Framework plugin for WordPress is vulnerable to generic SQL Injection via the 'appp_cam_file[name]' parameter in all versions up to, and including, 5.0.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Although the AJAX handler is registered for unauthenticated users, the only authorization gate is a nonce check, and the required nonce is only emitted to logged-in users viewing a page containing the [app-camera] shortcode, making Subscriber-level access the effective minimum requirement for exploitation. | ||||
| CVE-2026-118493 | 1 Apache | 1 Iggy | 2026-11-18 | N/A |
| Insertion of Sensitive Information into Log File vulnerability in the Apache Iggy server. If Apache Iggy 0.9.0 started without IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD, it generated a root password and wrote it to the server log file, which is enabled by default. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) let a user with only the read_servers permission download the server log files. That user could read the generated root password and log in as root. This issue affects Apache Iggy: 0.9.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue. Version 0.10.0 never generates a root password, and the snapshot requires the manage_servers permission. If a 0.9.0 server generated its root password, change that password. | ||||
| CVE-2026-132079 | 1 Apache | 1 Iggy Go Sdk | 2026-11-18 | N/A |
| Insufficient Session Expiration vulnerability in the Apache Iggy Go SDK. The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field that the server reads. The server read a nonzero expiry as 2^32 times the requested value. A token created through the Go TCP client therefore stayed valid about four billion times longer than the caller asked for. This issue affects Apache Iggy Go SDK: from 0.5.0 before 0.10.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue. Tokens that an earlier version created keep their long expiry on the server. Delete those tokens and create new ones. | ||||
| CVE-2026-132123 | 1 Modified-shop | 2 Modified-shop, Modified Ecommerce Shopsoftware | 2026-11-18 | 4.8 Medium |
| modified eCommerce Shopsoftware through 3.3.0 contains a stored cross-site scripting vulnerability that allows authenticated administrators to inject scripts via the cross_sell_group_name parameter in admin/cross_sell_groups.php. Attackers with per-page access to cross-selling groups can store a script payload that executes in other administrators' browsers, including full administrators, when they view the group listing. | ||||