Stored cross-site scripting in the CSS & JavaScript Toolbox plugin for WordPress (all versions through 12.0.6) enables authenticated attackers with contributor-level permissions to inject malicious scripts into pages via the cjtoolbox shortcode attributes. The injected code executes when any user, including administrators, views the compromised page, potentially leading to session theft or unauthorized actions. No public exploit has been identified, and the requirement for a valid contributor account limits exposure to sites that grant such access to untrusted users; this is a moderate-priority issue rather than a critical emergency.
Stored cross-site scripting in the WordPress plugin WP Maps - Google Maps, OpenStreetMap, Mapbox, Store Locator with Search, Filters & Listings (wp-google-map-plugin) in all versions up to and including 4.9.8 allows authenticated attackers holding only subscriber-level access to inject arbitrary JavaScript through the shapes_values parameter, which is insufficiently sanitized on input and unescaped on output. The nominal fc-call-nonce protection is ineffective because that nonce is exposed to every frontend visitor via window.wpgmp_local.nonce on map pages, and the drawing handler's secondary _wpnonce check can be bypassed simply by omitting the _wpnonce parameter from the request. Execution is deferred: the injected script fires when a victim (for example an administrator or any site visitor) later views the page containing the stored shape, and no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Stored cross-site scripting in the WordPress plugin User Profile Builder (Profile Builder by Cozmoslabs) through version 4.0.2 lets any authenticated user with Subscriber-level access plant script content in their avatar value and have it execute in a higher-privileged user's browser. The distinguishing enabler is a nonce-free GET request to /wp-admin/profile.php that writes a malicious attachment URL as the avatar without any profile-form submission or valid nonce, so a Subscriber only needs to reach that endpoint to seed the payload. The script then fires when an administrator opens that user's Edit User screen - a victim action that limits automatic exploitation - and the CVSS 3.1 base score is 6.4 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N per our assessment), with no public exploit code identified at time of analysis.
Stored cross-site scripting (XSS) in the wpForo Forum plugin for WordPress, affecting versions up to and including 3.1.6, allows authenticated attackers with subscriber-level access to inject arbitrary JavaScript through the 'telegram' profile field, which executes when any user views the injected profile page. This is a moderate-severity issue (CVSS 6.4) that requires an account on the target site, a condition trivially met if open registration is enabled; no public exploit identified at time of analysis. The flaw stems from insufficient input sanitization and output escaping in the profile update and render logic.
Stored DOM-based cross-site scripting in the Better Messages WordPress plugin (all versions up to and including 3.0.4) lets any authenticated subscriber-level user persist arbitrary script through their WordPress display name, which then executes in the browser of anyone who views a page that renders that name. Because the value is only run through sanitize_text_field() and the plugin subsequently decodes it server-side before rendering, a low-privilege account bypasses the normal unfiltered_html capability gate, and no victim interaction beyond page view is required. Rated CVSS 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), this is a mid-severity, authentication-gated issue with a realistic but bounded threat profile, most dangerous on sites that permit open or self-service registration; no public exploit identified at time of analysis.
Stored cross-site scripting in the Gutenverse - WordPress Blocks, Page Builder & Site Editor plugin (all versions up to and including 4.0.8) lets an authenticated attacker holding contributor-level access or above inject arbitrary JavaScript through the Post Comment Block's 'suffixMain' attribute, which is written into a Gutenberg block-delimiter comment and only converted into live HTML when the block is rendered server-side in PHP. The stored script then executes in the browser of any user who views the affected page, scoring CVSS 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) because exploitation crosses the block-content trust boundary even though the injected account is only a low-privileged author. Exposure is gated on the site actually granting contributor-level publishing rights and on a victim later visiting the poisoned page; no public exploit code was identified at time of analysis and the flaw is not confirmed as actively exploited (not listed in CISA KEV), which positions this as a genuine but moderate-priority issue rather than a critical one.
Stored cross-site scripting in the GeoDirectory WordPress business directory plugin (all versions up to and including 2.8.183) lets any authenticated subscriber-level user who owns a listing inject arbitrary JavaScript through the 'business_hours' parameter, which is then executed in the browser of any user who views the affected listing page. The AJAX save handler enforces only post authorship plus a nonce and performs no capability check or output escaping, so practical exploitability depends on whether the site allows low-privileged users to register and own listings, a common but not universal GeoDirectory configuration. Authentication is mandatory and impact is confined to browser-context script execution (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), making this a genuine but moderate-severity issue rather than a top-priority emergency; no public exploit code has been identified at time of analysis.
Stored cross-site scripting in the GeoDirectory WordPress business-directory and classified-listings plugin (all versions up to and including 2.8.181) lets an attacker with only a subscriber-level account plant arbitrary JavaScript that runs in the browser of any user who later views the injected listing. The payload is submitted through the AJAX geodir_save_post endpoint into a text-type custom field such as 'phone', using entity-encoded angle brackets to defeat the plugin's strpos()-gated tag-stripping check, and the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C, 6.4) reflects a scope change with limited confidentiality and integrity impact and no availability impact. There is no confirmed active exploitation (the issue is not in CISA KEV) and no public exploit code identified at time of analysis; practical risk rises sharply on sites that permit open user or lister self-registration, because obtaining the required subscriber account then becomes trivial, and impact is deferred until a victim renders the poisoned page.
Unbounded pre-authentication state accumulation in RabbitMQ's Web STOMP WebSocket handler lets an unauthenticated remote client hold connections open with a slow trickle of small frames, causing memory and resource exhaustion on the broker. Only deployments that enable the non-default rabbitmq_web_stomp plugin and expose its WebSocket listener are affected; a single request is not enough, since the attacker must open and sustain many slow connections over time (reflected as AT:P in the assessed vector). RabbitMQ 3.13.0 through 3.13.14, 4.0.x before 4.0.20, 4.1.x before 4.1.11, and 4.2.x before 4.2.6 are vulnerable, and no public exploit code has been identified at time of analysis.
Expired OAuth2 JWT access tokens are accepted indefinitely by RabbitMQ 4.2.0 through 4.2.8 and 4.3.0 through 4.3.2 when the rabbitmq_auth_backend_oauth2 backend is enabled and the identity provider emits the JWT 'exp' claim as a fractional (float) JSON number rather than an integer. Because the Erlang code guards expiry parsing with is_integer(Exp), both the login-time expiry check and the mid-connection disconnect timer silently fall through for float exp values, so an attacker holding a previously issued, correctly signed token can authenticate with it long after it has expired and keep connections open without being disconnected. The CVSS 4.0 base score is 6.3, but exploitability is sharply conditional - a non-default IdP behavior plus possession of a valid signed token - and no public exploit code has been identified at time of analysis; the issue is fixed in RabbitMQ 4.2.9 and 4.3.3.
LDAP distinguished-name injection in the RabbitMQ rabbitmq_auth_backend_ldap plugin allows a remote, unauthenticated caller to manipulate the DN used for an LDAP bind by supplying a crafted username, because the ${username} placeholder is substituted into user_dn_pattern without RFC 4514 escaping. Impact is limited to integrity (CVSS:4.0 6.3 / CVSS:3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) and exploitation is narrowly conditioned: the plugin must be enabled, user_dn_pattern must actually contain ${username}, the injected suffix must resolve to a useful directory entry, and the attacker must hold a password valid for that resulting DN. No public exploit code and no confirmed active exploitation were identified at time of analysis; upstream fix commits and patched releases exist, though the advisory's first-fixed version metadata is internally inconsistent for several maintenance lines.
A remote, unauthenticated denial-of-service condition exists in the RabbitMQ stream protocol when the stream plugin is enabled, allowing a client that completes the Tune handshake to declare a frame larger than the negotiated FrameMax and drive excessive memory consumption. Affected deployments are RabbitMQ 3.13.0 through 3.13.14, 4.0.x before 4.0.20, 4.1.x before 4.1.11, and 4.2.x before 4.2.6; the issue is availability-only with no confidentiality or integrity impact, and exploitation requires the non-default stream plugin (and its listener) to be exposed to the attacker. No public exploit code has been identified at time of analysis, and there is no confirmed active exploitation (CISA KEV) associated with this CVE. Independent assessment rates this as a genuine but low-to-moderate-severity DoS issue rather than a high-impact priority.
RabbitMQ 4.0.0 through 4.0.22, 4.1.x before 4.1.14, 4.2.x before 4.2.9, and 4.3.x before 4.3.3 exposes the complete binding topology of a virtual host to any authenticated AMQP 1.0 user, because the HTTP-over-AMQP management handler for GET /bindings (rabbit_amqp_management) returns the binding list without performing the resource-level read/write permission checks that every sibling operation in the same module performs. A low-privileged account with no management, monitoring, policymaker, or administrator tag - and no read/write permission on the relevant exchanges or queues - can enumerate source exchanges, destination queues and exchanges, routing keys, and binding arguments for any vhost it can connect to; only routing metadata is disclosed, not message payloads, and the classic HTTP management API GET /api/bindings is not affected because it validates permissions. Exploitation requires valid broker credentials (unauthenticated remote access is not sufficient), and no public exploit code or confirmed active exploitation was identified at time of analysis; the CVSS 4.0 base score of 6.3 primarily reflects the low-privilege network-reachable precondition with a high subsequent-system confidentiality contribution in the assessing vector, while an independent CVSS 3.1 assessment scores the flaw 6.1-class impact as limited to confidentiality only.
Stored cross-site scripting in Zammad's Knowledge Base video widget lets an authenticated user who holds Knowledge Base editing rights for a category publish an answer whose crafted video 'id' value breaks out of the generated <iframe> attribute context and injects arbitrary HTML; when a second, more privileged user who can switch between user sessions opens that published answer, the injected markup silently fires a request to Zammad's session-switching endpoint and forces the victim's session onto an account chosen by the attacker. Exploitation requires two distinct privileges (a Knowledge Base editor on the attacker side and session-switch/impersonation permission on the victim side) plus the victim simply viewing the published answer, and no public exploit code has been identified at time of analysis. The flaw is tracked as CWE-79 and is fixed in Zammad 7.1.2; the circumstances make this a genuine but conditionally gated stored XSS that chains into a forced session-switch account takeover rather than a raw remote flaw.
Stored cross-site scripting (XSS) in the AIL Framework crawler splash domain page allows an authenticated user-role API client to inject JavaScript payloads via crafted crawler captures. The payloads are stored in the application's data layer and execute in the browser of any user who views the affected domain page, potentially enabling session hijacking, data exfiltration, or unauthorized actions. The vulnerability requires a valid API user-role credential (PR:L) and victim interaction (UI:R); no public exploit code has been identified, and no confirmed active exploitation is reported.
Cross-tenant authorization bypass in the AIL Framework crawler task API (api_add_crawler_task) lets an authenticated user who can create one-shot or scheduled crawler tasks attach another organization's cookiejar by UUID and have the crawler reuse that organization's stored cookies and session tokens during web crawls, leaking the victim tenant's session data. Cookiejar UUIDs are random and not enumerable, so the attacker must already know or obtain a valid victim UUID, and the flaw only has security consequence in multi-organization (multi-tenant) deployments - single-organization installs have no tenant boundary to cross. Rated CVSS 6.3 by the vendor (4.0 vector with PR:L and SC:H) and assessed here as CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N - a genuine but moderate CWE-639 IDOR rather than a critical drive-by; no public exploit code was identified at time of analysis.
Command injection in MISP misp-modules' cisco_firesight_manager_ACL_rule_export can cause arbitrary shell commands to be embedded in generated .sh export scripts when an authenticated MISP user with event/attribute submission privileges supplies values containing a single quote, such as a crafted ip-dst or url; an analyst who executes the script unmodified runs those commands with their own privileges. The issue requires active user interaction, does not directly compromise the MISP server, but can expose Cisco fireSIGHT Manager credentials, alter ACL rules, or compromise the analyst workstation, with a secondary NameError denial-of-service when the request lacks a config key. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; the independent assessment views this as a genuine but conditional risk, and the upstream patch commit 625b54908efbd6acc8343aa3370d401dd370e748 adds shlex.quote and initializes config.
Memory corruption and denial-of-service in Espruino's JavaScript lexer can be triggered by crafted raw or binary string input, causing a NULL pointer dereference in jslGetRawString() (src/jslex.c) when the lexer passes a NULL iterator target to jsvLockAgain(). Only RELEASE/NO_ASSERT builds are affected-assertion-enabled debug builds abort safely-and the CVSS vector (AV:L/PR:N) indicates unauthenticated local attackers who can supply script input via REPL, serial/USB console, or script loading can terminate the interpreter. EPSS is 0.14% (3rd percentile), no public exploit code has been identified, and an upstream fix commit (0db0663) is available.
Reflected cross-site scripting in Apache Roller 6.1.5 lets unauthenticated remote attackers inject script into the HTML form rendered by the optional LdapCommentAuthenticator, which writes request parameter values into the page without escaping (CVSS 6.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N). Exploitation is tightly constrained: only sites explicitly configured to use LdapCommentAuthenticator are affected, the victim's session must already have the authenticator form loaded, and the victim must follow an attacker-crafted link. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the credentials are credited to 姬珏 (CyberLeo); the net assessment is a low-to-moderate priority issue rather than an urgent one.
Stored cross-site scripting in Apache Roller 6.1.5 lets an unauthenticated remote attacker post a comment containing a javascript: URI that survives HTML comment formatting and executes in the browser of any visitor who clicks the crafted link. Exploitation is gated by a non-default configuration - the site must enable HTML in comments (users.comments.htmlenabled=true) and use the HTMLSubset comment formatter - and by required user interaction, while comment moderation, where enabled, delays publication of the malicious comment. Apache rates the issue Moderate (CVSS 3.1: 6.1, AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) and fixed it in 6.1.6 by restricting restored links to http, https and mailto URIs; no public exploit identified at time of analysis.
Stored cross-site scripting in the pfBlockerNG package for Netgate pfSense 26.03.1-RELEASE allows an unauthenticated remote attacker to inject script into a crafted DNS hostname, which is captured by DNSBL logging and later rendered unsafely in the pfBlockerNG report UI, executing in the browser of an administrator who opens the affected page and enabling escalation to command execution through the admin's authenticated session. The published CVSS 3.1 base score of 6.1 (Medium), derived from the standard reflected/stored XSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), understates the real-world impact, which the independent assessment re-scores to integrity and availability High (C:H/I:H/A:H) because the stored script can pivot to arbitrary code execution on the firewall. This is not part of the base pfSense install: pfBlockerNG must be installed and actively logging DNS via DNSBL, and an administrator must subsequently view the affected report/log page, so exploitation is not fully automatic despite the unauthenticated delivery vector (PR:N with UI:R confirmed from the CVSS vector); no confirmed public exploit code or CISA KEV listing was identified at time of analysis.
Stored cross-site scripting in Apache Roller 6.1.5 allows an unauthenticated remote attacker to persist a crafted comment-author URL through the incoming Trackback endpoint, which the shipped Trackback verification and moderation defaults approve and render as an active link; a visitor who clicks that link executes attacker-controlled script in the weblog's origin. Per the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) the attack requires no authentication but does require user interaction, since the payload only fires on click rather than automatically on page load, so it is not a self-executing compromise. No public exploit code and no confirmed active exploitation (CISA KEV) have been identified at time of analysis, and the vendor has released Apache Roller 6.1.6, which removes incoming Trackback support and suppresses non-HTTP(S) comment-author links.
Stored cross-site scripting in Readwise Reader for Android versions 8.7.2 through 8.10.1 allows an attacker who can place a crafted document into a victim's library to execute injected script when that document synchronizes to the device and is opened in the app's WebView. The flaw is unauthenticated from the attacker's perspective (CVSS vector PR:N) but requires victim interaction (UI:R): the document must be synced and rendered before the malicious metadata is interpolated into a URL and written into the DOM via innerHTML. Impact is scoped to the WebView context (S:C with C:L/I:L/A:N), yielding a 6.1 base score; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV), with CISA SSVC rating exploitation as none, automatable as no, and technical impact as partial.
Stored cross-site scripting in Readwise Reader for Android (versions 8.7.2 through 8.10.1) lets an attacker who controls a document's metadata - notably the author meta tag - inject script that runs inside the app's WebView when the victim opens the imported document on a synced device. The root problem is a missing HTML sanitization step: attacker-controlled metadata arrives at the WebView through innerHTML without escaping. Exploitation is unauthenticated (CVSS PR:N) but requires the victim to open specifically crafted content (UI:R), and the resulting impact is partial confidentiality and integrity within the WebView context (CVSS 6.1); no public exploit identified at time of analysis, and the CISA SSVC assessment records exploitation as none with the flaw not automatable at scale, making this a low real-world priority rather than an urgent threat.
Client-side cross-site scripting in Readwise Reader for Android versions 8.7.2 up to but not including 8.10.1 lets an attacker craft a document containing malicious SVG markup whose event-handler attributes (such as 'onload' or 'onerror') survive the app's sanitize-html pass and execute inside the Reader WebView when the victim opens it. Exploitation requires user interaction - the victim must add and render the attacker-supplied document - and the impact is scoped to the WebView rather than the underlying device; the attacker needs no credentials to author the content, but delivery depends on getting it in front of the victim. There is no public exploit identified at time of analysis, CISA SSVC records exploitation as 'none' with partial technical impact, and the assessment places real-world risk at a moderate level consistent with a CVSS 3.1 score of 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).
Stored cross-site scripting in the MediaWiki Thanks extension (CWE-79) allows an authenticated user to persist a malicious script payload through a Thanks-related action or field, which then executes in the browser of any victim who later views the affected page or notification. All versions before 1.43.10, 1.45.5, and 1.46.1 are affected, and successful exploitation requires victim interaction with the rendered content; because the injected script executes in the victim's browser session, the CVSS 3.1 base score is 6.1 (Medium) with a scope change, but only low confidentiality and integrity impact and no availability impact. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment rates exploitation as none and automatable as no; vendor patches are available.
Stored cross-site scripting in Apache Roller 6.1.5 lets an unauthenticated remote attacker persist a crafted URL in the comment-author field so that script executes in the browser session of a weblog moderator or global administrator who later opens the comment moderation page. The flaw is rated CVSS 3.1 6.1 (medium) with vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, reflecting unauthenticated submission, required reviewer interaction, and impact scoped to the privileged reviewer's session with no availability loss. No public exploit code has been identified at time of analysis - no public exploit identified at time of analysis - and exploitation is not confirmed actively exploited (CISA KEV); successful abuse requires that the site allow comments on at least one weblog and that a moderator actually review the pending comment in the web UI, but the vendor states no non-default server setting is required.
Reflected cross-site scripting in Apache Roller 6.1.5 lets remote attackers inject script into the frontpage theme's directory page by supplying a crafted blog-directory parameter that is reflected without proper escaping; the script then executes in the browser of any visitor who follows the crafted link. Only weblogs using the bundled 'frontpage' theme are affected, and exploitation requires the victim to click a malicious link (UI:R) - no credentials are needed to craft or deliver it, but no public exploit code has been identified at time of analysis. The NVD CVSS 3.1 score of 6.1 (medium, AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) reflects limited confidentiality and integrity impact confined to the weblog origin, with the theme dependency and mandatory user interaction keeping real-world exploitability below what the network-reachable vector suggests.
Reflected cross-site scripting in the SSL Zen - SSL Certificate Installer & HTTPS Redirects WordPress plugin, versions up to and including 4.7.42, allows an unauthenticated remote attacker to inject arbitrary JavaScript into a victim's browser session through the base64-encoded 'uri' and 'host' request parameters. The plugin decodes these parameters after running sanitize_text_field() on them, so HTML and script markup that is hidden inside the base64 blob survives filtering and is then echoed unescaped by showMessage(), landing in the page as executable content. Exploitation requires the victim to click a crafted link (CVSS vector UI:R), making it a social-engineering-dependent attack rather than a passively triggered one; the impact is scoped to the victim's browser session with low confidentiality and integrity impact, and no public exploit code was identified at time of analysis, so it is not confirmed as actively exploited. The impact is materially elevated when the crafted link is opened by a logged-in WordPress administrator, because the injected script then runs in an authenticated administrative context.
Reflected cross-site scripting in the WPForms - AI Form Builder for WordPress plugin (versions up to and including 2.0.2) allows unauthenticated remote attackers to inject arbitrary JavaScript into a victim's browser by submitting a crafted 'page_title' POST value, which is then rendered unescaped through the {page_title} Smart Tag. Exploitation is conditional: it only works on forms where an administrator has deliberately placed the {page_title} Smart Tag inside an HTML attribute context within the form's confirmation message, so many default WPForms deployments are not exploitable. The attack requires user interaction (UI:R) - the victim must be tricked into clicking a crafted link or otherwise submitting the malicious POST value - and there is no public exploit identified at time of analysis and no CISA KEV confirmation of active exploitation; impact is limited to script execution in the victim's browser session (scope change), not server compromise.
Reflected cross-site scripting in the JetFormBuilder - Dynamic Blocks Form Builder WordPress plugin (all versions up to and including 3.6.5.3) allows unauthenticated attackers to inject arbitrary JavaScript into a page by supplying a crafted 'jfb_xss' URL query variable that is carried into a Calculated Field. Exploitation is not automatic: the targeted site must host a form that pairs a URL Query Variable preset field with a Calculated Field referencing that preset, and the victim must be induced to click an attacker-crafted link (UI:R), so the realistically exploitable population is a subset of installs rather than every default configuration. There is no CISA KEV listing and no public exploit identified at time of analysis, and the independent assessment rates this as a genuine but moderate-severity issue rather than a top-priority emergency.
Loopback source-address restriction bypass in RabbitMQ's native MQTT and MQTT-over-WebSocket listeners (all releases from 3.13.0 up to the fixed versions 3.13.18, 4.0.23, 4.1.14, 4.2.9 and 4.3.3) allows an authenticated attacker holding valid credentials for a loopback-restricted account to reach that account from a non-loopback address. The flaw only manifests when such a listener runs behind a trusted frontend that speaks PROXY Protocol: the proxy-derived client address is dropped before the MQTT authentication path evaluates the loopback_users setting, so the frontend-to-broker connection is mistakenly judged as loopback. Password authentication itself is not bypassed, CVSS 4.0 base is 6.0 with high attack complexity and a present attack requirement reflecting how deployment-specific the trigger is, no public exploit code has been identified at time of analysis, and the issue is not confirmed actively exploited (no CISA KEV listing).
Denial of service via atom exhaustion in RabbitMQ Server when the rabbitmq_auth_backend_oauth2 plugin is enabled and configured with an identity provider that allows user-influenced scope values in signed JWTs. Affected versions include 3.13.0 through 3.13.14, 4.0.x before 4.0.22, 4.1.x before 4.1.11, 4.2.x before 4.2.6, and 4.3.x before 4.3.1. Exploitation requires valid signed tokens bearing novel 'tag:' scope values across many repeated logins, and no public exploit code has been identified at time of analysis; independent assessment rates real-world risk as low due to the non-default plugin, permissive IdP dependency, and high volume of authentications needed.
Atom table exhaustion in RabbitMQ's management HTTP API lets an authenticated user who holds only the 'management' tag crash the broker's Erlang VM, taking down every vhost and tenant hosted on that node. The 'node' JSON field accepted by PUT /api/queues/:vhost/:name - and by the equivalent exchanges and bindings endpoints - is passed through rabbit_nodes:make/1 to list_to_atom/1 in rabbit_mgmt_util.erl:get_node/1 (lines ~880-885) with no cluster-membership check first, so each unique value permanently leaks one atom until the VM hits system_limit. About 900,000 unique requests are needed rather than a single call, which keeps this a moderate-severity, sustained-abuse availability issue; no public exploit code has been identified at time of analysis, and deployments are fixed by upgrading to 3.13.15, 4.0.20, 4.1.11 or 4.2.6.
RabbitMQ's Federation plugin (3.13.0 up to the fixed 3.13.18, 4.0.24, 4.1.14, 4.2.9 and 4.3.3 releases) validates a federation upstream URI without performing any vhost-access authorization check, letting a principal that holds policymaker rights on one virtual host point an upstream at a different vhost and read and drain messages it has no permission on. With the default ack-mode the source messages are consumed (deleted) rather than copied, so the flaw combines unauthorized cross-vhost disclosure with destructive consumption. Exploitation is authenticated (CVSS PR:L) and contingent on a multi-tenant broker that actually runs Federation and grants untrusted principals policymaker rights, and no public exploit code or CISA KEV entry was identified at the time of analysis, making this a moderate authorization-boundary issue rather than a mass-exploitable emergency.
Authenticated RabbitMQ tenants on affected releases can exhaust broker scheduler CPU and degrade or deny service to all co-tenants by creating a binding with a crafted rjms_erlang_selector LIKE expression on an x-jms-topic exchange. Only deployments running the optional rabbitmq_jms_topic_exchange plugin are exposed, and the attacker needs permissions both to create bindings on that exchange and to publish messages routing through them; no public exploit has been identified at time of analysis and the issue is not in CISA KEV. Impact is availability-only - confidentiality and integrity are unaffected - but a single malicious tenant can degrade a shared broker, so the issue warrants prompt patching rather than emergency escalation.
Authenticated InvoicePlane administrators can store a crafted custom_field_table value that is later concatenated into SQL identifier positions when the custom-field edit form is opened, producing a second-order SQL injection in releases prior to 1.7.2. The flaw can expose arbitrary database schema data and cause application errors or denial of service, but it requires a high-privilege administrator account (PR:H), so it is a modest-priority issue that mainly affects malicious insiders or already-compromised admin sessions. Vendor-released patch: 1.7.2; no public exploit identified at time of analysis.
Information disclosure in the kitty terminal emulator versions 0.47.0 through 0.48.x lets a program that can write escape sequences to the terminal read the contents of files a user merely drags over a kitty window, without ever completing the drop. The drag-and-drop handler in kitty/dnd.c serves a client's drag-data request without first verifying that a drop has actually occurred, and drop_left_child() keeps the offered URI list, directory handles, an open file descriptor and its main-loop transfer timer alive after the drag leaves the window, so a client can keep reading through a retained directory handle or let an in-flight file transfer continue streaming with no drag in progress. The CVSS 4.0 base score is 6.0 (moderate), the request path is unauthenticated (PR:N) and the decisive precondition is user interaction: the victim must drag a file or directory over the window; no public exploit code was identified at time of analysis, and vendor-released patch kitty 0.49.0 is available.
Missing authorization enforcement in GLPI's REST API v2 (the 'HL' API) lets a low-privileged authenticated user perform ticket team-member add/remove/list operations and entity transfers that the web interface would deny, because the API update flow does not re-apply per-object and per-right checks. Only GLPI 11.0.0 through 11.0.7 are affected - API v2 exists only in the 11.x line - and exploitation requires a valid, working low-privileged account using the API rather than the UI (authentication required, PR:L in both the vendor CVSS 4.0 vector and our assessed CVSS 3.1 vector). Impact is integrity-dominant (I:H) with limited confidentiality/availability effects; a vendor patch is available in 11.0.8 and no public exploit code or confirmed active exploitation was identified at time of analysis.
Improper authorization in GLPI lets an authenticated administrator who holds the delegated 'Update auth and sync' or 'Update auth, sync and 2FA' right (User::UPDATEAUTHENT) change the authentication method and disable two-factor authentication for user accounts that lie outside that administrator's own entity scope. The weakness affects GLPI from 0.84 up to (but not including) 10.0.26, and the 11.x line from 11.0.0 up to but not including 11.0.8; it is only meaningful in multi-entity installations, since in single-entity deployments the administrator already legitimately controls every account. The impact is bounded to authentication-method changes and 2FA toggling rather than arbitrary account modification, vendor-released patches are available in 10.0.26 and 11.0.8, and no public exploit code has been identified at time of analysis.
Denial of service in RabbitMQ 4.2.x (4.2.0 through before 4.2.9) and 4.3.x (before 4.3.3) lets an already highly privileged, authenticated user submit crafted Shovel runtime parameters through the Management HTTP API, causing the parser to intern attacker-controlled strings as Erlang atoms until the node-wide atom table is exhausted and the broker can no longer function. Exploitation demands network reach to the Management API plus credentials carrying both the management and policymaker tags, write permission on a vhost, and the non-default rabbitmq_shovel and rabbitmq_shovel_management plugins enabled; because the malicious parameters are persisted durably and re-parsed when workers start, the resource pressure can return after a restart without the attacker being connected. No public exploit code or evidence of active exploitation was identified at time of analysis, and the independent assessment rates this a genuine but low-priority DoS whose high-scoring optics are tempered by those heavy preconditions. Fixed in 4.2.9 and 4.3.3.
Authenticated denial of service in RabbitMQ brokers running 3.13.0 through the fixed releases 3.13.15, 4.0.20, 4.1.11 and 4.2.6 lets a management user holding the policymaker tag exhaust the Erlang VM atom table and crash the node by submitting an auth_mechanism value containing a very large number of colon-delimited tokens. Exploitation is sharply gated: the Shovel or Federation plugin must be enabled on the target node, and only the privileged policymaker tag can set the auth_mechanism field, so the actor must already be a trusted high-privilege operator rather than an anonymous remote client. Impact is availability-only (node crash), with no data disclosure or modification; no public exploit code has been identified at time of analysis, and vendor-released patches (3.13.15, 4.0.20, 4.1.11, 4.2.6) are available.
Flame dashboards running version 2.4.0 and earlier will sign administrator JSON Web Tokens with whatever lifespan a caller supplies, letting a previously privileged user mint a near-permanent admin token that survives password changes and account deprovisioning. Exploitation is authenticated (PR:H in the assessed vector) and requires that the attacker already held admin access at least once, so this is a persistence and re-entry flaw rather than a route to first-time compromise. Because every token is verified against a single static JWT secret that Flame generates once and never rotates, revocation is effectively impossible without manual secret replacement; no public exploit code or confirmed active exploitation was identified at time of analysis.
Atom-table exhaustion in RabbitMQ 4.x lets an authenticated user who holds the 'policymaker' tag crash a broker node by sending a sustained stream of requests (roughly one million) to the Management plugin's /api/global-parameters/:name endpoint, each with a unique name value. The handler passes the URL segment through rabbit_data_coercion:to_atom/1, which uses the unsafe binary_to_atom/2; because Erlang atoms are never garbage collected, every novel name permanently consumes an atom-table slot until the VM aborts. Exposure requires the Management plugin to be enabled and an account above the management tag (but below administrator); it is not reachable unauthenticated, and the assessed impact is availability-only (no confidentiality or integrity loss). No public exploit code or confirmed active exploitation was identified at time of analysis, and the issue is fixed in RabbitMQ 4.0.22, 4.1.14, 4.2.7 and 4.3.1.
Cross-site request forgery in Horilla HR (horilla-hr) versions before 2.0.0 allows an unauthenticated attacker to silently approve pending attendance requests under a logged-in manager's identity, because the /attendance/approve-validate-attendance-request/ endpoint performed state-changing work (setting attendance_validated, is_validate_request_approved, approved_by and related pending-request flags, then calling attendance.save()) over an HTTP GET that Django's CSRF middleware never validates. The CVSS 3.1 assessment rates this AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, i.e. a low-integrity-impact flaw that requires a manager holding attendance.change_attendance to be authenticated and tricked into visiting attacker-controlled content while that session is active; the attacker cannot choose the approving identity and the impact is bounded to what that victim manager could approve. Vendor-released patch: 2.0.0. No public exploit identified at time of analysis, and the flaw is not confirmed actively exploited (not in CISA KEV).
Improperly controlled modification of dynamically-determined object attributes in the Ash framework for Elixir (ash 2.17.15 through 3.33.10) lets a caller set private action arguments, declared with public?: false, on the bulk update and bulk destroy code paths. The affected matching logic in Ash.Actions.Destroy.Bulk.base_changeset/5 and Ash.Actions.Update.Bulk.base_changeset/5 compares every key of a caller-supplied parameter map against all of the action's arguments without checking public?, so any application that forwards end-user parameters into Ash.bulk_update/4 or Ash.bulk_destroy/4 (for example via AshJsonApi, AshGraphql, or a controller) can have a private argument injected; when that argument is referenced by an arg(...) template driving authorization, record ownership, or audit metadata, the result is an integrity violation or privilege escalation. The vendor has released a patch in 3.33.11 that requires public? in the bulk argument matching; no public exploit code has been identified at time of analysis, and the impact is conditional on the application both exposing a bulk action to untrusted input and using a security-relevant private argument.
Missing authentication in the GibbonEdu Gibbon Unit Planner endpoint modules/Planner/units_add_blockAjax.php (makeBlock function) lets remote attackers reach an AJAX action that should require a valid session, allowing manipulation of the gibbonUnitBlockID and mode arguments against Gibbon 30.0.01 and earlier without credentials. The CVE description states that exploit code has been disclosed publicly and may be used, so exposure should be treated as foreseeable; there is no CISA KEV entry indicating confirmed active exploitation. Impact is limited to low-level confidentiality exposure of unit-planner block data according to the independent assessment, making this a moderate-severity issue rather than an urgent-priority one.
Risk cannot be meaningfully assessed from the provided data. CVE-2026-94282 is reported solely by the vendor source 'ubuntu', indicating that a package distributed through Ubuntu channels is affected, but no description, CVSS score, CVSS vector, CWE identifier, or affected-version metadata accompanies the record, so the nature of the flaw, the attack surface, and the deployment contexts at risk are all unknown. Exploitation status: no public exploit identified at time of analysis. Authentication requirements are not confirmed from available data, and no CISA KEV listing or EPSS score was provided to indicate real-world exploitation or likelihood. Until the corresponding Ubuntu Security Notice and upstream advisory are retrieved, this record should be treated as an unresolved tracking identifier rather than a characterized vulnerability.
Secret disclosure in kitty 0.25.0 through versions before 0.49.0 lets a second local user on the same host capture text that the victim types into prompts rendered by kitty itself, including masked password prompts, without holding any privilege on the victim's account. The askpass escape-code handler in kitty/window.py (handle_remote_askpass) opens a POSIX shared-memory object named in an attacker-supplied device control string and later writes the typed answer back into an object of that same name, never verifying that the object is owned by the user running kitty or that its permissions exclude other users, unlike the equivalent ssh kitten path which performs exactly that check. Exploitation is tightly bounded: it requires a POSIX shared-memory namespace shared between attacker and victim, attacker-influenced bytes being displayed in the victim's terminal, and the victim actually answering the rendered prompt; no public exploit code has been identified at time of analysis and this CVE is not in CISA KEV, and hosts with isolated shared memory, single-user workstations, and kitty 0.49.0 or later are not affected.
Kernel-log flooding in the Linux kernel's in-kernel ksmbd SMB3 server lets an authenticated SMB client degrade host availability by submitting a single DACL containing many structurally valid but unmapped SIDs, each of which previously produced an unthrottled kernel error message. Only systems that have enabled ksmbd and exposed a share are affected (not a default configuration on most distributions, which ship userspace Samba or no SMB server), and the attacker must already hold a valid SMB session, so the practical exposure is narrow; realized impact is limited to availability/log degradation with no confidentiality, integrity, or code-execution consequence. EPSS is low (0.20%, 9th percentile), the issue is not listed in CISA KEV, and the flaw is not known to be actively exploited; vendor patches are available in the listed stable kernel releases. A public fix commit exists upstream, but no verified working exploit code has been identified at time of analysis.