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.
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 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.
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.
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.
An information disclosure flaw in FFmpeg's Go2Meeting (G2M) decoder lets an attacker who supplies a crafted G2M3/G2M4 stream read uninitialized stack memory, because out-of-range Kempf palette indices cause kempf_restore_buf() to copy stale stack bytes - potentially pointers or stack guards - into the decoded frame. FFmpeg 2.0 through 9.0.2 are affected; exploitation requires the victim or an automated media pipeline to decode the crafted file and a way to observe the resulting decoded output, and it grants no integrity or availability impact. The upstream fix (commit edad2d0dafcf44fa315eab716fd0183ce808053b, PR 24858) adds a col >= npal bounds check; no public exploit code has been identified at time of analysis and CVE-2026-120243 is not in CISA KEV.
Authenticated users with low privileges on WordPress sites running the Crocoblock JetFormBuilder plugin through 3.6.7.1 can exploit a path traversal flaw to delete files outside the intended directory, degrading availability (CVSS 6.5, availability-only impact). The issue is network-reachable with low complexity and no user interaction, but it requires a logged-in account (PR:L), so sites that allow open or low-barrier registration carry the highest practical exposure. No public exploit code or CISA KEV entry is associated with this CVE in the available data, and the exact vulnerable endpoint or path parameter is not identified in the sources; the priority label assigned is 'this_month'.
Apache Wicket 8.x through 10.x can be made to return the HTML markup template of an application's own component class instead of the static file that the package resource guard approved, giving a remote unauthenticated attacker read access to developer-authored template source. Exposure is conditional: the application must contain a component class whose simple name includes an underscore and for which no shorter underscore-delimited prefix is itself a class (for example Report_v2 or Wizard_Step1), and disclosure is confined to HTML files in that component's own package - component structure, developer comments, conditional markup, inline script and named endpoints, but no user data, credentials or session material. No public exploit code is identified at time of analysis, and the vendor has released fixed versions 8.20.0, 9.25.0 and 10.12.0.
Markup template disclosure in Apache Wicket 8.0.0-8.19.0, 9.0.0-9.24.0 and 10.0.0-10.11.0 allows unauthenticated remote attackers to fetch a component's HTML markup template over HTTP with status 200 by requesting its package-resource URL. The flaw only manifests in non-standard deployments where wicket-core is loaded by a class loader that cannot see the application's component classes (shared servlet-container library directory, EAR lib directory with the WAR-hosted application, application-server global module, or OSGi bundle); the ordinary WAR layout with wicket-core in WEB-INF/lib is not affected. Impact is strictly read-only disclosure of developer-authored template content - component structure, comments, conditionally rendered markup, inline script and named endpoints - with no user data, credentials or session material reachable and no integrity or availability effect; no public exploit code was identified at time of analysis and there is no CISA KEV listing, and the priority signal is this_month rather than immediate action.
Apache Wicket's resource authorization check is bypassed when a restricted resource is served through a component that was constructed with an IResource instance instead of a ResourceReference. The framework enforces IAuthorizationStrategy#isResourceAuthorized() and the wicket-auth-roles @AuthorizeResource annotation at only one point - ResourceRequestHandler - so ResourceLink(String, IResource), Image, ImageButton and AjaxDownloadBehavior call IResource#respond() directly from their own request listener and never consult the strategy; for Image and ImageButton the listener URL is written into the tag's src attribute, so a browser fetches the protected content with no user action. Affected versions are 8.0.0 through 8.19.0, 9.0.0 through 9.24.0 and 10.0.0 through 10.11.0; only applications that actually restrict a resource and then hand that same instance to one of these components are exposed, and ExportToolbar in wicket-extensions triggers the pattern for data-table exports. No public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS data was not provided; severity is rated medium (vendor CVSS 4.0 base 6.3).
Missing authorization in Apache Wicket's native WebSocket transport allows a remote caller who holds a bound Wicket session to invoke the callbacks of a registered `WebSocketResource` shared resource without the application's `IAuthorizationStrategy` ever being consulted, so class-level restrictions such as `@AuthorizeResource` are silently ignored. The flaw is unauthenticated per the CVSS vector (PR:N) and affects Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, 10.0.0 through 10.11.0, and older unsupported 7.x releases, but only where an application registers a `WebSocketResource` as a shared resource and relies on the authorization strategy to protect it. Impact is bounded to whatever the targeted resource's `onConnect()` and `onMessage()` callbacks do with an attacker-supplied text or binary message, and because the connection registers under the caller's own session there is no path to another user's connection; no public exploit code has been identified at time of analysis, and the vendor has released fixed versions 8.20.0, 9.25.0 and 10.12.0.
OpenAlgo 1.0.0.29 up to but excluding 2.0.3.1 ships SMTP client code that switches off TLS certificate and hostname verification, so a network-positioned attacker who can intercept the path between OpenAlgo and its configured mail server can present a forged certificate, terminate the TLS session, and read the SMTP username and password along with every subsequent message - including password-reset links. The weakness is in the shipped code itself (utils/email_utils.py and utils/email_debug.py) and applies to both STARTTLS and implicit SMTPS paths, so any affected instance that sends mail is exposed without special configuration. Exploitation still requires the attacker to hold an active man-in-the-middle position (AV:A, AC:H, AT:P), which is the main limiter; no public exploit has been identified at time of analysis and no active exploitation is confirmed, making this a medium-severity confidentiality issue suited to scheduled, this-month remediation rather than emergency response.
Presenton 0.9.11-beta and earlier ship an Electron desktop build whose local Next.js and FastAPI HTTP servers accept requests without authentication, allowing anonymous clients that can reach those loopback services to use internal REST, export and local-file-read functionality and to read files the app can access. Exploitation is narrowed by the loopback binding: a genuinely remote attacker needs local access to the host or must induce a victim's browser to issue cross-port or DNS-rebinding requests to localhost, so the assessed CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N yielding low confidentiality, integrity and availability impact. The CVSS 4.0 vector supplied by the CNA rates exploitation maturity as proof-of-concept (E:P) and the CVE text asserts that exploit code has been made public; that claim is not independently verified here, no CISA KEV entry is associated, and the vendor resolves the issue in 0.9.12-beta.
Code injection in the Groovy Script Executor component of beecue FastBee up to and including 2.1.0 lets a remote attacker who holds a high-privilege account submit crafted script content through /iot/script and have it executed by the platform, producing limited confidentiality, integrity and availability impact. The CVSS 4.0 base score is 5.1, and the CVSS 3.1 assessment places it at PR:H, so exploitation is confined to authorized operators or attackers who have already obtained privileged credentials. A vendor fix is available as the Gitee commit 890a33846005a937a58cccd738b7fb9821b82ea9; no public exploit code and no confirmed active exploitation are identified at time of analysis.
OS command injection in Minimax Code 0.5.8 lets an attacker who controls the -exec argument of the Find Command Handler inject and execute operating-system commands. Exploitation requires a valid low-privilege account (PR:L) plus passive user interaction (UI:P), and only version 0.5.8 is identified as affected; the vector's low confidentiality, integrity and availability ratings indicate command execution in a constrained context rather than full host takeover. No public exploit code has been identified at time of analysis, the vendor was contacted but did not respond, and this is tracked as a medium-severity, this-month priority item rather than an emergency.
Stored cross-site scripting in Thelia's back-office store configuration lets an authenticated administrator holding store update permission upload SVG logo or banner images whose event handlers and script content are stored intact, creating a persistent script implant on the shop origin. The same bytes execute against higher-privileged administrators at /admin/store-media/logo and against anonymous visitors, crawlers and link-preview fetchers via the image cache copy mirrored into the document root and advertised in every front-office page's og:image meta. The vendor fixed the flaw in Thelia 3.1.1 and back-office default-twig template 1.1.1, and the GitHub advisory carries a step-by-step PoC walkthrough, so a public PoC reference exists; it is not verified as working exploit code, and the issue is not confirmed actively exploited (CISA KEV).