Stored cross-site scripting in the Kirki WordPress plugin affects versions 6.0.0 through 6.3.0, which allow SVG files to be uploaded site-wide without sanitization; an authenticated user with Author-level access or higher can upload an SVG carrying embedded JavaScript that is then served from the site's own origin. When a victim - ideally an administrator - opens or views that file, the script runs in their session, giving the attacker same-origin script execution with high confidentiality and integrity impact (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H), and publicly available exploit code exists. This is a genuine but conditionally-gated stored-XSS priority rather than a mass-exploitation emergency: it requires an authenticated Author-level account and a victim interacting with the uploaded file, and it is fully mitigated by upgrading to 6.3.1.
Stored cross-site scripting in the Master Slider WordPress plugin (versions through 3.11.2) lets an authenticated user with the Contributor role or higher inject script payloads via unsanitised shortcode attributes that are written into an inline script when a post is rendered. The payload fires only when a victim - a higher-privileged user or any site visitor - views the affected post, so exploitation hinges on a crafted post combined with victim interaction; publicly available exploit code exists, though there is no confirmed active exploitation (no CISA KEV listing) and no vendor-released patch. Because lower-trust accounts on multi-author sites can typically create posts containing the ms_slider shortcode, the practical risk is concentrated on sites that grant Contributor access to untrusted users.
An authenticated user holding the quiz-import capability in the Forminator Forms WordPress plugin (versions 1.57.0 through before 1.57.2.1) can escalate to full site control by embedding a role-assigning registration form inside an imported quiz and publishing it, granting any role - including administrator - to anyone who submits the public form. The plugin enforces role validation in the ordinary form editor and ordinary form import paths but omits that check in the quiz-import code path, making the nested-quiz route the only viable bypass; the identical form is rejected through both normal routes. A vendor patch is available (1.57.2.1) and publicly available exploit code exists, so although the vendor scores this 6.6 (AC:H/PR:H), the assessed vector (AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:H) is materially higher given that a non-administrator with delegated import rights can achieve complete site compromise.
Unauthenticated attackers can invoke arbitrary registered shortcodes on WordPress sites running the Meow Gallery plugin before version 5.5.5, due to insufficient sanitization of a user-supplied value concatenated into a shortcode string on a publicly reachable endpoint. This allows disclosure of non-public gallery content, but does not permit code execution or availability impact; publicly available exploit code exists, and the vendor has released a patch (5.5.5).
Heap-based buffer overflow in Kamailio's CDP (C Diameter Peer) module allows a remote party that can deliver a malformed Diameter message to a peer socket to corrupt shared-memory (shm) heap state and potentially disrupt or compromise the process. Affected builds are Kamailio up to 5.8.8, 6.0.7, 6.1.4 and 6.2.0-dev1 that actually load the cdp module; SIP-only deployments are not exposed. Publicly available exploit code exists (referenced from a public GitHub issue, with the fix in PR 4877), and while the vendor's CVSS 4.0 base score is 5.5, an independent assessment scores it CVSS:3.1 7.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H), reflecting full availability impact on the affected process; no confirmed active exploitation (CISA KEV) was identified at time of analysis.
Path traversal in the create_file tool served by the 03-lovepreetSingh MCP application's /api/mcp route lets remote, unauthenticated attackers supply a crafted filePath that escapes the intended base directory and write attacker-controlled content to arbitrary locations on the host filesystem. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:N/I:H/A:L) reflects a high integrity impact with a limited availability impact, and publicly available exploit code exists via the project's own issue tracker (GitHub issue #3); there is no evidence of confirmed active exploitation (CISA KEV). Because the project is unversioned, the maintainer has not responded to the report, and no fixed release exists, the only realistic limit on real-world risk is deployment scarcity: this is a hobby MCP implementation with negligible confirmed production footprint, though any internet-reachable instance is trivially testable.
SQL injection in SourceCodester Online Reviewer Management System 1.0 allows remote attackers to alter SQL queries through the Course parameter of /reviewer_0/admins/assessments/course/btn_functions.php, enabling data disclosure along with limited integrity and availability impact. Publicly available exploit code exists via a GitHub PoC issue, but there is no evidence of active exploitation, and the feed CVSS 4.0 score of 6.9 overstates practical risk. The independent assessment rates this as LOW priority because the affected product is a niche educational PHP application with a single known version, negligible internet-facing deployment, and an unverified access-control prerequisite, consistent with an assessed CVSS 3.1 vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L.
Server-side request forgery in vas3k TaxHacker up to and including 0.8.5 lets an attacker who can reach the LLM-provider configuration function force the server to issue requests to an arbitrary URL of their choosing. The flaw lives in the testLLMProviderAction server action in app/(app)/apps/settings/actions.ts, where the attacker-supplied baseUrl is used as the destination of an outbound HTTP request without validation; publicly available exploit code exists and the project has not responded to the reported issue. Independent assessment places the realistic severity lower than the vendor's CVSS 4.0 score of 5.5: because TaxHacker is a self-hosted, login-gated application, practical exploitation requires an authenticated session and a working LLM-configuration screen, and the achievable impact is limited to confidentiality (reading responses from internal endpoints the server can reach) rather than code execution or data modification.
Server-side request forgery in NonceGeek dim-sum-app's Deno backend lets remote, unauthenticated attackers redirect outbound requests to an arbitrary host by supplying a crafted supabase_url query parameter to the textSearchV2Handler endpoint (deno/main.tsx). Because the handler builds a Supabase client from that attacker-controlled URL and passes the deployment's SUPABASE_SERVICE_ROLE_KEY as the credential, a successful attack both forces the server to issue requests to attacker-chosen destinations and discloses the service-role key to that endpoint, which in standard deployments can be leveraged for full privileged access to the backing Supabase project and, from there, potential impact on any data or services reachable with that key. The issue is confirmed with publicly available exploit code (disclosed via the project's GitHub issue tracker) but is not listed in CISA KEV, so no confirmed in-the-wild exploitation is established; the vendor has published a fix commit.
Server-side request forgery in vas3k TaxHacker up to 0.8.5 lets an attacker control the businessLogo argument passed to the generateInvoicePDF function in /apps/invoices/actions.ts and force the server-side invoice PDF renderer to fetch an arbitrary URL. The independent assessment rates this as moderate severity (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), with exploitation requiring an account on the self-hosted instance that can configure business branding and trigger invoice generation, rather than an anonymous internet attacker. Publicly available exploit code exists, the issue was reported to the project early via GitHub issue #186 without a vendor response, and no CISA KEV listing was identified - impact is limited to low confidentiality, integrity, and availability with no code execution.
The certificate validation route in Nginx Proxy Manager through 2.15.1 (internalCertificate.validate in backend/internal/certificate.js) is reachable without authentication, letting any remote caller submit arbitrary certificate material to the backend. Publicly available exploit code exists, but the project has not responded to the early issue report, so no fixed release is confirmed; the practical impact is constrained because the endpoint parses and echoes back only the certificate the caller supplied rather than returning stored data, leaving malformed-input handling in the OpenSSL parsing path as the main residual concern. As our independent assessment notes, this is a moderate-priority issue and the raw 6.9 CVSS 4.0 score somewhat overstates the real-world risk.
SQL injection in SourceCodester Online Reviewer Management System 1.0 lets remote attackers inject arbitrary SQL through the courseID argument handled by /reviewer_0/admins/assessments/course/btn_functions.php, giving read access to backend data and limited ability to modify or disrupt it (integrity and availability impact rated Low, confidentiality High in our independent assessment). Publicly available exploit code exists - a proof-of-concept has been published via the GitHub issue referenced by VulDB - and the vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) claims unauthenticated, no-interaction exploitation. Despite the 6.9 score, real-world risk is bounded: exploitation requires that the script be reachable, and because it lives under an /admins/ directory, practical unauthenticated access depends on the deployment lacking a session or authorization guard on that path, a common but unverified trait of SourceCodester projects. No CISA KEV entry or confirmed in-the-wild exploitation was identified at time of analysis.
SQL injection in SourceCodester Drug Recommendation System 1.0 lets a remote attacker manipulate the SQL query behind /drug_recommender/Admin/edit_user.php by tampering with the ID parameter, enabling unauthorized read and modification of backend data. The vulnerability carries a publicly available exploit (proof-of-concept published on GitHub), so exploitation is trivial for anyone who can reach the endpoint, though no confirmed active exploitation (CISA KEV) has been reported. Scoring is split: the CNA/VulDB vector rates it CVSS 4.0 at 6.9 with PR:N, while our independent assessment scores it CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, because the /Admin/ path strongly suggests an authenticated administrative session is normally required, which markedly reduces the realistic attack surface and real-world priority despite the alarming-looking technical impact.
SQL injection in SourceCodester Drug Recommendation System 1.0 allows remote attackers to manipulate the ID parameter in /Admin/edit_symptom.php, causing the application to execute attacker-influenced SQL against its backend database and potentially read or alter symptom records. Publicly available exploit code exists, but there is no CISA KEV confirmation of active exploitation; independent assessment treats this as a lower real-world priority because the /Admin/ endpoint is normally protected by an admin login and the product's deployment base is very small. The vendor's CVSS 4.0 vector rates it 6.9 with PR:N, while the independent CVSS 3.1 assessment requires admin-level authentication (PR:L) and assigns high confidentiality and integrity impact with limited availability impact.
SQL injection in the Admin Login Form of Code-Projects Internship Management System 1.0 lets remote attackers manipulate the Password parameter of /admin/login.php to inject arbitrary SQL into the backend database query. Per the CVSS 4.0 vector the flaw is reachable without authentication (PR:N, AV:N, AC:L), and publicly available exploit code exists - a public proof-of-concept write-up is referenced in the CVE record - so exploitation requires no special conditions against a default installation. The practical risk is tempered by deployment scarcity: this is an obscure open-source PHP student-style project that is rarely exposed on production internet-facing hosts, and there is no indication of confirmed active exploitation (not listed in CISA KEV).
Unauthenticated SQL injection in the /employer/login.php login form of code-projects Internship Management System 1.0 lets remote attackers inject arbitrary SQL through the Password parameter, potentially reading or altering the underlying database. The flaw is remotely reachable without credentials or user interaction, and publicly available exploit code exists (VulDB-reported, with a public PoC write-up linked from the CVE record); no CISA KEV listing indicates confirmed active exploitation. Although the independent assessment rates the technical severity as high (CVSS 3.1 8.3-adjacent vector: AV:N/AC:L/PR:N/UI:N with high confidentiality and integrity impact), real-world priority is low because the application is a niche, code-projects.org PHP teaching/demo system with a very small internet-facing deployment footprint.
Unauthenticated SQL injection in the /login.php login form of code-projects Internship Management System 1.0 allows remote attackers to manipulate the Password parameter and inject arbitrary SQL into the backend query, with public exploit code already available (no CISA KEV confirmation of active exploitation). The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) and the independent 3.1 assessment (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L) both confirm this is a pre-authentication, network-reachable flaw requiring no credentials and no user interaction, which materially raises risk versus a post-auth injection. Practical exposure is limited mainly by prevalence: this is a niche hobbyist-style PHP project, and successful data extraction depends on the backend DBMS and query structure, so exploitation in the wild against internet-facing production deployments is plausible but constrained.
SQL injection in SourceCodester Online Reviewer Management System 1.0 allows remote attackers to manipulate the ID parameter of /reviewer_0/admins/assessments/subject/btn_functions.php?action=remove and execute attacker-controlled SQL against the application's backend database, potentially exposing or altering stored records. Publicly available exploit code exists (a public proof-of-concept referenced from VulDB and a public GitHub issue), which lowers the skill barrier, but there is no confirmed actively exploited (CISA KEV) status and no EPSS estimate was supplied. Impact is bounded rather than catastrophic: the vendor vector rates confidentiality, integrity and availability impact as low (VC:L/VI:L/VA:L, E:P), and our independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L - a classic low-real-priority SQL injection for a niche PHP project despite a mid-range base score, with the main open question being whether the administrative script is actually reachable without a valid admin session.
Unauthenticated attackers can tamper with arbitrary bookings on any internet-reachable WordPress site running the Tripzzy plugin in versions 1.3.4 through 1.5.0, because its administrative booking-management actions perform no capability or ownership checks and are gated only by a token the plugin hands to any anonymous visitor on request. Exploitation allows alteration of booking contents, stored totals, and notes (integrity impact only; no confidentiality or availability impact was assessed), and publicly available exploit code exists - the WPScan entry is tagged as an exploit reference. No special configuration is required, no credentials or user interaction are needed, and there is no indication of confirmed active exploitation in CISA KEV at the time of analysis; EPSS data was not provided.
Sign-up Sheets WordPress plugin versions before 2.4.0 allows an attacker to delete sign-up records via a forged cross-site request when a logged-in user with deletion privileges is tricked into loading a malicious link or page. The vulnerability (CWE-352) has publicly available exploit code, and a vendor patch is available in version 2.4.0. Exploitation requires user interaction and a victim with the appropriate capability, resulting in only a low integrity impact (CVSS 4.3).
Improper authorization in the WordPress plugin Photo Gallery, Sliders, Proofing and Themes before version 4.5.0 lets a user who has been granted the plugin's gallery-management capability delete, copy, and re-tag images that belong to other users' galleries. The flaw is an IDOR-class (CWE-639) authorization bypass that requires an authenticated WordPress account already holding that capability (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L per our independent assessment; the published score is 4.2 with a more conservative AC:H vector), so anonymous visitors cannot reach it. Publicly available exploit code exists (WPScan), but there is no confirmed active exploitation (CISA KEV) and vendor-released patched version 4.5.0 is available.
Server-side request forgery in the WordPress plugin Import and Export Users and Customers (versions before 2.4.5) causes the server to fetch an attacker-supplied URL during a CSV import because the plugin fails to validate that URL before making the request. Exploitation is gated behind a high-privileged, authenticated WordPress user with the capability to run the plugin's user/customer CSV import (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N), so a successful attack yields read-only SSRF probing and limited data reflection rather than code execution or data modification. Publicly available exploit code exists, but there is no confirmed active exploitation (CISA KEV), and the practical impact depends entirely on whether internal services or a cloud metadata endpoint are reachable from the web server - making this a genuinely low-priority issue.
Unauthenticated username enumeration in Dromara UJCMS through version 12.3.1 allows remote attackers to query the UserController username-existence endpoint and determine whether a given account name is registered on the target site, leaking account information without any credentials, user interaction, or special configuration. The independent assessment rates this as a low-impact confidentiality leak (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), whose practical value lies in feeding follow-on password-guessing or credential-stuffing campaigns against confirmed accounts rather than in direct compromise. No public exploit code has been identified at time of analysis and the vulnerability is not confirmed as actively exploited (no CISA KEV listing); the vendor was notified via a GitHub issue but has not responded, so no fixed release is available.
Hardcoded default secrets and credentials in aiyiyi121 SxDevOps 1.0/1.1 let unauthenticated remote attackers obtain sensitive information from instances that still run the shipped defaults - a Django SECRET_KEY of 'change-me' and the documented demo/admin password (for example Admin@123456) published in the project README. The issue is CWE-200 (exposure of sensitive information), rated CVSS 4.0 6.9 with confidentiality-only impact; no public exploit code has been identified at time of analysis, and any operator who set a strong SECRET_KEY, changed the admin/demo password, or disabled the demo accounts before exposing the service is not affected, so realistic risk is confined to negligently configured default installs of a niche self-hosted tool. The vendor was contacted early and issued a fix in commit 2b4bf8585c3e731e7a8af30801ea46680bc783f9.
Hard-coded default superuser credentials in aiyiyi121 SxDevOps 1.0/1.1 let unauthenticated remote attackers log in to the management/API interface as a superuser, because the shipped password (Admin@123456, published in the project's own README) is generated by ensure_default_superuser in rbac/services.py and is never forced to be changed. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N, VC/VI/VA:L) confirms no authentication or user interaction is required and that the attack is network-reachable; our own assessment rates the true impact higher (C/I/A:H) since a superuser session yields full control of managed hosts and tasks, limited only by whether the operator changed the default after initialization. The vendor has published a fix commit and states a corrected version was released; no public exploit code was identified at time of analysis, but exploitation requires no tooling beyond the documented credential, and there is no CISA KEV listing for this issue. EPSS data was not provided.
SxDevOps 1.0 and 1.1 seed demo and administrator accounts with a hard-coded default password ('Admin@123456') that is also documented in the project README, letting an unauthenticated remote attacker who can reach the login interface sign in with full administrative privileges. The flaw is only exploitable on deployments that were initialized with the demo accounts and where the password was never rotated or the accounts disabled before exposing the service; instances that set SXDEVOPS_DEMO_PASSWORD/SXDEVOPS_ADMIN_INITIAL_PASSWORD or applied the vendor fix are not affected. No public exploit code was identified at time of analysis, and the vendor has published a fixing commit (2b4bf8585c3e731e7a8af30801ea46680bc783f9).
Unauthenticated attackers can disable self-service password recovery in NivoCart through 2.4.0 by sending a GET request with a missing or invalid code parameter to the admin password-reset controller, causing the application to set config_password to 0. The impact is limited to a reversible denial of the password recovery feature; no authentication bypass, data exposure, or code execution occurs, and independent assessment rates this as low priority (CVSS 3.1 base 5.3). No public exploit identified at time of analysis.
Local, low-privileged attackers can delete arbitrary files with SYSTEM privileges on Windows hosts running WatchDog Antivirus 1.8.640 with the wsdkd.sys driver version 1.3.0.0 or earlier by sending crafted IOCTL requests to the \Device\wsdk device. This missing authorization flaw bypasses NTFS access controls, potentially allowing attackers to disable security products or destabilize the operating system. No public exploit has been identified at time of analysis, and the vendor has not confirmed active exploitation; the risk is a moderate local privilege-escalation-class issue.
Authentication bypass in the Tencent BrowserSkill local WebSocket daemon (bsk-cli, through v0.3.0) allows any installed browser extension that presents a syntactically valid 32-character Chrome extension ID to register as a client and intercept or manipulate the page content, DOM, and screenshots returned to the AI agent. The root cause is a missing origin allowlist (CWE-346) rather than a memory-safety bug, so exploitation is limited to hosts where a hostile extension can be loaded into the browser and the daemon is running - reflected in the assessed CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N with high integrity impact (I:H) and low confidentiality/availability impact, and in the supplied CVSS 4.0 score of 6.9. No public exploit code was identified at time of analysis, the issue is not listed in CISA KEV, and the overall risk is best characterized as a moderate, locally-scoped integrity risk rather than a widespread emergency.
The ZTE SmartLife client application ships with a hardcoded cryptographic key stored in plaintext within its code, allowing anyone who obtains and reverse-engineers the app package to recover the key and decrypt the embedded account-server information. Exploitation is local in nature - the attacker must first acquire the application binary and perform static analysis - and what is exposed is backend account-server configuration data rather than per-user credentials. No public exploit code or confirmed active exploitation has been identified at time of analysis; the vendor scores this 6.2 with high confidentiality impact, while independent assessment rates confidentiality impact as Low, framing this as a defense-in-depth weakness rather than an urgent, remotely-weaponizable flaw.
Improper default filesystem permissions in WatchDog Anti-Virus for Windows let any local, low-privileged user take over the installation directory, because the default installer grants the Users group Full Control over C:\Program Files (x86)\Watchdog Anti-Virus. That access alone is enough to disable protection by deleting or rewriting antivirus binaries and configuration files, and it can escalate to privileged code execution if a tampered binary is subsequently loaded by an elevated WatchDog process, for example after a service restart, scheduled scan, or update cycle. The flaw requires an existing local user account (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; vendor CVSS 4.0 base 5.9, PR:L) and is confined to hosts still running the affected installer build; no public exploit code was identified at time of analysis, and WatchDog's release notes reference the corrected build.
A race condition in the Free5GC AMF network function, affecting releases up to and including 4.2.3, allows remote attackers to interleave GMM/NAS signalling with SCTP-association teardown so that concurrent unsynchronised access to the AmfUe.RanUe map occurs, which in Go produces a fatal "concurrent map read and map write" runtime error and crashes the AMF, disrupting UE registration and NAS transport for all attached subscribers. Both the supplier's CVSS 4.0 vector (6.9) and our independent assessment treat the flaw as unauthenticated (PR:N) but timing-dependent, with reach limited to the private 5G control plane - a malicious or compromised gNB, or a UE capable of driving registration/transport signalling over the N2 interface - rather than the public internet, and only availability is demonstrably impacted (C:N/I:N/A:H); the supplied "Information Disclosure" tag is not substantiated by the code path. No public exploit was identified at time of analysis (the supplier vector's E:P value reflects proof-of-concept-level maturity only), and an upstream fix is available as commit e323b01464355781b8b8d5dd695e05cbc00a62f2 (PR #238) that serialises RanUe access behind a sync.RWMutex.
SQL injection in SourceCodester Online Reviewer Management System 1.0 allows remote attackers to manipulate the ID parameter of /reviewer_0/admins/assessments/databank/btn_functions.php?action=remove, potentially altering backend database queries. The endpoint resides under the administrative /admins/ path and likely requires an authenticated administrator session (independent assessment PR:L), despite the vendor's CVSS 4.0 vector listing PR:N; a public proof-of-concept exploit has been published and publicly available exploit code exists, though no confirmed active exploitation (CISA KEV) is reported. The vendor CVSS 4.0 base score is 5.5 with an E:P temporal indicator.
Code injection in DedeCMS through version 5.7.118 lets remote, unauthenticated attackers manipulate the 'aid' argument handled by plus/mytag_js.php to inject attacker-controlled code into the application's processing path, with the vendor-scored impact limited to low confidentiality, integrity and availability effects. A public exploit for this issue exists, so any internet-reachable installation that still exposes the plus/ auxiliary scripts should be considered at risk of opportunistic scanning and exploitation; CISA KEV does not list this CVE, indicating no confirmed active exploitation at time of analysis. Because the technical impact is constrained rather than a full compromise chain, this is a moderate-priority hardening item rather than an emergency patch-and-isolate scenario.
ZTE SmartLife's backend signup interface (/account/person/signup.serv) creates accounts for arbitrary email addresses without verifying that the requester owns the address, so an attacker who has extracted the app's runtime-generated authentication parameters can complete registration against any email string. The assigned vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, 4.3) and our independent assessment agree on moderate severity: the primary barrier is first obtaining the client-generated app authentication parameters - obtainable via reverse engineering or traffic interception and reflected as PR:L - with no per-victim credentials, user interaction, or non-default configuration required and the endpoint network-reachable. No KEV entry and no public exploit identified at time of analysis, so real-world urgency is genuinely low, though the integrity impact on account/identity assurance is real anywhere the platform subsequently trusts the registered email for identity, notifications, or recovery.
Command injection in SxDevOps 1.0 and 1.1 allows a high-privileged, authenticated operator to escape intended command restrictions when running TASK_RUN_COMMAND host tasks, because the user-supplied 'command' value is passed without neutralization to paramiko.SSHClient.exec_command in backend/ops/host_tasks.py (CWE-77). Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L) the attacker must already hold a role permitted to create and execute host tasks, so the practical gain is bypassing command constraints via shell metacharacters (';', '&&', '||', '|', '$(', backticks, newlines) rather than obtaining access the operator lacks. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor shipped a fix (commit 2b4bf8585c3e731e7a8af30801ea46680bc783f9) after being contacted early in the disclosure process.
Command injection in SxDevOps 1.0 and 1.1 lets an authenticated user who can manage MCP STDIO server configurations run arbitrary operating-system commands on the host by supplying shell metacharacters in the endpoint_or_command field, which is passed unchecked to subprocess.Popen. Exploitation requires high privileges (CVSS PR:H) because the attacker must be able to create or modify MCP STDIO server entries, and the feature must be reachable on an unpatched 1.0/1.1 build; there is no public exploit identified at time of analysis and no confirmed active exploitation. The issue is rated moderate by the independent assessment (CVSS:3.1 base 7.2) and is fixed upstream in commit 2b4bf8585c3e731e7a8af30801ea46680bc783f9, which the vendor released after being contacted.
Integer underflow in the PE parser of Manalyze 1.0.0 (PE::_parse_debug in manape/pe.cpp) can be triggered when the tool processes a crafted Portable Executable whose IMAGE_DEBUG_MISC debug-directory entry declares a Length smaller than the misc structure header, causing the computed string length to wrap to a very large unsigned value and the parser to read beyond the intended buffer. Exploitation is not remote in practice: it requires a local user (typically a malware analyst) to voluntarily run the unpatched Manalyze CLI against the malicious sample, so the assessed risk is low (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L), with impact largely confined to the parsing process - the tag 'Information Disclosure' reflects the out-of-bounds read potential rather than confirmed data exfiltration. No public exploit code and no active exploitation have been identified at time of analysis, and an upstream fix commit (3e299685759f4f767088871de58c5d07f98ee382) is available.
Information disclosure in D-Link DIR-X1860Z routers running firmware up to 1.0.2.220120.165402 lets unauthenticated users on the same local network segment read sensitive data through two ubus JSON-RPC handlers, routerd.wificfg_get and routerd.get_rand_key. The bug is reachable only from the adjacent network (LAN, guest WiFi, or a compromised local device) and carries low confidentiality impact with no integrity or availability effect, and no public exploit identified at time of analysis. D-Link ships a HOTFIX firmware (1.0.7.260821.161908) that resolves the issue, but the DIR-X1860Z is an end-of-life product, so exposure is concentrated on unpatched units still in service.
Authenticated command injection in SxDevOps 1.0/1.1 lets a signed-in user with host-task/command-generation rights defeat the platform's built-in dangerous-command filter and have arbitrary shell content reach managed hosts through the Command Handler (generate_host_task in backend/aiops/services.py). The pre-patch filter relied on substring matching of strings such as 'rm -rf', 'shutdown' and 'reboot', so shell metacharacters (; && || | backtick $() and newlines) could be smuggled into the 'command' argument to chain or substitute commands. Exploitation requires valid credentials plus at least one managed host configured to receive tasks, and no public exploit code has been identified at time of analysis; the vendor was contacted early and shipped a fix under commit 2b4bf8585c3e731e7a8af30801ea46680bc783f9, making this a lower-priority safety-filter bypass rather than an unauthenticated takeover, consistent with the independent assessment scoring it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L.
Local privilege escalation in WatchDog Anti-Virus 1.8.640 on Windows lets an unprivileged local user redirect the quarantine restoration workflow so a quarantined file is written to an attacker-chosen filesystem location, by planting an NTFS directory junction at the file's original path before an administrator triggers a restore. The defect is root-caused as improper link resolution before file access (CWE-59); the vector requires local access (PR:L in the CVSS 4.0 vector) and an administrator actively performing the restore (UI:A), so the privileged write cannot be triggered by the attacker alone. Successful exploitation can overwrite protected files and, with a well-chosen target path, support DLL hijacking for SYSTEM-level code execution, but there is no indication of active exploitation, no CISA KEV listing, and no public exploit code identified at time of analysis; this is treated as a genuine but conditional local privilege-escalation issue rather than an urgent remote threat.
Improper privilege management in SxDevOps 1.0/1.1 allows an authenticated user to escalate their own privileges by manipulating the update path of the UserSerializer in backend/rbac/serializers.py, reachable remotely over the network against the RBAC user-update API. The vulnerability is rated medium (CVSS 4.0 base 5.1, AV:N/AC:L/PR:H/UI:N/VC:N/VI:L/VA:L), with the main impact being integrity of role/permission data; a public exploit has not been identified at time of analysis and there is no CISA KEV listing. The vendor was contacted early, responded promptly, and published a fix in commit 2b4bf8585c3e731e7a8af30801ea46680bc783f9, so patched deployments are no longer exposed.
Information disclosure in ZTE SmartLife allows an attacker who can extract the app's runtime-generated application authentication parameters to query the backend /account/verify.serv endpoint, confirm whether a target email address is registered, and retrieve the corresponding real backend account ID. The independent assessment treats the issue as network-reachable and unauthenticated from the backend's perspective because those parameters are obtainable by running or reverse-engineering the SmartLife client, though the practical impact is limited to email enumeration and account-ID leakage in ZTE's SmartLife ecosystem, not a full privilege escalation. No CISA KEV entry and no public exploit were identified at time of analysis.