| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| The Toocheke Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'meta[<meta_id>][value]' parameter in all versions up to, and including, 2.39 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 is possible because omitting the comic_blog_post_editor field from the POST request bypasses the plugin's sanitization callback entirely, causing WordPress core to store the raw payload byte-for-byte via update_post_meta(). |
| The Recipe Card Blocks Lite plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.0.2 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 overwrite the post_content of arbitrary posts on the site, including Administrator-owned published posts, bypassing the edit_others_posts and edit_published_posts capability checks. This vulnerability is only exploitable when the wpzoom_rcb_settings_synchronize_recipe_post setting is enabled, and requires the target post to contain at least one Recipe Card block whose twin can be matched to the attacker's draft recipe post. |
| The Nelio Content – Editorial Calendar & Social Media Auto-Posting plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.0.1. 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 view the titles, publication dates, author display names, and author email addresses (including those of administrators) of private, draft, and pending posts they cannot access, and to write arbitrary _nc_url metadata onto posts they cannot edit. |
| The Nelio Content – Editorial Calendar & Social Media Auto-Posting plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'values' parameter in versions up to, and including, 5.0.1. This is due to the /nelio-content/v1/post/(?P<id>[\d]+)/items REST route registering the 'values' argument with no sanitize_callback, storing values['efiUrl'] raw to the _nelioefi_url post-meta via update_post_meta(), and then interpolating that stored value into a style attribute via generate_style_tag() with no esc_attr/esc_url before splicing it into the img tag emitted by the_post_thumbnail(). 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 Toocheke Companion plugin for WordPress is vulnerable to Missing Authorization leading to arbitrary post and attachment deletion in versions up to, and including, 2.38. This is due to a missing object-level capability check in the toocheke_tapas_ajax_cleanup_start() and toocheke_tapas_ajax_cleanup_step() AJAX handlers; the toocheke_tapas_cleanup_ajax_guard() method only verifies the primitive delete_posts capability (held by every Contributor) and never calls current_user_can('delete_post', $post_id) or delete_others_posts before passing the attacker-supplied series_post_id to wp_delete_post() and wp_delete_attachment() with force-delete enabled. The required nonce is emitted on the Import: Tapas admin page, which is gated only by edit_posts, so a Contributor can read it. This makes it possible for authenticated attackers, with Contributor-level access and above, to permanently delete any importer-created series post, every child 'comic' post attached to it, and every Media Library attachment belonging to those posts — regardless of which user originally created them. |
| The Charitable – Donation & Fundraising Platform (Donation Forms, Recurring Donations & Fundraising Campaigns) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'stripe_payment_method' parameter in all versions up to, and including, 1.8.15.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 nonce required to reach the nopriv AJAX endpoint is publicly obtainable from any rendered campaign donation form, making exploitation trivially accessible to unauthenticated visitors on sites with Stripe configured as a payment gateway. |
| The WPZOOM Forms – Drag & Drop Contact Form Builder for WordPress plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.0.12 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 view the Name, Email address, and message excerpt stored in the _wpzf_fields meta of every form submission site-wide, regardless of submission ownership. Because public form submissions are stored with post_author=0, WordPress's built-in author-scoping guard in WP_Posts_List_Table is bypassed for Contributors who own zero submissions, causing the list query to return all submissions site-wide rather than only the authenticated user's own records. |
| The PDF Poster – Let visitors read PDF’s without leaving the page plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.6.5 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 retrieve the titles and identifiers of other users' private, draft, pending, and scheduled pdfposter posts, and retrieve the title of any arbitrary post by ID across the entire site. |
| The Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title' parameter in all versions up to, and including, 7.1.0.51 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 at save time does not strip angle-bracket-free double-quote breakout payloads in shortcode attribute values, leaving injected event handlers intact in stored post content. |
| The Kognetiks Chatbot plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 2.5.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 TeX payload survives WordPress core comment kses intact because it contains no HTML tags, and MathJax is active on fresh installs by default due to the 'chatbot_chatgpt_enable_mathjax' option defaulting to 'Yes' with no page or shortcode presence guard on enqueue. |
| The PayPlus Payment Gateway plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 8.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 subscriber-level access and above, to generate PayPlus payment page links for arbitrary WooCommerce orders belonging to any customer, overwrite those orders' payment method and PayPlus-related order meta, and trigger PayPlus API calls using the store's credentials — including, when a POS EMV device is configured, initiating a charge request to the store's physical POS terminal. The exploit requires no nonce and no special capability beyond being logged in, as the authorization block is unreachable on the AJAX path due to the inverted isset() predicate. |
| Allocation of Resources Without Limits or Throttling vulnerability in benoitc hackney allows Flooding.
The URL parser in src/hackney_url.erl converts every unrecognized URL scheme to a permanent BEAM atom via binary_to_atom/2. BEAM atoms are never garbage-collected and the atom table defaults to a hard limit of 1,048,576 entries. An attacker who can supply URLs with attacker-chosen scheme prefixes — directly as request targets, as configured webhook URLs, or via Location headers followed during redirects — can exhaust the atom table and crash the entire BEAM VM with system_limit.
This issue affects hackney: from 2.0.0 before 4.0.1. |
| Missing Authorization vulnerability in NSquared Simply Schedule Appointments simply-schedule-appointments allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Simply Schedule Appointments: from n/a through 1.6.13.6. |
| Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Winwar Medi WP Flipclock wp-flipclock allows Stored XSS.This issue affects WP Flipclock: from n/a through 1.10.1. |
| A flaw has been found in mozilla-ai llamafile up to .0.10.5. This issue affects the function llamafile_open_zip of the file llamafile/llamafile.c of the component Container Parser. This manipulation of the argument size causes out-of-bounds read. The attack is possible to be carried out remotely. Upgrading to version 0.10.6 is capable of addressing this issue. Patch name: 5ac1c4dbb76737fee71a54922df95342c667ba6f. It is advisable to upgrade the affected component. |
| Mattermost versions 11.2.x <= 11.2.4 fail to validate that the redirect target on the web app landing page that prompts users to open links in the desktop app stays on the Mattermost origin which allows an unauthenticated attacker to redirect a user to an arbitrary external site via a crafted link. Mattermost Advisory ID: MMSA-2026-00893 |
| Flowintel's community data launcher script passes the admin API key as a command-line argument to a child Python helper process. On Unix-like systems, process arguments are readable by all local users via standard tools such as ps or by reading /proc/<pid>/cmdline, allowing any local user to observe the key while the helper process is running.
An attacker with local access to the host can capture the admin API key during the brief window in which the helper process is active. Possession of the key grants full administrative access to the Flowintel REST API, enabling unauthorized creation, modification, or deletion of threat intelligence data, users, roles, and organisations.
Preconditions:
- The victim must invoke the community data import or deletion command (launch.sh -tdc or -dtdc) with the API key supplied as a positional argument.
- The attacker must have a local user account on the same host and be able to observe process listings during the helper execution window.
Impact:
- Disclosure of the Flowintel admin API key to any local user.
- Subsequent full administrative control over the Flowintel instance via its REST API.
Affected: <4.1.0 |
| Improper Validation of Unsafe Equivalence in Input vulnerability in Liquid Web / StellarWP GiveWP give allows Authentication Bypass.This issue affects GiveWP: from n/a through 4.16.9. |
| When validating JSON data into a model allowing extra data, the keys of extra data aren't validated against the key type annotated on __pydantic_extra__, resulting in extra data not matching the declared type. This is the case if you define __pydantic_extra__ as e.g. dict[Annotated[str, Field(pattern=r'^x_')], int].
The validate_json_by_iteration() method (in pydantic-core/src/validators/model_fields.rs), used to validate JSON data into models, only validates the values of extra data, and stores the keys as is.
The issue was fixed in commit 4c65dbda9970a488e2ff21c8693fc6f6d70a3358.
Impact: validation bypass, as extra data returned by validation doesn't match the declared type. Affected are applications validating untrusted JSON data into models allowing extra data (with extra='allow'), with a key type annotated on __pydantic_extra__ (e.g. dict[Annotated[str, Field(pattern=...)], int]), using Pydantic from 2.13.0 up to (but excluding) 2.14.2.
Python mode validation isn't affected. |
| A vulnerability was detected in itsourcecode Banking Management System 1.0. This vulnerability affects unknown code of the file navbar.php. The manipulation of the argument page results in cross site scripting. The attack can be executed remotely. The exploit is now public and may be used. |