Stored cross-site scripting in the Wpmet Metform WordPress plugin (versions through 4.3.0) lets a low-privilege authenticated user, such as a contributor, plant a malicious script inside form fields or plugin settings; the payload is then stored and executes in the browser of any higher-privileged user (typically an administrator or editor) who views the affected page. The base CVSS score is 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), and the practical risk is LOW-to-MEDIUM because exploitation is gated by two prerequisites: an authenticated account with at least contributor-level access and a victim who subsequently opens the page where the stored payload renders. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, so this is a latent persistence-and-privilege-abuse vector rather than an actively exploited campaign.
Stored cross-site scripting (XSS) in ElementsKit Lite (a WordPress plugin) versions up to 4.0.6 allows an authenticated attacker with contributor or author privileges to inject malicious JavaScript into a page via a vulnerable widget, which then executes in the browser of any user who views the compromised page. The vulnerability requires a separate user to trigger the payload (UI:R) and is limited to the Lite edition; it is rated moderate severity (CVSS 6.5) with no public exploit identified at time of analysis. No evidence of elevated real-world risk or active exploitation (CISA KEV) is present.
Stored cross-site scripting (XSS) in ElementsKit Lite (ElementsKit Elementor addons Lite) versions up to and including 4.0.6 allows an authenticated attacker with contributor-level privileges to inject malicious scripts into Elementor widget content, which then execute in the browser of any user viewing the affected page. The vendor (Patchstack) rates this as medium severity with a CVSS 3.1 score of 6.5, but our assessment confirms it requires user interaction and results in partial confidentiality and integrity loss without availability impact. No public exploit code or active exploitation has been identified at time of analysis.
Stored cross-site scripting (XSS) in the FluentForm WordPress plugin (versions through 6.2.14) allows authenticated attackers with low privileges to inject malicious scripts into form fields, which execute when other users view the affected page. Exploitation requires victim interaction and a low-privileged WordPress account, limiting the attack to authenticated scenarios. No public exploit code has been identified, and the risk is considered moderate due to these prerequisites.
Denial of service in JetBrains YouTrack instances running versions before 2026.2.19422 lets an authenticated user who can upload attachments hang or crash the server by submitting a crafted PSD file that drives the image-processing path into an infinite loop. The attack is network-reachable and needs no victim interaction, but it requires a valid low-privileged account (PR:L), so it is not exploitable by fully anonymous visitors unless the instance permits self-registration or guest attachment uploads; impact is confined to availability, with no confidentiality or integrity loss. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
Authorization bypass in JetBrains YouTrack before 2026.2.19422 allows an authenticated user with only low privileges to read the activity history of restricted issues they are not authorized to view. The root cause is an insecure direct object reference in the issue activities API, where the endpoint resolves a caller-supplied issue identifier without verifying that the caller holds read access to that issue. Exploitation requires valid low-privileged credentials but no user interaction or non-default configuration, and the impact is confidentiality-only (CVSS 3.1 base 6.5, C:H/I:N/A:N); no public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released a fix in 2026.2.19422.
Unauthenticated attackers can overwrite the CRM integration endpoint and stored credentials of any WordPress site running WP Fusion Lite versions from 3.37.14 up to but not including 3.48.0, redirecting the plugin's outbound data sync to a server they control. Because the vulnerable settings handler runs on the WordPress admin initialization hook without any capability or nonce check, a crafted request needing no login, no user interaction, and no special configuration is sufficient (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, rated 6.5). The practical payoff is ongoing exfiltration of synced user records to the attacker's host, so sites with substantial synced customer data face the greatest exposure; no confirmed active exploitation or public exploit code was identified at time of analysis, and a vendor patch is available.
HTML injection in HCL Digital Experience portals allows unauthenticated remote attackers to place attacker-controlled markup into portal pages, spoofing content that appears to be served from the trusted portal domain; exploitation requires the victim to load the crafted page or link (UI:R), and the assessed impact is integrity-only with no confidentiality or availability loss. No public exploit code or confirmed active exploitation was identified at the time of analysis, and signals are consistent in pointing to a moderate, non-urgent issue. A vendor fix is available in HCL Digital Experience 9.5 CF238 or later.
Stored cross-site scripting in the Essential Blocks - Page Builder for Gutenberg Blocks & Patterns WordPress plugin (versions up to and including 6.4.5) allows authenticated attackers with Contributor-level access or higher to inject arbitrary JavaScript that executes when a victim views the affected page. The flaw sits in the Google Map block's 'marker' attribute: marker title/content values are stored as JSON and later decoded and concatenated directly into raw HTML by the frontend InfoWindow builder, so it is insufficient input sanitization plus missing output escaping rather than a logic error. It is network-reachable at low complexity with a scope change (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, 6.4 Medium); the practical barrier is the Contributor authentication requirement, and no public exploit code was identified at time of analysis. Sites that allow open registration or grant Contributor roles to low-trust users should treat this as a priority upgrade.
Signature verification failure in the Apache APISIX saml-auth plugin (versions 3.17.0 through 3.18.0) allows an attacker to forge SAML assertions and impersonate arbitrary users on every route protected by that plugin, and the plugin's DEFAULT configuration is vulnerable, so no additional misconfiguration or attacker-controlled precondition is needed. The vendor's CVSS 4.0 vector scores the issue 6.4 with PR:L and no direct CIA impact on the vulnerable component (only SC:H/SI:H on subsequent systems), which understates the practical effect described by the vendor itself as 'any unauthenticated attacker could impersonate any user'; our independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N, and the PR:N versus PR:L discrepancy between the description and the vendor vector should be verified. No public exploit code and no confirmed active exploitation were identified at time of analysis; exposure is limited to the two-release version window and to deployments that actually enable saml-auth on at least one route.
Stored cross-site scripting in the WordPress plugin Duplicate Post (copy-delete-posts) through version 1.5.6 lets an authenticated subscriber-level user inject arbitrary JavaScript via the 'noti_token' parameter, which then executes in the browser of anyone who later views the affected page. Exploitation is not unconditional: the site owner must have enabled the plugin's User Level Permissions for the Subscriber role, a non-default setting that exposes the i_saw_this_noti AJAX branch used to deliver the payload, so default installations are not reachable by low-privilege users. No public exploit code has been identified at time of analysis, and no KEV listing applies, though the stored nature of the flaw means a single successful injection can affect privileged administrators and visitors; the vendor has released version 1.5.7 as the fix.
Stored cross-site scripting in the Awesome Support WordPress helpdesk plugin (all versions through 6.4.0) lets an authenticated attacker with only Subscriber-level access persist arbitrary JavaScript through the 'gdpr-data' parameter, which then executes in the browser of any user who later views the injected page, including administrators. The prerequisite bar is unusually low for an authenticated XSS: the required wpas-gdpr-nonce is emitted via wp_localize_script to every logged-in user on frontend plugin pages and on /wp-admin/profile.php, and the AJAX handlers accept an arbitrary 'gdpr-user' ID without checking ownership, so a Subscriber can target other accounts rather than only their own. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing); an upstream fix changeset is referenced but no tagged patched version is independently confirmed. This is a moderate, authenticated-only web vulnerability that does not warrant emergency prioritization.
Stored cross-site scripting in bbp Style Pack (a WordPress plugin) versions up to and including 6.4.8 allows authenticated attackers with subscriber-level access to inject arbitrary web scripts via the display_name and bbp_reply_content parameters. Successful exploitation requires wrapping the crafted reply in a <pre> block to bypass WordPress's wpautop/wptexturize quote conversion, and the injected script executes when any user views the affected page. No public exploit code is identified, and there is no indication of active exploitation in the provided intelligence; the CVSS 3.1 vector (6.4 Medium) reflects network-reachable, low-privilege exploitation with scope change.
Stored cross-site scripting in the Redux Framework WordPress plugin affects all versions up to and including 4.5.14, letting an authenticated attacker with only Subscriber-level access plant a persistent script payload that later executes in the browsers of other users, including administrators. The chain works by storing a malicious value in user-meta fields (biography, session_tokens via a crafted login User-Agent, or persisted_preferences via the REST API) and then having that tainted data promoted into the site-wide redux_demo option when a media-URL repair runs on the Redux demo panel; the merged value is rendered without output escaping through the 'user-mediaurl' media field path and the bundled jsonview.js. Rated CVSS 3.1 6.4 Medium (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), it requires a low-privileged account and no victim interaction once the merge has occurred, and no public exploit code or confirmed active exploitation was identified at time of analysis; a fix is available in version 4.5.15.
Stored cross-site scripting in the Download Manager WordPress plugin before 3.3.71 lets an authenticated user with the WordPress Author role or higher save a crafted package setting that is later output without sufficient escaping, so script executes in the browser of any visitor who opens that package's download dialogue - including administrators. Exploitation is gated by two conditions: the site must run PHP below 8.1, because the sanitisation applied at save time only neutralises single quotes on PHP 8.1 and later, and the attacker must already hold an Author-level account or above. Our assessment rates this CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N - a genuine but conditional issue rather than a widespread emergency; vendor-released patch 3.3.71 is available and no public exploit code was identified at time of analysis.
Information disclosure in Next.js 16.3.0 through 16.3.7 is a modest-severity cache-correctness flaw that can serve cached content for one root-param value to requests for a different root-param value when the opt-in Cache Components feature is enabled, allowing remote unauthenticated requests to receive content intended for another tenant, locale, or region. The flaw requires nested use cache functions where an inner function reads next/root-params; the leaked content is not attacker-controlled and depends on which invocation first populates the shared cache entry. Vendor-released patch: 16.3.8; no public exploit identified at time of analysis.
Heap buffer overflow in the Perl Imager module before version 1.037 allows memory corruption inside i_gsampf_fp when a host application asks for float samples across more than one channel of an attacker-supplied paletted image, with the image's own palette controlling the bytes written past the end of the allocation. The vulnerable path is conditional rather than universal: it is only reached when an application calls getsamples() with type 'float' on a palette-type image and requests multiple channels, so real-world exposure depends on how the embedding application uses the library. No public exploit code and no confirmed active exploitation were identified at time of analysis, and CISA's SSVC evaluation rates exploitation as 'none' and automatable as 'no'; the vendor CVSS vector indicates low privileges required (PR:L) while our independent assessment treats the vector as unauthenticated with high attack complexity (PR:N/AC:H), so authentication requirements are not consistent across sources.
Unauthenticated WebSocket access in Podgrab can expose playback metadata and server-side file paths when the /ws route bypasses configured BasicAuth, allowing remote attackers to join the allConnections set and replay captured PlayerExists broadcasts as RegisterPlayer messages. This is a moderate-priority issue: the independent assessment rates it CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N because meaningful data theft depends on a legitimate authenticated user generating broadcasts concurrently, and impact is limited to information disclosure plus possible playback disruption; no public exploit identified at time of analysis.
WP Project Manager 4.0.7 and earlier contains a broken access control flaw that lets an authenticated low-privilege user - a WordPress subscriber - perform actions beyond the capabilities their role should permit, yielding limited but real confidentiality, integrity, and availability impact (CVSS 6.3, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L). Exploitation requires network reachability plus a valid subscriber-level account, so it is practical mainly on sites with open or self-service user registration enabled; no user interaction and no non-default plugin configuration are needed. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the reported EPSS signal does not elevate this beyond a moderate, authenticated authorization weakness. This is a moderate-risk authenticated authorization issue rather than a critical unauthenticated exposure.
Apache APISIX versions 2.14.1 through 3.18.0 can serve requests to protected upstream endpoints without authentication when a permissive (public) route overlaps the path space of a protected route and the client supplies a crafted encoded, non-canonical path. Because authorization is evaluated against the permissive route while the request ultimately resolves to the protected upstream, the protected route's policies are bypassed entirely; the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N) reflects a fully remote, unauthenticated attack that is gated only by the non-default requirement of an overlapping permissive-and-protected route configuration. There is no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV), and the issue is fixed by upgrading to Apache APISIX 3.19.0.
Unauthenticated attackers can advance suspended n8n workflow executions by submitting resume requests that the Send and Wait node in 'Approve Within Chat' mode accepts without verifying the requester's identity or approval permissions. Affected are n8n releases before 2.39.6 and 2.40.0 releases before 2.40.1; exploitation is only possible when a workflow is actively paused at such an approval node, and the resulting impact is integrity-only, limited to advancing that execution and any actions it guards. No public exploit code has been identified at time of analysis, and CISA KEV does not list this issue; vendor patches are available in 2.39.6 and 2.40.1.
Quadratic CPU consumption in the JSONC parser and verifier of the stream-json npm package (stream-json/jsonc/parser.js and jsonc/verifier.js) before version 3.6.0 lets an unauthenticated local attacker stall a Node.js process by supplying one large valid block or line comment split across many small input chunks. Only the JSONC code path is affected; the plain JSON parser discards consumed string and number data and is explicitly not vulnerable. Impact is availability-only (CVSS 3.1 6.2, AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - event-loop stall, no confidentiality or integrity loss), and the maintainer frames the vector as local because documented JSONC input is locally owned or user-controlled configuration rather than internet-facing data. No public exploit code identified at time of analysis; a vendor patch is available in 3.6.0.
Missing authentication in the Instant Buy component of ZongXR SuperMarket 1.0.0.0 lets remote attackers invoke the startBuy function without proving a valid session, simply by manipulating the Username argument passed to InstantBuyController.java. Impact is limited to integrity and availability at low severity (assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L), with no confidentiality loss, and publicly available exploit code exists though there is no confirmation of active exploitation. The authentication prerequisite is ambiguous - the CWE-306 classification and description imply no credentials are needed, while the vendor's CVSS 4.0 vector encodes low-privilege (PR:L) access - so the true auth requirement should be treated as unconfirmed. Real-world risk is low primarily because this is an obscure hobby/open-source project that is rarely exposed in production.
Reflected cross-site scripting in the WordPress plugin Social Media Share Buttons & Social Sharing Icons (slug ultimate-social-media-icons, vendor inisev) affects all versions up to and including 3.0.1, allowing an unauthenticated attacker to inject script into a crafted URL that executes in the browser of a victim who opens it and triggers the plugin's WeChat share dialog. Exploitation is gated by two conditions baked into the vulnerable path: the victim must be browsing with a mobile user-agent and must click the WeChat share icon, after which the injected script runs automatically without further interaction (CVSS 3.1 base 6.1, AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N). No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the practical risk is lower than the unauthenticated network framing suggests because of the mobile-agent and share-click preconditions.
Reflected cross-site scripting in the Ad Inserter - Ad Manager & AdSense Ads plugin for WordPress affects all versions up to and including 2.8.18, letting unauthenticated remote attackers run arbitrary JavaScript in a victim's browser session. The flaw lives in the '{search-query}' dynamic tag: when an ad block uses that tag, the plugin reads the Referer header, is trivially fooled by any referrer containing a '/google.com/'-style segment, and injects the decoded query string into the page without escaping. Because the request is cross-site and carries no authentication privilege (PR:N), the attacker must lure a victim - ideally a signed-in administrator - to an attacker-controlled page that frames or links to an ordinary post on the target site (UI:R); the configuration precondition is a site that uses the '{search-query}' tag with automatic insertion enabled, an opt-in, non-default feature. No public exploit code was identified at time of analysis, and no CISA KEV entry is associated with this CVE; the vulnerability is fixed in plugin version 2.8.19.
Reflected cross-site scripting (XSS) in the Ad Inserter - Ad Manager & AdSense Ads WordPress plugin through 2.8.18 allows unauthenticated attackers to inject arbitrary script through the 's' search parameter, which executes in a victim's browser if they are tricked into clicking a crafted link. Real-world exploitation is constrained by two gates: an administrator must have configured at least one block using the {title} or {short-title} placeholder with that block enabled on search pages (a documented but non-default setting), and a victim must interact with the malicious URL (CVSS UI:R). No public exploit code has been identified at time of analysis, and no EPSS score or CISA KEV entry was provided; the issue is fixed in version 2.8.19.
Server-side request forgery in Form Tools through 3.1.1 allows an authenticated low-privileged user to make the server issue arbitrary outbound HTTP requests by supplying a crafted 'url' argument to the smart_fill function in /global/code/actions.php, with no user interaction required. Impact is confined to low confidentiality (probing internal services and cloud metadata endpoints reachable from the host) rather than code execution, so realistic risk is modest and depends heavily on what the server can reach. Publicly available exploit code exists, the flaw is not confirmed as actively exploited (no CISA KEV listing), and no vendor-released patch has been identified at time of analysis.
Improper access control in David-Crty databasement up to and including 1.7.1 allows an authenticated low-privileged user to read snapshot records that belong outside their authorized organization or scope through the /api/v1/snapshots endpoint, where SnapshotPolicy.viewAny and SnapshotPolicy.view fail to enforce proper scoping. Because the CVSS vector carries PR:L, exploitation requires a valid account on a multi-user or multi-organization deployment, and the assessed impact is limited to low confidentiality with no integrity or availability effect (CVSS 4.0 base 5.3; independently assessed CVSS 3.1 5.3). Publicly available exploit code exists, and the flaw is fully addressed by upgrading to version 1.7.2, which hardens organization scoping.
Post-login redirection in OpenShift's oauth-proxy fails to validate the `rd` destination parameter, so a remote unauthenticated attacker who convinces a user to follow a crafted link can send that user's browser to an arbitrary external website once authentication completes (CWE-601, CVSS 6.1). Red Hat OpenShift Container Platform 4 deployments that expose oauth-proxy login flows are affected, and exploitation depends on the victim clicking the attacker's link and authenticating through that proxy (UI:R); the resulting impact is a browser redirect rather than code execution or data compromise, with real risk arising when the victim is socially engineered into trusting the attacker-controlled landing page for phishing or credential harvesting. No public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score was supplied with the source data.
Reflected DOM-based cross-site scripting in the CodePeople Calculated Fields Form plugin for WordPress (all versions up to and including 5.5.1.3) allows unauthenticated attackers to execute arbitrary script in a victim's browser, but only on sites that have been specifically configured to expose the flaw. The issue is conditional rather than a default-configuration defect: the site must host a public form with a Select2-enabled dropdown whose choices are built by a calculated equation that pipes a URL parameter through GETURLPARAMETER() into setChoices({texts:[...]}); where that wiring exists, a single crafted link is enough to trigger script execution when a user clicks it. No public exploit code has been identified at time of analysis, and there is no confirmed active exploitation; the assessed severity is moderate (CVSS 6.1), with impact confined to the victim's session (C:L/I:L/A:N) and victim interaction required (UI:R).
OpenConstructionERP through 14.8.1 can leak one user's data to another user's session through the AI Provider Configuration Handler implemented in backend/app/modules/ai/ai_client.py. The issue is only reachable by an account that is already authenticated on the instance (CVSS vector PR:L) and impact is limited to confidentiality and integrity of AI provider configuration data rather than full system compromise; the independent assessment rates the overall risk as low-to-moderate rather than a priority issue. Publicly available exploit code exists and the CVSS 4.0 vector carries an E:P (proof-of-concept) exploit-maturity score, so the flaw should still be treated as practically exploitable, but there is no confirmed actively exploited (CISA KEV) status for this CVE.
Unrestricted file upload in Form Tools 3.1.1 and earlier lets an authenticated, low-privileged user push attacker-controlled files onto a self-hosted instance by invoking the Files::uploadFile function in the Ajax Handler (global/code/actions.php). Publicly available exploit code exists, but the attack is access-gated: it requires a reachable Form Tools deployment plus a valid low-privilege session, and practical severity depends on whether uploaded files are written to a web-executable directory. No vendor-released patch is available because the project has not responded to the reported issue, so overall risk is best characterized as low-to-moderate and access-gated rather than urgent.
Server-side template injection (SSTI) in formtools.org Form Tools up to and including version 3.1.1 allows an authenticated low-privilege user to inject template-engine metacharacters via the page_titles argument in Clients::updateClientSettingsTab, potentially causing limited information disclosure and modification within the application. Publicly available exploit code exists, but exploitation requires a valid low-privilege account and the assessed impact is capped at Low for confidentiality, integrity, and availability. The vendor was notified early through a GitHub issue but has not responded, and no patched version has been released.
Cross-site scripting in rhukster/dom-sanitizer through 1.0.15 lets an attacker who can submit HTML that the library sanitizes slip script-capable URLs into attributes the filter never checked - form action, cite, poster, src, srcset, and background - because DOMSanitizer::isDangerousUrl() only scheme-validated href and xlink:href. The headline case is a form action="javascript:..." that survives end-to-end as a complete, submittable form (form, button/input and type are all allow-listed), firing when a victim views the stored content and interacts with it. Publicly available exploit code exists (published alongside the GHSA-mrpv-6x26-mf6c advisory); there is no confirmed active exploitation and this CVE is not in CISA KEV. Vendor-released patch: 1.0.16.
Fail-open error handling in the Data Masking utility of Powertools for AWS Lambda (Python) before 3.35.0 can cause sensitive field values to be emitted unmasked into logs or storage whenever a masking operation fails at runtime. The flaw (CVSS 5.3, vector AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N) is only reachable in applications that actually apply Data Masking to sensitive fields, and only when a masking rule errors - an invalid masking path, a regular expression that cannot be compiled, or a masking-provider failure - after which the original value is returned with nothing more than a warning instead of an exception. There is no public exploit identified at time of analysis; this is a genuine data-confidentiality weakness but a low-urgency one in real terms, because the attacker must also obtain access to the downstream destination (log store or storage) where the unmasked value is written.
Path traversal and symlink-validation flaws in ansible-runner's unstream_dir() (CVE-2026-103754) let an authenticated, low-privilege actor who can inject crafted archive content into the transmit/worker protocol create files, create symlinks, or change permissions outside the intended extraction directory, which can be leveraged toward code execution. The issue affects ansible-runner as shipped in Red Hat Ansible Automation Platform 2 (and upstream/AWX deployments) prior to the PR #1550 fix and carries a vendor-assigned CVSS 3.1 base score of 5.9 (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L). No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation is constrained by the need to supply crafted archive members into this specific worker protocol path.
Cross-site request forgery in Pandora FMS version 777 and later allows an unauthenticated attacker to force deletion of alert commands in a target console, provided an authenticated administrator with a live session visits an attacker-controlled page. The flaw (CWE-352) exists because state-changing alert-command deletion is exposed through GET requests that carry no anti-CSRF validation, so a malicious page can issue sequential requests that the console accepts as legitimate. The vendor scored it 5.9 (Medium) under CVSS 4.0 (AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:L), and no public exploit code has been identified at time of analysis; exploitation requires victim interaction and administrator privileges on the victim account.
Cross-site request forgery (CSRF) in Pandora FMS 777 and later allows a remote attacker to delete event responses by luring a logged-in administrator to a malicious page that issues a forged GET request to the event-response deletion function. The attacker needs no credentials of their own - the CVSS 4.0 vector carries PR:N with UI:A, and the independent assessment records PR:N/UI:R - but the victim must hold an active administrative session and must perform the interaction of visiting the attacker-controlled page, making this a social-engineering-dependent attack rather than a fully autonomous one. No public exploit code or confirmed active exploitation has been identified at time of analysis, no EPSS score was supplied, and the vendor maintains a security advisory index at https://pandorafms.com/en/security/common-vulnerabilities-and-exposures/. Impact is bounded to the deletion of event responses (high integrity, low availability per the assessment) rather than full administrative takeover, giving a constrained but genuine risk profile for privileged monitoring workflows.
High-privilege authenticated users can abuse the agent upgrade feature in Genian NAC and Genian ZTNA to write files outside the intended extraction directory via a ZIP Slip path traversal (CWE-862, missing authorization and integrity verification), which can result in arbitrary code execution on the appliance. Affected releases include Genian NAC 4.0.175, 5.0.65 LTS, 5.0.75 LTS, 5.0.85 Stable, and 5.0.86, plus Genian ZTNA 6.0.26 LTS, 6.0.35 LTS, 6.0.45 Stable, and 6.0.46. Exploitation is gated by high attack complexity and a high privilege requirement (PR:H) on the upgrade/management function, and there is no public exploit identified at time of analysis; the vendor (via KrCERT) scores it CVSS 4.0 5.9 Medium with integrity-only impact, while an independent assessment rates CVSS 3.1 7.0 (AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H) reflecting the possible RCE outcome.
Cross-site scripting (CWE-79) in an unidentified Johnson Controls web application component affects builds prior to 3.0b63, allowing an attacker with a low-privileged authenticated session (CVSS PR:L) to submit crafted input into a field that is rendered to other users without proper neutralization. The reported CVSS 4.0 base score is 5.8 (Medium), with scope-change metrics (SC:H/SI:H/SA:H) indicating the impact can extend beyond the vulnerable component into the browser session or downstream consumers of the page. The affected product cannot be pinned down from the source data because the CPE entry resolves to a generic classification label ('CWE-79 - Cross-site Scripting' / 'CAPEC-63') rather than a real product name, so the specific Johnson Controls offering, the vulnerable feature, and whether the flaw is stored or reflected remain unconfirmed; the only vendor reference is the Johnson Controls cybersecurity advisory page. There is no confirmed CISA KEV listing (not confirmed actively exploited (CISA KEV)), but the CVSS 4.0 Exploit Maturity value of Proof-of-Concept (E:P) indicates publicly available exploit code exists, and our independent assessment notes that reliable exploitation depends on a second user rendering the injected content, which limits reliability and scope.
Credential tampering in n8n versions before 1.123.80 lets an authenticated user with editor access to a shared workflow bypass the workflow credential tamper guard by constructing a node whose ID duplicates an existing node while its name does not match, allowing the attacker to retain the victim's credentials and redirect secrets to attacker-controlled hosts. Exploitation is not available to anonymous or read-only users: it requires editor privileges on a workflow shared with a higher-privileged credential owner, so realistic risk is concentrated in multi-tenant or team deployments where low-privilege editors collaborate on workflows containing credentials owned by others, while single-user or fully-trusted-editor installations are effectively unaffected. There is no public exploit identified at time of analysis, and the vendor has released a fix in n8n 1.123.80; this is a moderate-risk authenticated authorization flaw (CWE-639, vendor-assigned CVSS 5.8 with changed scope) rather than a top-priority emergency.
Apache APISIX 3.17.0 can write an unmasked sensitive header value into its configured log sink when a specific, conditional response structure occurs, allowing anyone who can read those logs to recover data that should have been masked. The assessed CVSS:3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N) shows the exposure is contingent on logging being enabled and capturing the affected header, on the attacker holding at least low privileges, and on log-sink readability, so an authenticated local actor with log access is the realistic threat model rather than an unauthenticated remote attacker. This is a genuinely low-to-moderate priority information-disclosure issue, not a high-urgency flaw; no public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor-released fix is Apache APISIX 3.18.0.
OS command injection in Johnson Controls EasyIO FS32 building-automation controllers running firmware before 3.0b63 allows an attacker who already holds high-privileged access on the device to execute arbitrary operating-system commands, with the 7.2 High score reflecting adjacent-network reachability, high attack complexity, and additional attack requirements as well as severe availability and downstream scope impact. Only firmware versions prior to 3.0b63 are affected, and exploitation is not a remote-internet scenario: the attacker must be positioned on the adjacent building-automation/OT network and must already be authenticated with elevated privileges, which effectively limits realistic abuse to insiders or adversaries who have established an OT foothold. There is no public exploit code identified at time of analysis and the vulnerability is not confirmed actively exploited (no CISA KEV listing); the exact feature or parameter carrying the injected command is not specified in the available description.
Authentication abuse in Johnson Controls EasyIO FS32 building-automation controllers running firmware earlier than 3.0b63 lets an attacker who already holds privileged access on the adjacent network leverage an insecurely initialized default resource to subvert authentication, with assessed consequences spanning integrity and availability of the controller and knock-on effects at system scope. Exploitation is heavily gated: the attacker must sit on the adjacent/local network (AV:A, not internet-reachable), must already be privileged (PR:H), must clear high attack complexity (AC:H) and a specific attack requirement (AT:P), so this is realistically reachable only by someone with an existing foothold on the building-automation network, not by an unauthenticated remote actor. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the CVSS 4.0 base score is 5.6 (medium).
Johnson Controls EasyIO FS32 building-automation controllers running firmware before 3.0b63 expose a file/path-handling function to externally controlled input (CWE-73), allowing a high-privileged, authenticated attacker with adjacent-network access to supply crafted file names or paths and reach files outside the intended location, with the potential to read sensitive data and to overwrite or corrupt files that affect device integrity and availability. Exploitation is constrained: it requires a foothold on the OT/building-automation network segment (CVSS AV:A), an elevated privileged session on the device (PR:H), a specific attack prerequisite (AT:P), and a high-complexity sequence (AC:H), yielding a base score of 5.6 under CVSS 4.0 and an assessed CVSS 3.1 vector of AV:A/AC:H/PR:H/UI:N/S:C/C:L/I:H/A:H. No public exploit code was identified at time of analysis and there is no CISA KEV listing, so this should be treated as a genuine but non-urgent issue whose practical risk is materially lower than the path-traversal label alone suggests.
Password spraying attacks against EasyIO FG controllers running firmware before 2.0b52 can succeed due to hard-coded credentials (CWE-798), enabling unauthenticated remote attackers to bypass authentication and potentially achieve high integrity and availability impact with low confidentiality impact. Affected devices are those with firmware versions prior to 2.0b52, and exploitation requires use of a vendor hard-coded credential and access to the controller's management interface, which may be exposed via BACnet/IP, web, or integration ports. This is a moderate-priority, context-dependent issue rather than an internet-wide emergency; no public exploit code or confirmed active exploitation has been identified at time of analysis, and the assessed CVSS v3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H.
Local privilege escalation in Johnson Controls Easy IO FG controllers prior to version 2.0b52 allows an authenticated attacker with low-privileged local access to brute-force privilege management controls, potentially leading to high integrity and availability impact. Exploitation is complex and requires a specific attack precondition, and no public exploit code has been identified at the time of analysis. This is a medium-severity, operator-dependent flaw in a niche building-automation controller, not a high-priority mass-exploitation risk.
Server-side request forgery in JetBrains YouTrack before 2026.2.19422 allows an authenticated user holding administrative or project-level privileges to abuse the GitHub VCS integration and coerce the YouTrack server into issuing requests to destinations of the attacker's choosing. With a CVSS 3.1 base score of 5.5 (AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N), the impact is bounded to limited confidentiality and integrity loss with a scope change, and the high privilege prerequisite is the dominant limiting factor - this is a moderate-severity, low-real-world-priority issue rather than an anonymous or default-configuration exposure. At the time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis.
GEGL's Radiance HDR loader reads past the end of a memory-mapped image when a crafted .hdr file declares a scanline width larger than the actual data present in an uncompressed scanline, crashing the application that consumes the library - most notably GIMP, which uses GEGL for image processing. Any local user who opens such a file is affected; no authentication is required to the library, but the attacker must convince a victim to open the crafted file (UI:R), and the impact is availability-only (CVSS 5.5, AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, consistent with a low-priority, local denial-of-service rather than a code-execution primitive.
Missing current-password confirmation in Filament's app-based multi-factor authentication management actions (set-up, disable, regenerate recovery codes) allows an attacker who already holds an authenticated user session to enroll a new TOTP authenticator and harvest fresh recovery codes, or to disable existing app-based MFA and regenerate its recovery codes, by supplying only an existing valid app code or recovery code. The flaw affects Filament 4.0.0 through <4.13.3 and the 5.x line before 5.8.3, carrying a CVSS 3.1 score of 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L) - the required authenticated session, per the independent assessment, is the limiting factor, and there is no path to unauthenticated sign-in through this issue. There is no public exploit identified at time of analysis and no CISA KEV listing; vendor-released patches exist in 4.13.3 and 5.8.3.