Unauthenticated attackers can forge TiendaCrypto para WooCommerce payment webhooks - versions 1.0.1 through 1.2.1 - to mark arbitrary WooCommerce orders as paid, because the plugin validates the request signature against a key that is always empty. The exposure is narrow: it applies only where the webhook endpoint is reachable and the web server preserves the case of request header names, which is why it is scored 3.7 with AC:H and integrity-only impact. A public PoC reference exists (the WPScan entry); it is not verified as working exploit code, EPSS is 0.11% (1st percentile), there is no CISA KEV listing, and the priority label is monitor.
Cross-site scripting in the CKEditor 5 engine (@ckeditor/ckeditor5-engine) allows crafted markup to execute attacker-controlled JavaScript when the editor processes it, but only on installations where General HTML Support is enabled and explicitly configured to permit inserting object content. Exposed versions are 29.0.0 through 47.7.3 and 48.0.0 through 48.5.0; default builds and deployments without that non-default GHS object allowlist are not affected. Per the vendor and the assessed vector (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N), the injected script runs in a browser context isolated from the embedding application's origin, so the vendor models no confidentiality impact and only low integrity impact; no public exploit was identified at the time of analysis and the issue is tracked as monitor priority.
Path traversal in the model persistor of crownpku Rasa_NLU_Chi (versions 0.12.0 through 0.12.2) lets an attacker who can influence a model archive that the Persistor later decompresses write outside the intended extraction directory, with low confidentiality, integrity and availability impact. The CVSS 4.0 vector (2.1, AV:N/AC:L/PR:L/UI:N) requires low-privilege access and the ability to supply or alter the model artifact being loaded or restored rather than simple anonymous reach. A public PoC reference exists; it is not verified as working exploit code, and there is no confirmed active exploitation (not in CISA KEV). The project was notified through GitHub issue #138 and has not responded, and no vendor-released patch has been identified at time of analysis, so the practical exposure is limited to deployments running this unmaintained fork.
Improper validation of an integrity check value in VideoLLaMA2's model-loading routine (load_pretrained_model in videollama2/model/__init__.py) allows a tampered model artifact to be accepted when an operator loads a model from an attacker-influenced path supplied through the _name_or_path argument. Versions 1.0 and 1.1 are affected; because the flaw lives in a library function rather than an always-on service, exploitation requires passive user interaction - someone must actively initiate a load from the hostile source - and impact is bounded to low integrity and low availability with no confidentiality effect. A public reference to the issue exists (the upstream GitHub issue report), but it is not verified as working exploit code, there is no CISA KEV listing, and EPSS is 0.15% (4th percentile), so all available signals point to a low real-world priority and a monitor-level decision.
Chitchatter's embedded SDK mode can be tricked into accepting forged configuration and identity keys from an attacker-controlled parent frame, because the postMessage CONFIG handler in src/Bootstrap.tsx fails to properly authenticate the sender when the supplied parentDomain is manipulated (CWE-287). Only deployments running Chitchatter inside an iframe with the embedded/SDK flags set are exposed; a victim has to load or interact with the attacker's embedding page (CVSS 3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N, low severity), while standalone Chitchatter use is not affected. The flaw was fixed in upstream commit e3babb5cd83bfe3b99f1d82358ac5c1ea8e8a688 (PR #635), and a public PoC reference exists but is not verified as working exploit code; there is no CISA KEV entry, and the current triage decision is monitor.
Path traversal in the Dexbotic gr00tsonic Checkpoint Loader (dexbotic/model/gr00tsonic/gr00tsonic_arch.py, function load_pretrained_gr00t) allows an attacker who controls the weight_map argument to cause file paths outside the intended checkpoint location to be used during checkpoint loading. Dexbotic 0.1 and 0.2.0 are listed as affected (CPE cpe:2.3:a:dexmal:dexbotic:*), and exploitation is remote but requires the victim to actually load an attacker-influenced pretrained checkpoint - per the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L vector no authentication is needed, while passive user interaction is the primary limiting factor. There is no CISA KEV entry and no confirmed active exploitation; a public PoC reference exists but it is not verified as working exploit code, and the project has been notified through an issue report without a response, so the issue is assessed as low priority (monitor).
Cross-site scripting in the chat.php endpoint of Saruf-Ratul's HR-Payroll-Management-System allows an attacker to inject script through the ID argument, with execution occurring in a logged-in victim's browser after that user is induced to open a crafted request or link. The flaw is remotely reachable but requires a low-privileged authenticated session (PR:L) plus victim interaction (UI:P), and the assessed impact is limited to script execution in the victim's browser context with no confidentiality or availability impact as scored. A public PoC reference exists in the project's issue tracker; it is not verified as working exploit code, CISA KEV does not list the product, EPSS is 0.20% (10th percentile), SSVC rates exploitation as 'poc' with partial technical impact, and the tracking decision is monitor.
Reflected cross-site scripting in the chat.php script of MD-MAFUJUL-HASAN Online-Payroll-Management-System allows an authenticated low-privileged user to manipulate the ID argument so that attacker-supplied script runs in a victim's browser when the victim follows a crafted link. Scoring is low: the CVE carries CVSS 4.0 base 2.0 and our independent assessment rates it CVSS 3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N, with impact confined to limited integrity change and no confidentiality or availability effect. A public PoC reference exists at the project's GitHub issue tracker; it is not verified as working exploit code, EPSS is 0.20% (10th percentile), there is no CISA KEV entry and no confirmed active exploitation, and the maintainer has not responded to the report, so no fixed release is available for this rolling-release project.
Code injection in the Remotedev Server component of redux-devtools 5.0.0 allows a locally positioned attacker with low-level privileges to inject code through a crafted value passed to the action argument of the evalAction function. Because the attack vector is local (AV:L) and requires pre-existing privileges (PR:L), the practical exposure is confined to developer and debugging environments where the Remotedev Server is reachable by an already-present user; no user interaction is needed. The flaw was reported to the project through a GitHub issue (reduxjs/redux-devtools#2125) but no vendor response or patch has been identified, and a public PoC reference exists that is not verified as working exploit code - no confirmed active exploitation (CISA KEV) was recorded, and the priority assessment is 'monitor'.
Relative path traversal in Dell PowerProtect Data Domain (Feature Release 7.7.1.0 through 8.8, LTS2024 7.13.1.0-7.13.1.80, LTS2025 8.3.1.0-8.3.1.40, and LTS2026 8.6.1.0-8.6.1.20) lets an attacker who already holds a high-privileged, administrative-level account and network access to the appliance manipulate files outside their intended location, producing limited integrity tampering and limited availability impact with no confidentiality loss. The privilege precondition (PR:H) is the dominant limiting factor: this is not reachable by unauthenticated or low-privileged remote users. No public exploit identified at time of analysis; vendor fixes are published in the 7.13.1.90, 8.3.1.50, 8.6.1.30 and 8.9.0.0 builds, and overall priority is low (monitor).
Session revocation bypass in @fastify/session before 11.1.6 lets an authenticated remote attacker who already holds a victim's valid signed session cookie keep that session alive after logout by winning a narrow timing race: a request that restored the session before the logout can still write its own copy of the store entry after another request's Session#destroy() has completed, recreating the destroyed identifier with its authenticated data. The default rolling: true behavior is required, no cookie theft or signature forgery is involved, and the attacker gains nothing beyond a session they could already use - the flaw extends or resurrects an existing session rather than creating initial access (CVSS 3.1 base 3.7, AV:N/AC:H/PR:L/UI:R, C:L/I:L/A:N). No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the vendor has released a fix in 11.1.6 that adds a per-session generation marker plus a conditional store write.
Local information disclosure in Tanium Threat Response Client Extension and Endpoint Configuration Toolset Solution is reachable only by a low-privileged local user and depends on a high-complexity condition outside the attacker's control, so impact is limited to low confidentiality exposure and minor availability loss. No public exploit code was identified at time of analysis, and Tanium has published fixed builds under advisory TAN-2026-056.
Nextcloud Richdocuments, the Collabora/WOPI integration for Nextcloud, at version 11.0.0 or earlier does not validate the token type on a WOPI configuration endpoint, so a holder of a valid low-privilege user or guest token can retrieve additional configuration information. The impact is limited to low confidentiality disclosure (CVSS 3.5; C:L only) and requires an authenticated token (PR:L); no public exploit is identified at time of analysis and the priority is monitor.
Recipients of a public share link in Nextcloud Collectives 4.0.0 can create pages inside the shared collective, an action the link-recipient role should not have permitted under the intended access model. The flaw is an improper access-control weakness (CWE-284) with a low integrity-only impact - no confidentiality or availability effect is described - and it is exploitable remotely by an authenticated low-privileged user per the CVSS vector (AV:N/AC:L/PR:L/UI:R). Only 4.0.0 is listed as affected, no public exploit code has been identified at time of analysis (the sole public reference is the originating HackerOne report), and the vuln.today decision label is monitor with no CISA KEV listing.
Path traversal in the Linux networkStats() implementation of systeminformation before 5.33.14 allows a caller who controls the iface value, together with a locally planted directory of symlinked statistics files, to disclose the first line of any file readable by the Node.js process. The package exposes no network endpoint, so reaching the vulnerable path requires local filesystem write access or a consuming application that forwards untrusted input into networkStats(); the demonstrated impact is limited to a single line of a readable file, and the Windows and macOS implementations are not described as affected. A public proof-of-concept reference is included in the GitHub advisory; it is not verified as working exploit code, and no active exploitation is indicated.
An information-disclosure flaw in the Nextcloud Tables app (versions 0.8.1 through 2.0.0) lets an authenticated user who holds only read-data access to a table retrieve the full list of share recipients and their permission levels by calling the share-listing endpoint directly. The web UI correctly blocks these users from viewing that information, but the endpoint itself never verifies manage-level permission, so a low-privileged account can enumerate affected users, groups and teams along with their access levels for any table it can reach. The disclosure is limited to sharing metadata - table content is not exposed beyond what the existing read-data grant already allows - and no public exploit code or active exploitation is identified at time of analysis, with a low CVSS base score (3.3 vendor / AV:N per independent assessment) and a monitor-level priority.
Unbounded, persistent memory retention in the russh SSH agent server (russh::keys::agent::server::serve) before 0.65.0 allows any process able to reach the agent socket to grow the agent's heap without limit by repeatedly submitting key-addition requests padded with SSH_AGENT_CONSTRAIN_CONFIRM (0x02) records. Each 1-byte record on the wire becomes a 56-byte retained Constraint::Confirm value inside the keystore, and because keys without a lifetime constraint never expire, that memory is never reclaimed for the life of the process. Severity is low and availability-only (CVSS 3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, 3.3), the vendor fixed the issue in 0.65.0, there is no CISA KEV listing for this CVE, and the published GHSA advisory supplies a verified proof-of-concept harness rather than any indication of active exploitation.
Infinite-loop denial of service in Tanium Threat Response client extension and Endpoint Configuration Toolset Solution allows a local user with low privileges to hang the affected endpoint component, reducing availability only. Affected builds are Threat Response CX before 1.17.802, 1.18.2732, 1.19.2213, 1.20.2271, and 1.21.1673, and Endpoint Configuration Toolset Solution before 1.51.60, 1.59.50, and 1.71.25. The vendor has released fixes, no public exploit identified at time of analysis, no CISA KEV entry, and the issue is rated monitor priority.
Predictable session-token generation in the HTML5 KVM-over-IP console of the Supermicro MBD-X12SPI BMC/IPMI web interface (firmware 01.07.20) allows a remote attacker to guess a token issued by the web interface and hijack an active KVM session, gaining access to the console's display and input path. Per the assessed vector the flaw is network-reachable and unauthenticated (AV:N/PR:N), but exploitation is constrained by high attack complexity (the token must actually be guessed or predicted) and by the requirement that a legitimate KVM session already be in use (UI:R). It is not listed in CISA KEV, no public exploit code has been identified at time of analysis, and EPSS is 0.15% (4th percentile), consistent with a 'monitor' decision label and low real-world priority; the dominant limiting factor remains deployment, since BMC management interfaces are normally confined to an isolated management LAN.
Insufficient logging in Tanium Server branches 7.7.3, 7.8.2, and 7.8.4 can cause certain privileged operations to be incompletely recorded in audit logs, weakening forensic visibility and log integrity (CWE-778); the flaw requires high-privileged authenticated access (PR:H) and carries a low CVSS score of 2.7. No public exploit code has been identified at time of analysis, and Tanium has released fixed builds for all three affected branches.
A use-after-free memory-corruption flaw in the Tanium Threat Response Client Extension requires local access to a host plus pre-existing low-level privileges, and its worst outcome is partial availability loss of the client extension - no confidentiality or integrity impact. Tanium has released fixed builds across the Endpoint Configuration Toolset Solution (1.51, 1.59, 1.71 branches) and multiple threat-response-cx branches per advisory TAN-2026-068. This is a low-priority issue: no public exploit code, PoC reference, or CISA KEV entry is present in the available data, and the priority label is monitor.
Out-of-bounds write in Asterisk's T.140 RED generation accumulation can corrupt memory, crash the process, or potentially enable code execution, but only for deployments running the legacy chan_sip channel driver with the non-default textsupport option enabled and only by an authenticated attacker sending crafted packets. The vendor CVSS 4.0 score is 2.3 and the independent assessment treats exploitation as high-complexity with low confidentiality, integrity, and availability impact; no public exploit identified at time of analysis and the vuln.today priority is monitor.
Filesystem path disclosure in Tidewave Phoenix 0.8.0 through 0.9.1 lets a hostile web page read the framework's configuration tag - including the application root path, Mix dependency paths, project name and local port - either from the /tidewave/connect JSON response or from the toolbar meta tag injected into rendered HTML pages. Neither response validates the Host header, so a page that DNS-rebinds its own domain to the loopback address can retrieve the tag with a same-origin request, which carries no Origin header, exposing the developer's local username and project layout. The issue is unauthenticated per the CVSS vector but requires the victim to visit the attacker's page; impact is limited to low-sensitivity reconnaissance (confidentiality only, no code execution or access gain), no public exploit code was identified at time of analysis, and the vendor fix is version 0.9.2.
Memory corruption and denial of service in Asterisk's optional SMS dialplan application can be triggered when malformed SMS protocol data supplies length or user-data-header fields that overflow fixed in-struct buffers in app_sms.c. Asterisk 20.x through 20.20.0, 21.x through 21.12.2, 22.x through 22.10.0, 23.x through 23.4.0, and Certified Asterisk 20.7-cert10 and 22.8-cert2 and earlier are affected; exploitation requires the SMS application to be explicitly deployed (meaningful mainly for analog-device routing) and requires some authorized access to the SMS path, with the advisory also requiring that administrators have not ensured the data passed to the application is valid. The vendor has released fixed versions, the confirmed impact is a crash or memory corruption affecting availability, and no public exploit or active exploitation is identified at time of analysis, so the priority is monitor.
Memory exhaustion in the pageant crate's raw PageantStream transport affects versions 0.2.0 through 0.2.4: PageantStream::new reads a peer-supplied four-byte length prefix and buffers up to len + 4 bytes without checking it against the fixed 8 KiB _AGENT_MAX_MSGLEN transport limit, so a malicious SSH server can claim a frame of up to ~4 GiB and either stream that much data or stall mid-frame, keeping the partial buffer resident. Exploitation is narrowly scoped - Windows only, and only for applications that bridge an SSH forwarded-agent channel directly to the raw stream (e.g. copy_bidirectional); russh's typed AgentClient path bounds frames at 256 KiB and is not affected. The advisory includes a proof-of-concept that the reporter observed growing a pageant 0.2.4 process from ~7.4 MB to ~264.7 MB working set on Windows 11; the flaw is fixed in pageant 0.2.5, no CISA KEV entry or active exploitation is reported, and the priority label is monitor with an assessed CVSS 3.1 of AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L.
Heap buffer overflow in Asterisk's T.140 RED handling (res_rtp_asterisk.c) lets an authenticated attacker crash the PBX or potentially execute code, but only in deployments where the legacy chan_sip channel driver is installed and configured with its non-default textsupport option enabled. Exposure is sharply narrow because chan_sip was deprecated in Asterisk 20 and removed from all later release tracks, so only Asterisk 20.x and the Certified 20.7 and 22.8 branches are realistically exploitable; the trigger requires a valid authenticated session (PR:L) plus a non-default configuration. No public exploit code or CISA KEV entry is associated with this issue at time of analysis, and the reported CVSS 4.0 score is 2.3 with a 'monitor' priority label, consistent with a low-priority defect rather than an actively exploited one.
REDAXO backend sessions in versions up to and including 5.21.4 survive a password change: the fix in 5.21.5 shows that the current session id was not regenerated and, when 'stay logged in' was enabled, its stay-logged-in key was left valid for up to three months. An attacker who has already obtained the victim's PHP session id or stay-logged-in cookie through a separate vector - malware, a shared computer, or another flaw - therefore keeps backend access after the legitimate user changes their password, while only the user's other sessions are dropped. Both credentials live in HttpOnly cookies and theft of one is an explicit precondition, so this is a persistence weakness rather than an entry point; no public exploit code has been identified at time of analysis, exploitation is not confirmed and SSVC marks it non-automatable, and the vendor notes that simply logging out after the password change removes the session and its key.
Cross-origin information disclosure in the Vaadin Flow server-push endpoint allows a page on any origin to make a credentialed request to an authenticated user's push endpoint and read the response, because Flow configures Atmosphere with DROP_ACCESS_CONTROL_ALLOW_ORIGIN_HEADER set to false and its CorsInterceptor echoes the request Origin into Access-Control-Allow-Origin while permitting credentials. Exposure is narrow: only applications using @Push over a non-WebSocket (HTTP/long-polling) transport are affected, and reading anything useful beyond triggering the request also requires the target session's push identifier, which is why CVSS 4.0 scores the issue only 2.3 and the priority decision is 'monitor'. No public exploit code was identified at time of analysis and there is no KEV listing or EPSS score in the available data.
Reflected cross-site scripting in the REDAXO backend packages API affects core releases before 5.21.0, where the `function` request parameter is concatenated into an 'Unknown package function' exception message and rendered by rex_view::error() without HTML escaping. Exploitation is heavily constrained: the crafted request must carry a valid session-bound CSRF token for the packages API and the victim must follow the resulting backend link while logged in, so the vendor scores confidentiality, integrity and availability impact as low (CVSS 4.0 base 2.1; independent assessment CVSS 3.1 AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N). A proof-of-concept script that assembles the exploitation link is included in the GitHub security advisory, but it requires an already-valid backend PHPSESSID to harvest the token; the issue is not in CISA KEV and the vuln.today priority decision is monitor rather than act-now.
Reflected cross-site scripting in REDAXO core before 5.21.0 lets an attacker with an authenticated backend session and metainfo privileges craft a link that injects HTML through the type parameter, which rex_view::message() renders unescaped in a victim's backend session. Exploitation also requires a valid per-session CSRF token and a backend user who opens the crafted link; CVSS 4.0 score is 2.1, SSVC records no exploitation and automatable: no, the vuln.today priority label is monitor, and the independent assessment rates real-world risk low. A public PoC reference exists in the GitHub advisory but is not independently verified as working exploit code; REDAXO 5.21.0 fixes the issue.
Stored cross-site scripting in REDAXO 5.18.0 through 5.21.3 allows an authenticated backend user with mediapool upload or edit rights to leave a script-bearing SVG publicly served from /media/, where a victim who opens the raw file can execute script in the backend origin. The flaw is a move-before-sanitize ordering issue: the race path is explicitly unreliable, while the persistent path depends on the sanitizer exhausting memory_limit or max_execution_time, and backend-session impact also assumes a single-domain deployment where /media/ shares the backend origin. No public exploit was identified at time of analysis, CISA SSVC rates exploitation as none and automatable as no, the decision signal is monitor, and REDAXO 5.21.4 contains the vendor fix.
Inconsistent HTTP response framing in CPython's http.client allows a malformed Content-Length header or chunked chunk-size field - for example '+5', '5_0', '0x5', '1_f', '-5' or a leading-space value - to be accepted by Python's permissive int() parsing while a strict RFC 9112 peer rejects or frames it differently, so an application can misinterpret HTTP response contents. The exposure is limited to deployments where CPython below 3.16.0 parses responses that also traverse a strict intermediary such as a proxy or cache, and to applications that pass attacker-influenced responses into http.client (directly or via libraries built on it); the vendor's CVSS 4.0 score is 2.0 with only low integrity impact on the subsequent system and no confidentiality or availability effect, and the independent assessment likewise treats it as low priority. No public exploit code has been identified at time of analysis and there is no CISA KEV entry; the issue is rated 'monitor' in the vuln.today priority scheme.
Out-of-bounds write in Qt QTextCodec's iconv-based encoding path, exposed through the Qt 5 Compatibility APIs (qt5compat), can crash an affected application and may produce limited data-integrity effects when it encodes attacker-influenced text. Exposure is limited to applications built against qt5compat that use the iconv-based QTextCodec encoding path and fall within the listed Qt version ranges; the exact triggering condition is not described in available sources. The issue is assessed as low priority (decision label: monitor), with no public exploit identified at time of analysis and patch availability reported by the vendor.
Input validation bypass in dcmjs (npm package `dcmjs`) before 0.52.0 allows unauthenticated attackers to force Infinity or NaN into parsed DICOM DS (Decimal String) and IS (Integer String) numeric values by supplying scientific-notation overflow such as '1e999999' or a sign-only remnant produced when '-inf' is sanitized down to '-'. The corrupted numbers only cause harm where the downstream consumer - OHIF Viewer, Cornerstone.js or another DICOMweb pipeline built on dcmjs - fails to range-check parsed values, which the maintainer notes callers are expected to do regardless, so the practical severity depends on the host application rather than on dcmjs alone. Realistic outcomes are corrupted spatial geometry, windowing, rescale and dosimetry values, or frame-count overflow; no public exploit was identified at time of analysis and this CVE is not in CISA KEV, with the maintainer rating it low versus the reporter's 7.5 assessment.