Path traversal in the argocd-mcp (Argo CD MCP Server) delete_application tool through 0.9.0 allows authenticated MCP clients to smuggle single DELETE requests onto unintended Argo CD API routes, so an applicationName value such as '../repositories/' can cause deletion of repositories, clusters, or projects instead of an application. The attacker must be a valid MCP client - or an LLM manipulated by prompt injection - operating with a token that already carries the corresponding RBAC permissions, so it is authenticated (PR:L) and impact is bounded to destructive writes (I:L/A:L) with no confidentiality exposure. No CISA KEV listing or public exploit code has been flagged in the available intelligence, though a public technical writeup and the implicated source lines are referenced; CVSS 4.0 rates this 5.3 (Medium) and the independent 3.1 assessment is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L.
Unauthenticated attackers who already know a registered customer's primary phone number or email can read that customer's stored name, email, phone and internal notes from WordPress sites running the Bookly - Online Scheduling and Appointment Booking System plugin in versions up to and including 28.4. The classic booking form's Details step endpoint bookly_render_details is registered for wp_ajax_nopriv, its csrfTokenValid() check is overridden to always return true, and InfoText::getCodes() loads a persisted Customer entity keyed solely by the attacker-supplied phone or email without ever calling the plugin's customerIdentityConfirmed() predicate, so {client_name}, {client_email}, {client_phone} and {client_note} placeholders are substituted into the returned HTML. Exploitation requires a non-default site configuration (the administrator must have inserted at least one of those placeholders into the Details step's Appearance information text) and a valid victim identifier, which limits this to targeted per-victim disclosure rather than bulk enumeration; no public exploit was identified at time of analysis. The flaw is fixed in Bookly 28.5.
Authenticated SQL injection in the FireBox - WooCommerce Popup Builder, Exit Intent Popup, Email Optin & Cart Abandonment plugin for WordPress (all versions up to and including 3.1.13) lets a user holding the edit_fireboxes capability append arbitrary SQL to the plugin's Form Display Condition query and read sensitive data from the site database. Because the preserveCampaignRoleAccess() migration on sites upgraded from before 3.1.10 grants edit_fireboxes to any role that previously held edit_posts, exploitation is possible at Author level on upgraded installations, while fresh installs from 3.1.10 onward require administrator access. The issue is rated CVSS 5.3 (AC:H, PR:L, confidentiality-only) and no public exploit identified at time of analysis.
Sensitive customer records - booking names, email addresses, and phone numbers - can be pulled without authentication from any WordPress site running the Booking Calendar plugin through version 11.4.3, because the wpbc_is_show_popover_in_flex_timeline() function returns booking data without an authorization check. The flaw is reachable against default installations over the network with no privileges or user interaction (CVSS 3.1: AV:N/AC:L/PR:N/UI:N, 5.3 Medium), and its only prerequisite is that the site already holds bookings containing PII; sites with no bookings leak nothing. Impact is confined to confidentiality (C:L) with no write, code-execution, or availability effect, no public exploit code and no confirmed active exploitation were identified at time of analysis, and upgrading beyond 11.4.3 removes the exposure.
Server-side request forgery in the Jawn webhook sender of Helicone (affected through v2025.08.21-1) allows authenticated organization users to create webhooks whose public hostnames resolve - or are DNS-rebound - to loopback or internal addresses, causing the Jawn backend to issue blind POST requests to internal HTTPS services. Rated 5.3 (CVSS 4.0 AV:N/AC:L/AT:N/PR:L/UI:N with only VI:L and no confidentiality, availability, or subsequent-system impact), the vulnerability yields integrity-side effects on reachable internal endpoints rather than data readback. Exploitation requires a valid account within a Helicone organization (PR:L) plus control of a hostname that can resolve or rebind to private space; there is no public exploit identified at time of analysis and CISA KEV does not list this CVE.
Heap memory corruption in Apache DataSketches C++ (datasketches-cpp) versions 4.1.0 through 5.2.0 allows remote attackers to trigger out-of-bounds reads and writes via a crafted Count-Min sketch submitted to the deserialize() function. The flaw combines a missing preamble size check that permits up to 16 bytes over-read on truncated input, and a 32-bit integer overflow in the serialized bucket count that can wrap to zero, resulting in an empty table and subsequent heap memory corruption during updates or estimate queries. Exploitation requires an application to deserialize Count-Min sketches from untrusted sources; no public exploit code or active exploitation has been identified at time of analysis, and the vendor rates the severity as moderate.
Unauthenticated remote attackers can retrieve embedded sensitive system information from WordPress/WooCommerce sites running the YITH WooCommerce Product Add-Ons plugin through version 4.34.0. The flaw (CWE-497) is network-reachable with no privileges or user interaction required per the CVSS vector AV:N/AC:L/PR:N/UI:N, but the confidentiality impact is bounded (C:L), so exposure is limited to a specific set of sensitive data rather than a full site or database compromise, yielding a moderate CVSS 3.1 score of 5.3. No public exploit code or confirmed active exploitation was identified at time of analysis, and EPSS/KEV signals were not provided in the source data; risk is concentrated among unpatched sites with this plugin installed and active.
OAuth tag-scope enforcement bypass in 1MCP Agent 0.20.0 through 0.39.0 lets an authenticated client holding a valid single-tag OAuth token list and invoke tools on backend MCP servers outside its granted scopes by supplying a negated advanced tag-filter expression such as 'not <granted-tag>'. The flaw is rated medium severity (vendor CVSS 4.0 base 5.3, assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) and requires both a valid token (PR:L) and a multi-scope or multi-tenant gateway configuration using OAuth tag-scope enforcement with negation-capable filters, limiting overall impact to low confidentiality and integrity effects. There is no public exploit identified at time of analysis and no CISA KEV confirmation; exploitation depends on the attacker already holding a scoped OAuth token.
Unauthenticated arbitrary file upload in WP CV Builder plugin versions up to and including 1.3.1 allows remote attackers to write arbitrary content as .png files to the WordPress uploads directory via the 'wp_save_signature_image' function, which lacks a capability check. This integrity-only primitive requires no authentication and affects default installations, but does not directly enable code execution. No public exploit identified at time of analysis.
Incorrect authorization in the Simply Schedule Appointments WordPress plugin (all versions up to and including 1.6.11.11) allows unauthenticated attackers who possess a valid per-appointment booking token to modify admin-controlled fields on that appointment, including faking payment confirmation, reassigning the appointment to another user, and changing the service type. The weakness is a business-logic authorization flaw (CWE-863) confined to appointment records: it grants no server access, no data disclosure, and no code execution, which is why it carries a moderate CVSS score of 5.3 (integrity-only, low impact). No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, though sites that rely on the plugin's payment-confirmation or service-assignment fields (for example, paid bookings) face the greatest practical exposure.
Unauthenticated information disclosure in the Booking Package WordPress plugin before 1.7.30 lets remote attackers retrieve other customers' stored reservation details and booking cancellation tokens because the data-returning endpoint omits authorization checks. Any WordPress site running the affected plugin with stored reservations is exposed over the network without credentials, though impact is confined to confidentiality and availability/integrity are unaffected (CVSS 5.3, CWE-200). No public exploit code or confirmed active exploitation was identified in the available intelligence.
Unauthenticated information disclosure in the WordPress plugin 'Accept PayPal Payments using Contact Form 7' (all versions before 4.0.7) allows any remote visitor to download the stored form submissions - name, email, telephone, postal address, message and associated payment metadata - of every person who submitted a payment form. The plugin's export routine performs no authorization check whatsoever, so exploitation requires no account, no user interaction and no non-default configuration; the only practical preconditions are that the plugin is installed and that at least one submission has been stored. Our independent assessment rates confidentiality impact as High (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) rather than the feed-supplied C:L, and no public exploit code or confirmed active exploitation has been identified at time of analysis; a vendor fix is available in version 4.0.7.
Unrestricted brute-forcing of the email-verification PIN in the Contest Gallery WordPress plugin (all versions before 33.0.1) lets unauthenticated attackers guess a short numeric code and complete front-end registration for an email address they do not own, resulting in an authenticated WordPress session that the plugin treats as verified. Exploitation requires that the plugin's public front-end registration with email verification be enabled, and the practical ceiling is the privilege level the plugin assigns to self-registered accounts - typically low-privilege - rather than administrative access, which keeps this a genuine but moderate-severity authentication weakness rather than a critical one. No public exploit code was identified at time of analysis and the flaw is not confirmed actively exploited (no CISA KEV listing); the vendor has released a fix in version 33.0.1.
Unauthenticated attackers can forge stored transaction statuses and inject the Accept PayPal Payments using Contact Form 7 plugin's status metadata onto arbitrary WordPress posts, affecting all versions of the plugin prior to 4.0.7. The flaw (CVE-2026-105989, CVSS 5.3, CWE-862 Missing Authorization) stems from an AJAX action that ships without any authorization or nonce/request-validation check, so it is reachable by remote unauthenticated requests against default installations with the plugin active; the CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no authentication or user interaction is required. Impact is confined to integrity (C:N/I:L/A:N), and no public exploit code or confirmed active exploitation has been identified at time of analysis.
An unauthenticated bypass in the 'Pay With MetaMask For WooCommerce - Cryptocurrency Payment Gateway' WordPress plugin (all versions up to and including 1.7.2) lets remote attackers circumvent the plugin's authenticity/verification checks, altering limited aspects of application state without logging in, per CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N. Because the vector carries PR:N and UI:N, unauthenticated remote attackers can trigger the flaw on any site where the plugin is active, but the impact is confined to integrity only (I:L) with no confidentiality or availability effect, keeping this a moderate-severity issue rather than a critical one. No CISA KEV listing and no public exploit code were identified at time of analysis, and no EPSS signal was supplied; the affected population is limited to WordPress/WooCommerce sites running this niche cryptocurrency payment gateway.
Authenticated directory traversal in the Post Export Import with Media plugin for WordPress through 1.17.1 allows administrator-level users to read arbitrary files from the server by importing a crafted ZIP whose media_metadata.json file_path field contains traversal sequences while the destination filename uses an allowed extension. Although rated CVSS 4.9, real-world priority is materially reduced because the vector requires PR:H, meaning the attacker already holds WordPress administrator credentials; impact is read-only confidentiality disclosure with no integrity or availability effect. No public exploit code or CISA KEV confirmation was identified at time of analysis.
Arbitrary file deletion in the WordPress plugin Listdom: AI-powered Business Directory with Classifieds Ads Listings (all versions up to and including 6.1.2) lets an authenticated administrator delete files anywhere on the server by supplying a traversal path to the plugin's CSV import routine (LSD_Menus_IX_CSV::import). The practical impact is high for integrity and availability - deleting a sensitive file such as wp-config.php can drop the site into a re-installation state and enable full takeover/RCE - but the requirement for administrator-level access (CVSS PR:H) makes this a high-barrier, medium-severity issue rather than a widespread emergency. No public exploit code and no confirmed active exploitation were identified at time of analysis.
SQL injection in the 'sidx' parameter of the Smart Popup by Supsystic WordPress plugin (all versions up to and including 1.13.2) lets authenticated attackers with administrator-level privileges append arbitrary SQL statements to existing queries and extract sensitive data from the site's database. The CVSS vector confirms high privileges are required (PR:H) and impact is limited to confidentiality (C:H/I:N/A:N), and no public exploit or CISA KEV entry has been recorded - no public exploit identified at time of analysis - so despite a CVSS base score of 4.9 this is a low real-world-priority issue because an attacker must already hold the broad database and site access that administrators legitimately possess. Affected deployments are those running 1.13.2 or earlier; the vendor released 1.13.3 to remediate it.
Path traversal in slide-maker through 5.8.0 lets an attacker who can influence the deck source material cause the image-generation script generate_images_openai.py to write generated image files outside the intended output directory, creating directories and overwriting existing files at arbitrary filesystem paths. The attack is local: a victim must actually run the image-generation step on the tainted deck (UI:P / UI:R), and impact is limited to integrity of files writable by that user, with no confidentiality or availability effect, so purely trusted, self-authored decks are not at risk. No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis.
Reflected cross-site scripting in WPForms Lite through 2.0.2.1 allows an unauthenticated attacker to execute arbitrary script in a victim's browser if the site administrator previously saved a form whose description embeds a {query_var} Smart Tag inside an iframe srcdoc attribute and enabled Show Description on a public-facing page. The attacker must trick a victim into clicking a crafted link containing a malicious value for the referenced query parameter, and the flaw is rated CVSS 4.7 with high attack complexity and required user interaction. No public exploit code was identified at time of analysis and CISA KEV does not list this CVE.
Reflected cross-site scripting in the Fluent Forms WordPress plugin (all versions up to and including 6.2.14) allows unauthenticated attackers to inject arbitrary script into pages via a crafted query parameter that is substituted into a {get.NAME} SmartCode. Exploitation is not possible on a default install: a site administrator must first have placed a {get.*} SmartCode inside a URL-accepting attribute (such as an iframe src or anchor href) within a Custom HTML field on a published form, and a victim with a session on the site must then be tricked into clicking an attacker-supplied link. No public exploit identified at time of analysis, and the issue is a genuine-but-moderate-priority problem rather than a drop-everything emergency given the non-default configuration prerequisite and the AC:H/UI:R scoring.
Reflected DOM-based cross-site scripting in the JetFormBuilder WordPress plugin (Dynamic Blocks Form Builder) affects all versions up to and including 3.6.6, allowing unauthenticated attackers to inject arbitrary web scripts via an attacker-chosen query variable whose name matches a form preset's query_var setting. Exploitation is heavily constrained: it requires a page that embeds a form containing a text field configured with a query_var Dynamic Preset together with a data-jfb-macro or JFB_FIELD:: macro reference to that field, and it also requires the victim to click an attacker-supplied link (UI:R), which is why the assessed CVSS is 4.7 with high attack complexity despite the network vector and no authentication requirement. There is no CISA KEV listing and no public exploit identified at time of analysis; the changeset in the plugin's Trac points to an upstream fix in trunk, but a patched tagged plugin release has not been independently confirmed.
Authenticated attackers with Contributor-level access can exploit missing authorization checks in the Portfolio Filter Gallery WordPress plugin (versions before 2.2.1) to read, modify, and delete other users' galleries and site-wide gallery filters. This is a moderate-severity issue (CVSS 4.7) requiring a valid low-privileged account; no public exploit identified at time of analysis. A vendor patch is available in version 2.2.1.
Stored cross-site scripting in the Responsive Lightbox & Gallery WordPress plugin (all versions through 2.7.9) lets authenticated attackers with editor-level privileges or higher inject arbitrary web scripts through the 'comment' parameter, which then execute when a site visitor opens the lightbox on an affected image. Realistic exploitation is heavily constrained by stacked prerequisites: the plugin's 'Comments' lightbox setting must be explicitly enabled (it is off by default), a moderator must approve the injected comment, the attacker must already hold a high-privilege account, and a visitor must click the affected image - which is why this is assessed as a low-priority issue despite the network attack vector. No public exploit code has been identified at the time of analysis and the flaw is not listed in CISA KEV; the CVSS 3.1 base score is 4.4 (assessed vector AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N).
Authenticated subscribers (or any logged-in user) on WordPress sites running the AutomatorWP plugin up to and including 5.8.4 can enumerate Fluent Forms records - specifically form IDs and titles from the fluentform_forms database table - because a plugin AJAX handler performs no authorization check. The flaw is network-reachable but requires a valid low-privilege account plus the Fluent Forms plugin and AutomatorWP's Fluent Forms integration to be active, and exposure is limited to form identifiers and titles rather than submissions or configuration data (CVSS 4.3, CWE-862). There is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); overall this is a genuinely low-priority information-disclosure defect.
Sensitive information exposure in the WordPress Download Manager plugin (codename065) through version 3.3.71 lets an authenticated subscriber-level user harvest the administrator's full Cookie header - including wordpress_logged_in_* session cookies - by abusing the 'first_name' parameter when the administrator triggers the plugin's 'Suspend' action against the attacker's account. Because the suspension email is compiled and sent synchronously inside the administrator's own authenticated HTTP request, the site's email template engine can resolve the admin's request context (Cookie header) at send time and inject it into the outgoing message, enabling session hijack and full account takeover once the attacker reads that email. Exploitation is not fully attacker-controlled: it depends on an administrator performing the Suspend action while authenticated, so the plugin carries a CVSS 3.1 base of 4.3 (independent assessment: AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N), and no public exploit code or confirmed active exploitation was identified at time of analysis.
Missing authorization in the LatePoint Appointment Booking plugin for WordPress (versions up to and including 5.7.2) allows unauthenticated attackers to create approved appointments against other customers' order items by sending a non-empty params[presets][order_item_id] to the publicly reachable steps__start and steps__load_step routes. The plugin's is_bundle_scheduling() discriminator is only an !empty(order_item_id) truthiness check, so supplying any value causes the booking flow to strip out the customer and payment steps and to skip ownership, bundle-membership, paid-status, and remaining-capacity validation. Successful requests leak the targeted customer's name, email address, and order code in the booking confirmation; exploitation is limited in practice by the need to know or guess a valid order item ID of a victim. No public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated low-privilege users on WordPress/WooCommerce sites running the ALD - Dropshipping and Fulfillment for AliExpress and WooCommerce plugin (woo-alidropship) through version 2.2.4 can reach plugin functionality they are not authorized to use, because affected endpoints omit authorization/capability checks (CWE-862). Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, base 4.3), the practical impact is limited to low-integrity modification - no confidentiality or availability loss - and exploitation requires the attacker to already hold a valid low-privilege account on the target site, so sites that do not allow untrusted user registration have sharply reduced exposure. No public exploit code or confirmed active exploitation was identified at time of analysis, and this remains a low-to-moderate priority issue rather than an emergency patch item.
SQL injection in Rank Math SEO before 1.0.280 allows an authenticated high-privilege user, such as an administrator, to inject arbitrary SQL through an unsanitized parameter, potentially reading limited data from the WordPress database. The requirement for administrator-level access (CVSS PR:H) sharply limits realistic risk; no public exploit was identified at time of analysis, and the issue is assessed as low priority despite network exploitability. A vendor patch is available in version 1.0.280.