Overview 205,722 matches · 7,722 in Waratek scope · 0 protected · 2,683 exploited · 631 CISA KEV · 3,431 public PoC · 727 EPSS ≥ 0.5
205,722matches
7,722in Waratek scope3.8%
0protected0.0%
2,683exploited1.3%
631CISA KEV0.3%
3,431public PoC1.7%
727EPSS ≥ 0.50.4%
Protected by Waratek
0
0.0%
Rule in development
4
0.0%
Mitigation candidate
95
0.0%
No exploit published
7,623
3.7%
Outside Waratek scope
578
0.3%
Not applicable
191,236
93.0%
Withdrawn CVE
6,186
3.0%
Critical
22,302
10.8%
High
78,187
38.0%
Medium
83,900
40.8%
Low
10,624
5.2%
None
79
0.0%
Unknown
10,630
5.2%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
205,722
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 37,594 / quarter
Q3 232,818
No exploit published51
Outside Waratek scope18
Not applicable2,069
Withdrawn CVE680
Critical376
High849
Medium870
Low43
Unknown680
not blocked2,818
Exploited50
Working exploit published40
Proof of concept only520
Forecast only2
No public exploit2,206
Q4 237,876
Mitigation candidate13
No exploit published234
Outside Waratek scope53
Not applicable7,439
Withdrawn CVE137
Critical1,350
High3,242
Medium3,077
Low69
Unknown138
not blocked7,876
Exploited134
Working exploit published80
Proof of concept only924
Forecast only28
No public exploit6,710
Q1 248,870
Mitigation candidate13
No exploit published202
Outside Waratek scope49
Not applicable8,382
Withdrawn CVE224
Critical1,407
High3,317
Medium3,781
Low138
Unknown227
not blocked8,870
Exploited179
Working exploit published99
Proof of concept only1,920
Forecast only14
No public exploit6,658
Q2 2411,990
Mitigation candidate4
No exploit published165
Outside Waratek scope41
Not applicable11,467
Withdrawn CVE313
Critical1,212
High4,542
Medium5,686
Low235
Unknown315
not blocked11,990
Exploited208
Working exploit published100
Proof of concept only1,804
Forecast only53
No public exploit9,825
Q3 248,634
Mitigation candidate6
No exploit published110
Outside Waratek scope25
Not applicable8,357
Withdrawn CVE136
Critical1,036
High3,288
Medium4,014
Low160
Unknown136
not blocked8,634
Exploited166
Working exploit published107
Proof of concept only1,861
Forecast only8
No public exploit6,492
Q4 2411,102
Mitigation candidate5
No exploit published142
Outside Waratek scope72
Not applicable10,805
Withdrawn CVE78
Critical1,182
High4,138
Medium5,498
Low203
None1
Unknown80
not blocked11,102
Exploited183
Working exploit published93
Proof of concept only1,862
Forecast only7
No public exploit8,957
Q1 2512,391
Mitigation candidate4
No exploit published151
Outside Waratek scope23
Not applicable11,747
Withdrawn CVE466
Critical1,144
High4,298
Medium6,184
Low299
Unknown466
not blocked12,391
Exploited168
Working exploit published138
Proof of concept only2,404
Forecast only6
No public exploit9,675
Q2 2512,173
Rule in development1
Mitigation candidate8
No exploit published153
Outside Waratek scope31
Not applicable11,470
Withdrawn CVE510
Critical1,082
High3,921
Medium6,096
Low558
None6
Unknown510
not blocked12,173
Exploited194
Working exploit published88
Proof of concept only2,803
Forecast only9
No public exploit9,079
Q3 2512,184
Rule in development1
Mitigation candidate6
No exploit published237
Outside Waratek scope40
Not applicable11,418
Withdrawn CVE482
Critical1,198
High3,987
Medium5,267
Low1,249
None1
Unknown482
not blocked12,184
Exploited192
Working exploit published294
Proof of concept only3,014
Forecast only1
No public exploit8,683
Q4 2513,119
Rule in development2
Mitigation candidate5
No exploit published189
Outside Waratek scope46
Not applicable12,513
Withdrawn CVE364
Critical1,030
High4,437
Medium5,459
Low929
None3
Unknown1,261
not blocked13,119
Exploited181
Working exploit published70
Proof of concept only2,737
No public exploit10,131
Q1 2616,221
Mitigation candidate8
No exploit published160
Outside Waratek scope62
Not applicable14,888
Withdrawn CVE1,103
Critical1,657
High5,949
Medium6,174
Low1,209
None33
Unknown1,199
not blocked16,221
Exploited199
Working exploit published135
Proof of concept only4,202
Forecast only3
No public exploit11,682
Q2 2620,779
Mitigation candidate11
No exploit published755
Outside Waratek scope49
Not applicable19,781
Withdrawn CVE183
Critical2,268
High8,490
Medium8,199
Low1,628
None11
Unknown183
not blocked20,779
Exploited248
Working exploit published148
Proof of concept only5,180
Forecast only2
No public exploit15,201
Q3 2637,594
Mitigation candidate11
No exploit published3,208
Outside Waratek scope47
Not applicable33,568
Withdrawn CVE760
Critical4,726
High15,783
Medium12,155
Low2,205
None19
Unknown2,706
not blocked37,594
Exploited311
Working exploit published145
Proof of concept only6,492
No public exploit30,646
Q4 2629,971
Mitigation candidate1
No exploit published1,866
Outside Waratek scope22
Not applicable27,332
Withdrawn CVE750
Critical2,634
High11,946
Medium11,440
Low1,699
None5
Unknown2,247
not blocked29,971
Exploited270
Working exploit published49
Proof of concept only3,917
No public exploit25,735
Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-96991 | High | 2026-11-21 | Not applicable | No public exploit | The SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via WebPage JSON-LD Description in all versions up to, and including, 3.1.3 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. Exploitation requires that the target page renders a core/latest-comments block with the displayExcerpt option enabled, causing comment content to be incorporated into the WebPage JSON-LD description output in wp_head. |
| CVE-2026-87092 | Medium | 2026-11-21 | Not applicable | No public exploit | The Unlimited Elements For Elementor plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.0.26 via the getFileContentByUrl function. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information. The nonce protecting the get_addon_output_data AJAX endpoint is emitted on the Elementor editor page, which is accessible to Contributors, making the endpoint reachable by any authenticated user at that privilege level or above. |
| CVE-2026-19793 | High | 2026-11-21 | Not applicable | No public exploit | The WP Import Export Lite plugin for WordPress is vulnerable to Limited Code Injection in all versions up to, and including, 3.9.32 via the 'comment' parameter. This is due to a two-stage shortcode check that evaluates the raw mapping placeholder before data substitution, causing the neutralizer to be skipped when attacker-controlled comment content containing a malicious [wpie_function] shortcode is substituted at runtime. This makes it possible for unauthenticated attackers to inject arbitrary PHP callables on the server. Exploitation requires an Administrator to perform the standard Export With Settings For Import followed by a New Import migration workflow, which is a routine operational task; the attacker themselves requires no account or authentication, needing only the ability to submit a pending comment on any comments-open post. |
| CVE-2026-133964 | Medium | 2026-11-21 | Not applicable | No public exploit | A security vulnerability has been detected in Bytebase DBHub up to 2.0.0. Impacted is the function escapeHatchFunctionKeywords of the file src/utils/allowed-keywords.ts of the component Read Only Mode. The manipulation of the argument tool leads to incomplete blacklist. Remote exploitation of the attack is possible. The vendor was contacted early about this disclosure but did not respond in any way. |
| CVE-2026-133963 | Medium | 2026-11-21 | Not applicable | No public exploit | A vulnerability was determined in MaysWind AriaNg-Native up to 1.3.14. Affected by this issue is the function shell.openPath of the file main/ipc/main-process.js of the component IPC Handler. This manipulation of the argument dir causes improper input validation. The attack can be initiated remotely. Upgrading to version 1.3.15 can resolve this issue. Patch name: ac5a4bcf102f605b160f19fcc9fbaec67f9596d7. You should upgrade the affected component. |
| CVE-2026-133958 | Medium | 2026-11-21 | Not applicable | No public exploit | A flaw was found in Quay. Insufficient validation of repository notification webhook URLs allows an authenticated administrator to trigger Server-Side Request Forgery (SSRF). By specifying an internal URL or a redirect to an internal destination, an attacker can force the Quay worker to issue unauthorized HTTP requests to internal network locations and cloud metadata services. |
| CVE-2026-133471 | Medium | 2026-11-21 | Not applicable | No public exploit | The Fastcache by Host.it plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 's' parameter in all versions up to, and including, 1.7.14 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. This code path is only reachable when both the Light Images feature and the DOMDocument entity-decode branch are enabled (lightimgs_status = 1 and img_processing_entity_decode = 1), which reflect the default plugin configuration. |
| CVE-2026-133439 | Medium | 2026-11-21 | Not applicable | No public exploit | The Coupon Creator plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_title' parameter in all versions up to, and including, 3.6.5 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. This vulnerability is only exploitable when an administrator has enabled the 'Disable Print View' option (cctor_hide_print_link), as this setting is required to reach the vulnerable else branch; the default configuration is not affected. |
| CVE-2026-133369 | Medium | 2026-11-21 | Not applicable | No public exploit | The CodePeople Post Map for Google Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'cpm_map[api_key]' parameter in all versions up to, and including, 1.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The settings form nonce is itself rendered on the Subscriber-accessible page (reachable via a trailing-slash bypass of the slug guard), making nonce verification no real barrier to the unauthorized save. |
| CVE-2026-133367 | High | 2026-11-21 | Not applicable | No public exploit | The WPC Frequently Bought Together for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'variation' parameter in all versions up to, and including, 8.0.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. The nonce protecting the woobt_add_all_to_cart AJAX handler is emitted to all unauthenticated visitors via wp_localize_script, effectively nullifying the nonce as an authentication barrier and making the handler reachable without any login. |
| CVE-2026-133361 | High | 2026-11-21 | Not applicable | No public exploit | The BlockStrap Page Builder – Bootstrap Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 0.1.65 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. Successful exploitation requires that the attacker has previously had at least one comment approved for a given name and email address, allowing subsequent comments from that author to bypass moderation under WordPress's default policy; exploitation is also limited to sites using a block theme, which is the WordPress default. |
| CVE-2026-132781 | Medium | 2026-11-21 | Not applicable | No public exploit | The Booking Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'booking' shortcode in all versions up to, and including, 12.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. |
| CVE-2026-132620 | High | 2026-11-21 | Not applicable | No public exploit | The WPBot – AI ChatBot for WordPress & Growth Suite: SEO, AI Writer, Email Marketing, Social Media plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'text' parameter in all versions up to, and including, 9.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 exploit is triggered when an administrator opens the Chat Sessions screen, at which point the plugin's bundled Bootstrap 3.3.7 affix data-API passes the attacker-controlled data-target attribute value to jQuery as HTML, executing the injected script in the administrator's session. |
| CVE-2026-132089 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Newsletter WordPress plugin before 9.4.0 does not keep a subscriber's secret key out of the redirect it returns after a subscription request when double opt-in is enabled, allowing unauthenticated attackers to confirm a subscription for any email address without access to its mailbox and, when the address already has an unconfirmed subscription, to reset that record with their own details. |
| CVE-2026-132082 | Unknown | 2026-11-21 | Not applicable | No public exploit | The RSVPMaker for Toastmasters WordPress plugin before 6.9.3 does not sanitise and escape a parameter before outputting it back in an admin page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin. |
| CVE-2026-132081 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Titan Anti-spam & Security WordPress plugin before 7.5.5 does not protect or remove the diagnostic archive it writes to the uploads folder when an administrator exports its logs, and names it after the export date alone, allowing unauthenticated visitors to download the Titan Anti-spam & Security WordPress plugin before 7.5.5's logs, including visitor IP addresses, and the site's system information. |
| CVE-2026-132073 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Keywords to Links Converter WordPress plugin before 2.2.5 does not validate a value submitted to one of its AJAX actions before saving it as an option that it later uses in an arithmetic operation on every admin and front-end request, allowing users with a role as low as Subscriber to make the whole site return a fatal error until the option is manually reset. |
| CVE-2026-132044 | Unknown | 2026-11-21 | Not applicable | No public exploit | The FluentCommunity WordPress plugin before 2.8.0 does not check that a lesson belongs to the course a course creator is authorised to manage before moving it, allowing a user with the Course Creator role to move lessons out of other creators' courses into their own and read their content. |
| CVE-2026-132042 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Keywords to Links Converter WordPress plugin before 2.2.5 does not sanitise and escape a parameter before using it in a SQL statement via an AJAX action available to any authenticated user, allowing users with a role as low as Subscriber to perform SQL injection attacks and read arbitrary data from the database. |
| CVE-2026-131985 | Unknown | 2026-11-21 | Not applicable | No public exploit | The FluentCommunity WordPress plugin before 2.13.0 does not verify that a referenced media item belongs to the user, or is not already attached elsewhere, before re-linking it to their own content, and its media identifiers are predictable from public post data, allowing users with a role as low as Subscriber to take over and delete media uploaded by other users, including administrators. |
| CVE-2026-131984 | Unknown | 2026-11-21 | Not applicable | No public exploit | The FluentCommunity WordPress plugin before 2.7.0 does not verify that the user is allowed to manage the space it actually modifies or deletes, allowing a user who administers any one space to modify or permanently delete any other space on the site, together with its posts, comments, reactions and memberships. |
| CVE-2026-131983 | Unknown | 2026-11-21 | Not applicable | No public exploit | The FluentCommunity WordPress plugin before 2.13.0 does not apply the per-link visibility rules of space sidebar links when listing spaces in its space discovery feature, allowing unauthenticated visitors to retrieve the titles and URLs of links restricted to logged-in users or specific memberships, as well as disabled links, for every public and private space. |
| CVE-2026-131979 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Shortcodes Ultimate WordPress plugin before 7.9.1 does not restrict the content type of its lightbox shortcode, allowing users with the contributor role and above to make the lightbox fetch HTML from an attacker-controlled server and insert it into the page unsanitised, leading to Stored Cross-Site Scripting when a user opens the lightbox. |
| CVE-2026-131978 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Shortcodes Ultimate WordPress plugin before 7.9.1 does not restrict which PHP functions a shortcode's filter attribute can call, allowing users with a role as low as Contributor to remove WordPress' term-slug sanitization and perform SQL injection attacks through another shortcode's taxonomy term attribute. |
| CVE-2026-131977 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Shortcodes Ultimate WordPress plugin before 7.9.1 does not escape the error message returned when a remote feed cannot be retrieved before outputting it, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks against administrators by pointing the feed at a server they control. |
| CVE-2026-131976 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Shortcodes Ultimate WordPress plugin before 7.9.1 does not prevent placeholders in a shortcode attribute from being expanded with unescaped nested shortcode output, allowing users with a role as low as contributor to perform Stored Cross-Site Scripting attacks. |
| CVE-2026-131975 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Shortcodes Ultimate WordPress plugin before 7.9.1 does not prevent format specifiers in a shortcode attribute from being interpreted when building navigation menu markup, which could allow users with a role as low as Contributor to perform Stored Cross-Site Scripting attacks. |
| CVE-2026-131971 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Payment forms, Buy now buttons, and Invoicing System | GetPaid WordPress plugin before 2.8.63 does not check that the visitor is allowed to view an invoice before rendering it through its single-invoice shortcode, and its payment-form embed page lets unauthenticated users render that shortcode for any invoice ID, disclosing customers' names, billing addresses, phone numbers, line items and payment status. |
| CVE-2026-131822 | High | 2026-11-21 | Not applicable | No public exploit | The Contact Form to Any API plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'your-message (any CF7 form field)' parameter in all versions up to, and including, 3.0.7 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 malicious payload is stored via a single unauthenticated POST to Contact Form 7's public REST feedback endpoint, which uses permission_callback __return_true and requires no authentication or prior interaction to submit. |
| CVE-2026-131651 | Medium | 2026-11-21 | Not applicable | No public exploit | The rtMedia for WordPress, BuddyPress and bbPress plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'media_title' parameter in all versions up to, and including, 4.7.18 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability is only triggerable via the Backbone.js-rendered "Load More" pagination path; the server-side PHP gallery rendering correctly escapes media_title with esc_attr() and is not affected. |
| CVE-2026-131609 | High | 2026-11-21 | Not applicable | No public exploit | The Germanized for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'billing_address.first_name (Store API checkout) → stored on parent order; withdrawal get_first_name() fallback' parameter in all versions up to, and including, 4.1.8 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 payload is planted via an unauthenticated guest checkout order's billing first name through the WooCommerce Store API, with execution triggered by a subsequent unauthenticated withdrawal request submission whose nonce is publicly available on the /withdraw-from-contract/ page. |
| CVE-2026-131577 | Medium | 2026-11-21 | Not applicable | No public exploit | The WSMS (formerly WP SMS): SMS Notifications, OTP Login and WooCommerce SMS plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.2.14. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with author-level access and above, to send arbitrary SMS messages to attacker-chosen phone numbers from the site's trusted sender ID, incurring per-message gateway charges to the site owner and enabling SMS spam or phishing campaigns. |
| CVE-2026-130894 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Newsletter WordPress plugin before 9.4.0 does not protect its unsubscription actions against Cross-Site Request Forgery for subscribers it identifies from its own tracking cookie, allowing attackers to unsubscribe a subscriber from the site's newsletter by making them visit a malicious page. |
| CVE-2026-130892 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Newsletter WordPress plugin before 9.4.0 does not properly validate the destination of the redirect performed when a subscriber changes their list membership from a newsletter link, checking only that it begins with the site's URL, allowing unauthenticated attackers to redirect users to external sites whose address starts with the site's URL. |
| CVE-2026-130891 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Newsletter WordPress plugin before 9.4.0 does not check that a visitor is really the subscriber before showing them newsletters marked as private, and accepts a weaker subscriber identifier that anyone can obtain by submitting a known subscriber's email address to the public subscription form, allowing unauthenticated attackers who know a subscriber's email address to read every private newsletter sent to that subscriber. |
| CVE-2026-130323 | High | 2026-11-21 | Not applicable | No public exploit | The Accept Stripe Payments plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'href of any <a> element containing 'asp_action=show_pp&product_id='' parameter in all versions up to, and including, 2.1.4 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. Successful exploitation requires that a user clicks the attacker-placed comment link to trigger the sink; however, if the non-default 'Prefetch Payment Popup Scripts' option is enabled, execution occurs on page load with no user interaction required. |
| CVE-2026-130150 | Medium | 2026-11-21 | Not applicable | No public exploit | The Product Import Export for WooCommerce – CSV Product Importer & Exporter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'author (initial store via wp-comments-post.php) / CSV cell on import' parameter in all versions up to, and including, 2.6.9 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 exploit requires an administrator to approve the attacker's review, then export and re-import it using the plugin's default column mapping, with the import taking the INSERT branch — which occurs automatically on any site whose database table prefix is not the literal 'wp_', when the CSV has no comment_ID mapping, or when the original review has been trashed. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. |
| CVE-2026-130148 | Low | 2026-11-21 | Not applicable | No public exploit | The YMC Filter plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.14.1 via the 'post_status' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract retrieve rendered grid HTML containing titles, excerpts, author names, dates, categories, tags, and thumbnails of private, draft, pending, and future posts they do not have permission to view. Exposure only occurs when an administrator has configured at least one non-publish status in the filter grid's Appearance → Post Status setting, as attacker-supplied statuses are intersected with this administrator-defined allowlist before being passed to WP_Query. |
| CVE-2026-129814 | Low | 2026-11-21 | Not applicable | No public exploit | The SDO Information Get Object Description and Get Entry Description responses copy the object or entry name into the mailbox data area and then write a null terminator byte. The copy loops ran up to the last available byte in the buffer, leaving no room for the terminator. When an object or entry name exactly fills the available space the terminator is written one byte past the end of the mailbox data buffer. |
| CVE-2026-129813 | Medium | 2026-11-21 | Not applicable | No public exploit | The CoE complete-access download handler iterated over all subindices of an object and wrote the master-supplied payload into each writable entry. Entries that hold a constant have write-access flags set but carry a NULL data pointer. The handler did not check for this and wrote the master payload through the NULL pointer. |
| CVE-2026-129812 | Medium | 2026-11-21 | Not applicable | No public exploit | An object dictionary entry that holds a constant has no process data storage and carries a NULL data pointer. sizeOfPDO did not check for this when resolving a mapped entry to its descriptor. A master that maps such an entry to a PDO causes COE_pdoPack or COE_pdoUnpack to dereference the NULL data pointer on every process data exchange after the mapping is activated. |
| CVE-2026-129811 | High | 2026-11-21 | Not applicable | No public exploit | The PDO mapping bit lengths stored in the mapping objects are writable by the master via SDO. sizeOfPDO summed them without checking the total against the size of the rxpdo[] or txpdo[] process data buffers. A master can craft a mapping whose total bit count exceeds those buffers, causing COE_pdoPack and COE_pdoUnpack to write past their ends during each process data cycle after the PREOP to SAFEOP transition. |
| CVE-2026-129810 | Medium | 2026-11-21 | Not applicable | No public exploit | ESC_eoeprocess and ESC_eoeprocess_tx can be reached before the application calls EOE_config to supply the callback table pointer. When eoe_cfg is NULL the receive handler dereferenced it while processing an incoming EoE frame, and the transmit polling function dereferenced it on each cycle, causing NULL pointer dereferences. |
| CVE-2026-129809 | Medium | 2026-11-21 | Not applicable | No public exploit | ESC_foeprocess can be reached by an incoming mailbox frame before the application calls FOE_config to supply the file table and flush buffer pointers. When foe_cfg or its fbuffer field is NULL the handler dereferenced those pointers while processing the frame, causing a NULL pointer dereference. |
| CVE-2026-129808 | Medium | 2026-11-21 | Not applicable | No public exploit | The EoE receive and transmit paths call the handle_recv_buffer and fetch_send_buffer callbacks without first checking whether they are set. Both callbacks are documented as optional; an application that omits either one causes a call through a NULL function pointer when the first EoE frame arrives or when the transmit polling loop runs. |
| CVE-2026-129807 | Medium | 2026-11-21 | Not applicable | No public exploit | The FoE file table allows entries to omit a write handler by setting write_function to NULL, making the file read-only. FOE_fopen did not check whether write_function was present before accepting a write request; a master sending a WRQ for a read-only file caused a call through a NULL function pointer. |
| CVE-2026-129806 | Medium | 2026-11-21 | Not applicable | No public exploit | The CoE SDO upload handler enters its normal-response path (used for objects longer than 4 bytes) and passes (objd + nsub)->data directly to the pre-object handler and to the response copy. Entries that hold a constant in the value field have data set to NULL; a master can request such an entry and cause a NULL pointer dereference in the upload path. |
| CVE-2026-129805 | Medium | 2026-11-21 | Not applicable | No public exploit | An object dictionary entry can carry write-access flags and still have a NULL data pointer, for example when a constant value is held in the value field rather than in addressable storage. The CoE SDO download handler checked write access but not whether storage was present, then wrote the master-supplied payload through the NULL pointer. |
| CVE-2026-129804 | Medium | 2026-11-21 | Not applicable | No public exploit | FOE_read and FOE_write store the filename length as uint8_t, truncating it modulo 256. When (mbxheader.length - ESC_FOEHSIZE) is a multiple of 256, the length becomes 0. Additionally, a request whose mailbox length equals ESC_FOEHSIZE exactly also produces a length of 0 without any truncation. In both cases FOE_fopen calls strncmp with a length of 0, which always returns equal, so the first registered file whose password is 0 is opened regardless of the filename the master sent. |
| CVE-2026-129803 | Medium | 2026-11-21 | Not applicable | No public exploit | The CoE entry gate accepts frames with mbxheader.length as low as COE_MINIMUM_LENGTH (8), but a normal SDO Download requires at least COE_HEADERSIZE (10) bytes of CoE payload to carry its header fields. With mbxheader.length of 8 or 9, the segmented-transfer branch misevaluates due to unsigned wrap, leaving the declared SDO size unclamped. copy2mbx then reads that many bytes starting past the end of the actual payload and writes them into the object buffer. |
| CVE-2026-129802 | Medium | 2026-11-21 | Not applicable | No public exploit | EOE_set_ip reads each network parameter field (MAC, IP, subnet, gateway, DNS IP, DNS name) from the mailbox payload before checking whether the payload is large enough to contain them. The single bounds check at the end of the function does not prevent the reads from happening. A master can send a Set-IP frame with all flags set and mbxheader.length equal to the minimum, causing all reads to access memory past the end of the payload. |
| CVE-2026-129801 | High | 2026-11-21 | Not applicable | No public exploit | The FoE DATA frame handler computes the payload length from the master-supplied mailbox length field and passes it directly to FOE_fwrite. The length is checked against the remaining file capacity but not against the physical mailbox buffer size. A master can declare a large length while sending a short frame, causing FOE_fwrite to read past the end of the mailbox buffer. |
| CVE-2026-129800 | Medium | 2026-11-21 | Not applicable | No public exploit | sizeOfPDO, called during state transitions, uses the subindex-0 count of the SM-assign and PDO-mapping objects as loop bounds without checking those counts against the descriptor array sizes. On builds where those subindex-0 values are writable via SDO, a master can write 0xFF and cause sizeOfPDO to read past the end of the descriptor arrays on the next transition to SAFEOP. |
| CVE-2026-129799 | Medium | 2026-11-21 | Not applicable | No public exploit | A CoE SDO request for index 0xFFFF matches the object list terminator entry instead of returning not-found. The terminator has a NULL objdesc pointer. Callers dereference it without checking, crashing the slave. |
| CVE-2026-129798 | High | 2026-11-21 | Not applicable | No public exploit | The CoE SDO segmented download handler advances a write pointer by each incoming segment's size but does not track how many bytes have been written in total. A master can keep sending non-last segments until the pointer has walked past the end of the object buffer or the complete-access staging buffer. |
| CVE-2026-129797 | High | 2026-11-21 | Not applicable | No public exploit | SDO_downloadsegment is called whenever a mailbox frame carries the DOWNLOADSEGREQ command byte, regardless of whether a segmented download is actually in progress. ESCvar.data, which the handler writes through, is NULL until a segmented transfer is started. A master can send a DOWNLOADSEGREQ at any time and write through a NULL or stale pointer. |
| CVE-2026-129796 | High | 2026-11-21 | Not applicable | No public exploit | The CoE SDO download handler for flexible-length objects (VISIBLE_STRING, OCTET_STRING, and similar) does not check that the master-declared transfer size fits within the object before writing. Two distinct writes are affected: the VISIBLE_STRING zero-padding memset and the first-frame copy into the object buffer. |
| CVE-2026-129795 | Medium | 2026-11-21 | Not applicable | No public exploit | When the last EoE fragment has the TIME_APPEND flag set, the handler subtracts 4 from rxframeoffset to strip the timestamp. There is no check that rxframeoffset is at least 4. A fragment carrying fewer than 4 bytes of payload that is also marked LAST causes rxframeoffset to wrap to 0xFFFFFFFC, which is then stored as the buffer length and handed to the TCP/IP stack. |
| CVE-2026-129794 | High | 2026-11-21 | Not applicable | No public exploit | The EoE fragment reassembly code uses a frame size from the wire as the bound for memcpy into the application receive buffer, without checking that the declared size fits in the actual buffer. A master can write up to 2016 bytes into a buffer the application may have sized much smaller. |
| CVE-2026-129344 | High | 2026-11-21 | Not applicable | No public exploit | Uncaught Exception vulnerability in phoenixframework phoenix allows an unauthenticated attacker to cause a denial of service via a client-selected legacy serializer on binary channel broadcasts. When an application broadcasts {:binary, data} payloads on a channel topic, any client that connects without a vsn parameter, or with vsn=1.0.0, and joins that topic makes those broadcasts fail. Phoenix.Channel.Server.send/4 encodes each broadcast with every subscriber's own serializer inside the PubSub dispatch loop, calling fastlane!/1 with no rescue, and the negotiated Phoenix.Socket.V1.JSONSerializer raises Protocol.UndefinedError on a binary payload. Every binary broadcast on the topic then crashes the broadcasting process and skips every subscriber dispatched after the attacker. For broadcasts arriving from other nodes the loop runs in the PubSub adapter worker, whose repeated crashes restart the PubSub supervisor and empty the node's subscription registry while sockets stay connected. This issue affects phoenix: from 1.5.7 before 1.5.16, from 1.6.0-rc.0 before 1.6.18, from 1.7.0-rc.0 before 1.7.25, and from 1.8.0-rc.0 before 1.8.17. |
| CVE-2026-129220 | High | 2026-11-21 | Not applicable | No public exploit | The Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.6.4 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with everest_forms_create_forms capabilities, to activate any already-installed inactive plugin on the server by supplying an arbitrary slug, triggering its activation hooks and escalating privileges up to administrator level. Exploitation requires that a site administrator has delegated the everest_forms_create_forms capability to a lower-privileged role via the plugin's Role & Permission feature, and that at least one inactive installed plugin whose main file follows the slug/slug.php naming convention exists on the server. |
| CVE-2026-129096 | Medium | 2026-11-21 | Not applicable | No public exploit | The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameter in all versions up to, and including, 7.8.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. |
| CVE-2026-129095 | Medium | 2026-11-21 | Not applicable | No public exploit | The Social Media Auto Poster – Schedule & Publish to Buffer plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.2.9. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to delete Buffer sync log history for and disclose Buffer sync log contents of arbitrary posts, including those authored by administrators. The nonce used as the sole gate is not bound to any specific post ID, so a nonce harvested from the attacker's own draft editor screen is valid against any arbitrary post ID submitted in the request. |
| CVE-2026-128361 | High | 2026-11-21 | Not applicable | No public exploit | Improper Input Validation vulnerability in phoenixframework phoenix (Phoenix.Presence) allows an attacker who can join a channel to cause a denial of service via a non-string presence key. track/3,4 accepts any term as the presence key, such as a JSON object taken from a join payload. The key is converted with to_string/1 only later, in Phoenix.Presence.group/1, which raises Protocol.UndefinedError on a map. group/1 runs whenever presences are listed and when each presence diff is broadcast, together with the application's fetch/2, which can likewise raise on an unexpected key. Once such a key is tracked, every process that lists presences on the topic crashes, typically each channel that joins it, and presence diffs for the topic are lost. From 1.7.0 the diff runs in a Task.Supervisor.async task linked to the tracker shard, and Phoenix.Presence.handle_info/2 has no clause for its failure. The shard then terminates, taking down every channel and LiveView process tracked on it and erasing presence state for all its topics. Repeated joins exhaust the restart intensity and take down the application supervisor. This issue affects phoenix: from 1.2.0 before 1.5.16, from 1.6.0-rc.0 before 1.6.18, from 1.7.0-rc.0 before 1.7.25, and from 1.8.0-rc.0 before 1.8.17. |
| CVE-2026-127133 | Medium | 2026-11-21 | Not applicable | No public exploit | The Stream – Activity Log & Audit Trail plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'group-name' parameter in all versions up to, and including, 4.5.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires BuddyPress to be active with its Groups component enabled and default group-creation permissions in place, allowing any logged-in member to create groups. |
| CVE-2026-127002 | Unknown | 2026-11-21 | Not applicable | No public exploit | The RSVP and Event Management WordPress plugin before 2.7.19 does not escape a submitted value before outputting it back in its RSVP form when the form is re-displayed after a failed submission, leading to a Reflected Cross-Site Scripting which could be used against high-privilege users such as admins. |
| CVE-2026-126705 | Medium | 2026-11-21 | Not applicable | No public exploit | The WP Job Portal – AI-Powered Recruitment System for Company or Job Board website plugin for WordPress is vulnerable to time-based SQL Injection via the 'columns[<attacker-chosen key>]' parameter in all versions up to, and including, 2.8.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 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. |
| CVE-2026-126701 | Medium | 2026-11-21 | Not applicable | No public exploit | The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameter in all versions up to, and including, 7.8.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The wp_kses_post filter applied during save is ineffective against tagless attribute-breakout payloads, as it only strips disallowed HTML tags and cannot neutralize a payload containing no '<' characters; the element_id is then echoed without esc_attr() inside a data-id HTML attribute in template-tab.php. |
| CVE-2026-126039 | Unknown | 2026-11-21 | Not applicable | No public exploit | The Hide My WP Ghost WordPress plugin before 7.0.19 does not limit one of its HTML output rewriting patterns to the markup it targets, allowing unauthenticated attackers to inject HTML attributes through a comment author name that execute as Stored XSS for any visitor, including logged-in administrators, on pages that list recent comments. |
| CVE-2026-126011 | High | 2026-11-21 | Not applicable | No public exploit | The Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.5.6 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. This requires the site administrator to have configured the Thickbox lightbox effect with the "Try to apply to all images" context (thumbEffectContext=all_images), and exploitation additionally depends on an administrator approving the attacker's initial comment so that subsequent comments from that author are auto-approved. |
| CVE-2026-125932 | Medium | 2026-11-21 | Not applicable | No public exploit | The Coupon Creator plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'metavalue (with metakeyinput=cctor_expiration)' parameter in all versions up to, and including, 3.6.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit is possible because the cctor_coupon post type advertises 'custom-fields' support, enabling WordPress core's Custom Fields metabox for Contributors, and the unregistered cctor_expiration meta key causes sanitize_meta() to be a no-op, allowing raw HTML to be stored verbatim in the database via a single AJAX request. |
| CVE-2026-125054 | High | 2026-11-21 | Not applicable | No public exploit | The SiteOrigin CSS plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'class' parameter in all versions up to, and including, 1.6.9 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. Successful exploitation requires a Contributor-level or higher attacker to store a crafted class attribute value in a post, which then fires when a user with the edit_theme_options capability opens the Visual Inspector on the affected post and clicks anywhere in the preview iframe. Exploitation by unauthenticated attackers requires that a third-party plugin providing wp_kses_post()-filtered unauthenticated front-end submission is installed and configured, and a moderator approves the submission. On a default installation, where that is not configured, the vulnerability requires attackers with contributor-level access and above. |
| CVE-2026-125039 | High | 2026-11-21 | Not applicable | No public exploit | The EZ SQL Reports Shortcode Widget and DB Backup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'User-Agent header (stored to comment_agent)' parameter in all versions up to, and including, 5.26.45 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. Successful exploitation requires that an administrator has saved a report whose SQL query selects attacker-controlled data such as comment_agent, and that the attacker can identify the saved report's slug — a condition trivially met when the administrator publishes the report on a public page via the [SQLREPORT] shortcode. |
| CVE-2026-125011 | Medium | 2026-11-21 | Not applicable | No public exploit | The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameter in all versions up to, and including, 7.8.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. |
| CVE-2026-124976 | High | 2026-11-21 | Not applicable | No public exploit | The Swift Performance Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '<attacker-chosen parameter name>' parameter in all versions up to, and including, 2.3.7.5 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. This requires that an administrator has configured at least one Cacheable AJAX Action via the plugin's AJAX Cache feature, a condition attackers can confirm by probing for a swift-performance: HIT response header. |
| CVE-2026-124248 | Medium | 2026-11-21 | Not applicable | No public exploit | The GPTranslate – Multilingual AI Translation Agent for WordPress: Translate Your Site with AI plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 2.34.17 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. Exploitation requires the plugin's non-default 'HTML DOM method' to be enabled for server-side translation, and a translation row for the target language-prefixed URL must exist to arm the output buffer that routes page content through the vulnerable Simple HTML DOM parser. |
| CVE-2026-124216 | High | 2026-11-21 | Not applicable | No public exploit | The Orphans plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 3.4.5 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. Exploitation requires a two-step comment chain: a benign first comment must be approved under a given name and email so that WordPress's comment_previously_approved mechanism auto-publishes the attacker's payload comment without moderation. |
| CVE-2026-124214 | Medium | 2026-11-21 | Not applicable | No public exploit | The WP Data Access – App Builder for Tables, Forms, Dashboards, Charts & Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'HyperlinkObject.label (percent-encoded)' parameter in all versions up to, and including, 5.5.92 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. This requires the WordPress site to have a published Anonymous-access Registration Form app configured against a table with a HyperlinkObject column, and a legacy Data Project list using a $$link$$ Dynamic Hyperlink against that same column; given this configuration, any unauthenticated visitor can plant the payload. |
| CVE-2026-123970 | Medium | 2026-11-21 | Not applicable | No public exploit | The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'thread[body]' parameter in all versions up to, and including, 3.2.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful execution of the injected script is limited to viewers whose forum access profile denies attachment viewing (va=0 or caa=0), meaning exploitation depends on an administrator having configured a custom forum access profile that permits reading but denies attachment viewing — this is not the default shipped configuration. |
| CVE-2026-123830 | High | 2026-11-21 | Not applicable | No public exploit | The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data[display_name]' parameter in all versions up to, and including, 3.2.4 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. This requires public user registration to be enabled (users_can_register=1) and a valid _wpfnonce fetched from the public sign-up page, but is otherwise fully unauthenticated. |
| CVE-2026-123663 | Unknown | 2026-11-21 | Not applicable | No public exploit | The ProfilePress WordPress plugin before 4.18.1 takes the role for an account registered through a combined login and registration form from the separate registration form that shares its numeric ID, allowing unauthenticated users to register with the elevated role, such as Editor, assigned by an unpublished registration form. |
| CVE-2026-123086 | High | 2026-11-21 | Not applicable | No public exploit | The PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.3.4 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to permanently force-delete arbitrary trashed posts, pages, and revisions owned by any user, including higher-privileged users. The required nonce is trivially harvested by any Contributor-level user because the static 'revisions-deleted' nonce action is emitted in a redirect header on the init hook before WordPress enforces edit.php's capability check, and once obtained it authorizes deletion of any trashed post or revision on the site. |
| CVE-2026-122264 | Medium | 2026-11-21 | Not applicable | No public exploit | The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'member[about]' parameter in all versions up to, and including, 3.2.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the attacking subscriber to have met the default antispam threshold of at least 3 forum posts before the account editing page becomes accessible. |
| CVE-2026-122230 | High | 2026-11-21 | Not applicable | No public exploit | The Thim Kit for Elementor – Pre-built Templates & Widgets for Elementor plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.4.8 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. Exploitation requires that the Post Comment widget is used with the Text Reveal entrance animation (Elementor class 'ekit--fx-word-reveal') on a Single Post template, and the comment widget must be within the initial viewport; once the first comment by an attacker is approved, or if comment moderation is disabled, subsequent payloads fire automatically for every visitor who loads the affected page. |
| CVE-2026-122228 | Medium | 2026-11-21 | Not applicable | No public exploit | The ProfilePress – Paid Membership, Online Courses (LMS), Ecommerce, User Registration & Login Form, User Profile & Restrict Content plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.18.0 via the 'sortby<form_id>, filter<form_id>' parameter. This makes it possible for unauthenticated attackers to extract reconstruct any listed member's full e-mail address one character at a time via a boolean LIKE oracle, and enumerate users holding arbitrary usermeta keys such as ppress_billing_phone. The e-mail address oracle is reachable on any default install that used the plugin's 'Create pages' onboarding notice, because pp_email_address is enabled as a search field by default and the resulting directory page is published with no capability or nonce gate. |
| CVE-2026-122223 | Medium | 2026-11-21 | Not applicable | No public exploit | The plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'values[text_shadow_color]' parameter in all versions up to, and including, 9.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The wp_kses_post sanitization applied at save time does not strip the payload because it is stored as URL-encoded JSON inside a shortcode attribute, containing no literal HTML tags for kses to tokenize, leaving the malicious value intact until render time. |
| CVE-2026-122221 | Medium | 2026-11-21 | Not applicable | No public exploit | The plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'section_title_tag' parameter in all versions up to, and including, 9.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Although the plugin ships a resolveSectionTitleTag() helper that enforces an [h1–h6, p] allow-list, the accordion render path never invokes it, and the wp_kses_post sanitization applied to post_content on save does not parse shortcode attribute text, leaving the malicious value stored verbatim. |
| CVE-2026-122161 | Medium | 2026-11-21 | Not applicable | No public exploit | The plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'hover_custom_background' parameter in all versions up to, and including, 9.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. wp_kses_post applied to post content on save does not parse shortcode attribute text, allowing injected double-quotes to survive storage and break out of the style attribute context at render time. |
| CVE-2026-121155 | Unknown | 2026-11-21 | Not applicable | No public exploit | The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 do not preserve the escaping of JSON-formatted database values when they rewrite the database during a restore to a new address or server, which could allow unauthenticated attackers to plant harmless-looking escaped markup, for example in a comment author name, that becomes Stored Cross-Site Scripting once an administrator performs such a restore. |
| CVE-2026-121154 | Unknown | 2026-11-21 | Not applicable | No public exploit | The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 do not keep serialized string lengths consistent when their database search and replace processes certain serialized values, allowing users with a role as low as Subscriber to plant data that becomes an attacker-chosen PHP object after an administrator runs a URL-lengthening search and replace or a migration restore. When the replacement changes the length of the text, the declared string lengths inside the stored value no longer match and the corrupted value is written back, so when WordPress later reads it the trailing bytes are parsed as further serialized structure, including an object of a class the attacker named. No gadget chain is known in the UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 themselves; further impact depends on classes available from other installed code. |
| CVE-2026-121153 | Unknown | 2026-11-21 | Not applicable | No public exploit | The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 do not keep a serialized value inert when their database search and replace reaches its recursion limit, allowing users with a role as low as Subscriber to plant data in their own user meta that is rewritten into a live PHP object when an administrator later runs a search and replace or a migration restore, and is then instantiated by WordPress on a later read. This is distinct from CVE-2024-10957, whose fix restricted the unserialize call but left this path in place. No gadget chain is present in WordPress core or the UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 themselves; further impact depends on a suitable class from another installed UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 or . |
| CVE-2026-121152 | Unknown | 2026-11-21 | Not applicable | No public exploit | The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 do not safely process the output of the external database dump tool when backing up large tables, allowing users with a role as low as Subscriber to store profile data that turns into SQL executed when an administrator later restores the backup, for example to grant themselves the administrator role. |
| CVE-2026-121151 | Unknown | 2026-11-21 | Not applicable | No public exploit | The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 do not preserve long database values byte-for-byte when restoring a database backup, allowing users with a role as low as Subscriber to plant a serialized value that becomes a PHP Object Injection once an administrator backs up and restores the database. No gadget chain is known in the UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 or WordPress core, so the demonstrated effect is instantiation of an attacker-chosen class in the attacker's own requests. Exploitation requires the planted data to line up exactly with how the backup is read back, which depends on details of the attacker's row and the database dump format. |
| CVE-2026-121150 | Unknown | 2026-11-21 | Not applicable | No public exploit | The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 do not correctly handle comment-like content found in the middle of a long SQL statement when restoring a database backup, allowing users with a role as low as Subscriber who have stored crafted content in their own profile to have SQL executed when an administrator later restores a backup, and so escalate their account to administrator. This is a different code path from the backup restore issue fixed in 1.26.10, and it does not depend on the database server's maximum packet size. |
| CVE-2026-120745 | High | 2026-11-21 | Not applicable | No public exploit | The Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'reg_bio' parameter in all versions up to, and including, 4.18.0 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 reg_bio parameter is accepted by the registration handler's allowlist even when the rendered registration form does not include a biography field, meaning an unauthenticated attacker can supply the payload via a raw POST request without needing a visible biography input on the form. |
| CVE-2026-120743 | Medium | 2026-11-21 | Not applicable | No public exploit | The Simply Schedule Appointments plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'payment_method' parameter in all versions up to, and including, 1.6.13.4 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 stored payload is only rendered when an administrator navigates to the hidden support page (/wp-admin/admin.php?ssa-support-admin=1) and triggers the 'Fix appointment durations' action, a condition reliably engineered by the attacker by smuggling a '+1 day' suffix in the start_date field to create a persistent duration mismatch that routes the malicious booking through the vulnerable echo path. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. |
| CVE-2026-120738 | Medium | 2026-11-21 | Not applicable | No public exploit | The Organize Media Folder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'EXIF.DateTimeOriginal' parameter in all versions up to, and including, 2.00 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This bypass of wp_filter_post_kses means the injected payload survives regardless of the uploader's unfiltered_html capability; Subscriber-level access becomes sufficient when a front-end attachment-upload integration such as bbPress with forumAttachments is active, and exploitation requires no special configuration because the %created_timestamp% placeholder is included in the caption template by default. Exploitation by attackers with subscriber-level access and above requires that bbPress and gd-bbpress-attachments (forumAttachments) are installed and configured so that Subscribers/Participants can post attachments through a frontend forum form. On a default installation, where that is not configured, the vulnerability requires attackers with author-level access and above. |
| CVE-2026-120736 | High | 2026-11-21 | Not applicable | No public exploit | The AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'your-message (any CF7 form field used in a form_field: tag)' parameter in all versions up to, and including, 6.0.9 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. This requires an administrator to have configured a public 'Guest submits a form' automation whose Send-an-email action embeds a form_field tag, after which the payload fires the next time any user opens the affected automation's email log entry. |
| CVE-2026-120679 | Medium | 2026-11-21 | Not applicable | No public exploit | The Redux Framework plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '<opt_name>[<color-field-id>]' parameter in all versions up to, and including, 4.5.17 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The wp_kses_post() sanitization applied via Redux_Helpers::sanitize_array() is bypassed — not broken — because an <a class="thickbox" title="&lt;img onerror=...&gt;"> payload uses only kses-allowed tags and attributes, with the entity-encoded onerror handler surviving storage as inert text that the browser decodes when WordPress core's thickbox.js reads the title attribute and writes it into the modal as HTML. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. |
| CVE-2026-120676 | High | 2026-11-21 | Not applicable | No public exploit | The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'upload-1 (the File Upload field's element_id)' parameter in all versions up to, and including, 1.58.4 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. This vulnerability is an incomplete fix for CVE-2024-1794; exploitation requires that the Forminator form's File Upload field is left at plugin defaults (no 'custom-files' restriction configured) and that the server maps no Content-Type to the .rtx extension — the default behavior of the Debian/Ubuntu Apache package used by the official WordPress Docker image and many shared hosts. |