NukeViet CMS is a multi Content Management System. From the 3.x release line until 4.6.01, an unauthenticated visitor can submit a Contact module message containing an event-handler attribute prefixed by a slash. NukeViet\Core\Request::filterTags() tokenizes attributes using only ASCII spaces, so it sees /onerror and misses the ^on denylist, while the browser treats the slash as a separator and activates onerror. The message is stored and rendered without output encoding in the administration panel, which lacks a Content Security Policy, allowing same-origin JavaScript execution when an administrator opens the message. This issue is fixed in version 4.6.01.
NukeViet CMS versions from 4.5.00 up to but not including 4.6.01 contain a path traversal vulnerability in the smimeadd handler of the settings module. An authenticated administrator can upload a PKCS#12 S/MIME certificate with an X.509 Subject CN containing path traversal sequences, allowing overwriting of certificate files outside the intended directory. This can lead to overwriting critical assets such as DKIM private keys and, if curl.cainfo is empty, the cacert.pem file, potentially undermining TLS verification. The issue is fixed in version 4.6.01.
NukeViet CMS versions 4.6.00 to before 4.6.01 contain a server-side request forgery (SSRF) vulnerability. An unauthenticated attacker can manipulate the X-Forwarded-Host header to cause the system to send requests to attacker-controlled internal hosts, ports, and paths. This issue allows invocation of internal HTTP endpoints and is fixed in version 4.6.01.
libumqtt is vulnerable to an integer underflow which may allow a remote attacker to cause a denial of service, memory corruption, or information disclosure.
NukeViet CMS is a multi Content Management System. Prior to 4.6.01, a super-administrator satisfying the NV_IS_SPADMIN gate can use modules/users/admin/fields.php to store an arbitrary existing PHP function in the func_callback setting for a custom profile field because the callback name is checked only with function_exists() and no allowlist restricts which function may be selected. modules/users/fields.check.php later invokes that function through call_user_func() when the field is validated through registration, profile editing, or administrator editing. Selecting a command-execution function crosses the super-administrator to operating-system boundary and executes commands as the web-server account, while ordinary users can trigger the stored callback after it is configured. Because the remediation validates callbacks only when they are written, upgrading does not remove a malicious callback already stored in the database, which must be cleaned manually. This issue is fixed in version 4.6.01.
NukeViet CMS is a multi Content Management System. In 4.6.00, an unauthenticated attacker can rotate X-Forwarded-For because vendor/vinades/nukeviet/Core/Ips.php accepts forwarded client-IP headers without first confirming that REMOTE_ADDR is a trusted proxy. The resulting NV_CLIENT_IP keys the administrator login blocker in includes/core/admin_login.php; changing only the header value bypasses that lockout and permits effectively unlimited password guesses. The same spoofable address is also consumed by the user login blocker in modules/users/funcs/login.php, IP restrictions, bans, flood controls, and security logs, but those additional code-level effects were not dynamically demonstrated. This issue is fixed in version 4.6.01.
Improper limitation of a pathname to a restricted directory in the file access checks in Amazon awslabs.document-loader-mcp-server 1.0.10 through 1.0.20 might allow a context-dependent actor, via crafted document content processed by an MCP client, to read files outside the intended base directory and, in 1.0.12 through 1.0.20, to write PNG slide images outside it. This occurs when DOCUMENT_BASE_DIR is not set or is empty and the CI, GITHUB_ACTIONS or PYTEST_CURRENT_TEST environment variable is present. Versions before 1.0.10 do not restrict file access to a base directory.
To remediate this issue, users should upgrade to version 1.0.21 or later. Users who cannot upgrade immediately can set DOCUMENT_BASE_DIR to the directory that holds their documents. Do not set it to /, which removes the restriction.
NukeViet CMS is a multi Content Management System. Prior to 4.6.00, a network attacker who can alter outbound traffic to the extension store can exploit the HTTP client's disabled sslverify setting to substitute a serialized response. Extension-store handlers pass the response to unserialize() without an allowed_classes restriction, allowing an in-tree GuzzleHttp\Cookie\FileCookieJar gadget to write attacker-controlled content to a chosen path. When a GODADMIN opens or uses the store list, detail, install, or update functions, the substituted response can write a PHP file under the web root and execute code as the web-server user. This issue is fixed in version 4.6.00.
NukeViet CMS versions prior to 4.5.09 contain a persistent cross-site scripting (XSS) vulnerability. This flaw allows users with news-posting permissions to bypass input filtering by exploiting differences in how PHP and browsers handle certain characters in event-handler attributes and javascript: URIs. The vulnerability enables execution of malicious scripts for visitors, including administrators. The issue is resolved in version 4.5.09.
CVE-2026-54065 is a path traversal vulnerability in NukeViet CMS versions prior to 4.5.09. An authenticated administrator can exploit this flaw by submitting a crafted attach value that bypasses validation, allowing traversal paths to be stored in the database. When a comment is deleted, this can lead to deletion of critical application files such as config.php, causing service outage. The issue is fixed in version 4.5.09.
NukeViet CMS is a multi Content Management System. Prior to 4.5.09, the Comment module accepts attacker-controlled base64 content in the status_comment parameter through modules/comment/funcs/main.php; modules/comment/comment.php decodes it with nv_base64_decode() and assigns it to STATUS_COMMENT without output escaping. The required checkss token was derived from the site-wide NV_CACHE_PREFIX rather than NV_CHECK_SESSION, so a token disclosed in public comment markup could be reused across sessions in a crafted URL. An unauthenticated attacker can therefore cause decoded HTML or JavaScript to render in a victim's browser and perform phishing or same-origin actions. This issue is fixed in version 4.5.09.
NukeViet CMS versions prior to 4.5.09 contain a stored cross-site scripting (XSS) vulnerability in the first_name and last_name profile fields. A low-privileged authenticated user can inject script-breaking content that is used in comment display names. This leads to execution of attacker-controlled JavaScript when a visitor clicks the Reply link in comments, potentially compromising administrator sessions. The vulnerability is fixed in version 4.5.09.
NukeViet CMS is a multi Content Management System. Prior to 4.5.09, an unauthenticated attacker can submit the __serverInfoUpdate=1 field while controlling X-Forwarded-Host and X-Forwarded-Proto. NukeViet\Core\Server::standardizeHost() did not validate the forwarded host against my_domains, and a trailing slash could preserve an attacker-selected port that server_info_update() used to construct a cURL request in includes/ini.php before authentication. The blind, HEAD-only request uses a fixed path, but it permits internal host and port discovery and can poison cached server_headers. This issue is fixed in version 4.5.09.
MONAI Label versions up to 0.8.5 contain a path traversal vulnerability via the image parameter in the PUT /datastore/image endpoint. This flaw allows attackers to perform directory traversal, potentially leading to remote code execution. The vulnerability has a critical severity with a CVSS score of 9.8. Exploitation in the wild was reported starting in September 2026.
The WPvivid Backup, Migration & Staging plugin for WordPress versions up to and including 0.9.134 contains an arbitrary file deletion vulnerability. This arises from a timing side channel in RSA decryption, insufficient validation of migration receiver backup records, and missing path validation in the cleanup_local_backup() function. An unauthenticated attacker with access to an unexpired receiver key can inject a backup record with path traversal, causing scheduled cleanup to delete arbitrary files writable by the web server.
The GiveWP WordPress plugin is vulnerable to a Cross-Site Request Forgery (CSRF) flaw in all versions up to and including 4.16.7.2. This vulnerability arises from missing nonce validation in the give_render_donor_view() function, allowing unauthenticated attackers to reassign donor records to arbitrary WordPress users if a site administrator is tricked into clicking a malicious link. This reassignment changes donor-account ownership and can enable a related account takeover vulnerability (CVE-2026-82675).
The GiveWP Donation Plugin for WordPress up to version 4.17.0 contains a vulnerability that allows unauthenticated attackers to reset the password of any WordPress account linked to a donor record. This occurs because the plugin does not properly validate donor identity before updating linked WordPress account passwords. Exploiting this flaw can lead to full site compromise and remote code execution if the targeted account has administrator privileges. The attack requires a published GiveWP form with a usable gateway, enabled donor email access (default setting), knowledge of the donor's email address, and an existing linked account. This vulnerability can be combined with CVE-2026-82676 to facilitate administrator account takeover.
A vulnerability in WhatsApp for Android and WhatsApp Business for Android before version 2.26.17.4 involves incomplete validation of external ad-reply URLs. This flaw could allow an attacker to cause a target device to reveal its IP information by sending media from an attacker-controlled URL within a crafted Click to WhatsApp ad-reply message. The issue may have been exploited alongside specific spam messages. The CVSS score is 3.5, indicating a low severity impact.
A vulnerability in the quarkus-rest-jsonb component of Quarkus allows an unauthenticated remote attacker to cause a Denial of Service (DoS) by sending HTTP requests with deeply nested JSON payloads. This triggers excessive logging of large error traces, which can exhaust disk space or overwhelm log processing, degrading service availability. The impact is limited to availability degradation without affecting confidentiality or integrity. No patch or mitigation meeting Red Hat's criteria is currently available. The vulnerability affects deployments using JSON-B with flexible or recursive types, while those using other serialization frameworks or strict schemas are not vulnerable.