Reflected cross-site scripting in the Persian WooCommerce SMS WordPress plugin (versions 7.2.0 up to, but not including, 7.3.2) lets an unauthenticated attacker reflect an unsanitised parameter into an HTML attribute, so script runs in the browser session of a logged-in privileged user who is tricked into submitting a crafted cross-site request. The attacker does not need credentials (PR:N), but successful exploitation depends on social-engineering a high-privilege account such as a WordPress administrator into triggering the request (UI:R), which is why the practical risk is moderate rather than urgent. A vendor fix is available in 7.3.2, EPSS is low at 0.17% (6th percentile), and no public exploit has been identified at time of analysis; the issue is not reported as confirmed actively exploited (CISA KEV).
AXIS Camera Station Pro and Camera Station 5 weakly encrypt database backups (CWE-326), so an attacker who obtains a backup file can attack it offline and recover the credentials stored inside. The exposure covers backups created before the fix and the extra recovery backup that Camera Station automatically creates when the update is applied; the CVSS 7.1 vector (AV:L/PR:L, UI:N) means local access to the backup artifacts and low privileges are required, not remote reachability. No public exploit code or confirmed active exploitation was identified at time of analysis, and updating alone does not remove already-exposed backups.
OS command injection in CherryTree through 1.7.2 lets an attacker run arbitrary commands with the victim's privileges when the victim opens a crafted document and clicks a web link containing unquoted shell metacharacters such as $(...), backticks, or semicolons. The vulnerable path is only reached when the non-default 'Custom Web Link Clicked Action' option is enabled and the link is handed to std::system via CtActions::link_clicked; with the default configuration that code path is not taken. Exploitation is therefore condition-gated and depends on victim interaction rather than remote or automatic attack, and no public exploit was identified at time of analysis.
Prototype pollution in n8n allows an authenticated low-privileged user who can create and save workflows to corrupt built-in JavaScript object behaviour, which then causes logins and writes to fail with server errors across the instance. The flaw lives in the routine that diffs workflow connection sets: a connections key named with a reserved property such as __proto__, constructor, or prototype is used directly as an object member, and the periodic workflow-history compaction task later processes it, polluting the process-wide object prototype. Instances running n8n before 2.41.4 or 2.42.x before 2.42.1 are affected, workflow history is enabled by default, and no public exploit code was identified at time of analysis.
An authenticated n8n member who can create and run workflows can freeze the entire instance by supplying a wildcard-heavy File(s) Selector glob pattern to the Read/Write Files from Disk node, which compiles to a catastrophically backtracking regular expression and blocks the Node.js event loop with no time limit. The result is a denial of service in which the UI, API, webhooks and health checks stop responding until the process is restarted; there is no data disclosure or modification. Affected are n8n releases before 1.123.85, before 2.43.5 and before 2.44.1, and exploitation requires a valid member-level account with workflow create/execute rights plus the readWriteFile node being enabled. No public exploit code has been identified at time of analysis, and the vendor has released fixed versions.
Integer underflow in Juniper Networks Session Smart Router's DhcpMessageDecoder allows an attacker on the adjacent network to cause information disclosure and denial of service by sending a malicious DHCP reply. The issue affects Session Smart Router deployments where the router processes DHCP replies as a client or relay on an attacker-reachable Layer 2 segment; the CVSS 3.1 vector is AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H, so no authentication or user interaction is required but exploitation is confined to local-segment presence. No public exploit code or active exploitation is identified in the provided data, and the priority label is this_week.
Broken object-level authorization in Xibo CMS 4.4.2 and earlier allows a logged-in user to point PUT and DELETE requests at /action/{id} and modify or delete Layout actions attached to any Layout in the CMS, not just their own. The CVSS vector confirms the attacker must be authenticated (PR:L) but needs no user interaction; the vendor notes the only required privilege - permission to edit, including delete, all created Layouts - is granted to non-administrators as standard, so ordinary accounts typically qualify. Integrity impact is high with a limited availability impact, confidentiality is unaffected, and there is no public exploit code identified at time of analysis; the vendor has released 4.4.3 and this is scheduled as this-week remediation rather than an emergency.
Missing authorization in NORA Registry (nora-registry) 0.9.4 and earlier lets any valid read-scoped bearer token enumerate token metadata - ID, owner, role, description, expiry and last-use - for every user through the globally scoped token-management list endpoint, while a write-scoped bearer token or write-capable OIDC workload identity can additionally revoke arbitrary admin and service tokens by ID, disrupting the registry and forcing credential recovery. The flaw is CWE-862: auth_middleware() authenticates /ui/tokens and /api/ui/tokens but only checks role.can_write() instead of role.can_admin(), so the handlers operate across all accounts. No CISA KEV entry or confirmed active exploitation was reported; the vendor advisory includes reproduction steps (a PoC reference) rather than verified working exploit code, and exploitation requires auth to be enabled, the token endpoints to be network-reachable, and the attacker to already hold a valid registry credential.
Stored cross-site scripting in the SliceWP WordPress plugin through 1.2.13 lets an attacker who can persist input through a SliceWP field have script run in a victim's browser when the affected page is later viewed. The victim must load the crafted page (UI:R), and exploitation depends on the plugin being installed and active; the specific form or endpoint carrying the injectable input is not described in the available sources. The reporter scored the issue 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L), but an independent assessment treats the unauthenticated claim as unverified and scopes out availability impact; no public exploit was identified at time of analysis.
Reflected cross-site scripting in the WordPress plugin Unlimited Elements For Elementor (Free Widgets, Addons, Templates) through version 2.0.24 lets remote attackers supply crafted input that the plugin reflects into a generated page without proper neutralization, so that script supplied by the attacker executes in the browser of a victim who follows a crafted request or URL. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) shows no authentication is needed but successful exploitation depends on the victim interacting with the crafted request, making social engineering the practical limiting factor rather than silent remote compromise. No public exploit code and no confirmed active exploitation are recorded in the available sources, and the specific parameter or page that reflects the input is not described in the available sources.
Reflected cross-site scripting (CWE-79) in the impleCode eCommerce Product Catalog WordPress plugin through version 3.6.4 allows a remote, unauthenticated attacker to run script in a victim's browser by persuading the victim to open a crafted URL that reflects an unsanitized input. Exploitation is constrained by the required victim interaction (UI:R) and the fact that the payload is not stored, so each target has to be lured individually; no public exploit code or proof-of-concept is referenced in the available intelligence, and the case is queued for handling this week under the vuln.today priority. No vendor-released fixed version is identified in the supplied data, and the advisory of record is the Patchstack database entry.
Stored cross-site scripting in the Crowd Favorite DXP ToolKit WordPress plugin, affecting versions from an unspecified starting point through 2.0.1, lets an attacker persist script content that executes in the browser of any user who later views the page rendering it. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, 7.1) indicates network reachability and no privileges required, but a victim must load the affected page for the payload to fire, and the scope change reflects impact escaping the vulnerable component into the surrounding WordPress site. No public exploit code or active exploitation has been identified at time of analysis, and exploitation is further constrained by the plugin's niche deployment footprint. Patchstack is the reporting source and the linked advisory is the only reference available.
Stored cross-site scripting in the GetPaid WordPress invoicing plugin, affecting versions through 2.8.62, allows remote attackers to plant script payloads that execute in the browser of any user who later views the affected page. The CVSS 3.1 score of 7.1 reflects network reachability and no authentication requirement for introducing the payload (PR:N), offset by a required victim interaction (UI:R) and a scope change (S:C) that lets the injected script act beyond the plugin's own context. No public exploit identified at time of analysis.
Path traversal in Progress Telerik Document Processing Libraries before 2026.3.1027 allows an authenticated, low-privilege user who can supply arguments to the Convert and Merge AI agent tools to read files outside the configured output directory and to overwrite any of those files that the process account can write. Supplied relative paths resolve against the process's current working directory instead of being confined to the output directory, yielding high confidentiality and limited integrity impact (CVSS 7.1, PR:L). No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the vendor's complete fix is an update to 2026.3.1027 or later, which puts this in the 'this week' remediation queue rather than an emergency.
Dell PowerProtect Data Domain Management Center enforces incomplete authorization checks, letting a low-privileged authenticated user perform operations they should not be permitted to carry out, with high integrity impact and limited availability impact and no confidentiality impact (CVSS 7.1). Exploitation requires a pre-existing low-privileged account on the management appliance plus network reachability; an unauthenticated outsider cannot trigger it directly, and the sources do not identify which specific management feature or endpoint lacks the check. No KEV entry, no SSVC emergency flag and no public exploit reference are present - no public exploit identified at time of analysis - but a patch is available from Dell and the release is prioritised as a near-term (this week) patching item rather than an emergency.
Local privilege escalation in Acronis Cyber Protect Cloud Agent (Windows) before build 42569 and Acronis Cyber Protect 17 (Windows) before build 42587 lets an authenticated local user with low privileges abuse improper authentication in the agent to reach high confidentiality and integrity impact. The weakness is CWE-1390 (improper authentication) and requires an existing local foothold on the Windows host - there is no remote vector and no user interaction is needed; availability is not affected. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so this is a moderate, local-only risk rather than an emergency, though the vendor did report it and patched builds are available.
Filter injection in the n8n Quick Base node allows an external caller to rewrite the 'Where' filter that a workflow passes to the Quick Base API as raw query text, so a Get Many operation returns every record in the table and a Delete operation removes every record using the privileges of the workflow's stored Quick Base credential. Affected releases are n8n before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1; exploitation is not automatic and requires a non-default workflow that builds the Where filter from untrusted input, such as a webhook payload, via an expression. No public exploit code has been identified at time of analysis, and this is tracked as a prioritize-this-week item whose real-world risk is strongly gated by workflow configuration rather than by CVSS severity alone.
Heap-based out-of-bounds write in USB Test 1.1.4 and earlier lets a rogue USB flash drive with crafted firmware corrupt the heap of the elevated Windows CLI process, crashing it and, per the vendor advisory, credibly opening a path to arbitrary code execution when a user starts a drive test. The utility trusts the DISK_GEOMETRY.BytesPerSector value returned by IOCTL_DISK_GET_DRIVE_GEOMETRY without checking the call result or bounding the value, so a device reporting fewer than 8 bytes per sector under-sizes a heap buffer that then receives an 8-byte memcpy on every loop iteration; a reported value of 0 triggers a divide-by-zero and an enormous value causes std::bad_alloc. Exploitation requires a physically attached malicious device and a user who launches the tool, selects that drive and starts a test, which keeps the exposure narrow despite the vendor rating of 7.0; the vendor fix is version 1.1.5, and a public PoC reference exists (an in-source simulation of the untrusted value) but it is not verified as working exploit code.
Path traversal in Axel Download Accelerator 2.17.14 and earlier lets a crafted download URL write the retrieved file outside the intended output directory - anywhere writable relative to axel's current working directory - because the filename is percent-decoded only after the URL has been parsed. The flaw is unauthenticated (PR:N) but requires the victim to actively launch a download against an attacker-influenced URL (UI:A), and confidentiality is unaffected since the primitive is write-only; integrity and availability impacts are High. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the vendor has an upstream fix in PR 483, but a tagged patched release is not independently confirmed.
Apache Qpid Proton C through 0.40.0 performs TLS peer hostname verification with its own hand-rolled logic, and a certificate carrying a wildcard entry that does not conform to RFC9525 causes a stack buffer over-read during that check. A malicious TLS peer - or an attacker in a man-in-the-middle position injecting a crafted certificate - can therefore disrupt the connecting client; the assessed impact is availability-only (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L), with the user-interaction requirement reflecting that the victim client must actually connect to the attacker-controlled endpoint with verification enabled. Certificates that comply with RFC9525 never trigger the flaw, and the issue is fixed in 0.41.1; no public exploit code was identified at time of analysis and the issue is not in CISA KEV, which is consistent with the low-priority, awaiting-data decision signal.
An authentication bypass in Apache Qpid Proton C through 0.40.0 lets a remote peer step past SASL authentication by sending AMQP performatives that claim to be SASL frames, which the vendor rates as important severity. Impact is conditional rather than automatic: the bypass leaves no user name set, so authentication has not actually completed, and the real outcome depends on whether the hosting application tolerates an identity-less session or falls back to a default identity. No public exploit code or active exploitation was identified at time of analysis, and the vendor has published 0.41.1 as the fixed release tracked under PROTON-2945.
Stack-exhausting unbounded recursion in Apache Qpid Proton C through 0.40.0 lets a deeply nested AMQP message body crash the process when an application decodes it with pn_message_body(). The flaw is availability-only (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H): no code execution or data exposure is described, but any service that passes untrusted AMQP bodies to that decoder can be taken down by a single crafted message. No public exploit code or PoC has been identified at time of analysis, no CISA KEV entry exists, and the vendor has released a fix in 0.41.1.
Memory exhaustion in the Apache Kafka broker lets an authenticated principal holding Write permission on a topic submit a roughly 90-byte, CRC-valid compressed produce request that declares a decompressed record body of up to about 2 GiB, forcing the broker to attempt that allocation and raise OutOfMemoryError. The flaw is reachable on the produce-validation path when a batch's codec differs from the topic's configured compression.type and records are re-encoded, and a crafted record accepted at ingest can also kill the single default log-cleaner thread when it is later read on a compacted topic, stopping compaction broker-wide (including __consumer_offsets and __transaction_state) across restarts until the record is removed; because OutOfMemoryError is an Error rather than an Exception, the cleaner thread is not restarted. Impact is availability only - no data disclosure or modification - and no public exploit code has been identified at time of analysis. Critically, patching alone does not close exposure: the new max.decompressed.message.bytes setting defaults to an effectively unlimited (~2 GiB) value for backward compatibility, so operators must both upgrade and configure a bounded limit.
Apache Kafka brokers that have an authorizer enabled will read a file or environment variable from the broker host and return its contents to any authenticated principal, including one holding no ACL grants at all - not even ALTER_CONFIGS. The flaw is a missing-authorization ordering problem (CWE-862): an IncrementalAlterConfigs or AlterConfigs request aimed at a BROKER resource reaches configuration validation, which resolves ${file:/path:key} or ${env:VAR} variables through a ConfigProvider instantiated from the request, before any authorization check is applied, and a type-validation error reflects the resolved secret back to the caller. This defeats the org.apache.kafka.automatic.config.providers allowlist introduced for CVE-2024-31141, but the read is bounded by the broker process's OS file permissions and impacts only confidentiality, not cluster availability or data integrity; there is no public exploit identified at time of analysis and the vendor-supplied fix set is Kafka 4.2.2, 4.3.2, and 4.4.0.
Network-reachable, unauthenticated deserialization flaws in Apache Kafka’s clients library and Kafka Streams can force multi-gigabyte allocations and crash the consuming application or Streams thread with an OutOfMemoryError; the broker and other cluster components are unaffected. Versions 0.10.0.0 through 4.1.2, 4.2.0 through 4.2.1, and 4.3.0 through 4.3.1 are affected across the Kafka Streams paths (ProcessorRecordContext, ChangedDeserializer, CombinedKeySchema, ProcessorMetadata, AssignmentInfo) and the clients ListDeserializer used by ListSerde. Exploitation requires the ability to place crafted data on the relevant deserialization path-writing to internal changelog or repartition topics, committing offset metadata, supplying crafted group-assignment data as Streams group leader, or producing to a topic consumed with ListSerde; Kafka ACLs block many of these paths when authorization is enabled, no CISA KEV entry is reported in the supplied data, no EPSS score is available, and no public exploit identified at time of analysis.
Unauthenticated remote attackers can exhaust broker heap and trigger process-wide GC stalls on Apache Kafka by declaring an enormous tagged-field count in the flexible request header, which generated readers accept without checking it against the remaining buffer. The affected lines are 2.4.0 through 4.1.2, 4.2.0 through 4.2.1, and 4.3.0 through 4.3.1; because each declared field costs one RawTaggedField allocation and can be encoded in as little as two bytes, a request of a few tens of megabytes can force roughly 20 million allocations, and this happens on the network thread before authentication, request dispatch and request-time quota accounting, so APIs such as ApiVersions v3 are reachable pre-authentication. The outcome is availability-only denial of service; no public exploit identified at time of analysis, and vendor fixes are available in 4.2.2, 4.3.2 and 4.4.0, making this a this-week priority rather than an emergency.
Heap exhaustion in Apache Kafka allows remote attackers to crash brokers by sending requests that declare an array element count far exceeding the actual buffer contents, causing generated protocol readers to pre-allocate an ImplicitLinkedHashCollection with capacity 2*count+1 before reading any elements. Because parsing happens before authorization, listeners without authentication such as PLAINTEXT are exposed to unauthenticated attackers, while authenticated listeners require valid credentials but no specific ACL; the reporter demonstrated three concurrent ~90 MB ProduceRequest v3 connections exhausting a 1 GB heap (~8x amplification). Affected releases are prior to 4.2.2, 4.3.2, and 4.4.0, and no public exploit code has been identified at time of analysis.
Apache Kafka brokers that run SASL/OAUTHBEARER with the default DefaultJwtValidator and leave sasl.oauthbearer.jwks.endpoint.url unset silently fall back to a validator that performs no JWT signature, algorithm, or issuer checks, allowing unauthenticated remote attackers with listener reachability to forge tokens for arbitrary principals, including configured superusers, and gain full cluster access. The flaw is a residual of CVE-2026-33557 and only affects brokers in this specific OAUTHBEARER-without-JWKS-URL configuration with no custom verification key resolver; brokers that set the JWKS URL verify signatures and are not affected. No CISA KEV listing or public exploit code is identified in the available data, no public exploit identified at time of analysis, and no EPSS score is provided.