Authentication Bypass

Unauthenticated account takeover of WordPress sites running miniOrange OTP Login, Verification and SMS Notifications through 5.5.8 is possible because the Delay OTP grace flag is stored per user rather than being bound to the originating session, cookie, IP address, or device. When OTP-only login and Delay OTP Verification are enabled and the target account is inside its grace interval, an attacker can submit a known username with `mo_wp_login_intent=otp` and any non-empty password to inherit that user's verified state and log in as any account, including administrators. No public exploit code or CISA KEV active exploitation was identified at time of analysis, and exploitation is constrained by non-default settings plus a race-window timing precondition (CVSS 8.1, AC:H).

Apache Kylin 4.0.0 through 5.0.4 exposes an unauthenticated in-house broadcast function that is paired with polymorphic deserialization, creating a remote attack path that can lead to high confidentiality, integrity, and availability impact on Internet-exposed Kylin services. The Apache advisory states that direct public-network exposure is not common and that in-house deployments are mostly not impacted, so practical risk is concentrated on services reachable from untrusted networks. No CISA KEV entry is present in the supplied data and no public exploit was identified at time of analysis; EPSS is low at 0.24% (14th percentile), while the supplied decision label is act_now.

Authentication bypass in Apache Kylin 4.0.4 through 5.0.4 allows unauthenticated network attackers to reach protected functionality when the Kylin web/REST service is directly exposed, with the 9.8 CVSS vector indicating high confidentiality, integrity, and availability impact. EPSS is just 0.25% (15th percentile) and no public exploit code was identified at time of analysis, while the vendor emphasizes that typical internal-only Kylin deployments are mostly not impacted and that public exposure of Kylin services is uncommon. The practical risk is therefore driven primarily by network exposure rather than by the headline score.

Unauthenticated access control bypass in Apache Kylin 4.0.0 through 5.0.4 allows network-reachable attackers to invoke the platform's normally protected system cleanup actions without any credentials, giving them integrity and availability impact against the Kylin service (CWE-287; assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:N with I:H/A:H). The vendor emphasizes that only Kylin instances directly exposed to the public internet are materially at risk and that typical in-house/internal deployments are mostly not impacted, so exposure is governed by network reachability rather than by any configuration toggle. EPSS is low at 0.25% (15th percentile) and no public exploit code has been identified at time of analysis; there is no KEV listing.

Remote, unauthenticated attackers can access password-less development tools under /wheels/* in Wheels 4.0.0 through 4.1.2 when enablePublicComponent=true (the default in development mode), exposing application settings, environment and datasource details, and routes, and allowing them to start test runs that may write to the real application database. This incorrect authorization flaw (CWE-863) does not affect production-mode deployments by default, and the separately protected migrator and CLI endpoints are not impacted. No public exploit identified at time of analysis.

Opening an attacker-crafted repository in Z.ai ZCode v3.11.2.6792 can lead to arbitrary code execution because the IDE automatically connects to MCP (Model Context Protocol) servers declared in the repository's workspace configuration without requiring user approval. The flaw is rated CVSS 7.8 with a local attack vector and required user interaction - a victim must actively open the malicious repository - and publicly available exploit code exists, though there is no confirmed active exploitation (not in CISA KEV), so the threat is conditional and interaction-dependent rather than a mass-exploitation emergency. Exploitation is unauthenticated from the attacker's perspective and grants high confidentiality, integrity, and availability impact on the affected host.

Improper authorization in Lenovo Baiying PC Client - software distributed exclusively in the Chinese market - lets a local, already-authenticated user execute arbitrary code with elevated privileges, resulting in high impact to confidentiality, integrity, and availability. The vendor rates it 7.0 under CVSS 4.0 (CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N), and our independent CVSS 3.1 assessment is consistent: the vector is strictly local (AV:L), requires a valid logged-in session (PR:L) and some passive user interaction (UI:P), so it is not remotely triggerable. There is no public exploit identified at time of analysis and the CVE is not in CISA KEV, so real-world risk is concentrated in Chinese-market endpoints where a low-privileged local user has interactive access.

Multiple Lenovo consumer tablets - including the Idea Tab Pro (TB373FU), Idea Tab / Lenovo Tab K11 Gen 2 (TB336FU/TB336ZU), Tab M11 (TB330FU/TB330XU), Legion Tab 8.8" Gen 3 (TB321FU), Tab Extreme (TB570FU/TB570ZU), and a broader set of Tab and Yoga Tab models - contain a physical-access authentication bypass (CWE-288) that lets someone in direct possession of the device defeat the lock/authentication flow and gain unauthorized access to the device and its data. Rated 7.0 under CVSS 4.0 (AV:P/AC:L/AT:N/PR:N/UI:N with high confidentiality, integrity and availability impact), the issue requires no credentials (PR:N) and no user interaction (UI:N), so the decisive limiting factor is the Physical attack vector: there is no remote or adjacent-network exposure and only lost, stolen or unattended units are at risk. No public exploit code has been identified at time of analysis, and the specific alternate authentication path involved has not been disclosed by the vendor.

Incorrect authorization in ClassroomIO through 1.0.0 allows any authenticated course member, including students, to modify or delete lessons in any course or organization by supplying arbitrary lesson IDs to the PUT and DELETE /:lessonId routes. The vulnerability stems from a middleware that verifies course membership but fails to scope lesson access to the caller's course. No public exploit code has been identified at time of analysis, and exploitation requires a valid course-member session plus knowledge or enumeration of target lesson IDs.

Authorization bypass in cool-admin-midway through 8.0.0 lets a department-scoped administrator holding sys:user:* permissions read, modify, or delete user records belonging to other departments by supplying an arbitrary user id to the /admin/sys/user/info, /admin/sys/user/update, or /admin/sys/user/delete endpoints. Because the base CRUD service never validates that the requested user id falls within the caller's department, the attacker can reset the password or roles of higher-privileged accounts (turning limited departmental admin rights into full account takeover) or delete accounts outright. Exploitation requires a valid authenticated admin account with user-management permissions, no anonymous access is possible, and no public exploit code was identified at time of analysis; the independently assessed vector (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates this as high severity, treating the department-scoped admin as a low-privilege authenticated user rather than the high-privilege PR:H reading used in the 4.0 vector accompanying the CVE record.

Authorization bypass in Cool Admin Midway through 8.0.0 allows an authenticated non-superadmin administrator who holds sys:role permissions to read, update, or delete other administrators' role records by supplying arbitrary role IDs to the base CRUD role endpoints. This changes menu and department grants for other users and can escalate the attacker's effective access; exploitation requires a valid admin session with role-management rights, making the realistic threat a malicious or compromised low-privilege admin rather than an anonymous remote attacker. The assessed CVSS 3.1 vector is 7.0 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L), and no public exploit identified at time of analysis.

Authenticated insecure direct object reference in MinDoc through 2.2-beta.2 lets any user holding a non-observer role on at least one book read markdown and HTML documents belonging to private books they were never granted access to. Because the DocumentController.Content endpoint authorizes the caller only by document ID and not by the book the document belongs to, an attacker can name any target book and iterate predictable, sequential document IDs to harvest its contents. Exploitation requires a valid low-privileged account (authentication requirements confirmed as authenticated per the CVSS vector, PR:L) and is read-only, with no write, integrity, or availability impact; no public exploit code was identified at time of analysis, though a detailed public technical writeup of the flaw exists.

Authenticated low-privileged users can read other users' and tenants' extracted document text in Bisheng through 3.0.0-beta4 by enumerating sequential file IDs against the GET /api/v1/knowledge/file_bbox endpoint, which lacks per-user ownership checks. This IDOR vulnerability (CWE-639) requires only a valid account on a network-reachable instance and poses a bounded confidentiality risk; no public exploit code or active exploitation has been identified at time of analysis. In multi-tenant deployments, the flaw can expose sensitive parsed documents across tenant boundaries.

CRMEB versions 5.6.1 through 6.0.0 are affected by an insecure direct object reference (IDOR) in the gift-order API, enabling authenticated storefront users to read and claim other users' orders by enumerating sequential order IDs. Attackers can retrieve buyer identities and gift keys via the gift_detail endpoint and then use receive_gift to redirect paid goods to an address they control. Exploitation requires a low-privilege account (obtainable via self-registration) and the gift-order feature to be active; no public exploit identified at time of analysis, though a detailed public writeup exists.

Privilege escalation in ThinkCMF through 8.0.1 allows an authenticated restricted backend administrator with a valid admin-type API token to call every admin REST API endpoint because RestAdminBaseController's Auth::check() fails open when no admin_api authorization rule exists. Such an attacker can list member emails and mobile numbers, disable members, and invoke PUT admin/roles/{id}/authorize to grant themselves full administrator rights. This is an elevated-priority issue gated by the precondition of possessing an admin-tier token, not an unauthenticated remote compromise; no CISA KEV entry is provided and no public exploit was identified at time of analysis.

Unauthenticated attackers with network access to Archon 0.2.13 through 0.11.1 can execute arbitrary commands on the host as the Archon user by sending messages to the AI coding agent through the exposed /api/* control API. The API binds to 0.0.0.0 by default and lacks any authentication, while the agent runs with bypassPermissions, directly translating messages into host command execution. No public exploit code has been identified at the time of analysis, but the issue is rated critical (CVSS 9.3) and affects all default deployments unless the API is network-restricted.

OpenHealth through 0.2.0 fails to enforce authentication or ownership checks in the /api/health-data/[id] GET, PATCH, and DELETE handlers, allowing unauthenticated attackers who know a HealthData record id to read another user's medical record data and file metadata, overwrite the record with arbitrary JSON, or delete it. The issue is rated CVSS 4.0 9.2 and is reported by VulnCheck; no public exploit identified at time of analysis, and no CISA KEV active-exploitation confirmation is provided. Exploitation still depends on obtaining a valid record id: if ids are sequential or otherwise enumerable, the impact scales to mass medical-record theft or tampering, while high-entropy UUIDs narrow exploitation to targeted abuse after an id leak.

Unauthenticated attackers can bypass authentication on BMC Helix Network Management on-prem deployments (versions before 26.3.01) when SAML single sign-on is configured, logging in as the local administrator with any password to obtain a SuperAdmin session. This flaw allows modification of device credentials, execution of device commands, and alteration of audit records. No public exploit code has been identified at time of analysis, but the vulnerability is remotely exploitable without authentication and requires only that the SAML SSO feature be enabled.

Remote code execution in Jooan JA-A12 IP cameras running firmware 009_20171107 or 05.02.31.105 allows unauthenticated attackers to execute root-level commands by abusing hard-coded credentials. An attacker sends singleCMD=SetDiagMode to /goform/SingleHandlebyCommand with attacker-controlled authserverip and authcode values, causing the jooandiag daemon to run commands through /bin/sh and granting full device control. Publicly available exploit code exists, and the provided CVSS 4.0 score is 9.3; no CISA KEV listing is present in the supplied data.

NivoCart through 2.5.1 allows unauthenticated attackers to retrieve guest order invoices via the account/order download() action by iterating order_id values, exposing sensitive customer information such as names, addresses, telephone numbers, emails, purchased items, and order totals. The missing authorization check (CWE-862) affects installations that use guest checkout, as guest orders are stored with customer_id 0. No public exploit identified at time of analysis, though the enumeration is straightforward due to the lack of authentication requirements (CVSS PR:N).

Security-feature bypass in Microsoft Office Word - including the wider Microsoft 365 Apps for Enterprise and Office LTSC 2021/2024 families on Windows and macOS - lets an attacker defeat a protection mechanism such as Protected View, mark-of-the-web enforcement, or a trust/macro prompt by getting a victim to open or preview a crafted document. No attacker credentials or prior access are required (CVSS PR:N), but exploitation is local (AV:L) and depends on the target user interacting with the file (UI:R); a successful bypass yields high confidentiality, integrity, and availability impact for a 7.8 High severity rating. No public exploit code or confirmed active exploitation was identified at time of analysis, and Microsoft has released a patched update through its Update Guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-108433).

Account takeover in the EnergizeLab Eilik NestJS authentication service allows any registered user to hijack another account by manipulating a user ID field in account update requests, a mass assignment flaw (CWE-639). All versions of the service are affected (CPE: cpe:2.3:a:energizelab:nestjs_auth_service:*:*:*:*:*:*:*:*), and exploitation requires only a valid low-privilege account (PR:L) over the network with no user interaction. No public exploit has been identified at time of analysis, though the flaw is trivially automatable and carries a CVSS base score of 8.8.

EnergizeLab's station-middleware (a NestJS-based service distributed as Docker images 1.6.5 through 1.8.2) exposes administrative APIs that perform no role or authorization checks, so any authenticated user holding a valid low-privilege account can read AI provider API keys and modify configuration and object-store contents. Tracked as CWE-862 and rated 9.6 Critical (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N) because the flaw lets a low-privileged principal cross a security boundary to reach high-confidentiality and high-integrity resources; no availability impact is described. Exploitation requires pre-existing valid credentials plus network reachability to the middleware API - there is no pre-authentication path - and no public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS data was supplied.

Unauthenticated model administration in the EnergizeLab Eilik and EilikO companion robots allows any party who can reach the on-device FastAPI AI inference and profiling service over the network to alter AI model configuration and swap the model loaded at runtime, with no credentials or user interaction required (CWE-306). The supplied CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); an independent re-assessment keeps the same unauthenticated, network-reachable vector but rates confidentiality impact as Low and lands on AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H, reflecting that the exposed functions are configuration/administration rather than data-exfiltration endpoints. The practical constraint is exposure: the service runs on a consumer desktop robot that normally listens only on a local or home network, so an attacker generally needs LAN adjacency or a deliberately port-forwarded/exposed device. No public exploit code and no CISA KEV listing were identified at time of analysis, and no vendor-released patch was identified in the provided data.

The EnergizeLab Eilik NestJS authentication service grants device tokens for arbitrary robot serial numbers without requiring any credential, so an unauthenticated remote attacker can mint a valid token for any Eilik robot and impersonate that device against the vendor's cloud services. Rated 8.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N), the flaw is trivially reachable over the network with no authentication or user interaction, and the dominant impact is to integrity of device identity rather than to confidentiality or availability. There is no CISA KEV entry and no public exploit code identified at time of analysis, and no EPSS percentile was supplied with this record, so the practical risk is a genuinely easy-to-exploit flaw with bounded, identity-spoofing impact and no confirmation of real-world use; assessment signals point the same way.

The EnergizeLab AI Station (RK3562) firmware image ships with hard-coded root credentials and an SSH daemon enabled by default, so any attacker who can reach the device's SSH port from the same LAN or adjacent network segment can log in as root and take complete control of the unit. Rated CVSS 8.8 (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw needs no authentication, no user interaction, and no pre-existing privilege on the device - the only barrier is network reachability, per the adjacent-network attack vector. No vendor patch has been identified at time of analysis, and no public exploit code or confirmed active exploitation (CISA KEV) was identified; because every device running stock firmware is affected by design rather than by misconfiguration, this is a high-priority issue for any organization with these units deployed, not a paper-only finding.

BeyondTrust Remote Support appliances contain an authentication bypass (CWE-290) in internal components that fail to validate the origin of received messages, potentially allowing an attacker to perform file operations on the appliance. According to the CVSS 4.0 vector (9.3), no authentication or user interaction is required, but the vendor notes exploitation is conditional ('under the right conditions') and the independent assessment emphasizes that an attacker must reach the internal messaging path and spoof a trusted source. No public exploit code or active exploitation has been identified at time of analysis, though this is a credible high-priority issue given the high impact.

Authorization bypass in Netgate pfSense CE through 2.9.0 allows an authenticated WebGUI account that holds page privileges for services_acb.php, uploadconfig.php, diag_confbak.php, or diag_backup.php to replace config.xml despite lacking the 'User - Config: Deny Config Write' privilege; the account can otherwise be read-only. Successful exploitation can yield root-level code execution after a configuration reload or reboot, and publicly available exploit code exists. The independent assessment scores this CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.6), reflecting a remote authenticated low-privilege attacker with high confidentiality, integrity, and availability impact.

Unauthenticated authorization bypass in the OpenNMS Meridian and Horizon REST API lets any remote attacker who can reach /rest/** read the monitored inventory and create, modify, or delete resources without credentials. The flaw arises because the Spring Security intercept-url rules match the HTTP method as a case-sensitive uppercase token and the filter chains terminate without a deny rule, so a request using a non-canonical method token (for example 'get' or 'put' instead of 'GET'/'PUT') matches no rule and is served without authentication; the /rest/alarms chain additionally leaks whether a specific alarm exists via a difference in the response. All pre-fix Meridian and Horizon versions in default configuration are affected, the vendor-supplied CVSS 3.1 base score is 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, i.e. unauthenticated and low complexity), and no public exploit code was identified at time of analysis; the practical limiting factor is deployment posture, since the vendor states these products belong on private networks and should not be Internet-facing.

Authentication bypass in the joserfc Python library before 1.7.4 lets remote, unauthenticated attackers submit a JWS General JSON Serialization whose "signatures" array is empty and have joserfc.jws.deserialize_json() accept it as authenticated, so relying applications can be fooled into treating an arbitrary attacker-chosen payload as a signed, trustworthy message. Exposure is scoped: only the General JSON Serialization code path is affected - compact JWS, JWT decoding, Flattened JSON serialization, and JWE JSON processing do not reach the vulnerable logic - but where the vulnerable API is used and its success is treated as proof of authenticity, the integrity impact is high (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N per the independent assessment; the published base score is 9.1). No public exploit code or confirmed active exploitation has been identified at time of analysis; the fix commit, tests, and security advisory are publicly available.

Unauthenticated attackers who can reach the Nutanix Prism Element management API can bypass authentication completely by sending an HTTP request with a crafted "internal management" header that the application's authentication filter trusts, and the server then issues a Set-Cookie response containing a valid JSESSIONID that decodes to a JWT carrying maximum cluster administrative privileges. Successful exploitation lets the attacker run root-level commands on every Controller VM (CVM) in the cluster and reach VM memory and virtual disks, resulting in total cluster compromise; the vulnerability is rated 9.3 with an independently assessed CVSS 3.1 vector of AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, and publicly available exploit code exists (the CVSS 4.0 vector rates exploit maturity as Proof-of-Concept), while no confirmed active exploitation (CISA KEV) has been identified and the decisive exposure factor is whether the Prism management plane is reachable from untrusted networks.

Paid fulfillment bypass in Lychee (Supporter/Pro editions) before 7.7.0: the checkout validators accept any OmnipayProviderType enum value, including the Dummy test gateway that is deliberately hidden from production checkout, so a remote unauthenticated buyer - where webshop_allow_guest_checkout is enabled - can start and finalize a session against the Dummy gateway and, with webshop_auto_fulfill_enabled on, have OrderCompletedListener::fullfillOrder() release the purchasable item without any real payment. The integrity impact is genuine but conditional (CVSS 4.0 base 8.3 with Attack Requirements: Present; assessed CVSS 3.1 8.3, C:L/I:H/A:N), since exploitation requires a paid Supporter/Pro instance running the webshop with at least one enabled purchasable item and the relevant opt-in flags. No public exploit identified at time of analysis, and the vendor has released a fixed version, 7.7.0.

Unauthenticated attackers who know the shared identifier of a public, password-protected Lychee album can pull down a ZIP archive of the album's photos via GET /api/v2/Zip without ever supplying the album password, because the download authorization path never re-checks album access. All versions prior to 7.6.3 are affected, and the exposure escalates to full-resolution originals plus associated metadata when the album's grants_full_photo_access flag is also enabled. The flaw only triggers on a non-default sharing configuration (public + password-protected + grants_download on), and no public exploit identified at time of analysis; the vendor fix is 7.6.3.

Privilege escalation in Sonatype Nexus Repository 3 allows an authenticated user who holds the 'role create' or 'role update' permission to grant roles and privileges that their own account does not hold, escalating as far as full administrative access to the instance. The root cause is a missing authorization check (CWE-862) in the role-management functionality, so exposure is concentrated in deployments that delegate role administration to project or team leads rather than reserving it for trusted administrators; anonymous and ordinary unprivileged users cannot trigger it without that delegated permission. No public exploit code has been identified at time of analysis, and the vendor has shipped a fix in Nexus Repository 3.97.0.

Sonatype Nexus Repository 3 fails to enforce a write-authorization check on the NuGet symbol-package upload path, letting an account that holds only repository read and browse privileges persist .snupkg symbol packages into a hosted NuGet repository. The defect is an integrity-only issue (I:H, with no confidentiality or availability impact) and is reachable by remote, low-privileged authenticated users (CVSS 4.0 7.1 High; assessed CVSS 3.1 7.1 High with PR:L). Exploitation is conditional: the target must be a hosted (not proxy or group) NuGet repository with the Symbol Server feature explicitly enabled, and where anonymous access is on, the built-in anonymous account already carries read and browse rights and satisfies the privilege prerequisite without any credential. No public exploit code was identified at time of analysis and there is no CISA KEV listing; a vendor fix is available.

Improper authorization handling in OPNsense core before 26.1.11 lets an authenticated low-privileged user (CVSS PR:L) bypass the user-config-readonly restriction and persist configuration changes through MVC APIs that rely on the throwReadOnly() guard. The flaw only triggers for accounts whose privileges are assigned directly: when a user is given both a component write privilege and user-config-readonly inside one comma-separated <priv> value, ACL::hasPrivilege() fails to detect the read-only flag through its exact string comparison, so the write is allowed; accounts receiving privileges through groups are unaffected. Impact is confined to configuration integrity for the affected component (I:H with C:N and A:L), no public exploit has been identified at time of analysis, and the vendor has shipped the fix in OPNsense 26.1.11.

Improper authentication in Unitronics UniStream Pro B10/C10 controllers running UniLogic firmware prior to 1.41.329 allows a network-positioned attacker with low-level privileges to bypass authentication, yielding high confidentiality and integrity impact with low availability impact (CVSS 8.3). The flaw requires a valid low-privilege authenticated foothold (PR:L per the CVSS vector) and network reachability to the controller, with no user interaction; OT segmentation limits exposure. No public exploit code or active exploitation (CISA KEV) is identified at time of analysis, though the 'Authentication Bypass' tag suggests the exact authentication precondition should be confirmed in the INCD advisory.

Unauthenticated log injection in the OPNsense WebGUI login handler lets a network-adjacent attacker forge authentication events that manipulate the firewall's sshlockout protection state. Because the usernamefld parameter prior to version 26.1.11 passes carriage-return and line-feed characters through LOG_AUTH into the syslog-ng lockout pipeline, an attacker who can reach the login page can plant a fabricated failure event naming a victim IP, causing that address to be added to the sshlockout PF table and its active states killed, or plant a forged accepted event to reset their own brute-force counter and defeat password-guessing lockout. The flaw requires no authentication and no user interaction, but the assessed AV:A vector means exploitation presumes adjacency or management-network reachability to the GUI; impact is integrity of lockout state and availability of blocked systems (administrative, DNS, gateway, or monitoring addresses), with no confidentiality impact, and no public exploit or confirmed in-the-wild activity was identified at time of analysis.

Authenticated Grafana users holding only the Viewer role can create, modify, and delete Loki alerting rules because Grafana's data source proxy fails to apply role-based access control to write requests forwarded to the Loki rules API at /loki/api/v1/rules. Both Grafana OSS and Grafana Enterprise are affected whenever a Loki data source is configured, and because the rules live in Loki rather than in Grafana, a Viewer's changes silently take effect for every user of that data source. Exploitation requires a valid Viewer account plus a configured Loki data source; no public exploit code has been identified at time of analysis, and Loki itself is not vulnerable and needs no patching.

Authorization bypass in the Webba Booking Lite WordPress plugin (webba-booking-lite, all versions through 6.5.2) allows remote attackers to retrieve booking data they are not entitled to by supplying a user-controlled object identifier that the plugin fails to check against the requester's permissions. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, score 7.5 High) characterizes this as an unauthenticated, network-reachable confidentiality breach with no integrity or availability impact, though our independent assessment notes that IDORs of this class in WordPress plugins frequently require at least a low-privileged session in practice, so the authentication prerequisite should be confirmed against the Patchstack advisory. There is no CISA KEV listing and no public exploit code identified at time of analysis, and the practical exposure is limited to sites with the vulnerable plugin installed and active, with impact confined to unauthorized disclosure of booking/attendee data rather than modification or denial of service.

Rate limiting in Eclipse Connected Services Platform's api-gateway (up to and including 1.7.3) can be bypassed completely by any remote attacker who sends a distinct X-Forwarded-For header value on every request, because the shipped default ClientIpKeyResolver builds the per-client rate-limit bucket key from the unvalidated leftmost element of that client-supplied header. The result is an unlimited number of independent buckets on every route that uses the default configuration, letting unauthenticated attackers (CVSS:3.1 AV:N/AC:L/PR:N/UI:N) evade request throttling and degrade availability (C:N/I:N/A:H, score 7.5); confidentiality and integrity are unaffected. Exposure is configuration-dependent - gateways that swap in a trusted-proxy-aware key resolver or do not enforce rate limiting are not impacted, and no public exploit code was identified at time of analysis (SSVC exploitation: none).

Authenticated low-privilege users can exploit missing authorization checks in the ThemeGrill User Registration plugin (versions up to 5.2.8) to perform unauthorized actions, potentially altering site data or user information. This broken access control flaw (CWE-862) has a CVSS score of 7.1 and requires network access with low complexity, but no user interaction. No public exploit code or active exploitation has been identified at this time.

Unauthorized command execution in HPE NonStop SQL/MX SQLCAT allows remote attackers to run arbitrary commands through improperly validated input (CWE-20). The CVSS score is 7.4 with a vector indicating low-privileged authenticated access (PR:L), yet the HPE description states an unauthenticated user can exploit it, creating an unresolved contradiction that complicates prioritization. No public exploit code or active exploitation has been identified at time of analysis, and the risk is confined to HPE NonStop environments where the SQLCAT catalog manager is network-accessible.

QNAP HybridDesk Station (HD Station) before 4.2.22 contains a missing authentication flaw in a critical function, allowing unauthenticated attackers on an adjacent network to gain access to the system. Exploitation is constrained by a specific attack precondition and passive user interaction, and only QNAP NAS devices with the optional HD Station app installed and enabled are exposed. The vendor has released HybridDesk Station 4.2.22 and later as a fix; no public exploit was identified at time of analysis.

Unauthenticated remote attackers can read sensitive data from QNAP NAS devices running the optional Video Station (VideoStationPro) application prior to 5.8.8 by exploiting a CWE-639 authorization bypass through a user-controlled key. The vendor rates the flaw 8.7 under CVSS 4.0 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N) and our independent assessment scores it 7.5 under CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), reflecting a confidentiality-only impact with no integrity or availability loss. Exploitation requires Video Station to be installed and network-reachable on a QTS/QuTS NAS, and no public exploit code or CISA KEV listing was identified at time of analysis, so this is a high-priority information-disclosure issue rather than a confirmed actively exploited one.

Missing authentication in sMedio DTCP MOVE before version 1.4.5 lets remote, unauthenticated attackers reach critical functions of the DTCP-IP content-transfer service (sMedioDTCPServer) running on QNAP NAS devices, yielding high impact to confidentiality, integrity and availability (vendor CVSS 4.0 base 9.3; independent assessment CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The vendor has shipped a fixed release (1.4.5 and later), and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis. Real-world exposure is limited mainly by deployment scarcity - this is an optional, niche QNAP add-on rather than a default NAS service - and by whether the affected service is network-reachable rather than confined behind NAT or a segmented LAN.

Security-constraint bypass in Eclipse Jetty leaves some request URL patterns unprotected when annotation and deployment-descriptor security metadata are mixed, specifically in the jetty-annotations and jetty-eeN-annotations modules. The flaw triggers only in a narrow application layout: a servlet declared in web.xml with more than one url-pattern, a web.xml security-constraint that covers only a subset of those patterns, and @ServletSecurity annotations present at the same time, in which case the Jakarta Servlet specification's authoritative url-pattern precedence rules are not applied and the uncovered patterns remain reachable. Because the resulting access is reachable over the network with no credentials (CVSS 4.0 AV:N/PR:N/UI:N, independently assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:N), an unauthenticated remote attacker can read content that should have been restricted, yielding a high confidentiality impact with a low integrity impact and no availability impact; exploitation is strictly gated by the application-level web.xml/annotation layout rather than by the Jetty version alone, and no public exploit identified at time of analysis.

Authentication bypass in Diaple Stela versions prior to 1.60.1 allows an unauthenticated remote attacker to forge the client-side 'authProcess' cookie and impersonate any account, including one with SUPER_ADMIN privileges, ultimately obtaining a valid administrative JWT. Rated CVSS 4.0 9.3 (assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:N with high confidentiality and integrity impact, no availability impact), the flaw requires no credentials and no victim interaction - only network reachability to a vulnerable instance and knowledge or guessing of a valid target userId. No public exploit code has been identified at time of analysis.

FreeBSD classic (non-VNET) jails can bypass jail network isolation because the IPv6 UDP send path for unconnected sockets fails to rewrite a loopback destination to the jail’s primary IPv6 address, allowing an in-jail process to send datagrams to host services listening on ::1. The assessed vector (AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N) requires an existing low-privileged process inside a classic jail, IPv6 enabled on the host, and a target service bound to the host’s IPv6 loopback; VNET jails are unaffected and there is no exposure if these conditions are absent. The provided NVD-style vector (AV:N/PR:N) overstates reachability, and no public exploit was identified at time of analysis; EPSS is low (0.19%, 8th percentile).

Unauthenticated remote attackers can force-publish, rewrite, and create the managed pages of any WordPress site running Tutor LMS below 4.1.1, because the plugin's page-regeneration routine omits a capability check (CWE-862). Impact is confined to integrity - unpublished pages can be pushed live, existing page content overwritten, missing pages created, and the plugin options that reference those pages changed - with no confidentiality or availability effect and no code execution, so realistic damage is content tampering and manipulation of plugin page references rather than site takeover. Publicly available exploit code exists, and the CVSS 3.1 base score is 7.5 (HIGH) with vector AV:N/AC:L/PR:N/UI:N, making it trivially reachable on exposed sites; there is no CISA KEV entry indicating confirmed active exploitation at time of analysis.

An authorization bypass in the Checkout Field Manager (Checkout Manager) for WooCommerce plugin, affecting all versions up to and including 7.9.6, lets any logged-in user at subscriber level or above delete arbitrary attachments from the WordPress Media Library. The action handler fails to verify that the caller is permitted to remove the targeted attachment, so a low-privilege account - which many WooCommerce storefronts allow anyone to self-register for - is sufficient to destroy site media content. The vendor addressed the flaw in version 7.9.7; there is no public exploit code and no confirmed active exploitation (CISA KEV) at time of analysis, though the assessed EPSS-style risk is driven by how commonly subscriber registration is left open on commerce sites.

Authentication bypass in Znuny through 7.3.6 allows a remote, unauthenticated attacker to impersonate any existing account - including administrators - by sending a forged 'Remote-User' HTTP header, granting full access to confidential ticket data and system controls without any password. The flaw only manifests when the HTTPBasicAuth authentication backend (Kernel::System::Auth::HTTPBasicAuth for agents and/or Kernel::System::CustomerAuth::HTTPBasicAuth for customers) is configured, which is a non-default deployment choice, and when the fronting web server passes an inbound Remote-User header through to the Perl process unsanitized. No public exploit code and no confirmed active exploitation were identified in the available data, and the CNA's CVSS 9.5 rating is tempered by the genuine configuration prerequisite; installations using the default database or LDAP authentication backends are not affected.

SQL injection in the Wheels CFML framework versions 1.1.8 through 4.1.1 can let unauthenticated remote attackers alter SQL queries when applications pass caller-supplied string values into dynamic finders such as findOneByEmail, query-builder where(property, value) and where(property, operator, value), string/UUID-key lookup paths like findByKey, updateByKey, deleteByKey, findOrCreateBy..., or validatesUniquenessOf. The parser mishandles a doubled single quote by treating it as the end of a string literal, potentially exposing authentication, password-reset, and token lookups; the whereBetween() variant in 4.0.0 through 4.1.1 is additionally gated on MySQL/MariaDB running with backslash escaping enabled, and numeric-column values are not affected. The issue is fixed in 4.1.2, and no public exploit was identified at time of analysis.

Authorization bypass in IntentKit through 2.6.3 allows unauthenticated callers to execute owner-only, state-changing tools - wallet transfers, social posting, memory writes, and agent-to-agent calls - on agents reachable through WEB, API, Twitter, or Telegram contexts. The executor authorizes each tool call against the complete tool registry instead of the per-request narrowed tool advertisement enforced by ToolBindingMiddleware, so an attacker who knows the exact de-advertised tool name and supplies valid arguments can drive it via indirect prompt injection or by replaying checkpoint and history data on a reused thread, with no human-in-the-loop or approval gate intervening (CWE-862, missing authorization). No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis; risk is driven by the fully remote, unauthenticated, low-complexity vector with high integrity impact (CVSS 4.0 base 8.7), and exploitation still requires knowledge of the specific restricted tool names plus a working injection or replay channel against an agent that actually has those tools registered.

Unauthenticated remote attackers can cause a denial of service in the finger daemon of HPE NonStop TCP/IP UTILITIES (version T8602L01^BAA and earlier) by sending crafted requests to the network-reachable finger service. The flaw stems from missing authentication (CWE-306) in the daemon, allowing any remote user to disrupt availability without credentials. No public exploit code has been identified at time of analysis, but the service is legacy and often disabled or firewalled, limiting exposure.

Password reset authorization bypass in ELADMIN v2.7 and earlier allows any authenticated user, regardless of role, to reset arbitrary account passwords-including the built-in administrator-by sending PUT /api/users/resetPwd. The endpoint lacks the method-level authorization check applied to other user-management endpoints and performs no role or ownership validation in UserServiceImpl.resetPwd, so a low-privileged session can take over privileged accounts. No public exploit was identified at time of analysis, but the CVSS 3.1 score is 8.8 (PR:L) and the flaw is a genuine high-priority broken-access-control issue; risk is highest for internet-facing instances or those allowing self-service account creation.

Credential theft in Heym 0.0.55 through 0.0.120 allows a shared collaborator to seize the error_workflow_id execution field and repoint it at an attacker-controlled workflow containing an HTTP node, so that when the owner's parent workflow enters an error state the owner's decrypted credentials are injected into the attacker's workflow and exfiltrated over the network. The attack is remote and low-complexity, requiring only low privileges - an existing collaboration grant on the target workflow (PR:L per both the supplied CVSS 4.0 vector and the assessed CVSS 3.1 vector) - with no user interaction, producing high confidentiality impact and only low integrity impact from the single overwritten field. No public exploit code or CISA KEV entry was identified at time of analysis, and single-owner Heym deployments that do not use shared collaborators are not exposed.

Renovate before 44.60.1 on self-hosted instances lets an attacker with a legitimate foothold (PR:L in the assessed vector, i.e., control of a repository or externally sourced preset the instance already extends) bypass the restricted environment-variable allowlist by embedding an env block inside a shared preset, overriding variables such as PATH, LD_PRELOAD, NODE_OPTIONS, or GIT_SSL_CAINFO in child processes. Because those variables govern dynamic library loading, runtime module resolution, command lookup, and TLS trust stores, a successful bypass can escalate from a poisoned preset into arbitrary code execution or credential and traffic interception inside the Renovate execution context. The exposure is narrow but severe for the population it touches - self-hosted deployments that extend third-party or community presets while treating allowedEnv as a security boundary - and no public exploit identified at time of analysis; the record carries no KEV status or EPSS score.

Renovate before 44.60.1 permits authenticated repository users with configuration influence to circumvent the allowedHeaders restriction by embedding hostRules[].headers inside shared presets, causing custom HTTP headers to be injected into outbound requests Renovate makes to other hosts. This is an allowlist/authorization bypass requiring low privileges (PR:L per CVSS) and specific, condition-dependent prerequisites (AC:H), making it an insider or supply-chain-style abuse rather than anonymous remote exploitation. It is not confirmed as actively exploited (no CISA KEV entry) and no public exploit code has been identified at time of analysis.

Authentication bypass in Better Auth's OAuth Proxy plugin (versions 1.5.0-beta.12 through 1.7.6) lets unauthenticated remote attackers sign in as arbitrary users by forging encrypted profile state when the plugin is deployed with a shared global secret and cookie-stored OAuth state, abusing implicit account linking against a victim's verified email to seize the account. The vendor rates the flaw 9.1 (CVSS 4.0) with high attack complexity and a present attack requirement because exploitation depends on that specific shared-secret/cookie-state configuration rather than a default install; no public exploit code has been identified at time of analysis and there is no CISA KEV entry. Priority risk is therefore concentrated on deployments that have enabled the OAuth Proxy plugin in that exact configuration; upgrading to 1.7.7 or later closes the bypass.

Authentication bypass in Better Auth SSO (@better-auth/sso) 1.7.0-rc.2 through 1.7.2 allows an authenticated low-privilege user to sign in as other users by registering a personal SSO provider that copies a legitimate provider's OIDC issuer or SAML entity ID and asserts a victim's subject or NameID; the account lookup ignores providerId, so the forged personal provider can create a session for the victim account. Exploitation requires a valid account and that the application permits user-registerable personal SSO providers, and no public exploit has been identified at time of analysis. The issue is fixed in 1.7.3; CVSS 8.6 reflects high confidentiality and integrity impact.

An authentication bypass in Better Auth versions 1.4.0-beta.18 through 1.7.6 allows unauthenticated attackers to sign in as other users by reusing OAuth state values as Magic Link tokens. The attack requires the target application to have both an OAuth/social sign-in provider and the Magic Link plugin enabled; the attacker must also know the victim's email address. No public exploit identified at time of analysis, but the vulnerability is rated critical (CVSS 9.3 per CVSS 4.0, 9.8 per assessed CVSS 3.1).

Authorization bypass in n8n versions before 1.123.83 allows an authenticated member account to spoof workflow identity by supplying a trusted workflow identifier in the Execute Sub-workflow node's inline JSON mode, enabling credential resolution from projects the attacker does not belong to and unauthorized modification of another workflow's static data and error-workflow dispatch. The vulnerability (CWE-639, authorization bypass through user-controlled key) requires valid low-privilege credentials plus knowledge of a foreign workflow identifier, so single-tenant, single-project, or non-inline-JSON deployments are materially less exposed. No public exploit code or confirmed active exploitation was identified at time of analysis, and the independent assessment rates this as a moderate, authenticated-access issue rather than a mass-exploitation emergency.

Credential exfiltration in n8n versions before 2.41.4 and 2.42.0 before 2.42.1 allows an authenticated editor on a multi-user instance to abuse a shared workflow's 'Message an Agent' node in inline mode, causing the owner's stored credentials to be resolved and sent to an attacker-chosen destination. The flaw is an access-gated authorization bypass (CWE-863) requiring editor rights and a shared workflow that references higher-trust credentials; single-operator self-hosted deployments have limited practical exposure. No public exploit was identified at time of analysis.

A signature bypass in n8n's waiting-webhook endpoint allows attackers who possess a valid resume token for an existing Send-and-Wait execution to approve waiting executions intended for other users, causing downstream workflow actions to run under the workflow owner's credentials, which may include command execution if the workflow is configured to perform such actions. Affects n8n versions before 2.41.4 and 2.42.x before 2.42.1. No public exploit identified at time of analysis; exploitation requires a valid resume token (no authentication to n8n itself is needed beyond the token), and the impact is bounded by the target workflow's downstream nodes. This is a moderate-to-high priority issue for organizations running n8n, but not a drop-everything emergency.

Unauthenticated keyboard injection in the FreeRDP shadow server (versions 3.0.0 through 3.31.x) allows remote attackers to send synthetic keystrokes into a host user's X11 session via XTEST by delivering an input PDU during the Confirm Active state, before any authentication takes place. Exploitation requires the shadow/mirroring server to be network-reachable and the host to be running an X11 session over a TLS-only RDP negotiation; the confirmed impact is integrity-only (fabricated input) with no confidentiality or availability effect. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.

Unauthenticated remote attackers can mint valid JWT access tokens - and thereby log in as an administrator - on affected Hitachi Vantara deployments by abusing the private key shipped inside the product's default self-signed SSL certificate (CWE-321, hard-coded cryptographic key). Exploitation is gated by a single configuration precondition: the web interface must still be running the out-of-the-box default certificate whose key material is reused to sign session JWTs, which is why the vendor's CVSS 4.0 vector carries AT:P (attack requirements present) even though no authentication or user interaction is needed (PR:N/UI:N). Impact is bounded to administrative/configuration control such as changing service settings or requesting log collection - the vendor states device credentials and customer data are not reachable - and no public exploit was identified at time of analysis (the issue is not in CISA KEV).

User enumeration and credential-verification flaws in Omada Controller MSP mode allow an authenticated attacker to validate credentials for other accounts by manipulating the Identifier parameter, potentially leading to unauthorized access to MSP resources or account compromise. Exploitation requires the controller to be running in MSP mode, an existing authenticated session, and knowledge of the target account's Identifier; no public exploit code or active exploitation has been identified at time of analysis. The issue is rated moderate priority due to these prerequisites and the oracle-based nature of the leak, as the endpoint returns distinguishable responses for nonexistent users, invalid passwords, and successful authentication.

Authentication bypass in FileRise versions before 3.23.0 lets a remote attacker log in as an existing local account - including the built-in administrator - by presenting OIDC claims whose mutable preferred_username value, or an unverified email, collides with that account's local username; the flaw works even when OIDC automatic provisioning is disabled. Successful takeover yields full read, write, and delete control over the file manager and its stored files, consistent with the assessed CVSS 3.1 score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Exploitation is conditional, not universal: the deployment must be configured for OIDC SSO and the identity provider must allow the colliding claim or omit email_verified, which is what drives the High attack-complexity rating; no public exploit code was identified at time of analysis and the issue is not listed in CISA KEV. The vulnerability is fixed in FileRise 3.23.0.

File overwrite in FileRise prior to 3.18.0 allows an unauthenticated visitor who holds a valid upload-enabled shared-folder or upload-only link token - plus any configured share password - to re-upload a file using the exact name of an existing file and silently replace its contents while the original uploader metadata is preserved. The same missing replacement check affects ordinary authenticated uploads through /api/upload/upload.php and authenticated upload-only users who lack edit authority over the target file, so the outcome is a high-integrity, no-confidentiality loss (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L, 8.2). Exploitation requires that an administrator has actually created and shared an upload-capable link and that the attacker knows or guesses the target filename; impact is confined to overwriting existing files, with no data disclosure and no code execution path. No public exploit code was identified at time of analysis, and the vendor-released fix is FileRise 3.18.0.

Unauthenticated administrative account takeover in FileRise versions prior to 3.16.0: because the application treats an empty or missing users.txt as a fresh installation, a remote caller with no credentials can detect that first-run setup has silently reopened and create the next initial administrator account through the setup flow. The empty-user-store condition must first arise from storage loss, truncation, or another failure after setup previously completed (hence the AC:H rating), so reliably-stored, intact installations are not exposed; once that state exists, exploitation requires no authentication and no user interaction (PR:N/UI:N) and yields high confidentiality and integrity impact (CVSS 7.4). There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, though the flaw is trivially reproducible by anyone who notices the exposed setup page.

Cross-company record deletion in InvoiceShelf 2.3.3 and earlier allows an authenticated user with membership in any one company to destroy data belonging to other tenants on the same instance. The bulk-delete validators (DeleteCustomersRequest, DeleteEstimatesRequest, DeleteExpensesRequest, DeleteInvoiceRequest, DeleteItemsRequest, DeletePaymentsRequest and DeleteUserRequest) verify that submitted identifiers exist but do not consistently bind them to the caller's company_id, so an attacker who supplies a foreign numeric ID can delete customers, estimates, expenses, invoices, items, payments or user accounts outside their own tenant. Exploitation requires a valid account (PR:L) and a multi-tenant deployment; single-company self-hosted installs have no cross-tenant data to target. No public exploit code or active exploitation was identified at time of analysis, and the vendor released a fix in 2.4.0.

InvoiceShelf installs prior to 2.4.0 leak other customers' invoices, estimates, and payment PDFs through the public customer-portal token routes, because the EmailLog token is resolved by numeric mailable_id without checking mailable_type and the JSON handlers never enforce EmailLog::isExpired. An unauthenticated remote attacker holding any legitimate emailed customer link (PR:N, no account needed) can therefore retrieve a document belonging to a different company when numeric identifiers collide across tenants, or keep using an already-expired link indefinitely on the JSON routes GET /customer/invoices/{email_log:token}, GET /customer/estimates/{email_log:token}, and GET /customer/payments/{email_log:token}; the view handlers can additionally flip a mismatched invoice or estimate to 'viewed' and trigger a notification email. Rated CVSS 8.2 (C:H, I:L) as a genuine improper-authorization flaw (CWE-285), though the cross-tenant variant is opportunistic and gated by id collisions while the expired-token variant is fully reliable; no public exploit code has been identified at time of analysis and the issue is fixed in version 2.4.0.

Cross-tenant access control bypass in InvoiceShelf prior to 2.4.0 lets an authenticated staff user holding only ordinary 'view notes' or 'manage notes' permissions read, modify, or delete another company's reusable invoice, estimate, and payment note templates by supplying a sequential note ID belonging to that tenant. The flaw is a classic insecure direct object reference (CWE-639) - the route-bound Note object is never handed to NotePolicy::viewNotes/manageNotes, so the policy checks only the generic ability and never validates the note's company_id, and the Note model carries no global company scope. Authentication is required (CVSS PR:L) and impact is confined to note templates rather than full financial records, but note IDs are sequential so enumeration is trivial; no public exploit code has been identified at time of analysis, and the vendor has released a fixed version (2.4.0).

Cross-tenant IDOR in InvoiceShelf before 2.4.0 lets an authenticated user with the create-invoice ability convert an estimate belonging to a different company by calling POST /api/v1/estimates/{estimate}/convert-to-invoice. Because route-model binding resolves the estimate without a company check, the attacker can copy another tenant's line items, prices, taxes, totals, notes, currency and customer data into an invoice in their own company, and the victim's configured conversion action may also modify or delete the source estimate - an exposed-data and integrity impact scored CVSS 7.1 with PR:L, requiring an authenticated account. Exploitation is only meaningful on multi-company (multi-tenant) deployments and no public exploit code has been identified at time of analysis; the vendor-released fix is version 2.4.0.

Authenticated remote attackers who know a published project's public DeployBoard anchor can exploit an authorization bypass in Plane 1.3.1 and earlier to create or soft-delete file assets in any workspace project without being a member, leading to cross-workspace file injection, storage abuse, and data loss. The flaw is an IDOR (CWE-639) with a CVSS 8.1 rating (integrity and availability high, confidentiality none). No public exploit code identified at time of analysis; the issue is fixed in Plane 1.4.0.

Authentication bypass in FileRise (CWE-290) lets unauthenticated remote attackers impersonate any account - including an administrator - without a password or MFA in deployments prior to 3.16.0 that enable proxy-header authentication (AUTH_BYPASS) and expose the backend port directly. The flaw is that the configured reverse-proxy identity header (X-Remote-User) was trusted without validating that the request actually came from an address in FR_TRUSTED_PROXIES; an attacker who can reach the backend application port therefore simply supplies the header and receives a session for the named account. Exploitation requires proxy-header auth to be enabled, the trusted-proxy check to be absent or ineffective (exactly what 3.16.0 fixes), and a network path to the backend that bypasses the proxy, which is why it is scored AV:N/AC:H/PR:N/UI:N with full confidentiality, integrity, and availability impact (CVSS 3.1: 8.1 High); no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis.

Improper access control in the export settings feature of SonicWall Network Security Manager (NSM) on-prem let a remote authenticated attacker with only low-privilege NSM credentials retrieve sensitive information that should be restricted to higher-privileged users, which the vendor states could be used to escalate to administrator or to intercept other NSM users' communications. Affected deployments are NSM on-prem 4.3.1 and earlier; the hosted/SaaS NSM is not indicated as in scope, and exploitation requires a valid account plus access to the export settings functionality (CVSS 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). There is no public exploit code identified at time of analysis, no confirmed active exploitation (SSVC Exploitation: none), and EPSS is low at 0.20% (10th percentile), so this is a genuine but not emergency-grade priority - its realistic impact presumes a multi-user NSM deployment in which other privileged accounts or traffic exist to leverage.

Unauthenticated access-control failure in OpenAEV prior to 2.260622.0 allows anyone who knows a valid exercise UUID to read lessons-learned questions and answers - including the identity of each answer's author - and to create or overwrite answers attributed to an arbitrary user. The flaw affects default installations of the adversary-simulation platform and is remotely exploitable without credentials or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, base score 8.2), making it a high-priority exposure for unpatched instances; the sole prerequisite is possession or guessing of an exercise UUID, and no public exploit code has been identified at time of analysis.

Cross-tenant knowledge-base file read in Nexent through 2.7.0 allows any authenticated tenant to access other tenants' source documents by exploiting a missing tenant check in the check_file_access function for knowledge_base/ paths. Attackers in multi-tenant deployments can list objects via GET /file/storage to obtain presigned URLs or directly download files via GET /file/download/{object_name}. This is an authenticated information disclosure flaw requiring a valid account; no public exploit code or active exploitation has been identified at time of analysis.

Unauthenticated attackers can take over Databasus accounts, including administrator accounts, by exploiting an authentication bypass in versions 3.7.0 through 3.61.0. The flaw allows brute-forcing six-digit password reset codes via POST /api/v1/users/reset-password because the application lacks rate limiting, account lockout, and code invalidation after failed attempts. No public exploit code has been identified at time of analysis, and while the flaw is high severity, real-world priority is tempered by the product's limited deployment footprint and absence of active exploitation signals.

Unauthenticated attackers can bypass signature verification in FlexPrice's QuickBooks webhook handler (HandleQuickBooksWebhook) through version 2.1.38 by omitting the intuit-signature header, enabling forged payment notifications that can mark invoices paid or overpaid. Exploitation requires knowledge of a valid tenant and environment ID and an active, network-reachable QuickBooks integration; deployments not using QuickBooks webhooks are unaffected. No public exploit identified at time of analysis, though a public technical write-up is available, and this is a credible, moderate-to-high integrity risk.

Improper authentication in the SAML SSO identity-linking flow of self-hosted Sentry 26.5.0 through 26.7.1 lets an attacker who controls a SAML identity provider trick an already-authenticated user into opening a crafted URL, link the attacker's federated identity to that user's Sentry account, and achieve full account takeover (CVSS 4.0 base 7.6, High; independent assessment CVSS 3.1 7.6 with C:H/I:H). Exploitation is constrained by two prerequisites: the victim's browser must accept the cross-site cookie context (Firefox sending SameSite=None cookies, or Chromium with third-party cookies explicitly enabled, which is not the Chromium default), and the target deployment must have SAML SSO configured, so the realistically reachable population is narrower than the raw score suggests. Sentry SaaS was remediated on July 27, 2026 and is not affected; self-hosted instances are fixed in 26.7.2, and no public exploit code was identified at time of analysis.

Unauthenticated remote attackers who can reach Dgraph Zero's administrative HTTP port (default 6080) can read cluster topology via /state, allocate identifiers via /assign, invoke the exposed /moveTablet route, or remove cluster members via /removeNode in any Dgraph deployment prior to 25.4.0, destabilizing the Zero control plane and the Alpha nodes that depend on it. The /removeNode path accepts attacker-controlled id and group values and, when group 0 is supplied, reaches Server.RemoveNode and ProposePeerRemoval, giving a caller with only network access the ability to alter cluster membership. No public exploit identified at time of analysis, but the vendor CVSS 4.0 score of 9.2 reflects a fully remote, unauthenticated, low-complexity vector (PR:N confirmed) with high integrity and availability impact, cascading to dependent Alpha nodes; the practical limiting factor is network exposure of port 6080, which is intended to sit on a trusted network.

Eclipse Vert.x Web versions 4.0.0 through 4.5.34, 5.0.0 through 5.0.12, 5.1.0 through 5.1.9, and 5.2.0 contain a scope bypass in ChainAuthHandler that allows an authenticated remote attacker with a valid token but insufficient scopes to access resources protected by withScope() or withScopes() requirements. The flaw occurs when a preceding authentication handler in the request pipeline has already authenticated the user, causing ChainAuthHandler to skip scope validation in both any() and all() modes; the most common trigger is overlapping authentication handlers on nested routes. No public exploit code or active exploitation has been identified at time of analysis.

Insecure direct object reference in ServiceNext's /api/Usuario/GetUsuarios endpoint lets any authenticated user enumerate and retrieve the complete profile record of every other account - including passwords stored in cleartext - simply by iterating the numeric ID submitted in the request body, which enables account takeover and credential-stuffing. Rated CVSS 8.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), the flaw requires only a valid low-privileged token, no administrative role, no user interaction, and no non-default configuration, so exploitation works against default installations of the affected SerTec/ServiceNext 1.00 release. No public exploit code and no CISA KEV entry were identified at time of analysis, though the low complexity and the cleartext credential storage make the issue operationally severe once any account is obtained.

Authenticated users with query access to an administrator-configured DuckDB data source on Redash 26.0.0 through versions before 26.9.0 can read and write files on the Redash server with the privileges of the Redash process, because the DuckDB query runner opened connections with enable_external_access left at its default value of true. The practical impact escalates beyond data exposure: reading application secrets such as REDASH_COOKIE_SECRET or REDASH_SECRET_KEY allows forged session cookies and a full authentication bypass, which is why the issue carries a 9.3 CVSS 4.0 base score under a CWE-284 improper access control root cause. There is no public exploit identified at time of analysis, and exploitation is not possible without both an existing administrator-created DuckDB data source and a query-capable account (authenticated, low privileges per the CVSS PR:L metric), so instances that do not use the DuckDB query runner are unaffected.

Missing authorization in the Skydropx WordPress plugin (versions through 2.1.4) allows unauthenticated remote attackers to bypass access controls, potentially disclosing sensitive data with high confidentiality impact and limited integrity impact. The flaw is remotely exploitable with low complexity and requires no privileges or user interaction. No public exploit code has been identified at time of analysis, and there is no confirmation of active exploitation (CISA KEV).

Elevation of privilege in Microsoft SharePoint Server Subscription Edition lets an authenticated, low-privileged user perform actions reserved for higher-privileged accounts over the network, yielding high confidentiality, integrity, and availability impact across the affected server. The flaw is a missing authorization check (CWE-862) rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), so it is not usable by fully unauthenticated outsiders: the attacker must already hold a valid low-privilege SharePoint account and the site must be network-reachable, with no user interaction or non-default configuration required. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, so exploitation requires a motivated authenticated insider or an attacker who has already obtained low-privilege credentials; Microsoft has published a vendor patch, making this a straightforward fix-and-prioritize item for exposed SharePoint deployments.

Eclipse NetX Duo's NetX Secure DTLS server can be driven into completing handshakes with forged source addresses because the cookie it issues in a HelloVerifyRequest is never actually validated: the ClientHello parser copies the client-supplied cookie bytes over the value the server generated, and the server then treats the peer as verified based on the cookie's length alone, so a single arbitrary cookie byte in the first ClientHello skips the return-routability exchange entirely. The defect is remotely reachable with no authentication and no user interaction (CVSS 4.0 base 8.7, High; the independent assessment confirms AV:N/AC:L/PR:N/UI:N with an availability-only impact), and the practical harm is anti-spoofing and availability abuse - spoofed-source handshakes, amplification potential, and handshake state/resource exhaustion - not data compromise or code execution. No public exploit code has been identified at time of analysis, and CVE-2026-106465 is not listed in CISA KEV.