Unauthenticated attackers can delete arbitrary files stored under the user/data/ directory in installations of the Grav Data Manager plugin versions 1.4.0 through 1.4.5 when the classic Admin integration is active. The vulnerability arises from missing authorization checks and absent CSRF nonce validation, enabling requests with a delete parameter and a known data type/filename to remove files such as form submissions. This moderate-severity flaw (CVSS 4.0 base score 6.9; CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L) has no public exploit identified at time of analysis, and exploitation is limited to integrity and availability impacts on existing data files.
Blind server-side request forgery in Crawl4AI before 0.9.4 lets unauthenticated remote attackers bypass Docker egress controls via the RobotsParser.can_fetch robots.txt fetch path, using HTTP redirects or DNS rebinding to reach loopback, internal, and cloud-metadata addresses for service discovery. Rated CVSS 4.0 6.9 (Medium), exploitation requires the check_robots_txt behavior to be in effect when the service processes an attacker-influenced target URL, which makes the Docker service being reachable by untrusted callers a precondition. The SSRF is blind, so responses are not returned to the attacker, keeping confidentiality impact low; no public exploit code or confirmed active exploitation was identified at time of analysis.
Grav Star Ratings plugin versions 2.0.1 through 2.0.3 allow unauthenticated visitors to submit votes on restricted or disabled ratings because the vote_access and readonly restrictions are enforced only in client-side code. Attackers can obtain the anonymous nonce that getData() already emits publicly and call addVote() directly, manipulating rating aggregates; the confirmed impact is limited to data integrity with no confidentiality or availability loss. No public exploit code or active exploitation is identified at time of analysis.
A heap out-of-bounds read in FreeRDP's WinPR clipboard function convert_filedescriptors_to_file_list() allows a malicious RDP server to crash X11, Wayland, and SDL clients when an unauthenticated remote attacker sends an odd-length FILEDESCRIPTORW blob in a CB_FORMAT_DATA_RESPONSE and the victim pastes server-copied files. This medium-severity, availability-only vulnerability affects FreeRDP 3.0.0 through 3.31.x; exploitation requires the victim to initiate an RDP connection to an attacker-controlled server, have clipboard file redirection enabled, and actively paste the copied files. No public exploit identified at time of analysis; the vendor has released a patch in version 3.32.0.
Username enumeration in LogicalDOC Community Edition through 9.3 allows remote unauthenticated attackers to determine which accounts exist and to retrieve their profile pictures by requesting the /avatar endpoint with candidate usernames or numeric IDs. The AvatarServlet performed no session validation, so the only prerequisite is network reachability of the endpoint; identification relies on distinguishing a generic 1x1 transparent image returned for unknown identifiers from a real avatar returned for valid accounts. The disclosure is limited to account existence and profile imagery (confidentiality-low, no authentication, credentials, or write access granted), making this a low-to-moderate priority issue rather than a critical one; no public exploit code was identified at time of analysis and the issue is not known to be actively exploited.
Disabled Frappe Framework user accounts can continue receiving Document Follow email notifications in versions before 15.118.0 and 16.x before 16.31.0, disclosing document activity to users whose access should have been revoked. Exploitation requires that the affected account previously followed one or more documents while active and was later disabled rather than deleted; it does not grant new document access or enable arbitrary external attackers to access documents. The independent assessment rates this as a missing-authorization information-disclosure flaw with low confidentiality impact (CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:N/C:L/I:N/A:N); no public exploit identified at time of analysis.
Unauthenticated peers can evade ban enforcement in Zcash Zebra versions 2.3.0 through 6.3.x because the node keys ban decisions and misbehavior scores to exact IP addresses rather than network prefixes. An attacker controlling an IPv6 /64 allocation can rotate source addresses to sidestep bans, or can flood the 20,000-entry FIFO ban list to evict legitimate entries and restore access for previously banned peers. This is a moderate-severity protection-mechanism failure (CWE-693) with integrity-only impact - it does not grant code execution, data access, or node shutdown - and no public exploit identified at time of analysis.
Integrity-check bypass in the Hex package manager (hexpm hex) allows a compromised or attacker-controlled package mirror to substitute package contents when a developer runs `mix hex.package fetch PACKAGE VERSION --output -` and pipes standard output into an unpacker. The stdout code path writes the raw bytes returned by Hex.SCM.fetch/3 without the inner/outer checksum comparison that the default file-output path performs against the signed registry, and Hex's own diagnostics (a failed HTTP response body or an x-hex-message API warning) can likewise land on stdout as a tar archive ahead of any verified tarball. Hex versions from 0.20.2 up to but excluding 2.5.2 are affected; no public exploit code has been identified at time of analysis, and exploitation additionally requires a non-default mirror (HEX_MIRROR_URL or mirror_url) plus the specific stdout-piping command run by an unauthenticated remote attacker's victim, making this a genuine but conditionally gated supply-chain integrity flaw rather than a drop-everything emergency.
Out-of-bounds memory write in Samsung's HEIF decoder library (libsimba.heifdec.media.samsung.so) allows a local attacker to corrupt memory by supplying a crafted HEIF image to the cover-image decoding path. Only devices running builds prior to SMR Oct-2026 Release 1 are affected; the flaw is local (AV:L) but requires no privileges or user interaction once an app or process is present on the device, meaning a co-resident unprivileged application is sufficient. Impact is limited to integrity (no confidentiality or availability effect asserted), and no public exploit identified at time of analysis.
Local information disclosure in Samsung CmcCore allows a malicious or sideloaded application on a vulnerable handset to invoke privileged APIs because the component fails to enforce sufficient permission checks, exposing sensitive data with high confidentiality impact. Exploitation is strictly local-requiring code execution on the device-and affects firmware prior to SMR Oct-2026 Release 1; there is no remote vector and no integrity or availability impact. No public exploit identified at time of analysis, and CISA KEV does not list this CVE.
Local information disclosure in Samsung DownloadProvider allows an attacker-controlled Android application installed on a Samsung device to read files held in scoped storage that it should not be able to reach, yielding high confidentiality impact with only low integrity and availability impact. The flaw affects devices running firmware prior to the SMR Oct-2026 Release 1 maintenance release and requires no user interaction and no network access, because exploitation depends on a malicious app already running locally with low privileges. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited, making this a moderate-risk, local-only issue rather than a remotely triggerable emergency.
Samsung Account versions prior to 15.7.01.1 on Samsung Android devices expose an improperly exported application component that any other app installed on the same device can query to read sensitive account data. Exploitation requires a malicious or compromised local app already present on the device - there is no remote access, no user interaction, and no elevated privilege requirement per the CVSS vector (PR:N/UI:N) - making this a medium-severity local information-disclosure issue (CVSS 4.0 base 6.9). No public exploit code has been identified at time of analysis.
Physical access to a device running Samsung Smart Switch earlier than 3.7.73 allows an attacker to install arbitrary applications, because the tool does not adequately verify the authenticity of the data it transfers or restores. The assessed CVSS 3.1 vector (AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N, 6.9 Medium) confirms that no authentication or user interaction is required once the attacker has the device in hand, but the mandatory physical-access precondition rules out remote or large-scale exploitation and confines realistic exposure to unattended, lost, stolen, or supply-chain-handled devices. There is no public exploit identified at time of analysis, and the condition is removed by updating Smart Switch to 3.7.73 or later.
SQL injection in Frappe ERPNext (before 15.121.0 and 16.x before 16.34.0) allows an authenticated user holding high privileges to send specially crafted requests to endpoints that lack input validation, injecting SQL that lets them read sensitive information from the underlying database. Per the assessed vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, only confidentiality is affected - data can be read but not modified or destroyed - and the attacker must already hold an elevated/administrative account, which confines realistic risk to insiders or environments where a privileged account has been compromised. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, making this a genuine but moderate-priority issue rather than an emergency; vendor patches exist in 15.121.0 and 16.34.0.
Authentication bypass in Keycloak's Client-Initiated Backchannel Authentication (CIBA) implementation allows public clients without a client secret to initiate backchannel login requests, enabling an attacker to trick a user into approving a malicious login and gain full access to the user's account. The flaw stems from Keycloak failing to verify that a client is authorized to use the CIBA flow, and exploitation requires the CIBA grant to be enabled, high attack complexity, and active user interaction to approve the request. No public exploit identified at time of analysis; the assessed CVSS is 6.8 (medium).
Improper authorization in Samsung Smart Switch before version 3.7.73 lets an attacker with physical possession of a device invoke the application restore process without the expected authorization check, giving high confidentiality and integrity impact (CVSS 4.0 base 6.8). Exploitation is strictly gated by physical access (AV:P) with no user interaction or privileges required, so realistic exposure is limited to lost, stolen, unattended, or in-service devices rather than remote or opportunistic network attack. No public exploit code was identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV); the vendor has published a fixed version, 3.7.73.
A heap out-of-bounds read in FreeRDP's Remote Assistance invitation parsing (freerdp_assistance_parse_all_elements_of() in libfreerdp/common/assistance.c) crashes the xfreerdp client when it opens a crafted .msrcIncident file, and it occurs while decrypting and parsing the embedded ConnectionString2 blob, before any RDP session is negotiated. Affected builds are FreeRDP 3.0.0 through versions before 3.32.0, and the CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P, VA:H) reflects an unauthenticated local file-parsing attack that nevertheless requires the victim to be socially engineered into opening an attacker-supplied invitation plus its accompanying password. Impact is limited to a client-side denial of service; no confidentiality or integrity loss is scored, and no public exploit code or CISA KEV entry was identified at time of analysis. A vendor patch restoring the remaining-length accounting is available in the 3.32.0 release.
Insecure file permissions in FreeRDP's winpr-makecert certificate-generation utility (versions 2.0.0 through 3.31.x) cause newly generated private keys to be written without owner-only modes, so any local account on a multi-user Unix host can read them; exported PFX bundles are additionally protected only by the tool's hard-coded default password, so possession of the file is effectively equivalent to possession of the key. Exploitation requires an attacker who already holds a low-privileged local shell (PR:L) on a host where an administrator or user has actually run winpr-makecert, and it does not touch normal FreeRDP client or server RDP sessions that never invoke the tool - there is no public exploit code identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV). Impact is rated medium (CWE-732 permission assignment; CVSS 6.8 per the vendor scoring, with our independent assessment at CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N), because a stolen key enables credential-grade impersonation or decryption of RDP TLS traffic rather than a self-propagating compromise.
Local file disclosure in Hugo v0.162.0 through v0.166.x allows an attacker-controlled theme or module to place a symlink or NTFS junction at a virtual ancestor directory of a nested mount, causing resources.Match to list and publish files outside the theme/module root during a site build. Affected users must install and build with an untrusted third-party theme or module; exploitation is local to the build host and requires user interaction, with impact limited to disclosure of files readable by the build process. No public exploit identified at time of analysis; vendor-released patch is v0.167.0.
Path traversal in Hugo's asset pipeline lets a malicious theme or module bundle files from outside the project root into published JavaScript or CSS output, affecting Hugo from v0.84.0 up to (but not including) v0.167.0. Exploitation is build-time and supply-chain oriented: a maintainer must install the hostile component and run one of the affected functions (js.Build, js.Batch, or css.Build), and only files readable by the build user can be exfiltrated - there is no remote, unauthenticated exposure of an already-published site. The CVSS v4.0 vector is 6.7 with PR:N (no privileges required) but AV:L and UI:A, meaning local attacker access plus user interaction; no public exploit was identified at time of analysis and no KEV listing applies.
Path traversal in Hugo's css.Sass transpilation pipeline (all versions before v0.167.0) lets a malicious theme or module reference files outside the project root via relative, absolute, or symlinked @import/@use targets and have their contents compiled into the published site CSS. Exploitation is build-time rather than remote: a developer or CI job must voluntarily add the untrusted theme/module and run a build that uses css.Sass, and only files readable by the build process's user can be disclosed - a moderate information-disclosure risk rather than an urgent remote-execution priority. No public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); the vendor has released a fix in v0.167.0.
Local information disclosure in Samsung Locksettings (prior to SMR Oct-2026 Release 1) allows an attacker who already possesses root privilege on the device to read data belonging to a tied profile while the device is in the Before First Unlock (BFU) state. Exploitation is local-only (AV:L) and requires high privileges (PR:H), with no remote path; it does not enable privilege escalation, code execution, or data modification. No public exploit code exists, and the vulnerability is not listed in CISA KEV; EPSS data was not provided at time of analysis.
Denial of service in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 can be triggered by an authenticated user who holds INSERT privileges on a table containing one or more XML columns, potentially crashing or hanging the database instance under conditions IBM has not fully quantified. The flaw is classified as uncontrolled resource consumption (CWE-770) and carries a CVSS 3.1 score of 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), meaning the impact is confined to availability with no confidentiality or integrity loss. Exploitation requires a valid Db2 session (PR:L) and typical SQL INSERT access, but no public exploit code has been identified at time of analysis and there is no indication of active exploitation; this is a moderate-priority availability issue rather than a critical emergency. Vendor patches are available per IBM's advisory.
Unauthenticated flooding of crafted DHCPv6 RENEW messages can repeatedly crash odhcpd, the DHCPv6/DHCPv4/router-advertisement server shipped and enabled by default on OpenWrt, denying IPv6 address configuration to clients on the local link. An attacker who is network-adjacent (AV:A, PR:N, UI:N) must first complete two legitimate SOLICIT/REQUEST exchanges to obtain bindings, then send a single RENEW containing multiple IA_NA options that triggers an unsigned size_t underflow and lets attacker-controlled data be serialized past the 512-byte stack buffer pdbuf; the stack canary terminates the daemon and procd respawns it, so sustained packets cause recurring DHCPv6 outages. Impact is availability-only (C:N/I:N/A:H) and the observed configuration does not establish code execution; no public exploit identified at time of analysis, and the issue is fixed in OpenWrt 25.12.5.
An out-of-bounds heap write in Moonlight Qt 6.1.0 and earlier allows an attacker-controlled GameStream host to corrupt memory in the Moonlight client and reliably crash it during an active streaming session. Exploitation requires the victim to voluntarily initiate a session to the malicious host and requires Moonlight to select a decoder path that does not advertise CAPABILITY_REFERENCE_FRAME_INVALIDATION_AVC, which sends the server's H.264 SPS data through the vulnerable fixup path in app/streaming/video/ffmpeg.cpp, where a seq_parameter_set_id of 32 or greater is used unvalidated to index the 32-entry sps_table. The assessed impact is availability-only client crash and heap corruption (CVSS 6.5, AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H); despite metadata tags referencing RCE, code execution has not been established, and no public exploit code has been identified at time of analysis. This is a medium-severity, client-side denial-of-service issue rather than a high-priority remote compromise.
IBM DataStage on Cloud Pak for Data 5.4.0.0 exposes sensitive information to users who are not authorized to see it, letting an attacker who already holds a valid low-privilege account read data outside their intended scope over the network with no user interaction and low attack complexity. The independent assessment rates the flaw as confidentiality-only (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), so integrity and availability are not affected and the practical limiting factor is the requirement for authenticated access plus network reachability of the Cloud Pak for Data instance - this is not an anonymous, pre-authentication attack. The one caveat worth flagging is that IBM's own vector (9.6, S:C/I:H/I:H) asserts scope change and integrity impact that our assessment does not corroborate from the advisory text; there is no public exploit code and no CISA KEV entry, so there is no public exploit identified at time of analysis, and IBM has published a vendor advisory with patch guidance.
Server-side request forgery in Progress ShareFile Storage Zones Controller 5.12.6 and earlier lets a remote, unauthenticated attacker drive the component into issuing requests to unintended local handlers and performing unauthorized operations against its queue service, with no user interaction or privileges required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N). Impact is deliberately constrained - no confidentiality loss (C:N) and only low integrity and availability effects (I:L/A:L) - producing a medium severity score of 6.5, and no public exploit code or CISA KEV entry was identified at time of analysis. Exposure is limited to on-premises Storage Zones Controller instances that are network-reachable by the attacker, an extension or management component that is sometimes deployed internet-facing.
obsidian-tc versions prior to 1.3.1 fail to enforce folder access controls on direct file requests, allowing an authenticated MCP caller to read vault control-directory files such as .obsidian/plugins/*/data.json, which routinely store plugin API keys and Obsidian Sync passwords. Because an undefined readPaths/writePaths whitelist defaults to allow-all (a deliberate M0 back-compatibility behavior) and the strictReadDefault guard was silently stripped by config validation and never applied to direct request paths, even operators who believed they had locked the server down received no protection; .obsidian, .git, and .trash were filtered only during enumeration. The issue is a moderate-priority confidentiality-only flaw (CWE-200, CVSS 6.5, PR:L) with no integrity or availability impact and no public exploit identified at time of analysis; the vendor-released fix in v1.3.1 adds a hard default-deny baseline for control directories plus schema and request-path enforcement of strictReadDefault.
Code injection in IBM Maximo Application Suite's Location Service for Esri component (versions 9.0, 9.1, and 9.2) allows an authenticated attacker with high privileges (CVSS PR:H) and network access to supply an unsanitised container image configuration in the Kubernetes operator template, which the operator may then deploy. The issue is rated CVSS 6.5 Medium (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N) and can lead to high confidentiality and integrity impact, but requires privileged access to the MAS environment and affects an optional component. No public exploit identified at time of analysis, and no KEV or EPSS data indicates active exploitation.
Improper validation of the user-supplied sort parameter in Quarkus REST Data Panache's auto-generated REST endpoints allows remote attackers to learn information about entity fields they should not have access to and to degrade performance by forcing the underlying database to perform expensive ordering operations, up to a denial of service. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L, 6.5) indicates the issue is network-reachable and unauthenticated per PR:N, with low confidentiality and availability impact; real-world exposure is deployment-specific because it requires an application that has enabled and externally exposed these generated endpoints. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Authorization bypass through a user-controlled key in the WordPress 'Event Post' plugin (NOUS Ouvert Utile et Simple), affecting all versions through 6.1.1, allows an authenticated low-privilege user to reference and manipulate event objects belonging to other users by supplying a crafted identifier. The flaw is a classic IDOR (CWE-639) caused by an incorrectly configured access-control check, rated CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) - integrity impact only, with no confidentiality or availability loss and no user interaction required. The primary precondition is that the attacker holds any authenticated account on the target site, so exposure is greatest on sites that permit open or untrusted user registration; no public exploit code or confirmed active exploitation was identified at time of analysis, and no vendor-released fixed version appears in the available advisory data.
Authenticated users in Red Hat Satellite 6 (and the underlying Foreman permission-filter subsystem) can delete permission filters belonging to roles other than their own by abusing an API path that resolves filters by identifier without re-applying the caller's permission scope. The prerequisite is modest but not trivial: the attacker must already hold filter-delete rights for at least one role, and the victim roles must be unlocked - this is an insider or compromised semi-privileged account vector, not a default unauthenticated remote issue. Resulting impact is integrity-only (I:H, C:N/A:N) at CVSS 6.5, with other roles silently losing the access their deleted filters granted; no public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV).
Stored cross-site scripting in the Ad Inserter WordPress plugin (all versions through 2.8.18) allows an authenticated low-privilege user - a contributor, author, or any role permitted to create or edit ad blocks - to persist malicious script into plugin ad configuration, which then executes in the browser of another user, typically an administrator, when that page or the plugin's settings screen is rendered. Successful exploitation is bounded by two prerequisites: the attacker must already hold a suitably privileged WordPress account, and a second user must view the poisoned content, so this is not remotely exploitable against a default install by an anonymous visitor. Independently assessed as CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (6.5, moderate), and no public exploit identified at time of analysis; EPSS data was not supplied, so no exploitation-probability estimate can be cited.
Stored cross-site scripting in Crocoblock JetMenu (a WordPress mega-menu builder plugin) through version 3.0.5 lets an authenticated user with low-level content-authoring privileges inject script that is persisted and later executed in the browser of a higher-privileged viewer such as an administrator or editor. The flaw is rated CVSS 6.5 (Medium) under CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L, reflecting the need for a valid account (PR:L) and for a victim to render the poisoned menu content (UI:R), with scope change because the injected script runs in the victim's session context. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV); risk is concentrated on sites that grant untrusted or low-privilege users menu/content authoring capabilities.
Stored cross-site scripting in Crocoblock's JetElements For Elementor WordPress plugin (all versions through 2.9.2.3) allows an attacker holding a low-privilege account on the target site to persist malicious script through a JetElements input field, which then executes in the browser of any user who views the affected page. The vulnerable path requires an authenticated user with at least contributor/author-level posting capability and depends on a victim later visiting the poisoned content; successful exploitation runs script under the site's own origin, enabling session or credential theft and content/administrative action injection against higher-privileged viewers. There is no public exploit identified at time of analysis and no confirmed active exploitation; the issue is rated CVSS 3.1 base 6.5 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) and no patched version is specified in the available advisory data.
Stored cross-site scripting in the WordPress plugin Custom Query Blocks through version 5.6.0 lets an authenticated low-privilege user (for example a contributor or author) inject script that executes in the browser of any other user who later views the affected page, including administrators. The plugin fails to neutralize stored input before rendering it during web page generation (CWE-79), and exploitation requires both valid account credentials and a victim who loads the injected content, so the attack is not fully automatable. With a CVSS base score of 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L), impact is scoped to the victim's session and page context, and no public exploit code has been identified at time of analysis.
Authenticated users holding only subscriber-level privileges can permanently delete every comment on a WordPress site running the WP Comment Cleaner plugin in versions 6.1 up to (but not including) 7.2, because one of its bulk comment-deletion routines performs no capability check and no nonce validation (CWE-862). Scored CVSS 3.1 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N), the flaw is a moderate-priority access-control weakness confined to destruction of comment data, with no confidentiality or service-availability impact, rather than a code-execution emergency. No public exploit identified at time of analysis, but practical exploitation is easiest on sites that allow self-service registration, since that lets any attacker obtain the minimal account required; sites that disable open registration and tightly control accounts substantially shrink the attacker population.
Local privilege escalation in IBM Db2 11.5.0-11.5.9 and 12.1.0-12.1.5 allows an authenticated low-privileged user on the database host to abuse the db2pd monitoring and diagnostic utility to gain privileges beyond those they legitimately hold. Exploitation requires pre-existing local shell access and the ability to run db2pd, so the flaw is not reachable remotely or by unauthenticated actors; it matters most on shared, multi-tenant, or otherwise privileged-access Db2 servers. Our independent assessment rates the true impact higher than IBM's published CVSS 6.5, scoring it CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H; no public exploit code has been identified and the issue is not confirmed as actively exploited (not in CISA KEV), though a vendor patch is available and should be applied to remove the condition.
Stored cross-site scripting (XSS) in BdThemes Element Pack Elementor Addons versions up to and including 8.8.8 allows an authenticated attacker with low-level content-editing privileges to inject malicious scripts that execute in the browser of a higher-privileged user who views the affected page. This moderate-severity vulnerability (CVSS 6.5) requires victim interaction and is not exploitable without authentication; no public exploit code has been identified at time of analysis.
Stored cross-site scripting in the Premium Addons for Elementor WordPress plugin (through version 4.11.110) lets an authenticated user with low-level content-contribution privileges plant persistent JavaScript inside Elementor-built pages or widgets, which then executes in the browser of any user who renders that content. The CVSS 6.5 score (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) reflects a network-reachable, low-complexity attack that requires an account with at least contributor/author-tier access and victim interaction, with the changed-scope (S:C) metric indicating the injected script acts in the context of the site origin rather than a confined component. Only sites running the plugin at or below 4.11.110 are affected, and no public exploit code or CISA KEV entry was identified at time of analysis.
This moderate-severity DOM-based cross-site scripting issue affects the ExpressTech Quiz And Survey Master WordPress plugin through version 11.2.7. An authenticated attacker with at least low-level privileges can supply input that is later rendered into a client-side DOM sink, causing script execution in the browser of a victim who interacts with the affected quiz or survey page. The CVSS 3.1 score is 6.5 (Medium); no public exploit was identified at time of analysis, and exploitation requires victim interaction.
Server-side request forgery in Red Hat Quay allows an authenticated repository administrator to bypass the hostname blacklist enforced by the webhook notification feature, causing the Quay application to issue HTTP requests to attacker-chosen internal destinations such as cloud metadata endpoints or in-cluster services. Successful exploitation can disclose sensitive information returned by those internal services, though the CVSS 3.1 score of 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) reflects a moderate impact: the attacker must already hold a privileged in-application role, must use the webhook functionality, and the yield is bounded by which internal endpoints the Quay pod can actually reach. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the flaw is tracked by Red Hat under CVE-2026-85471 with all Quay 3 and Mirror Registry offerings listed as affected via wildcarded CPEs.
Build trigger management API in Red Hat Quay 3.x fails to verify that a requested trigger belongs to the specified repository, allowing an authenticated repository administrator to view, modify, or delete build triggers and associated write tokens in other repositories if they know the victim trigger's UUID. This is a moderate-severity authorization bypass (CWE-639) requiring prior knowledge of a random, non-enumerable UUID, which raises attack complexity (CVSS AC:H). As of analysis, no public exploit code has been identified; Red Hat has published an advisory and Bugzilla entry.
Uncontrolled recursion in ImageMagick's MVG/SVG decoding path allows a crafted image file with deeply nested image or drawing references to exhaust the process stack and crash the application, producing a denial of service. All ImageMagick releases before 6.9.13-57 on the legacy 6.x branch and before 7.1.2-32 on the 7.x branch are affected, and the MVG/SVG coders ship in default builds, so exposure is determined by whether a deployment routes untrusted input into ImageMagick's decoder pipeline (upload handling, conversion, thumbnailing). No public exploit code has been identified at time of analysis, this CVE is not in CISA KEV, and the CVSS 4.0 base score of 6.3 with an assessed CVSS 3.1 vector of AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L reflects a medium-severity availability-only impact with no confidentiality, integrity, or code-execution consequences.
Repeated wavelet-denoise processing of attacker-influenced images in ImageMagick 6.x before 6.9.13-57 and 7.x before 7.1.2-32 leaks the internal noise-image buffer whenever a required resource cannot be acquired on a resource-constrained host, letting remote unauthenticated attackers gradually degrade service availability through many requests. The leak is confined to the allocation-failure branch, so there is no single-shot crash, no code execution, and no data exposure, making this a medium/low-priority availability issue rather than a critical one. No public exploit code has been identified and there is no evidence of active exploitation, while vendor patches are available.
Denial of service in ImageMagick 7.1.2-30 and 7.1.2-31: a crafted image handled by the WBINFO (Amiga icon) decoder can corrupt memory through a use-after-free - classified in the CVE record as CWE-415 - and crash the process, but only when a memory allocation fails during that decode. The allocation-failure prerequisite (AT:P in the CVSS 4.0 vector) is the main limiter, since a remote attacker cannot reliably force the condition without the target already being under memory pressure, although no authentication (PR:N) and no user interaction (UI:N) are required where images are decoded automatically. No public exploit code and no CISA KEV listing were identified at time of analysis, and vendor patches are available.
Use-after-free in ImageMagick's PDF writer (coders/pdf.c) can crash the process when a CMYK-colorspace image is written to PDF using JPEG2000 compression; affected releases are ImageMagick before 6.9.13-57 and 7.x before 7.1.2-32. The attacker supplies the crafted CMYK image, but the trigger is the operator-side PDF export operation with JPEG2000 compression selected, which is not the default output mode - reading or decoding the image alone does not reach the vulnerable code path. The issue is a low-impact availability defect (no confidentiality or integrity loss), unauthenticated per the CVSS PR:N vector, and no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis; vendor patches exist as commits in the ImageMagick and ImageMagick6 repositories.
Memory exhaustion in ImageMagick before 6.9.13-57 (6.x line) and before 7.1.2-32 (7.x line) lets unauthenticated attackers leak memory by feeding crafted input to the YUV encoder, which fails to free allocated image buffers when a specific encoder operation fails. The impact is availability-only (CWE-401 memory leak, assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L; vendor/NVD CVSS 4.0 base 6.3), and because each failure leaks only incrementally, a practical denial of service requires repeated, high-volume triggering of the failing path. Exploitation is gated by the target application actually producing YUV output, since the flaw lives in coders/yuv.c WriteYUVImage and deployments that never write YUV are not exposed; no public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation.
Repeated GIF encoding of crafted or attacker-influenced images can steadily exhaust process memory in ImageMagick before 6.9.13-57 and 7.x before 7.1.2-32, because the GIF encoder fails to release allocated buffers when color quantization fails. Remote, unauthenticated attackers who can get an application to convert or write images to GIF output can trigger a small, bounded leak on each attempt, and enough repetitions degrade availability (CVSS 4.0 base 6.3; our independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L). No public exploit code was identified at time of analysis, and there is no code execution, data exposure, or privilege gain associated with this flaw.
A memory leak in ImageMagick's PNG encoder (coders/png.c, WriteOnePNGImage) fails to release the image and image_info structures when libpng write-structure initialization fails, allowing any unauthenticated remote party who can repeatedly drive PNG encoding operations into that failure path to steadily exhaust process memory and cause a denial of service. Affected are all ImageMagick 6.x releases before 6.9.13-57 and 7.x releases before 7.1.2-32; the vendor has released fixed versions (6.9.13-57 and 7.1.2-32) and upstream commits, and no public exploit code was identified at time of analysis. Impact is availability-only and low in magnitude per both the vendor's CVSS 4.0 score of 6.3 and our independent CVSS 3.1 assessment of AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L, because the leak only compounds after the host is already experiencing libpng allocation failures - the practical risk is moderate and typically relevant to services that encode attacker-supplied images at scale.