Command injection in the WAVLINK WL-WN530BE1-A router (build V251117) allows unauthenticated remote attackers to execute arbitrary shell commands on the device by sending crafted requests to /protocol.csp that reach the con_check_read_finish function with malicious group_name or IP-FROM values. Per the supplied CVSS vector (AV:N/AC:L/PR:N/UI:N), no credentials, user interaction, or non-default configuration are indicated as prerequisites, giving high confidentiality, integrity and availability impact. A public PoC reference exists (a GitHub write-up linked from the VulDB entry); it is not verified as working exploit code, and no CISA KEV listing is present in the supplied data, although the vuln.today decision label is act_now.
Unauthenticated OS command injection in the WAVLINK WL-WN579A3-A Initial Setup Wizard allows a remote attacker who can reach /cgi-bin/adm.cgi to execute arbitrary shell commands by supplying a crafted wlan_ssid argument to set_wzdgwMesh, with high confidentiality, integrity and availability impact (CVSS 4.0 score 9.3; assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H). The issue affects the named 2026-03-10-94f93d4 firmware and is tracked as CWE-78; a public PoC reference exists, but it is not verified as working exploit code, and no CISA KEV confirmation was provided. Exposure is mainly limited by whether the device HTTP management interface is reachable from untrusted networks, and the priority label is act_now with no vendor-released patch identified at time of analysis.
Stack-based buffer overflow in the TFTP upload filename handler of D-Link DIR-505 firmware 1.10B02 lets remote attackers send a crafted upload filename to /usr/bin/tftpd and corrupt stack memory, with high confidentiality, integrity, and availability impact under the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N). Exploitation requires the TFTP upload service to be running and reachable from the attacker's network position; the target is a specific retired travel-router model and firmware. No CISA KEV entry is present, but a public PoC reference exists on GitHub and has not been verified as working exploit code; the vuln.today decision label is act_now.
OS command injection in the WireGuard CLI group handler of the WAVLINK WN536AX6-A router (firmware V260507_2.0.0) lets an attacker who can reach the group-management interface inject arbitrary shell commands through the group_name argument processed by sub_41a1d8 in /bin/ioos, achieving full compromise of confidentiality, integrity and availability. The CVSS 4.0 score is 9.3 with a vector of AV:N/AC:L/AT:N/PR:N/UI:N, but authentication requirements are not confirmed from the available data, and if an admin session or LAN-only management access is actually needed that becomes the primary limiting factor; risk is highest where the management or WireGuard interface is exposed to the WAN. A public PoC reference exists (a GitHub write-up describing the wireguard_cli_group command injection); it is not verified as working exploit code, and there is no KEV listing or other confirmation of active exploitation.
OS command injection in the WAVLINK WN536AX6-A web management interface allows remote attackers to execute arbitrary shell commands as the device's ioos process by supplying a crafted group_name value to the OpenVPN CLI configuration handler (sub_416760 in /bin/ioos). Firmware V260507_2.0.0 is the version identified as affected in the disclosure, and the CVSS 4.0 score of 9.3 with a PR:N vector treats the endpoint as reachable without authentication, although the available sources do not confirm whether a prior login to the management UI is enforced before the vulnerable handler can be reached. A public PoC reference exists; it is not verified as working exploit code, no CISA KEV entry is associated with this CVE, and the vuln.today decision label for the issue is act_now based on the convergence of the command-injection impact, the public write-up, and the absence of a shipped fix.
OS command injection in WAVLINK WN553X1-B firmware 260403_2.0.0 allows remote attackers with high-privilege administrative access to execute arbitrary OS commands by manipulating the file_id argument passed to the sub_416B50 function in /bin/ioos. The assessed CVSS vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, so the main limiting prerequisite is authenticated administrative access rather than unauthenticated reachability. A public PoC reference exists at a GitHub advisory, but it is not verified as working exploit code, and no CISA KEV entry is indicated.
OS command injection in the del_vlan_group function of the WAVLINK WN701AE (firmware 260105) ioos web backend allows network-reachable attackers to execute arbitrary shell commands on the device. The CVSS 4.0 vector (PR:L, AC:L, UI:N) shows a low-complexity attack that requires a low-privilege authenticated session on the web management interface, with high confidentiality, integrity and availability impact across the vulnerable and subsequent systems; an EPSS-style exploitability metric of E:P and a public PoC reference (not verified as working exploit code) exist. No CISA KEV entry confirms active exploitation, but the flaw is considered high priority this week because of its severity and the presence of public technical detail.
OS command injection in the WAVLINK WN701AE (firmware M01AE_V260105) ioos web backend lets a network-positioned attacker who already holds a low-privileged account execute arbitrary OS commands on the device by manipulating the rule_name argument of the del_staticrule function in static_route_setting.sh. Successful exploitation compromises confidentiality, integrity and availability of the router itself and can extend to connected systems (assessed CVSS:3.1 8.6, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). A public PoC reference exists in a GitHub write-up; it is not verified as working exploit code, and no CISA KEV listing indicates confirmed active exploitation. The vendor was contacted about the disclosure.
OS command injection in the WAVLINK WN553X1-B WireGuard CLI group handler lets an attacker with low-privilege authenticated access pass crafted group_id or group_name values that are executed as operating-system commands by /bin/ioos (sub_41A748) on firmware V260403_2.0.0. The flaw is remotely reachable, requires no user interaction, and can yield high confidentiality, integrity, and availability impact on the device. A public PoC reference exists; it is not verified as working exploit code, and the issue is high severity and prioritized for this week rather than a confirmed widespread-exploitation emergency.
Authenticated low-privilege users of the WAVLINK WN553X1-B router (build V260403_2.0.0) can inject operating system commands through the WireGuard CLI handler in /bin/ioos by manipulating the file_id argument, giving full compromise of confidentiality, integrity and availability on the device. The flaw sits behind the management plane, so exploitation requires valid low-privilege credentials or an authenticated session plus network reachability of the admin/WireGuard interface; attackers on an exposed admin plane gain the highest practical benefit. A public proof-of-concept reference has been published on GitHub (a write-up under a 'HACKALL' repository) and is not verified as working exploit code; there is no CISA KEV entry, and the item is triaged as a this-week priority rather than an emergency.
OS command injection in the ovpn_file handler of the WAVLINK WN553X1-B router (firmware 260403_2.0.0) allows an authenticated, low-privileged attacker who can reach the management interface to pass a crafted file_id argument into an OS command executed by the /bin/ioos binary (function sub_4162A8). Successful exploitation gives high confidentiality, integrity and availability impact on the device and, per the CVSS 4.0 vector, on subsequent systems, with no user interaction required. A public PoC reference exists (a GitHub write-up); it is not verified as working exploit code, there is no CISA KEV listing, and the disclosure is tracked by VulDB with a this-week handling priority.
OS command injection in the OpenVPN CLI handler of WAVLINK WN553X1-B firmware V260403_2.0.0 allows a remote attacker holding low-level (authenticated) privileges to execute arbitrary OS commands by manipulating the file_id argument processed by sub_416568 in /bin/ioos. Successful exploitation gives full compromise of confidentiality, integrity and availability on the device, which is typically positioned at the network edge. No CISA KEV entry or other confirmation of active exploitation was supplied; a public PoC reference exists, but it is not verified as working exploit code, and the vulnerability is prioritized for remediation this week rather than as an emergency.
OS command injection in the port_forward handler of the WAVLINK WL-WN530HG4B router's web management CGI (/cgi-bin/wapi.cgi) allows an attacker who can reach and authenticate to the device's administrative interface to run arbitrary shell commands on the firmware by placing shell metacharacters in the Name argument of a port-forwarding configuration request. The issue affects firmware build M_V260724 and carries a CVSS 4.0 base score of 8.6, with high confidentiality, integrity and availability impact; the assessed vector (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms the PR:L prerequisite, meaning the practical bar is authenticated access to the management UI rather than a fully unauthenticated internet-wide attack. A public PoC reference has been published in a GitHub write-up, but it is not verified as working exploit code, and no CISA KEV listing or EPSS score is available at time of analysis.
OS command injection (CWE-78) in the WAVLINK WN579X3-D wireless router (reported at firmware V250402) lets an attacker who can reach the web management interface execute arbitrary shell commands on the device by supplying a crafted 'Name' argument to the port_forward function of /cgi-bin/wapi.cgi. The vendor's CVSS 4.0 vector scores this 8.6 (AV:N/AC:L/AT:N/PR:L/UI:N with high confidentiality, integrity and availability impact), and the parallel assessment confirms remote reachability with low attack complexity but requires a low-privilege authenticated session on the management interface, so this is not a fully unauthenticated attack; exposure rises sharply where the admin interface is reachable from the WAN or default/weak credentials remain in place. A public PoC reference exists (a GitHub write-up linked from the VulDB entry) but has not been verified as working exploit code, and no confirmed active exploitation (CISA KEV) has been reported. Successful exploitation gives full control of the device's configuration and the traffic it forwards.
OS command injection in WAVLINK WN553X1-B firmware V260403_2.0.0 lets a remote attacker with a low-privilege authenticated session execute arbitrary commands through the group_id and group_name arguments processed by sub_416D88 in /bin/ioos. The issue is CWE-78 and carries a CVSS 4.0 score of 8.6; exploitation requires reachability to the device's ioos Service, which is typically LAN-side or an exposed management interface rather than the open internet by default. A public PoC reference exists; it is not verified as working exploit code, and the supplied intelligence does not confirm active exploitation.
Improper authorization in Oray Pugongying X5 Pro routers (up to and including 7.6.1) lets an authenticated but low-privilege 'restricted' account reach privileged API functionality through the run_apis_by_json/run_async_task JSON batch dispatcher, and the public write-up demonstrates a restricted account invoking a factory reset. Exploitation requires valid restricted credentials plus network reachability to the device's API Authorization interface, with no user interaction needed, and results in high confidentiality, integrity and availability impact (VulDB CVSS 4.0 score 8.6; our CVSS 3.1 assessment is 8.8). No vendor patch is available since Oray did not respond to the disclosure; a public proof-of-concept reference exists but is not verified as working exploit code, there is no CISA KEV entry confirming active exploitation, and no EPSS score was supplied, with prioritization set to 'this week'.
Relative path traversal in the configuration-restore routine (config_restore_ex) of Oray Pugongying X5 Pro firmware up to 7.6.1 allows an authenticated router administrator to supply a crafted filename argument that escapes the intended restore directory; the public write-up links this traversal to root code execution on the device. Exploitation is remote but gated behind the operator/admin-level configuration-restore feature (PR:H in both the CVE and the assessed CVSS 3.1 vector), so a valid admin session or credentials are required first, and no user interaction is needed. A public PoC reference exists; it is not verified as working exploit code, no CISA KEV entry is present, and the vendor did not respond to the disclosure, so no vendor patch or advisory is available. Priority is this_week rather than immediate action: genuine but conditional risk confined to vulnerable firmware on an admin-gated endpoint.
Unauthenticated denial of service against Ruijie RG-ES205GC, RG-ES206GC-P, RG-ES208GC, RG-ES210GC-LP and RG-ES210GS-P Ethernet switches running firmware ESW_1.0(1)B1P48: anyone who can reach the Local Firmware Upgrade web interface can drive a buffer overflow through the httpupg.cgi endpoint and crash the device. The confirmed impact is availability only (VC:N/VI:N/VA:H) - reboot, lockup or loss of management access - with no demonstrated code execution or data compromise despite the CWE-120 overflow class. No vendor fix has been published (Ruijie did not respond to the disclosure), and a public PoC reference exists but is not verified as working exploit code, so priority is set to this_week rather than emergency.
Stored cross-site scripting in the Media Library Assistant WordPress plugin before 3.44 lets an authenticated user with at least the Contributor role place script in an unescaped shortcode attribute, which is then emitted inside a generated link and runs when a victim views the page. The practical bar is a low-trust account plus victim interaction, with the most useful target being a higher-privileged viewer; sites that do not grant Contributor-or-higher access to untrusted users are not practically exposed. No active exploitation is confirmed (SSVC exploitation: none), EPSS is 0.15% (4th percentile), and a public PoC reference exists but is not verified as working exploit code; the vendor has released 3.44 as the fixed version.
The Generative UI sandbox in prefab-ui 0.14.0 through 0.20.2 does not actually isolate caller-supplied Python: the Deno subprocess is launched with unrestricted --allow-read, --allow-write and --allow-net, and Pyodide's js module exposes the Deno global to sandboxed Python, so code can call Deno.readTextFileSync and Deno.writeTextFileSync as the server OS user, and can persist execution by writing a .pth file into the server virtualenv's site-packages. The documented remote path is FastMCP's GenerativeUI provider, which registers the MCP tool generate_prefab_ui and forwards that tool's code argument into this sandbox; on a FastMCP server with no authentication configured, any client that can reach the server can invoke it (CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, 10.0). Exposure is narrowed by the feature being opt-in and requiring Deno on the host, but the dedicated advisory, an act_now decision label and a vendor-released fix in 0.21.0 make this a high-priority item; no public exploit was identified at time of analysis.
Path traversal in the Beta9 gateway and worker lets a tenant holding a valid workspace token deploy a function, endpoint, or task queue with a volume identifier containing '..' segments, collapsing the gateway-built host path to the worker's filesystem root and bind-mounting it read-write into the sandbox. This allows an authenticated attacker to read and write the worker's files, including other tenants' volumes colocated on the same machine; CVSS 3.1 is 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) with scope change. Gateway 0.1.769 and worker 0.1.745 are confirmed vulnerable, with fixes released in gateway 0.1.776 and worker 0.1.756; no public exploit code was identified at time of analysis, but the vendor-supplied patch details are public and the priority label is act_now.
Sandbox file API path traversal in Beta9 worker before 0.1.756 lets a tenant holding a valid workspace token and one running sandbox read, write, list and delete arbitrary files on the hosting worker as root, including files belonging to other tenants on the same machine. The reporter's read-only proof pulled the worker pod's Kubernetes service account token through the file API via a path that did not exist inside the sandbox, and because the shipped remote-node manifests bind that service account to cluster-admin, host file access escalates to full cluster compromise, which is why the scope-changed CVSS score reaches 9.9. A proof-of-concept read is described by the reporter; no public exploit code is otherwise confirmed, the issue is not in CISA KEV, and the vendor has released a fix in worker 0.1.756. This is a genuine top-priority issue, not an inflated high-CVSS score.
Beta9 worker images before 0.1.756 execute every Buildah RUN step from a tenant-supplied image definition with chroot-only isolation, so a build submitted with an ordinary workspace token runs as uid 0 inside the worker pod's PID, network, IPC and user namespaces while retaining CAP_DAC_OVERRIDE. Because /proc/1/root resolves to the worker container's writable filesystem, that tenant build can reach the runc, buildah and runsc binaries the worker uses to launch other tenants' containers, the worker's Kubernetes service account token, and host directories mounted into the privileged pod, giving scope-changed confidentiality, integrity and availability impact (CVSS 9.9, S:C). The reporter documented a read-only proof confirming the shared namespaces and the worker's runc binary at /proc/1/root; no public exploit code is confirmed, and the vendor shipped the fix in worker 0.1.756.
Presenton's Electron desktop build, in versions up to and including 0.9.11-beta, exposes private application files through its internal HTTP services because those services run with authentication disabled and without a per-launch credential, letting a client that can reach them read configuration, database, log and export-task data under /app_data. Only the desktop (PRESENTON_ELECTRON=true) deployment mode is affected, and because the Next.js/FastAPI servers are loopback/internal services, practical reachability likely depends on a co-located local client or a browser-based cross-origin/cross-port path rather than arbitrary internet access; the impact is confidentiality-only and limited. A public PoC reference exists; it is not verified as working exploit code, and there is no confirmed active exploitation (CISA KEV). Vuln.today priority places this in the current monthly remediation cycle rather than an emergency response.
Cross-origin information disclosure in the ag-ui TypeScript client: HttpAgent builds the POST run request with the conversation payload and the developer's Authorization/Bearer headers, and in versions up to and including 0.0.58 it left fetch's redirect policy at its default, so a redirect served by the configured endpoint (or injected by a man-in-the-middle on that path) causes that request to be re-issued at another origin, leaking its contents. Exploitation therefore requires control of the upstream endpoint or the network path, not merely the ability to reach a well-behaved TLS endpoint; the CVSS 4.0 vector scores it 6.9 with PR:N, VC:L, and E:P. A public PoC reference exists (issue #2520); it is not verified as working exploit code, and there is no CISA KEV listing. The upstream fix is PR #2575, which pins redirect to "error".
Unauthenticated SQL injection in the BookIt WordPress plugin through 2.6.0.6 allows remote attackers to read data from an affected site's database, based on the assessed high confidentiality-only impact. Exploitation requires only network access to a WordPress installation with BookIt active, with no authentication or user interaction per the assessed vector, so exposure is limited to sites that have not updated past 2.6.0.6. No public exploit identified at time of analysis and no CISA KEV entry is present in the provided data, but the vuln.today decision label is act_now, so affected sites should be prioritized for remediation.
Unauthenticated information disclosure in the MapPress WordPress plugin before 2.97.15 allows any remote visitor to enumerate user IDs through the front-end map embed handler and retrieve each matching user's email address and display name. Because the handler does not restrict whose data it renders, exploitation needs no authentication, interaction, or unusual configuration - only a vulnerable version serving map embeds publicly, which is the plugin's normal function. Impact is limited to PII exposure (C:L/I:N/A:N, CVSS 5.3); no public working exploit code has been confirmed (a WPScan reference is available, not verified as working exploit code), EPSS is low at 0.14% (3rd percentile), CISA SSVC records no exploitation, and a vendor patch is available.
Memory corruption in the shield.sys kernel driver of Horizon DataSys Reboot Restore Standard (versions up to and including 13.2) allows a local user with only low-level privileges to corrupt kernel memory through the sub_23908 function, with high impact on confidentiality, integrity and availability. The attack is not remote and requires an existing foothold on a Windows host with the product installed, but no user interaction; successful abuse in the kernel context would potentially allow elevation to higher privileges. The CVE record states that exploit code is publicly available (a public gist is referenced), so local attackers who already hold a low-privileged account should be treated as capable of reproducing it; no CISA KEV entry confirms active exploitation.
Email address disclosure in Kali Forms versions before 2.4.30 allows authenticated Subscriber-level users to retrieve the email address of any registered user, including administrators, through the plugin's test-email handler. The handler lacks a capability check and relies only on a nonce available to any logged-in user, so minimal privileges are sufficient; exploitation requires a valid low-privilege account, which is most practical on sites allowing open registration. The issue is low-to-moderate severity (CVSS 4.3) with low EPSS (0.14%), no KEV active-exploitation report, and a public PoC reference that is not verified as working exploit code; a vendor patch is available in 2.4.30 and the priority label is this_month.
An information disclosure flaw in the WordPress plugin Media Library Assistant before version 3.44 lets any authenticated user, including a low-privilege subscriber, retrieve which taxonomy terms are assigned to private attachments and posts they are not permitted to view. The plugin omits the capability check before returning term assignments, so a valid session is all an attacker needs; only term metadata - not post content or media files - is exposed, which bounds the impact to limited confidentiality loss (CVSS 4.3). No active exploitation is known (not in CISA KEV, SSVC exploitation: none, EPSS ~0.13%) and only a reference-level PoC pointer exists, not verified working exploit code.
Kali Forms versions before 2.4.30 expose its test-email handler to any authenticated user, allowing a Subscriber-level account to make the site send email to an arbitrary recipient with a spoofed sender address. The flaw is a missing capability check (CWE-862) reachable by authenticated low-privileged users and does not provide server compromise. Vendor patch 2.4.30 is available, EPSS is 0.13%, and a public PoC reference exists; it is not verified as working exploit code.
Apache Wicket's form-less upload endpoint (AbstractFileUploadResource, the server side of FileUploadToResourceField, or a manually mounted FileUploadResourceReference) takes its upload bounds from client-supplied request parameters - maxSize, fileMaxSize and fileCountMax - instead of from the values the application configured via setMaxSize(), setFileMaxSize() and setFileCountMax(). A client that supplies a very large maxSize, or omits the per-part and part-count parameters, can therefore drive one repeatable request to spool unlimited data to disk or read non-file parts into the heap, exhausting disk or memory. Affected releases are 9.14.0 through 9.24.0 and 10.0.0 through 10.9.1; the 8.x line has no such resource, and the ordinary Form/FileUploadField and AjaxFileDropBehavior paths are unaffected because they read limits from the component. Rated CVSS 4.0 8.3 (with attack requirements present, AT:P, since the application must deliberately use or mount this resource) and rated 'this_week' by priority; no public exploit code was identified at time of analysis.
Heap-exhaustion denial of service in Apache Wicket 9.14.0 through 9.24.0 and 10.0.0 through 10.11.0, reachable without authentication (CVSS 4.0 PR:N) by any client that can load a page rendering the FileUploadToResourceField callback URL. The Ajax callback trusts the client-supplied filesInfo JSON without binding it to a real upload, and UploadInfo#get() allocates a byte array sized from the attacker-controlled UploadInfo#getSize() before opening any file, so a single small request can cost close to two gigabytes of heap and repeated requests exhaust the JVM heap for all requests; a size that converts to a negative int instead throws an uncaught NegativeArraySizeException into the application. Exploitation is narrowly scoped: the application must deliberately extend and mount this component (not the ordinary FileUploadField/Form path) and must call UploadInfo#get(); no public exploit code or active exploitation was identified at time of analysis, and the priority label is this_week.
Cross-site scripting in Apache Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0 and 10.0.0 through 10.11.0 allows text read from the application's resource bundles to escape the single-quoted JavaScript string literals and quoted HTML attribute values the framework generates, so a quote in that text ends the literal or attribute and what follows is parsed as script or markup in the application's origin when the page loads. Only bundle-sourced values rendered by specific components are affected - the org.apache.wicket.mfu.delete message in MultiFileUploadField, the hidden-fields CSS class in Form (and in Form#appendDefaultButtonField on the 8.x and 9.x ranges) and FilterForm, the UploadProgressBar.starting text, and TrapFocusBehavior's current CSS class on 9.0.0-9.24.0 and 10.0.0-10.11.0 - so exploitation depends on a non-default situation in which a bundle entry is influenced by another party, although an ordinary apostrophe in a legitimate translation is enough to break page rendering. The unauthenticated network vector requires the victim to load the generated page; no public exploit identified at time of analysis, and the default Content-Security-Policy in Wicket 9.x and 10.x blocks the attribute-injection cases but not the JavaScript string-literal cases because the generated script carries the per-response nonce the policy trusts.
Cross-site scripting in Apache Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0 and 10.0.0 through 10.11.0 lets a value that the application places into a component markup id or a component id break out of a single-quoted JavaScript string literal that Wicket itself generates, so the injected script executes in the application's origin when the page loads. Exploitation is conditional: Wicket never generates a quote or backslash in these identifiers, so the tainted value must originate from application data flow (a value passed to Component#setMarkupId, an id attribute in a template, or a component id derived from data), and a victim must load the affected rendered page; the supplied independent assessment scores this as CVSS 3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N, i.e. a genuine but conditional flaw rather than a trivially reachable one. No KEV listing is present and no public exploit code is identified in the available intelligence; the vendor's own advisory carries a CVSS 4.0 score of 7.6 and a this_week remediation priority.
Stored cross-site scripting in Apache Wicket's AjaxNewWindowNotifyingBehavior allows a client-supplied browser window name to be persisted in a page instance's serialized state and later emitted as raw, unescaped JavaScript, executing in the application's origin each time that page instance is rendered. Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0 and 10.0.0 through 10.11.0 are affected, but only applications that explicitly added the behaviour to a component are exposed, since the framework never installs it; the vector is unauthenticated (PR:N) yet requires victim interaction and specific attack prerequisites, so real-world priority is moderate rather than urgent. No public exploit identified at time of analysis, and the vendor has released fixes in 8.20.0, 9.25.0 and 10.12.0.
Cross-site scripting in Apache Wicket 8.0.0 through 8.19.0 lets remote attackers get script executed in the application's origin when an ExternalLink component is bound to a markup tag that is not an a, link or area element (such as a button or span) and the URL held in the component's model contains attacker-influenceable data, which the vendor describes as the component's ordinary use rather than a misuse. The URL is concatenated unescaped into a single-quoted JavaScript string inside the generated onclick handler, and also into the window.open() call built by PopupSettings when popup settings are attached; only attribute-level markup escaping is applied, and the browser decodes the apostrophe character reference before compiling the handler, restoring the quote and closing the literal. Exploitation is unauthenticated and remote but conditional: nothing executes until a user activates the affected element, and the deployment must bind the component to a non-anchor tag, which the Apache reporter scores as CVSS 4.0 7.4 (AT:P, UI:A); no public exploit identified at time of analysis.
Apache Wicket's public JavaScriptUtils.escapeQuotes() helper fails to escape backslashes before quotes, so attacker-influenced data containing a backslash immediately before a quote can terminate a JavaScript string literal and run script in the application's origin and the viewing user's session. The flaw affects Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0 and 10.0.0 through 10.11.0, but exploitation is conditional: an application must itself place the method's output inside a JavaScript string literal, and the bundled AjaxEditableLabel path additionally requires a custom validation message that interpolates submitted input or another attacker-controlled variable. No public exploit was identified at time of analysis, and the issue requires user interaction because the victim must view the page that renders the vulnerable response.
Cross-site scripting in Apache Wicket's SmartLinkLabel and SmartLinkMultiLineLabel components turns attacker-influenced text into anchors whose href is copied verbatim, so a value naming a script-executing scheme becomes a clickable script link in the application's origin and the reader's session. Affected are Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0 and 10.0.0 through 10.11.0, but only applications that render untrusted text through one of those two components; no other component uses DefaultLinkParser. Exploitation is not a drive-by: the reader must click the injected link, and on 9.x and 10.x the default nonce-based Content-Security-Policy blocks the script unless the deployment has weakened or disabled it, while 8.x has no CSP support and is exposed as it stands. No public exploit code was identified at time of analysis; fixed releases are 8.20.0, 9.25.0 and 10.12.0.
Session fixation in Apache Wicket's role-based authentication module leaves the container session id unchanged when an already-signed-in session authenticates a second time, so an attacker-planted session id can survive a successful login. Affected releases are 8.18.0 through 8.19.0, 9.23.0 through 9.24.0 and 10.9.0 through 10.11.0, and exploitation requires an application that authenticates via AuthenticatedWebSession, permits re-authentication of a signed-in session (step-up prompt, account switch, or a sign-in form still reachable after login), and an attacker who can plant a session id in the victim's browser and has already authenticated that session with a valid account (PR:L, UI:A). Successful exploitation yields high confidentiality and integrity impact within the vulnerable application; the vendor-released fix is available in 8.20.0, 9.25.0 and 10.12.0, and no public exploit has been identified at time of analysis. The CVSS 4.0 base score is 7.2 (High), though the vector is tempered by AT:P (an attack requirement outside the attacker's control) alongside PR:L and UI:A.
Stored cross-site scripting in the Nickboss WordPress File Upload plugin, versions up to and including 5.2.1, allows an attacker to persist script that executes in a victim's browser when the victim loads the affected page. The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, giving a base score of 7.1; the UI:R component means a user must load the page containing the stored payload for execution to occur. The CVSS vector lists no privileges required (PR:N), though the description does not state the required access level, so the unauthenticated nature should be verified with the vendor or Patchstack. No public exploit code or active exploitation is identified in the available sources at time of analysis, and no EPSS score was supplied.
The Thelia back-office Twig template bundle (thelia/backoffice-default-twig-template) before 1.1.1 exposes two admin catalogue routes - /admin/product/combinations/update and /admin/product/default-price/update - that accept GET requests and perform no anti-CSRF token validation, even though the legitimate form already emits a token in its action URL and the fix later moves it into a hidden field that is actually checked. An attacker who lures a logged-in administrator into a top-level navigation (a clicked link or a meta-refresh/location redirect) can rewrite product combination price, sale price, weight, stock, EAN and onsale/isnew flags across many SKUs in a single request, and price fields omitted from the payload are written as zero, turning items into free products. The attacker needs no account or credentials, but exploitation is bounded by mandatory administrator interaction and by the SameSite=Lax session cookie, which permits top-level GET navigations while refusing subresource requests such as an <img src> or prefetcher hits that arrive without the session; the vendor advisory publishes step-by-step reproduction requests, and a public PoC reference therefore exists, though it is not verified as packaged working exploit code. No CISA KEV entry is recorded and the vuln.today priority label is this_month, consistent with a genuine but moderate integrity-only issue rather than an emergency.
Missing authorization in Apache Wicket 8.x, 9.x and 10.x allows unauthenticated remote attackers to invoke a component's IRequestListener even though the application's IAuthorizationStrategy denied the Component.RENDER action for that component, or even though the application set the component invisible or disabled in Component#onConfigure(). The flaw is reachable with nothing more than a crafted or simply unmodified request, because Wicket can build a listener URL without a page identifier and then invokes the listener on a freshly constructed page instance before any render pass has populated the authorization-derived visibility flag; the impact is limited to integrity (low), with no confidentiality or availability effect assessed. Exploitation requires a Wicket application that withholds an individual component via a RENDER denial or via visibility/enablement set in onConfigure(), on a page that is reachable from a bookmarkable or mounted URL and has a public no-argument or PageParameters constructor; signals are moderate and broadly consistent, and no public exploit identified at time of analysis.
Missing authorization in Apache Wicket 10.3.0 through 10.11.0 allows a remote unauthenticated caller to invoke the server-side callbacks of a form submit control that the application deliberately withheld from them, because Form#findSubmitter() resolves the submitter from the request parameter name alone and the visible/enabled check runs only when no submitter is supplied. Where a Button or SubmitLink is hidden, disabled, or denied by IAuthorizationStrategy while the enclosing form stays available, a request naming that control still reaches its onSubmit() and onAfterSubmit(), and its onError() when validation fails - reaching onSubmit()/onAfterSubmit() with no validation at all when the button sets setDefaultFormProcessing(false). No public exploit code has been identified at time of analysis; Ajax submissions through AjaxFormSubmitBehavior, AjaxButton and AjaxSubmitLink are not affected, restrictions on the form or page are not bypassed, and the 9.x and 8.x lines are unaffected because the behaviour was introduced in 10.3.0.
Stack-based buffer overflow in imagecodecs (versions 2023.1.23 through 2026.10.10) is reachable through the lossless JPEG path, where decode_jpegsof3() parses a Define Huffman Table whose symbol counts wrap an 8-bit accumulator and overrun the fixed 32-entry HufVal and HufSz stack arrays. An attacker who can get a crafted JPEG SOF3 file decoded by the library - locally, with the victim or a service performing the decode - crashes the calling process; per the assessed CVSS:3.1 vector (AV:L/AC:L/PR:N/UI:R, C:N/I:N/A:H) impact is limited to availability, with no confidentiality or integrity effect. The issue is a medium-severity denial of service rather than a high-priority emergency: only the lossless-JPEG decode code path is affected, the attack is not remotely self-triggering, and no public exploit code has been identified at time of analysis.
Crafted CCITT Group 4 image data can hang processes that use imagecodecs 2026.3.6 through 2026.10.10: a stream missing the end-of-facsimile-block marker drives ccitt_fax4_decode_size() into an infinite loop, consuming full CPU until the process is terminated. The flaw is availability-only, with no confidentiality or integrity impact, and the supplied vector and independent assessment require a local decode path plus user interaction, so only deployments that decode untrusted G4 data are exposed. No public exploit was identified at time of analysis.
Heap memory disclosure in FFmpeg's Huffyuv decoder affects builds from 2.3 through 9.0.2: when a crafted Huffyuv (FFVHuff/HuffYUV) video in packed BGR24 or BGRA pixel format ends its entropy data early, decode_slice() adds uninitialized s->temp[0] bytes into the decoded frame, so heap contents are written into output pixels. The trigger is local with passive user interaction (CVSS:4.0/AV:L/UI:P, PR:N), and impact is confidentiality-only - no code execution, no crash, no integrity effect - and the attacker must be able to observe the decoded output to actually recover the leaked bytes. A vendor fix exists as an upstream PR/commit and the vuln.today decision label is this_month, indicating moderate rather than emergency priority; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Stack memory disclosure in FFmpeg 4.4 through 9.0.2 occurs in the niche CDXL decoder: when a crafted type-0 CDXL file is decoded in HAM6 or HAM8 mode, pixel values can index palette slots that import_palette() never populated, and those uninitialized stack bytes - including pointer fragments - are written into the BGR24 output frame. An attacker who can get a victim to open or process such a file, and who can observe the resulting decoded frames, may recover residual process memory; no authentication is required, but the assessed vector is local with passive user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), so impact is limited to confidentiality of data that is actually returned to the attacker. No public exploit code or CISA KEV entry is associated with this issue at time of analysis, and the vendor fix is upstreamed as a commit/PR rather than a confirmed tagged release.
FFmpeg 0.10 through 9.0.2 can leak heap memory when decoding a deliberately truncated 1-bit or 4-bit paletted Sun Raster (.ras/.sun) image. The bug is a use of uninitialized resource (CWE-908) in sunrast_decode_frame(): the temporary bitmap is never cleared, so when it is expanded into PAL8 pixels the decoded frame can contain stale heap bytes such as allocator words. Impact is confidentiality-only and requires the victim to process the crafted file and for the attacker to observe the decoded output; there is no public exploit identified at time of analysis, and the vendor has published upstream fix commits.
Heap memory disclosure in FFmpeg's PCX decoder affects versions 2.1 through 9.0.2: a crafted PCX image whose RLE-encoded scanline data terminates early causes pcx_decode_frame() to copy uninitialized av_malloc() buffer contents into the visible decoded pixels, leaking heap bytes to whoever receives the output image. Impact is confidentiality-only (no code execution, no write, no denial of service) and the assessed 3.1 vector is AV:L/AC:L/PR:N/UI:R, meaning the crafted file must reach a decode path - locally or through an automated service - before the leak occurs. No public exploit code and no confirmed active exploitation were identified at time of analysis; practical exposure is concentrated in media transcoders, thumbnail generators and upload-processing pipelines that automatically decode untrusted PCX input, and an upstream fix commit is available.