Stored cross-site scripting in the Analytics Insights - Google Analytics Dashboard for WordPress plugin allows script injection through the Page Title in versions up to and including 6.3.12, executing when a user later accesses the affected page. The supplied CVSS 3.1 vector is 7.2 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N), and EPSS is 0.24% at the 15th percentile, with no CISA KEV entry and no public exploit identified at time of analysis. The vector indicates unauthenticated, no-interaction exploitation, but the sources do not describe the exact endpoint or input path by which an unauthenticated attacker sets the Page Title.
Stored cross-site scripting in the Advanced Views - Display Framework - Gutenberg/Elementor/Shortcode plugin (acf-views) for WordPress, affecting all versions up to and including 3.9.6, allows unauthenticated visitors to plant script payloads through the public 'comment' parameter that later execute in the browser of anyone loading a page where an avf-layout block renders that comment's content. The decisive weakness is that the plugin's get_comment() lookup applies no approval-status filter, so a pending or unapproved comment is enough to trigger the payload - ordinary comment moderation does not mitigate the attack. Severity is rated CVSS 7.2 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, CWE-79) with a this_week priority label; no public exploit code and no CISA KEV entry were identified at time of analysis.
An out-of-bounds read in WatchGuard Fireware OS's FireCluster synchronization processing lets an attacker who already sits on the cluster interconnect - a compromised cluster peer or an on-path attacker on the sync link - repeatedly crash the cluster synchronization process with crafted traffic, producing a sustained denial of service. Only Fireboxes deployed in a FireCluster high-availability configuration are exposed; stand-alone Fireboxes are not reachable this way, and the CVSS 4.0 base score of 7.2 (HIGH) is driven almost entirely by high availability impact (VA:H) with only limited confidentiality/integrity effect (VC:L/VI:L) from the out-of-bounds read itself. Fixed builds are available from the vendor (12.12.4, 12.5.22 on the 12.0 LTS branch, and 2026.4 on the 2025.1 branch); no public exploit code has been identified at time of analysis and the flaw is not listed as actively exploited.
Arbitrary file read and deletion in GRR (JeromeDevome) up to and including 4.4.2 lets an authenticated administrator abuse the database restoration feature to point at files outside the intended restore location, disclosing sensitive data or destroying files and causing denial of service. The flaw sits in the admin-only restore controller, so exploitation is gated behind a high-privilege account, and the files actually reachable or deletable depend on the OS permissions of the web server process, with impact amplified when the server runs elevated. The vendor fix is version 4.5.0; no public exploit code was identified at time of analysis.
The CTFd Terraform Provider (ctfer-io/terraform-provider-ctfd) writes the ctfd_team.password attribute into Terraform state as a non-sensitive value in versions 0.1.5 through 2.8.1, so anyone who can read that state file obtains the CTFd team password directly, without needing the state encryption password or any further decryption step. The exposure is access-gated rather than anonymous: the attacker must already be able to read the state (a shared or compromised host, a state file committed to version control or leaked through CI logs, or an exposed remote backend), which is reflected in the assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N and a confidentiality-only impact limited to team passwords. The vendor addressed it in v2.8.2 by marking the schema attribute Sensitive, states that no workaround exists, and no public exploit code has been identified at time of analysis.
SQL injection in Asterisk's Channel Event Log database backends cel_pgsql and cel_tds allows attacker-influenced data placed in the CEL eventtype column to be executed as arbitrary SQL against the connected PostgreSQL or TDS/MSSQL database. Exposure is limited to deployments that load and configure one of those CEL backends, invoke the CELGenUserEvent dialplan application, and pass it unvalidated data that a caller or other untrusted source can influence; default installations without these backends and dialplans are not affected. Fixed releases are Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11 / 22.8-cert3; no public exploit was identified at time of analysis.
Stored cross-site scripting in the Autodesk Fusion desktop application allows a maliciously crafted HTML payload embedded in the description field of an electronic library (.lbr) file to execute when that library is imported and rendered in the Library Manager. Successful exploitation can let an attacker read local files or execute arbitrary code in the context of the Fusion process, so the impact extends beyond a typical cosmetic script injection even though the attack is not remotely triggerable. Affected builds are Fusion 2705.1.30 up to, but not including, 2706.1.14; the vendor has released a fix, no public exploit has been identified at time of analysis, and the current priority decision places remediation in the this_week window.
Reflected cross-site scripting in the Autodesk Fusion desktop application (builds 2705.1.30 up to, but not including, 2706.1.14) allows an attacker to run HTML/script in the context of the Fusion process when a user invokes a crafted Fusion protocol URL whose documentName parameter carries the payload. Successful exploitation can let the attacker read local files or execute arbitrary code as the current user, so the integrity and confidentiality impact is high, though the attack requires the victim to click or open the malicious link and cannot trigger autonomously (AV:L, UI:R, PR:N). No public exploit code has been identified at time of analysis and there is no CISA KEV listing; Autodesk has released a fixed build and the vendor advisory is available.
Stored cross-site scripting in Autodesk Fusion 2705.1.30 through versions before 2706.1.14 allows an attacker who delivers a design with a crafted name to run HTML/JavaScript when another user opens and views that design, potentially reading local files or executing code in the context of the Fusion process. This is a moderate, conditional risk rather than an emergency: exploitation requires user interaction (UI:R) on a local vector (AV:L) with no privileges required (PR:N), and no public exploit was identified at time of analysis. Updating to 2706.1.14 fully addresses the issue per the assessment.
Local privilege escalation and arbitrary file overwrite in WatchGuard Fireware OS let an attacker who already holds code execution as a low-privileged system process write files with root privileges and tamper with firewall IP set data. The attacker plants a crafted filesystem object such as a link in a location the firewall daemon processes, then triggers a firewall IP-set list update so the root-privileged daemon follows it; the written content is only partially constrained and the list-update precondition must be satisfied. No public exploit code was identified at time of analysis and the flaw is not listed in CISA KEV, with fixed builds available from the vendor.
Cross-site request forgery in the web/management interface of Ubiquiti airMAX M devices running firmware below 6.3.26 allows an attacker to make unauthorized configuration changes and push the device into a denial-of-service condition by luring an already-authenticated administrator to an attacker-controlled page. No credentials for the device are required (PR:N), but the forged request only takes effect against the victim's live session, so the required user interaction (UI:R) is the main limiting factor; integrity impact is low while availability impact is high. Severity is rated CVSS 7.1, EPSS is low at roughly 0.10% (1st percentile), no public exploit code or PoC reference has been identified at time of analysis, and the issue is not in CISA KEV; Ubiquiti has released a fixed firmware version.
Stack-based buffer overflow in WatchGuard Fireware OS lets a network-adjacent attacker execute arbitrary code with root privileges by presenting a specially crafted certificate to the logging service. Exploitation is condition-gated: the firewall must be configured to forward logs to a remote log server, and the attacker must be able to impersonate that server or intercept traffic to it. No public exploit was identified at the time of analysis, and the vendor has released fixed versions.
A stack buffer overflow in Asterisk's res_xmpp module allows an XMPP-authenticated attacker who can reach the PBX's configured XMPP connection to crash the Asterisk process, giving a high availability impact (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/A:H, 7.1). Only deployments where res_xmpp is loaded and an XMPP connection is defined in xmpp.conf are exposed - neither is part of a default configuration - and the attacker must hold a valid account on the same or a federated XMPP server. Fixed releases are available for all supported branches (20.20.1, 21.12.3, 22.10.1, 23.4.1, plus Certified 20.7-cert11 and 22.8-cert3); no public exploit has been identified at time of analysis and the issue is not in CISA KEV.
Improper output sanitization in Tanium Enforce 2.9, 2.10, and 3.0 allows a network-reachable attacker to craft malicious output that can lead to limited information disclosure and integrity impact when a legitimate user views or exports affected data (CVSS 7.1). The CVSS vector indicates no required privileges (PR:N) but user interaction (UI:R) is required, and whether injecting the payload itself requires prior authenticated access to Enforce is unverified; no public exploit identified at time of analysis. Tanium has released fixed builds in Enforce 2.9.736, 2.10.778, and 3.0.373, and the vuln.today priority engine rates remediation as 'this_week'.
Improper output sanitization in Tanium Comply allows a remote, unauthenticated attacker to introduce crafted content that is rendered or exported when an authorized operator views the affected output, with the scope change indicating impact beyond the attacker-controlled component, such as the operator's session or an exported file. Only Comply 2.32 before 2.32.263, 2.35 before 2.35.323, and 2.37 before 2.37.326 are affected; confidentiality, integrity, and availability impacts are Low, and the required user interaction is the main limiting factor. No public exploit was identified at the time of analysis, and patched builds are available from Tanium.
Server-side request forgery (SSRF) in NVIDIA TensorRT-LLM 1.3.0rc24 allows an attacker who can reach a local input vector to influence server-side requests and potentially disclose information. NVIDIA rates the issue CVSS 7.1 with a local attack vector (AV:L), no authentication required once that vector is reached, no user interaction, changed scope, and high confidentiality impact only. No public exploit code or active exploitation is identified in the available intelligence, and applicability to versions other than 1.3.0rc24 is not confirmed.
Server-side request forgery (CWE-918) in NVIDIA TensorRT-LLM, reported by NVIDIA at CVSS 7.1, allows an attacker positioned with local or adjacent access to the inference host to make the service issue requests to attacker-influenced destinations, yielding high confidentiality impact and possible data tampering under a scope change. No authentication and no user interaction are required once that local/adjacent access is obtained, and AC:L means no special timing or configuration hurdle is described. There is no public exploit identified at time of analysis and the CVE is not in CISA KEV; the EUVD record lists TensorRT-LLM 1.3.0rc24 as affected and the vuln.today decision label is this_week.
Broken access control in REDAXO core before 5.21.4 allows an authenticated editor to redirect slice write operations at content they are not permitted to change, by pairing an article they are allowed to edit with the id of a slice belonging to another category. Deleting and toggling other editors' slices online/offline require the fewest additional permissions, while moving them needs the global moveSlice[] right and overwriting content additionally requires a matching module/template constellation. This is a moderate-priority, authenticated authorization flaw rather than a widespread emergency: exploitation needs a valid editor session with content permission on at least one category, no public exploit code has been identified at time of analysis, and the vendor has released REDAXO 5.21.4 as the fix.
Missing authorization in REDAXO's media pool bulk move (core releases through 5.21.3) lets authenticated backend users with permission for just one media category pull files out of categories they are barred from and then silently replace their contents everywhere those files are embedded. The bulk move validates only the target category, and because media permissions are flat while search (notably searchmode=global) lists files outside permitted categories as selectable checkboxes, no crafted request or victim interaction is required. Integrity impact dominates: replacement is constrained by matching file extensions, a MIME allowlist and SVG sanitisation, and deletion of in-use files is refused. There is no public exploit identified at time of analysis, no confirmed active exploitation (CISA KEV), and vendor patches are available in 5.21.4, making this a this-week priority rather than an emergency.
Missing authorization in REDAXO core before 5.21.4 lets any authenticated backend user read the unpublished working version of any article by sending rex_version=1 to the structure/version preview, and lets users holding the history[article_rollback] permission read historic snapshots, including content that has since been deleted, through the structure/history preview using rex_history_date. Impact is confidentiality only; the article and clang are taken from freely chosen request parameters and can be enumerated, so exposure is systematic rather than a single object. No public exploit code has been identified at time of analysis, and the vendor-released fix is version 5.21.4.
Cross-site request forgery in Semantic MediaWiki's Special:SMWAdmin page allows an attacker to drive destructive maintenance actions - table schema setup (action=updatetables), entity disposal, and job enqueue or stop - through the browser session of a logged-in user holding the smw-admin right, producing semantic data loss, schema disruption and resource exhaustion. The flaw covers releases from 3.0.0 before 7.3.1; the vendor advisory confirms 7.3.0 and 7.3.1-alpha at revision 61805acbab50e2ffd4f75ebbb23ee9695c191fb8, with the corrected package `composer/mediawiki/semantic-media-wiki` fixed in 7.3.1. Exploitation is not self-service: the attacker is unauthenticated but must lure a privileged administrator to a malicious page while the targeted maintenance feature is enabled, so the practical exposure is bounded; the advisory publishes a source-predicted PoC HTTP request (not verified as working exploit code), no active exploitation is confirmed (not in CISA KEV), and the priority call for this CVE is patch within this week.
Semantic MediaWiki 2.5.0 through 7.3.1-alpha applies annotation-driven page protection without any authorization check, so an ordinary editor who can already edit an unprotected page in a semantic-enabled namespace can add [[Is edit protected::true]] and have indefinite edit and move restrictions imposed at the configured $smwgEditProtectionRight - a right the editor does not hold. The effect is a persistent denial of edit and move to other contributors, potentially including administrators who lack the configured SMW right, rather than any disclosure of data. Exposure is narrow: the feature is disabled by default and only wikis that deliberately enabled $smwgEditProtectionRight are affected, and while the vendor advisory documents an offline, network-isolated PHP harness confirming the updater's behavior, no end-to-end exploit against a live wiki is referenced and there is no KEV listing.
Wails v2's BindingsAllowedOrigins wildcard matching can be bypassed when an application is configured with a trailing or partial-label wildcard such as https://myapp.com*, allowing an attacker-controlled origin sharing that literal prefix, for example myapp.community or myapp.com.attacker.com, to invoke bound Go methods once that origin is loaded in the webview. The documented subdomain-prefix pattern https://*.myapp.com and default configurations without such a wildcard are not affected, and realized impact depends on which Go methods the application exposes. The vendor rates this 7.6 HIGH under CVSS 4.0; no public exploit identified at time of analysis and no CISA KEV listing, and exploitation requires the non-default misconfiguration plus user/webview interaction to load the attacker origin.