Information disclosure in Frappe ERPNext before 15.121.0 and 16.x before 16.34.0 lets any authenticated user with a low-privilege account read billable timesheet records they are not authorized to see, via the whitelisted endpoints get_projectwise_timesheet_data, get_timesheet_detail_rate, and get_timesheet. The affected code paths ran raw SQL that skipped Timesheet and Project doctype permission checks, exposing project names, billing amounts, currencies, activity types, and free-text work descriptions. Exploitation requires a valid ERPNext session (PR:L) but no admin rights, user interaction, or special configuration; there is no public exploit identified at time of analysis, and the assessed impact is confidentiality-only (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) with no data modification or denial of service.
Authenticated WordPress users who hold only the gallery-management capability of the plugin Photo Gallery, Sliders, Proofing and Themes can save site-wide image-sizing settings they are not entitled to change, because versions before 4.5.0 omit a capability check before writing those options. Only sites running the plugin at a version below 4.5.0 are affected, and the attacker must already have been granted the delegated gallery-management role by an administrator - this is a privilege-boundary erosion between two internal roles, not an unauthenticated compromise, and the impact is limited to the integrity of image-sizing configuration (no data disclosure, no availability loss). Severity is genuinely low (CVSS 3.1, assessed vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), and publicly available exploit code exists; there is no CISA KEV listing and therefore no confirmation of active exploitation in the wild.
Authenticated users who have been granted the plugin's gallery-management capability can overwrite the stored settings of any gallery on a WordPress site running the 'Photo Gallery, Sliders, Proofing and Themes' plugin before 4.5.0, including galleries belonging to other users and each gallery's stored filesystem path, because the save routine never checks that the submitted gallery ID belongs to the requesting account (CWE-639, IDOR). Impact is integrity-only and rated Low (CVSS 3.1); the flaw is not reported as actively exploited, but publicly available exploit code exists, and the vendor has released 4.5.0 to correct it. Note that the attacker is not an anonymous visitor - the actor must already hold a capability an administrator deliberately delegated, and must know the IDs of galleries they do not own.
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.
Information disclosure in the Meow Gallery WordPress plugin before 5.5.5 lets authenticated users holding Author-level access or higher pull back metadata - titles, authors, dates and publish statuses - belonging to other users' draft and private posts. The vulnerable post-data retrieval routine performs neither a proper capability check nor owner-scoping of results, so a low-trust Author account on a multi-author site can enumerate unpublished content it was never meant to see; post bodies themselves are not exposed and there is no write, modify or denial-of-service impact. A publicly available exploit code exists, but the flaw is not confirmed actively exploited (no CISA KEV listing), and the risk is genuinely low-priority: it is not reachable by anonymous visitors, requires a valid Author-or-higher login (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N in our assessment), and matters mainly on sites where lower-trust Author accounts coexist with genuinely sensitive unpublished material.
Missing object-level authorization in the Photo Gallery, Sliders, Proofing and Themes WordPress plugin before 4.5.0 allows authenticated users with the Contributor role or higher to read the stored metadata of any image on the site, including images that belong to other users' galleries; publicly available exploit code exists. Exploitation requires an authenticated Contributor+ account on a site running an affected version (3.59.5 through 4.5.0), needs no user interaction or special configuration, and is impossible for anonymous visitors, which caps the practical impact at low confidentiality loss. The disclosed data is limited to the image's stored EXIF subset (camera make and model, capture timestamp) plus internal checksums and identifiers that the plugin's own capability-gated read path normally reserves for administrators, so no image files, credentials, or user PII are exposed and overall priority is minor.
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.
Path traversal in 0215AndrewFeng ACE-MCP through 4.10.8 lets an authorized MCP tool client read arbitrary files from the host via the get_file_snippet tool: the attacker supplies both projectRootPath and filePath, and because projectRootPath is treated as trusted, setting projectRootPath=/etc with filePath=hosts satisfies the isPathInsideProjectRoot guard and exposes /etc/hosts. Exploitation requires the ability to invoke the MCP server's tool interface (authenticated, CVSS PR:L), needs no user interaction or special server configuration, and yields read-only confidentiality impact (no write or code execution). Publicly available exploit code exists and the issue was reported to the vendor, which has not responded or shipped a fix; the independent assessment rates confidentiality impact High, materially higher than the 2.1 CVSS 4.0 base score in the report, and no CISA KEV entry indicates confirmed active exploitation at time of analysis.
Server-side request forgery in Mealie up to 3.25.1 lets an authenticated user with permission to create or edit Recipe Actions coerce the server into making outbound HTTP requests to an arbitrary url argument, with no destination validation applied. Because Recipe Actions are outbound webhook POSTs, the flaw is effectively blind SSRF, so the primary risk is reaching internal-only services or the cloud metadata endpoint rather than directly exfiltrating data back to the attacker. Publicly available exploit code exists, and upgrading to 3.26.0 resolves the issue.
Improper privilege management in samanhappy MCPHub up to 1.0.32 lets any authenticated non-admin user import a configuration template that defines a 'privileged' server (a stdio server, any config carrying command/args, or any config with no remote target), which MCPHub then spawns locally as an operating-system command - resulting in arbitrary command execution as the MCPHub process. Exploitation only requires a valid low-privilege login and access to the Template Import Endpoint (CVSS 4.0 vector shows PR:L), and publicly available exploit code exists via GitHub issue #1094, so the practical risk is higher than the vendor's 5.3 score suggests; this assessment rates it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. The flaw is fixed in MCPHub 1.0.33, where importTemplate enforces the admin-only privileged-config policy.
Missing OAuth token validation in Pixelfed up to 0.12.11 allows an authenticated user without a valid OAuth token to reach the /api/v1 instancePeers endpoint and enumerate federated peer instances, a low-sensitivity information exposure tracked as CWE-306. Publicly available exploit code exists, and the vendor has released a patch (v0.12.10, commit 68dca5097305fa0065d029587b2233524636025a) with a GitHub issue and PR. The independent assessment treats this as low priority: the CVSS vector requires PR:L (authenticated) access, the exposed peer list is often publicly available anyway, and there is no user-data confidentiality, integrity-write, or availability impact beyond peer enumeration.
Path traversal (CWE-22) in the 00Kisumi00 mcp-file-analyzer MCP tool allows authenticated remote attackers to read arbitrary files by supplying a crafted filename to the analyze_csv_data function implemented in main.py's ControlFlowNode. Publicly available exploit code exists, but the vulnerability is low severity (CVSS 5.3; assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) and the project is a rolling-release hobby tool with near-zero deployment. No vendor patch has been released and the maintainer has not responded to the issue report.
Filter bypass in PHP-FTS (olivier-ls/php-fts) through version 1.1.3 allows an authenticated remote attacker to defeat document-scoping filters used by consuming applications for ownership or multi-tenant isolation, exposing search results the application intended to hide. The flaw resides in SearchEngine::matchesSingleFilter in src/SearchEngine.php, where filter values were compared with loose `==` and non-strict `in_array()`; because PHP treats any non-empty string as equal to boolean true, a filter value of true matched every document with a non-empty value in that field, and the string '42' matched the integer 42, enabling retrieval of other users' or tenants' records. Publicly available exploit code exists (a proof-of-concept write-up is referenced alongside the CVE from VulDB and a GitHub PoC repository), and the issue is not listed in CISA KEV, so no confirmed active exploitation is known; the risk is context-dependent and moderate, materializing only where the application relies on PHP-FTS filters as an access-control boundary and passes untyped request input directly into filter construction.
Cross-site scripting in SourceCodester Drug Recommendation System 1.0 allows unauthenticated remote attackers to inject arbitrary script through the 'full name' argument processed by /drug_recommender/index.php, with the payload executing in a victim's browser once the unsanitized value is rendered. Publicly available exploit code exists - a GitHub proof-of-concept README documents the injection path (profile XSS) - but there is no evidence of confirmed active exploitation, and the vendor/analyst scoring places this at 5.3 (CVSS 4.0 AV:N/AC:L/PR:N/UI:P, with the independent assessment using CVSS 3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), reflecting integrity-limited impact with no confidentiality or availability loss. Overall this is a low-to-moderate risk issue: it requires victim interaction and an internet-reachable deployment of an obscure PHP application unlikely to be exposed in production.
Denial of service in OpenClaw up to and including 2026.9.5 allows a remote attacker with low-privileged authenticated access to exhaust server memory by requesting large files through the Canvas Host Route, which buffers entire files into memory via readFile() in src/canvas/serve.runtime.ts with no streaming or size cap. Publicly available exploit code exists (a PoC report is published on GitHub), but there is no indication of confirmed active exploitation (not in CISA KEV). Impact is limited to transient availability degradation of the canvas extension's HTTP serve path - no data exposure, integrity loss, or code execution - and every signal, including the assessed CVSS:3.1 vector of 3.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L) and the vendor's CVSS 4.0 base score of 2.1, points to a genuinely low-priority issue.
Server-side request forgery in the pdf-tools-mcp MCP server bundled with the 0717376/cowork_bench project lets an attacker who can call its ControlFlowNode tool supply a crafted pdf_file_path argument and cause the server to issue requests to attacker-chosen destinations, yielding low confidentiality, integrity, and availability impact. The repository is a rolling-release personal project with no tagged versions, so all revisions up to commit d943e75bc0fc8e3b27141979300cd8cbcd1e890d are presumed affected, and the CVSS 4.0 vector (PR:L, E:P) indicates the tool interface requires some authenticated or privileged access rather than fully anonymous reach. Publicly available exploit code exists (published in a separate GitHub proof-of-concept repository), but there is no evidence of confirmed active exploitation, and the practical risk is heavily constrained by the product's negligible deployment footprint and the maintainer's failure to respond to the original issue report.
SQL injection in AdithyaYelloju Restaurant Management System allows an authenticated attacker with low-privilege admin panel access to execute arbitrary SQL commands via the item, price, image, or type parameters in admin/add_menu.php, leading to potential data theft or modification. Publicly available exploit code exists, but there is no confirmed active exploitation (CISA KEV); the independent assessment rates confidentiality and integrity impact as high and availability as low. Exploitation requires obtaining an authenticated session on the admin interface, and because the product is a niche self-hosted project with no version pinning, real-world exposure depends on the rare deployment being internet-reachable, making this a low-real-world-priority finding.
SQL injection in itsourcecode Leave Management System 1.0 lets an authenticated attacker with a low-privilege session (PR:L per the CVSS vectors) read and tamper with database contents through the ID parameter of /module/department/index.php; our independent assessment rates confidentiality impact high and integrity impact low. Publicly available exploit code exists, and the attack is network-reachable with no user interaction and no non-default configuration required. Real-world risk is moderate-to-low despite the published exploit, because the vulnerable endpoint sits inside the authenticated department administration module and the product itself is a rarely deployed hobbyist PHP application.
SQL injection in itsourcecode Leave Management System 1.0 allows an authenticated user to manipulate the DEPTID argument of /module/department/controller.php and inject arbitrary SQL into the application's backend queries. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N), the primary impact is high confidentiality loss with limited integrity effect, and exploitation requires a valid application session (PR:L) - no user interaction or non-default configuration is needed beyond the department module being reachable. Publicly available exploit code exists (a public proof-of-concept is referenced at github.com/VivianQYW/cve/issues/2 and the VulDB entry 407922), so the technical barrier to weaponization is low, though real-world risk is tempered by the product's very small deployment footprint; there is no indication of confirmed active exploitation (CISA KEV).
SQL injection in the admin/add_table.php endpoint of AdithyaYelloju Restaurant Management System allows authenticated attackers to inject arbitrary SQL through the table, members, and price parameters. The vulnerability requires a valid admin session (CVSS PR:L) and has publicly available exploit code, but its low severity score (5.3) and the product's rarity make it a genuine yet low-priority issue; no fixed build exists because the project uses rolling releases and has not responded to the report.
Path traversal in 06ketan slideshot through 4.4.0 allows manipulation of the htmlPath argument in the render_slides function of packages/cli/src/renderer.ts, enabling low-impact confidentiality exposure via traversal outside the intended rendering path. The CVSS 4.0 vector indicates network reachability, low privileges required (PR:L), and only low confidentiality impact (VC:L), which supports the independent assessment of LOW real-world risk despite the 5.3 score. Publicly available exploit code exists, but there is no confirmed active exploitation (CISA KEV); the project was reportedly notified through an issue but has not responded.
Stored cross-site scripting (XSS) in Newbee Mall (newbee-ltd newbee-mall) up to version 1.0.0 allows an authenticated low-privileged user to inject arbitrary JavaScript via the goodsName parameter on the Goods Save endpoint (controller/common/UploadController.java), which can be persisted and executed when a victim views the poisoned content if user uploads are served through the /upload/** static mapping. Exploitation requires authentication (PR:L) and victim interaction (UI:P), and publicly available exploit code exists; the independent assessment rates this as low-to-moderate real-world risk given the required privileges, user interaction, and the niche demo-project deployment base.
Authenticated privilege escalation in CodeAstro QR Code Attendance Management System 1.0 lets a logged-in, low-privileged user manipulate the role_id argument in the UserController Save action to assign elevated roles, up to administrator, to any account they control. The flaw is an improper privilege management weakness (CWE-269) exposed through the PHP web interface, and publicly available exploit code exists (a GitHub proof-of-concept), though there is no CISA KEV entry confirming active exploitation. Severity is modest and consistent with the raw numbers: vendor CVSS 5.1 with low confidentiality, integrity and availability impact, and independently assessed as requiring an authenticated session (PR:L) against this single, obscure application at version 1.0.
Stored cross-site scripting in SourceCodester Drug Recommendation System 1.0 allows an authenticated user with access to the User Management add_user function to inject malicious script via the txtname, txtemail, or txtpassword parameters, which then executes in the browser of any user who views the affected page. Publicly available exploit code exists, though exploitation requires authentication (PR:L per the assessed CVSS 3.1 vector) and victim interaction (UI:P), and the target is a niche application with essentially no production deployment, making the real-world risk low. The assessed impact is limited to browser-context integrity (VI:L) with no confidentiality or availability effect.
Stored/reflected cross-site scripting in code-projects Assessment Management 1.0 allows an authenticated lecturer to inject arbitrary script through the mark argument handled by lecturer/add-single-mark.php, which then executes in the browser of any user who renders the affected page. Exploitation is constrained: the attacker must hold a valid low-privilege lecturer-level account and a victim must interact with (view) the crafted page, so this is not a zero-click remote compromise, and the affected software is a niche academic PHP project rather than a widely deployed platform. Publicly available exploit code exists and may be utilized, but there is no CISA KEV listing, so there is no confirmed active exploitation; the 5.1 CVSS 4.0 score corresponds to a low-to-moderate real-world risk.
Unsafe deserialization in dmlc DGL (Deep Graph Library) up to and including 2.1.0 allows arbitrary code execution when a victim loads a crafted DGL graph info artifact through the load_info / _read_torch_data path in utils.py, which hands an attacker-influenced 'path' to torch.load and therefore to Python's pickle machinery. Per the authoritative assessment this is an untrusted-input/supply-chain scenario rather than a network-service exploit: no memory-safety trigger exists and DGL exposes no network-facing listener by default, so the attacker must deliver a malicious serialized file (shared dataset, model artifact, or downloaded graph) and induce the user to open it, which is why the assessed vector requires user interaction. A publicly available exploit code exists (linked to GitHub issue dmlc/dgl#7932) and the maintainers were notified via issue report but had not responded at the time of analysis; note that CVE-2026-94092 is not listed in CISA KEV, so there is no confirmation of active exploitation. Vendor data records a CVSS 4.0 score of 5.1 (AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/E:P), while our independent assessment rates the practical impact higher (CVSS:3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) because successful unpickling yields full code execution in the victim's context.
Deserialization of untrusted data in gensim's SaveLoad.load (gensim/utils.py) lets an attacker execute arbitrary code on any host that loads a crafted model file, affecting gensim versions up to and including 4.4.0 as well as the current develop HEAD. The flaw is reachable through the public model-loading API and requires the victim to load an attacker-supplied serialized model or vector file (no authentication is needed to craft or deliver the file; the assessed CVSS:3.1 vector is AV:N/AC:L/PR:N/UI:R with high confidentiality, integrity and availability impact, while the vendor-feed CVSS 4.0 score of 5.1 reflects a lower PR:L/E:P reading of the same issue). Publicly available exploit code exists, and because the maintainer closed issue #3663 without a comment, PR, or fix, no vendor patch is available and defense currently depends entirely on refusing to load untrusted files or wrapping the load path in a restricted unpickler.
Stored cross-site scripting in code-projects Assessment Management 1.0 allows an authenticated administrator to inject arbitrary script through the user-editing form at admin/edit-user.php, where the name, sname, email, username, password, and id parameters are written into the database or rendered without proper output encoding. The payload executes in the browser of any user who later views the manipulated record, so exploitation requires both prior access to the admin interface (PR:H) and victim interaction (UI:P/UI:R), which caps the incremental privilege gained by the attacker. Publicly available exploit code exists and has been disclosed via a GitHub proof-of-concept, but there is no indication of confirmed active exploitation (CISA KEV) and no EPSS score was supplied; the disclosed CVSS 4.0 base score is 4.8, and this is best treated as a low-priority, high-noise hardening issue rather than an emergency.
Stored cross-site scripting in the admin symptom-management form (drug_recommender/Admin/add_symptom) of SourceCodester Drug Recommendation System 1.0 lets a user supply malicious content through the txtname argument that is later rendered in a browser without proper output encoding. The attack is remote but gated behind a high-privilege administrator account (CVSS PR:H) and requires a victim to view the affected admin page (UI:P/UI:R), which effectively restricts exploitation to the admin context - closer to self-XSS than a cross-privilege attack - and makes this a low real-world priority despite a public exploit. Publicly available exploit code exists (a GitHub PoC walkthrough linked from the CVE record); there is no indication of confirmed active exploitation (not in CISA KEV), and the independent assessment rates the overall real-world risk as low.
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.
Signed 32-bit integer overflow in SerenityOS LibGfx's BMP decoder can crash the decoder when a victim opens a crafted BMP whose height field is INT32_MIN, affecting BMPLoader.cpp's decode_bmp_pixel_data and related DIB parsing. Publicly available exploit code exists, but exploitation requires user interaction and high complexity, and the realistic impact is minor availability loss only, with no code execution or data disclosure demonstrated. The CVSS 4.0 score of 2.3 and the independent assessment agree this is a low-priority issue.
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.
Non-privileged applications running on a ZTE nubia Z80 Ultra (NX741J) smartphone can retrieve the device's Wi-Fi MAC address by querying the read-only factory_mac_address field exposed through the Android Settings.Secure content database, defeating the platform's normal restriction on hardware MAC address access. The issue is purely local (assessed CVSS:3.1/AV:L/AC:L/PR:N/UI:N, base score 3.3, C:L/I:N/A:N), requires an attacker-supplied app to already be installed and executing on the handset, and leaks only a single low-sensitivity hardware identifier whose main value is device tracking rather than data compromise. According to available intelligence, no public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV; deployment is limited to a single consumer handset model, which keeps overall risk low.