Authentication Bypass
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
How It Works
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications. Instead of cracking passwords through brute force, attackers manipulate the authentication process itself to gain unauthorized entry. This typically occurs through one of several pathways: exploiting hardcoded credentials embedded in source code or configuration files, manipulating parameters in authentication requests to skip verification steps, or leveraging broken session management that fails to properly validate user identity.
The attack flow often begins with reconnaissance to identify authentication endpoints and their underlying logic. Attackers may probe for default administrative credentials that were never changed, test whether certain URL paths bypass login requirements entirely, or intercept and modify authentication tokens to escalate privileges. In multi-step authentication processes, flaws in state management can allow attackers to complete only partial verification steps while still gaining full access.
More sophisticated variants exploit single sign-on (SSO) or OAuth implementations where misconfigurations in trust relationships allow attackers to forge authentication assertions. Parameter tampering—such as changing a "role=user" field to "role=admin" in a request—can trick poorly designed systems into granting elevated access without proper verification.
Impact
- Complete account takeover — attackers gain full control of user accounts, including administrative accounts, without knowing legitimate credentials
- Unauthorized data access — ability to view, modify, or exfiltrate sensitive information including customer data, financial records, and intellectual property
- System-wide compromise — admin-level access enables installation of backdoors, modification of security controls, and complete infrastructure takeover
- Lateral movement — bypassed authentication provides a foothold for moving deeper into networks and accessing additional systems
- Compliance violations — unauthorized access triggers breach notification requirements and regulatory penalties
Real-World Examples
CrushFTP suffered a critical authentication bypass allowing attackers to access file-sharing functionality without any credentials. The vulnerability enabled direct server-side template injection, leading to remote code execution on affected systems. Attackers actively exploited this in the wild to establish persistent access to enterprise file servers.
Palo Alto's Expedition migration tool contained a flaw permitting attackers to reset administrative credentials without authentication. This allowed complete takeover of the migration environment, potentially exposing network configurations and security policies being transferred between systems.
SolarWinds Web Help Desk (CVE-2024-28987) shipped with hardcoded internal credentials that could not be changed through normal administrative functions. Attackers discovering these credentials gained full administrative access to helpdesk systems containing sensitive organizational information and user data.
Mitigation
- Implement multi-factor authentication (MFA) — requires attackers to compromise additional verification factors beyond bypassed primary authentication
- Eliminate hardcoded credentials — use secure credential management systems and rotate all default credentials during deployment
- Enforce authentication on all endpoints — verify every request requires valid authentication; no "hidden" administrative paths should exist
- Implement proper session management — use cryptographically secure session tokens, validate on server-side, enforce timeout policies
- Apply principle of least privilege — limit damage by ensuring even authenticated users only access necessary resources
- Regular security testing — conduct penetration testing specifically targeting authentication logic and flows
Recent CVEs (37369)
Broken access control in Frontend Admin by DynamiApps (WordPress plugin, versions ≤ 3.29.10) allows subscriber-level authenticated users to perform unauthorized privileged operations, resulting in high availability impact and limited integrity compromise on affected WordPress installations. The flaw stems from missing authorization checks (CWE-862), permitting low-privilege users to invoke restricted plugin functionality without proper capability verification. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Authentication bypass in the Login with Phone Number WordPress plugin (≤1.8.70) allows remote, unauthenticated attackers to circumvent the login mechanism via an authentication capture-replay technique (CWE-290), achieving full account takeover with high confidentiality, integrity, and availability impact. Exploitation carries high attack complexity (CVSS AC:H), meaning a specific race condition, token-interception window, or knowledge of a registered phone number is likely required. No public exploit or CISA KEV listing has been identified at time of analysis, but the attack surface is any internet-accessible WordPress site running the affected plugin.
Broken Access Control in the AnsPress WordPress plugin version 4.4.4 allows authenticated subscriber-level users to perform high-integrity write operations that should be restricted to higher-privileged roles. The CVSS vector (PR:L, I:H) confirms low-privilege network exploitation with no user interaction required, making any WordPress site with open user registration a viable target. No active exploitation has been confirmed (not in CISA KEV), and no public POC is referenced in available data.
Broken access control in the Staff Training WordPress plugin (versions ≤ 1.0.7, by Solutioned) exposes protected plugin functionality to unauthenticated remote attackers, enabling unauthorized read, write, and limited availability impacts against affected WordPress installations. The root cause is CWE-862 (Missing Authorization) - one or more plugin-registered endpoints fail to verify caller capabilities before executing privileged operations. No public exploit code or active exploitation has been confirmed at time of analysis, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates extremely low exploitation complexity against any reachable WordPress site running the affected plugin.
Unauthenticated IDOR in the Formidable Forms Signature Online Contract Automation WordPress plugin (≤2.0.1) exposes contract documents and signature records to any remote, unauthenticated attacker who can enumerate object reference identifiers. The CVSS 7.5 (High) rating reflects network-accessible exploitation with no authentication, no user interaction, and high confidentiality impact - consistent with unrestricted read access to potentially sensitive legal and personal contract data. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the low attack complexity makes this trivially scriptable.
Broken access control in the BOX NOW Delivery Croatia WordPress plugin (versions <= 3.3.0) allows unauthenticated remote attackers to access restricted plugin functionality due to missing authorization checks, exposing sensitive data with high confidentiality impact. Reported by Patchstack and tracked under EUVD-2026-53962, this flaw is exploitable over the network with no credentials or user interaction required, making it trivially accessible to any attacker who can reach a vulnerable WordPress installation. No public exploit code or active exploitation has been identified at time of analysis.
Broken access control in the JetFormBuilder WordPress plugin (versions ≤ 3.6.4.1) allows unauthenticated remote attackers to perform privileged actions due to missing authorization checks (CWE-862), resulting in high integrity impact. Reported by Patchstack, the CVSS vector AV:N/AC:L/PR:N/UI:N confirms exploitation requires no authentication, no user interaction, and no special configuration beyond having the plugin installed and active. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Privilege escalation in the Kadence WooCommerce Email Designer WordPress plugin (all versions up to and including 1.5.19) lets unauthenticated remote attackers gain elevated privileges due to a missing authorization check (CWE-862). Reported by Patchstack and tracked as EUVD-2026-53939, the flaw carries a CVSS 9.8 (AV:N/AC:L/PR:N/UI:N) rating, so no login or user interaction is required. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, so exploitation is not confirmed in the wild.
Remote attackers without any authentication can bypass authorization checks in the Simple Membership WordPress plugin (versions ≤ 4.7.8), enabling unauthorized write operations against membership-protected resources. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) confirms exploitation requires no credentials, no user interaction, and low complexity, making this trivially scriptable at scale against any WordPress site running the affected plugin. No public exploit code or CISA KEV listing has been identified at time of analysis, though the Patchstack disclosure provides sufficient detail for independent exploit development.
Unauthenticated arbitrary file read in OpenChamber 1.11.7 lets remote attackers pull any file off the host by setting the allowOutsideWorkspace=true query parameter with an absolute path against the /api/fs/read, /api/fs/stat, and /api/fs/raw endpoints. Because the workspace boundary check in resolveReadPathFromContext relies on a vacuous isPathWithinRoot guard, attackers can harvest the JWT signing secret, SSH private keys, and API credentials, then forge session cookies to fully bypass authentication on password-protected deployments. Reported by VulnCheck with an upstream fix committed; no public exploit identified at time of analysis.
Missing authorization checks in the Breakdance WordPress page builder plugin (all versions before 2.7) allow unauthenticated remote attackers to access protected functionality due to improperly configured access control levels. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) confirms network-reachable exploitation with no credentials required and high confidentiality impact, meaning sensitive data accessible only to authenticated users can be read by anonymous attackers. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Cryptographic timing side-channel in OMICRON StationScout before version 3.05 allows unauthenticated network attackers to forge valid authentication credentials, bypass authentication and authorization entirely, and impersonate legitimate clients - granting full access to system configuration and the ability to inject traffic into the connected substation network. The CVSS 4.0 vector confirms unauthenticated remote exploitability (PR:N, AV:N) with high complexity (AC:H) reflecting the statistical measurement precision timing attacks require, and scope-change indicators (SC:H/SI:H/SA:H) capture downstream risk to connected OT systems. No public exploit has been identified at time of analysis, and the CVSS 4.0 supplemental metric E:U corroborates absence of confirmed exploitation.
Authentication bypass in OMICRON StationGuard before version 4.10 enables unauthenticated remote attackers to forge valid credentials by exploiting a cryptographic timing side-channel in the backend authentication mechanism (CWE-208). Successful exploitation grants full administrative control over the substation monitoring system configuration, including the ability to modify, reset, or alter system parameters - a high-consequence outcome in operational technology environments where configuration integrity is safety-relevant. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV, but the network-reachable, zero-privilege attack surface warrants priority patching in OT network segments.
Authentication bypass in Apache CXF's OIDC relying-party implementation allows network-accessible attackers to forge self-issued ID tokens that skip all required OpenID Connect claim checks - issuer, subject, audience, time bounds, and sub_jwk binding - effectively impersonating any user identity. Affected are all Apache CXF versions prior to 4.2.3, 4.1.8, and 3.6.12 when the relying party is explicitly configured to accept self-issued OIDC tokens, a non-default setting. No public exploit or CISA KEV listing has been identified at time of analysis, but the attack surface is constrained to a narrow set of deliberately misconfigured deployments.
CatchPulse endpoint security software exposes an unrestricted kernel filter communication port that any non-administrative local user can connect to, enabling complete bypass of its security policy enforcement. The CVSS scope-changed vector (S:C, I:H, A:H) reflects that a low-privileged local user can subvert kernel-level security controls - effectively neutralizing the host's endpoint protection layer. No public exploit code has been identified at time of analysis, but the CSA Singapore advisory (AL-2026-098) indicates official government-level disclosure.
Authentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane, and the Carbon API Manager REST API Utility) allows remote unauthenticated attackers to forge JWT tokens because the authentication layer accepts tokens signed with algorithms outside the explicitly configured/supported set. By crafting a JWT with an unsupported or attacker-chosen algorithm that is then incorrectly validated, an attacker can gain unauthorized access up to full administrative account takeover. Rated CVSS 10.0 (scope-changed) by WSO2, with the description noting a contained 9.8 score for single-tenant deployments; no public exploit identified at time of analysis.
Unauthenticated license-key erasure and premium deactivation is possible in the Checkimate WooCommerce Checkout, Abandoned Cart Recovery & Order Bumps WordPress plugin through version 1.0.13. The plugin's license-management endpoint relies on a shared secret computed exclusively from publicly available site information - an authentication bypass that renders the access control trivially circumventable. Any remote attacker who can reach the WordPress site can permanently erase the stored license key and strip the installation of its paid premium status; a public proof-of-concept exists (reported by WPScan), though EPSS remains low at 0.14%, indicating opportunistic rather than widespread exploitation at time of analysis.
Payment amount manipulation in Stripe Payment Forms by WP Full Pay (WordPress plugin) before version 8.5.2 allows any unauthenticated visitor to arbitrarily lower - or potentially zero-out - the price of a Stripe payment intent before checkout completes. The flaw stems from an incomplete authorization fix in 8.5.0 that patched only one of the two vulnerable AJAX handlers, leaving the pricing-recalculation and payment-intent-update endpoints exposed. A publicly available proof-of-concept exists, and SSVC analysis confirms the vulnerability is automatable, raising the practical risk above what the low EPSS score (0.13%, 3rd percentile) alone would suggest.
Session hijacking via SAML assertion replay in Keycloak's SAML broker component allows adjacent-network attackers to authenticate as arbitrary users without credentials. When Keycloak is deployed as a SAML broker in IdP-Initiated flow mode, it fails to enforce the SAML OneTimeUse condition, permitting a captured assertion to be submitted multiple times. No public exploit has been identified at time of analysis, and EPSS sits at 0.14% (4th percentile), though SSVC rates technical impact as total - reflecting the full account takeover consequence if the preconditions are met.
Authentication bypass in WPMU DEV Dashboard (WordPress plugin) versions up to and including 5.0.0 enables unauthenticated remote attackers to invoke privileged Hub actions - including remote code execution by installing a plugin from an attacker-controlled URL, takeover of an administrator account via SSO, deletion of plugins and themes, and forced WordPress core upgrades - on any site not yet connected to the WPMU DEV Hub. The default post-installation state is unconnected, meaning every fresh installation is immediately exposed until Hub onboarding is completed. No public exploit or CISA KEV listing has been identified at time of analysis, though the impact ceiling (unauthenticated RCE) and the breadth of default-state exposure make this a high-priority remediation target.
Arbitrary file deletion and read access in the File Manager WordPress plugin (versions 6.0-6.9) allows any authenticated user with subscriber-level access or above to delete or read arbitrary server files, including wp-config.php, which can be leveraged for remote code execution. The flaw is rooted in a parameter-source discrepancy in elFinder's connector: the bind registration for the rm.pre permission handler reads exclusively from $_POST, while the dispatcher reads from the merged $_GET+$_POST superglobal - allowing an attacker to inject cmd=rm or cmf=file via the URL query string of a POST request, entirely bypassing authorization checks. A patched version (6.9.1) has been released per the WordPress plugin repository changeset; no public exploit has been identified at time of analysis, though the Wordfence disclosure provides sufficient technical specificity for exploitation.
Access control bypass in Open Library Foundation VuFind versions 11.0.3 and 4.1 allows unauthenticated remote attackers to invoke controller functions that should be restricted. The AbstractBase::validateAccessPermission logic returns an 'access denied' response to the requester but fails to halt request processing, so the protected function still executes server-side. Categorized as an authentication/authorization bypass (CWE-863) with a reported CVSS 9.8; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Missing authorization on the group DM recipient endpoint in Spacebar Server allows any authenticated user to add themselves or arbitrary third parties to private group DM channels without being a member. Versions prior to commit dcfd91035e3da42abf5f32d8d86a35219225b3d4 expose the unguarded PUT /channels/{channel_id}/recipients/{user_id} handler, granting attackers full read and write access to private conversation history. No public exploit code or active exploitation has been identified at time of analysis, but the commit diff and GHSA advisory are publicly available, lowering the bar for exploitation.
Hardcoded shared Bluetooth authentication key in KARR BT and DR-100 dealer-installed automotive anti-theft systems allows any attacker within Bluetooth range to issue unauthorized commands to affected vehicles without credentials. Exploitation requires only physical proximity and basic Bluetooth tooling, enabling door unlocking and engine immobilization on any unit sharing the static key. No public exploit or CISA KEV listing has been identified at time of analysis, but the hardcoded key class of vulnerability (CWE-321) is well-understood and trivially reversible once discovered.
Unauthenticated denial of service in Milvus through 2.6.22 and 3.0.0 allows any remote attacker with network access to port 9091 to immediately terminate core service components - proxy, datanode, or querynode - by issuing a single crafted HTTP GET request. The management server's /management/stop endpoint is not protected by the REST API authentication middleware, making exploitation trivial with a publicly available proof-of-concept. No CISA KEV listing exists at time of analysis, but the combination of zero-prerequisite exploitation, public PoC, and CVSS 4.0 score of 8.7 represents a high real-world availability risk for any Milvus deployment with port 9091 reachable beyond localhost.
Unauthenticated remote command execution in PraisonAI's bundled Claude GitHub Actions workflow (versions before 4.6.40) lets an outside contributor run arbitrary shell code on the CI runner by opening a fork pull request whose branch name contains shell metacharacters and posting an @claude comment. Two compounding flaws enable this: the workflow interpolates the attacker-controlled branch name directly into an unquoted Bash run: block, and it triggers for any @claude comment without verifying the commenter is a trusted collaborator. Because the job runs with a GitHub App token holding write permissions plus OIDC and gh/git access, injected commands can be chained via $GITHUB_PATH into later privileged steps to gain repository write, PR/issue manipulation, or OIDC-token abuse. No public exploit identified at time of analysis.
Cross-user chat history disclosure in IBM Langflow OSS 1.0.0-1.10.3 allows any authenticated user to read other users' conversation history by exploiting session_id collision in the MemoryComponent. The MemoryComponent.retrieve_messages and store_message methods validate only session_id when filtering records, omitting flow_id and user_id ownership checks, which exposes multiple REST API endpoints to unauthorized cross-user data access. No public exploit has been identified at time of analysis, but the straightforward exploitation path and High confidentiality impact make this a genuine remediation priority for any multi-user Langflow deployment.
Broken access control in IBM Langflow OSS 1.0.0-1.10.3 allows any authenticated user to inject arbitrary graph data into the shared execution cache for flows they do not own, via the deprecated POST /api/v1/build/{flow_id}/vertices endpoint. The endpoint performs no ownership validation, enabling cross-user cache pollution that can corrupt other users' workflow state, trigger unauthorized execution of foreign flows, or produce denial of service across a shared platform instance. No public exploit code exists and CISA KEV does not list this vulnerability; EPSS (0.20%, 10th percentile) and SSVC (exploitation: none, automatable: no) collectively indicate low immediate exploitation risk despite the high CVSS score.
Authentication bypass in IBM Langflow OSS 1.0.0 through 1.10.3 exposes the Model Context Protocol (MCP) composer endpoint to unauthenticated remote access when projects are configured with auth_type=oauth and MCP composer is enabled - which is the default deployment state. An unauthenticated network attacker can reach the MCP composer endpoint and read confidential project data (C:H) without supplying valid credentials, entirely bypassing the OAuth authentication gate. No public exploit code or CISA KEV listing has been identified at time of analysis, but the vendor (IBM) has confirmed the issue and released a patch.
Remote authenticated attackers can bypass localhost-only access restrictions in IBM Langflow OSS 1.0.0 through 1.10.3 to write arbitrary MCP (Model Context Protocol) server configurations to IDE configuration files on the underlying host system. The CVSS scope change (S:C) confirms this escapes the Langflow application boundary, enabling persistent manipulation of developer IDE environments on the host. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor-released patch is available.
Privilege escalation and authentication-boundary bypass in Cisco Catalyst SD-WAN Manager and SD-WAN Controller allows a low-privileged, remote authenticated attacker to abuse improper access-control checks (CWE-284) to reach functionality or data intended for higher-privileged roles, with full confidentiality, integrity, and availability impact (CVSS 9.9, scope changed). The flaw was discovered internally by Cisco during a proactive hardening review and shipped as part of a consolidated software-hardening release; there is no public exploit identified at time of analysis and it is not listed in CISA KEV. Because SD-WAN Manager is the central orchestration plane for an entire SD-WAN fabric, successful abuse can cascade beyond the compromised component to the managed network.
Authentication bypass and improper access control in Cisco IOS XE Software allow a remote, unauthenticated attacker to gain unauthorized access with a scope-changing impact affecting confidentiality, integrity, and availability across affected components. The issue was discovered internally by Cisco's engineering team during a proactive security review and is grouped under CWE-284 with a CVSS base score of 9.0, though the high attack complexity (AC:H) indicates non-trivial preconditions. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
Context isolation bypass in Electron allows untrusted web content loaded by an Electron app to escape the contextBridge security boundary and access the isolated preload world - and potentially Node.js - by hijacking Function.prototype.bind on exposed Promise-returning functions. The vulnerability (CVSS 7.5, S:C) affects the standard pattern developers use to wrap ipcRenderer.invoke calls, meaning a wide class of real-world apps is susceptible if they load any untrusted content. No vendor-side workarounds exist; patched releases are available across all active Electron version lines. No public exploit code or CISA KEV listing has been identified at time of analysis.
Authentication bypass in the ODBC App Server of Progress MarkLogic Server (before 11.3.6 and 12.0.3) lets an unauthenticated remote attacker circumvent password verification and run queries as any named user, including administrators. Because impersonation extends to admin-level accounts, an attacker gains full read/write control over the database and its data. No public exploit has been identified at time of analysis, but the CVSS 9.8 rating and admin-impersonation impact make this a critical, network-reachable flaw.
HTTP request smuggling in Progress MarkLogic Server's HTTP App Server (versions before 11.3.6 and 12.0.3) lets a remote attacker desynchronize request parsing between a fronting reverse proxy and MarkLogic, enabling authentication/authorization bypass, session hijacking, and credential capture. The flaw is exploitable over the network without authentication (PR:N) and carries a critical 9.1 CVSS with high confidentiality and integrity impact. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; no EPSS score was supplied.
Authentication bypass in Progress MarkLogic Server (versions before 11.3.6 and 12.0.3) lets an unauthenticated remote attacker forge SAML assertions and impersonate any user, including administrators, on deployments where SAML single sign-on is enabled. The flaw stems from improper cryptographic signature verification (CWE-347) in the SAML authentication module, yielding full identity spoofing over the network with low complexity and no user interaction. No public exploit identified at time of analysis, and the CVE is not listed in CISA KEV, but the 9.1 CVSS and pre-authentication admin impersonation make it a high-priority patch.
Account takeover in Apache Answer through 2.0.1 allows unauthenticated remote attackers to seize arbitrary user accounts by exploiting a missing authorization check in the external-login OAuth email binding workflow. The attacker crafts a malicious confirmation link and socially engineers a target into clicking it, after which the attacker's external identity is silently bound to the victim's Answer account. No active exploitation has been identified (CISA KEV absent, EPSS at 7th percentile), but the SSVC framework flags the attack as automatable, making phishing-at-scale campaigns mechanically feasible.
Account takeover in Keycloak (Red Hat build of Keycloak, Red Hat Single Sign-On 7) arises because the IdP-initiated SAML SSO endpoint does not verify whether an upstream identity provider is restricted to account-linking-only mode. An attacker who controls a linked upstream identity can drive that endpoint to complete a full login rather than a mere link operation, seizing complete access to the corresponding local user account. Red Hat has shipped fixes; there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.19%).
Account takeover in Flarum forum software before 1.8.16 lets remote unauthenticated attackers reuse expired password reset tokens by POSTing them directly to the reset endpoint, bypassing the 24-hour token lifetime that is only enforced when the reset form is rendered. Because SavePasswordController::handle() calls PasswordToken::findOrFail() with no expiry check, anyone holding a stale-but-still-existing token can set a new password and log in as that user. Reported by VulnCheck; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Missing authorization on Penpot's ::import-binfile RPC command allows any authenticated user to overwrite arbitrary files across team boundaries and subscribe to WebSocket events for any file on the instance, enabling cross-tenant data exfiltration and data poisoning. All Penpot deployments on versions up to and including 2.17.0 are affected per EUVD intelligence, with a proof-of-concept publicly documented by vokecyber.com. The provided CVSS vector critically understates impact: it omits confidentiality and integrity loss despite the described full data exfiltration and file overwrite capability, and marks the vulnerability as unauthenticated (PR:N) contrary to the description's explicit 'authenticated user' requirement - defenders should not rely on the published vector for risk prioritization.
Privilege escalation in Keycloak's Dynamic Client Registration (DCR) component allows attackers with standard user accounts and limited Initial Access Tokens to forge administrative roles directly into their own access tokens. The underlying flaw is a missing claim-path validation in the default DCR policy for User Property mappers, which permits writing attacker-controlled values into sensitive internal claim locations that normally carry role and privilege assertions. Successful exploitation enables takeover of other registered OAuth clients, exfiltration of confidential client secrets, and full administrative control over the affected Keycloak realm. No confirmed active exploitation or public exploit code is identified at time of analysis.
Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge SAML responses to hijack accounts when a SAML identity-provider's metadata was imported without explicit key-usage attributes, causing the keycloak-services identity-brokering engine to silently disable signature validation despite a signing certificate being present. Rated CVSS 9.1 with total technical impact per CISA SSVC, an attacker who knows a victim's external identifier can log in as that user. No public exploit identified at time of analysis, and EPSS is low (0.14%, 4th percentile), indicating the risk is currently theoretical/targeted rather than mass-exploited.
Unauthenticated REST API access in the wiseCampaign - WooCommerce Conversions Made Easy WordPress plugin (all versions through 1.1.16) allows any network attacker to read and overwrite the plugin's banner, stockbar, and core settings, and to upload arbitrary background image files via wp_handle_upload(), with zero authentication or nonce validation. Every REST endpoint the plugin registers uses the blanket permission callback '__return_true', which bypasses WordPress's built-in capability and nonce checks entirely. No public exploit code or CISA KEV listing has been identified at time of analysis, but the unauthenticated, low-complexity attack surface makes this straightforward to exploit opportunistically.
Missing authentication in the NASA-AMMOS ANMS reference implementation exposes the amp-manager REST API (CivetWeb, port 8089) directly on the host network, allowing any network-reachable client to command DTNMA agents without credentials. Because the shipped docker-compose.yml publishes the port and bypasses the CAM authentication gateway, unauthenticated remote attackers can enumerate agents, submit arbitrary EXECSET command sets to them, and clear stored reports. No public exploit identified at time of analysis; the flaw affects the reference/testbed implementation rather than onboard spacecraft flight software, though managed agents may represent real ground or space nodes depending on deployment.
Authentication bypass in iot-ecology's rust-iot-platform lets any remote attacker reach every endpoint guarded by the AuthToken request guard simply by sending a non-empty Authorization header such as 'Authorization: fake'. The Rocket request guard in api/src/main.rs checks only for the header's presence and never validates its value against a session, token store, or signature, so unauthenticated attackers gain full access to protected API functionality. No public exploit identified at time of analysis, but the flaw is trivial to trigger and carries a CVSS 9.1.
Unauthenticated network access to WLED's GET /json/cfg endpoint exposes full device configuration - including network credentials, hardware layout, and LED setup - to any client on the same network, while a separate global-state authentication flaw in wled.h allows any attacker who submits the correct 4-digit PIN via POST /json to instantly grant full write access to all subsequent unauthenticated clients until the device reboots. The write-access window enables critical operations including OTA firmware flashing, WiFi reconfiguration, and factory reset. No public exploit code or CISA KEV listing has been identified at time of analysis, but the 10,000-combination PIN space with no described rate-limiting makes the authentication bypass trivially automatable against any network-reachable WLED instance.
Missing authentication in IoTSharp's BlobStorageController lets unauthenticated remote attackers reach Upload, Download, List, Modify, and Delete blob endpoints that every other controller (Devices, Customers, Tenants) guards with [Authorize]. Because the path and filename parameters are written to disk without sanitization, attackers can traverse outside the blob directory to read, alter, or delete arbitrary files - and drop a webshell into a web-accessible path for remote code execution. No public exploit identified at time of analysis, but the combination of unauthenticated access and a clear RCE path makes this trivially weaponizable.
Unauthenticated remote write access in the toner-management PHP application allowed any attacker to invoke admin-tier database operations - INSERT, UPDATE, and DELETE - across inventory entities including toners, printers, consumers, tickets, and staff records. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no credentials, session token, or user interaction are required; the admin write handlers (add.php, edit.php, delete.php) were directly reachable over HTTP and processed SQL operations unconditionally. A fix has been merged via GitHub PR #1 adding session-based admin role validation to all affected handlers, but no formally tagged release version has been confirmed. No public exploit code and no CISA KEV listing are identified at time of analysis.
SQL injection in the Inventory-Management-System-PHP application (Harsh21Patel GitHub project) allows unauthenticated attackers to fully bypass authentication and destructively manipulate the product database. login.php concatenates raw POST email/password into its query, so a payload like email=' OR 1=1 LIMIT 1-- - logs in as the first user, while delete.php runs a DELETE on an unsanitized GET id parameter with no auth check, enabling arbitrary row deletion and blind SQLi. No public exploit identified at time of analysis, though the advisory itself publishes working payloads; the flaw carries CVSS 9.8 and is not listed in CISA KEV.
Cross-company note access in the Crater open-source invoice platform allows any authenticated user to read, modify, or delete notes belonging to an entirely different company by supplying a foreign note ID in the API. NotePolicy omits the company-ownership verification (hasCompany) that sibling policies such as InvoicePolicy correctly enforce, and NotesController's show(), update(), and destroy() actions call authorize() without passing the target Note model instance, meaning no per-resource ownership check ever executes. No public exploit has been identified at time of analysis, but the CVSS 8.3 rating reflects that the technique requires only sequential ID enumeration against a standard multi-tenant deployment - a low-effort, high-impact path to cross-tenant data exfiltration and tampering.
Five Flask API endpoints in Book-Management-System (/student, /record, /books, /find_stu_book, /find_not_return_book) are missing authentication controls, exposing student PII and borrowing history to any unauthenticated remote caller. Because the card_id parameter is a sequential integer, a trivial enumeration loop can drain the entire student database without credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, but the attack requires no sophistication and is fully network-accessible.
Full account takeover in DjangoCRM stems from a hardcoded Django SECRET_KEY committed in webcrm/settings.py, letting anyone who reads the public GitHub repository forge session cookies (including the superadmin), CSRF tokens, and password reset tokens. The default DEBUG=True setting compounds this by exposing database, email, and OAuth credentials plus internal paths on error pages. No public exploit is identified at time of analysis, but exploitation is trivial and requires no authentication (CVSS 9.1, PR:N).
Unauthenticated attachment download in Documize Community exposes all organization files to any remote attacker via a trivially bypassable token check. The Download handler in domain/attachment/endpoint.go, registered via AddPublic without auth middleware, validates the `secure` query parameter only by checking that it is non-empty (len(secureToken) > 0) rather than comparing it to a server-stored secret - meaning any request with `?secure=x` succeeds. Notably, sibling handlers in the same file (togglePublish, delete) enforce proper session-based authorization, confirming this is an implementation inconsistency rather than deliberate design. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis, but the attack requires no authentication, no special tools, and trivial construction.
Unauthenticated access to NeuVector's manager /network/graph API exposes cached network topology data in all versions through 5.4.9, allowing any network-reachable attacker to retrieve sensitive container environment details without credentials. The missing authentication on this endpoint (CWE-202) means the container security platform itself becomes a reconnaissance source, potentially revealing Kubernetes service relationships, container names, and network flow data to adversaries. No public exploit code or active exploitation (KEV) has been identified at time of analysis, but the unauthenticated network vector significantly lowers the bar for exploitation.
MailChimp Forms by MailMunch (WordPress plugin) versions up to and including 3.2.7 allows any authenticated subscriber-level user to silently hijack the site's MailMunch account integration, redirecting all captured lead data to an attacker-controlled account. The missing capability check on the `sign_in()` and `sign_up()` AJAX handlers (CWE-862) means a low-privilege WordPress account is sufficient to relink the plugin to an attacker's own MailMunch account - after which every form submission is delivered to the attacker and the site's forms and landing pages are served from the attacker's MailMunch workspace. No public exploit code has been identified at time of analysis, but the attack surface is trivially accessible to any authenticated user.
Unauthorized data modification in the Easy Post Submission plugin for WordPress (all versions through 2.3.0) lets unauthenticated attackers overwrite the title, content, excerpt, categories, tags, and publication status of any existing post by supplying its postId to a public AJAX endpoint. Because the rbsm_submit_post action is registered for logged-out users with no capability check, an anonymous request can silently rewrite or unpublish arbitrary site content, an integrity- and content-availability-focused flaw scored CVSS 9.1. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Authentication bypass in the NASA-AMMOS Aerie/PlanDev sequencing-server allows unauthenticated remote attackers to impersonate the aerie_admin role because the authorization middleware trusts a session_variables object supplied in the request body over the Authorization header JWT. An attacker who submits {"session_variables":{"x-hasura-role":"aerie_admin"}} to POST /command-expansion/put-expansion can insert arbitrary expansion rules that govern how spacecraft activities are translated into commands, and POST /put-dictionary is separately whitelisted for unauthenticated writes. Rated CVSS 9.8; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Cross-company customer record access in Crater 6.0.6 exposes a multi-tenant authorization flaw where any authenticated tenant user can read, modify, or permanently delete customer records owned by other companies. The CustomerPolicy authorization class omits the company_id ownership check that all other resource policies (Invoice, Estimate, Payment, Expense) correctly enforce, and route-model-bound customer lookups use unscoped queries (self::find($id)) that return records regardless of company ownership. No public exploit has been identified at time of analysis; the CVSS 8.3 (High) score reflects straightforward network-reachable exploitation by any low-privilege authenticated user, with cascading destruction of financial records as the worst-case availability impact.
Horizontal privilege escalation in Leantime through 3.6.2 allows any authenticated user to read live TOTP secrets or strip two-factor authentication from arbitrary accounts via unenforced JSON-RPC endpoints, fully defeating per-account 2FA protection. The four affected methods - getSetupData, saveSecret, verifyAndEnable, and disable2FA - accept a caller-supplied userId with no ownership check, session pinning, or permission gate, unlike other methods in the same RPC dispatcher. No public exploit has been identified at time of analysis and the flaw is not listed in CISA KEV, but the low exploitation complexity (authenticated, network-accessible, no user interaction) makes it a credible lateral-escalation risk in any multi-user Leantime deployment.
Sensitive information exposure in the Page and Post Restriction WordPress plugin (versions ≤ 1.4.0) allows unauthenticated attackers to read the full rendered content of every published page and post on sites relying on the plugin's global privacy toggles. The plugin's REST API guards - `papr_restrict_page_post_rest_api()` and the `the_posts` filter in `papr_filter_posts()` - consult only per-post/page metabox settings and completely ignore the 'Make all Pages Private' and 'Make all Posts Private' global options, leaving the `/wp-json/wp/v2/pages` and `/wp-json/wp/v2/posts` endpoints unguarded. No public exploit is identified at time of analysis, but the attack is trivially executable with a single unauthenticated HTTP GET request.
Unauthenticated access to the Material Dashboard WordPress plugin's task management AJAX endpoint exposes all WordPress sites running versions up to and including 1.4.10 to task enumeration, arbitrary task execution, and task deletion. The root cause is a missing capability check on the `amd_ajax_target_task_manager()` function, which is registered via the publicly accessible `public_amd_ajax_handler` AJAX action - reachable without any authentication by design of the hook registration. An attacker can enumerate scheduled tasks (potentially exposing PII stored in task parameters), force arbitrary task execution to trigger unintended server-side operations, or delete tasks to disrupt site functionality. No active exploitation confirmed at time of analysis; no public POC code referenced in available data.
Unauthenticated payment hijacking in WPFormify - Stripe Payments with Form and Checkout (all versions ≤ 1.1.1) allows any remote attacker to overwrite or delete the site's Stripe API credentials with zero authentication. Two plugin functions registered on WordPress's `admin_init` hook are reachable via the publicly accessible `admin-post.php` endpoint because they perform no capability check and no nonce verification. An attacker exploiting this can silently redirect all customer payments to an attacker-controlled Stripe account, or disable payment processing entirely by erasing the stored credentials - with no public exploit identified at time of analysis but trivially low exploitation complexity.
Unauthenticated sensitive information exposure in the AI Copilot - Content Generator plugin for WordPress (versions up to and including 1.4.6) allows any remote attacker to retrieve plaintext OpenAI API keys and full AI model configurations. The `getCurrentTaskResults()` method is exposed via `wp_ajax_nopriv_` AJAX hooks with no nonce validation, no authorization checks, and no permission guard - making task results freely accessible to unauthenticated callers. Attackers who enumerate sequential integer task IDs can exfiltrate every stored API key, prompt configuration, and keyword set from the site's database. No active exploitation is confirmed in CISA KEV, and no public exploit code has been identified at time of analysis, though the vulnerability is trivially exploitable given the low attack complexity.
Unauthorized arbitrary media deletion in the Multi Uploader for Gravity Forms WordPress plugin (all versions through 1.1.8) lets unauthenticated attackers permanently destroy any media library attachment. The flaw stems from the AJAX file-delete handler being wired to the nopriv hook without a capability check, while the CSRF nonce is leaked in page source, defeating the only protection present. No public exploit is identified at time of analysis, but exploitation is trivial and the EPSS/KEV signals are not yet populated for this recently disclosed issue.
Contest Gallery WordPress plugin before version 30.0.7 implements a custom front-end login mechanism that issues authentication cookies directly after password validation, entirely bypassing WordPress's standard authentication pipeline. This architectural shortcut renders all brute-force protection plugins and two-factor authentication plugins completely ineffective, allowing unlimited, unthrottled password guessing against any WordPress account - including administrators - up to full account takeover. A publicly available proof-of-concept exists per WPScan reporting, though CISA has not listed this in KEV and SSVC indicates no confirmed active exploitation at time of analysis.
Account takeover in the miniOrange 2FA WordPress plugin before 6.2.7 is enabled when an attacker already possesses a target user's password - the plugin fails to bind a newly configured second factor to the target account's existing registered factor during the pre-login two-factor challenge, allowing the attacker to redirect 2FA enrollment to an attacker-controlled device, complete the challenge, and authenticate as the victim including as site administrators. A publicly available proof-of-concept exists per WPScan, though EPSS sits at 0.14% (4th percentile), indicating exploitation has not yet become widespread. Critically, the published CVSS vector (C:N/I:N/A:H) severely misrepresents the actual impact - this is a full account-takeover flaw with high confidentiality and integrity consequences, not a denial-of-service; analysts should not use the published vector for risk calibration.
Two-factor authentication bypass in the WP 2FA WordPress plugin before 4.1.0 allows an attacker who possesses a valid user password to completely skip the second authentication factor and gain full account access, including administrator-level accounts. The plugin presents the 2FA challenge but fails to server-side validate the submitted factor for any of its supported methods, rendering 2FA protections entirely ineffective. A publicly available exploit exists (sourced from WPScan), though EPSS sits at 0.19% (9th percentile), indicating limited observed exploitation activity at time of analysis despite the public proof-of-concept.
Account takeover in the WordPress plugin "OTP Login With Phone Number, OTP Verification" before 1.8.71 stems from missing rate-limiting and non-invalidation of one-time login codes, letting an unauthenticated attacker request a login OTP for any account and brute-force the short numeric code to seize control of any user, including administrators. CVSS 9.1 (AV:N/AC:L/PR:N/UI:N) reflects trivial network exploitation with high confidentiality and integrity impact. Publicly available exploit code exists (reported by WPScan), though EPSS is low at 0.15% (4th percentile) and it is not in CISA KEV, so there is no public exploit identified as actively exploited in the wild.
Missing capability checks across multiple REST API routes in the YayPricing WordPress plugin (all versions before 3.5.7) allow any subscriber-level authenticated user to overwrite a WooCommerce store's complete pricing configuration and extract private coupon codes. The plugin incorrectly relies on a shared nonce as its sole authorization gate rather than WordPress capability checks, a fundamental access control failure classified under CWE-284. A publicly available exploit exists per WPScan (EUVD-2026-53116), though EPSS sits at 0.14% (4th percentile), indicating low automated exploitation activity; CISA KEV listing is absent, so active exploitation in the wild is not confirmed.
Registration enforcement bypass in the User Registration & Membership WordPress plugin (all versions before 5.2.6) allows unauthenticated users to create accounts on sites where the administrator has explicitly disabled open registration. The plugin processes registration form submissions without validating the site-level registration-disabled setting, effectively nullifying an administrative security control. A publicly available exploit exists per WPScan, though EPSS sits at a low 0.15% (4th percentile), indicating limited observed exploitation despite the accessible POC.
Broken object-level authorization in the MultiVendorX WordPress plugin before 5.0.11 allows any authenticated vendor (Store Owner role or above) to perform unauthorized cross-tenant operations against other vendors' stores via the REST API. The plugin fails to verify that the target store in a REST API request belongs to the authenticated vendor, enabling confidentiality breaches, store takeovers, permanent deletion, and arbitrary modification of competitor or co-platform stores. A publicly available exploit exists; EPSS probability is low (0.14%, 4th percentile) suggesting opportunistic or targeted exploitation rather than mass scanning, and this CVE is not currently listed in the CISA KEV catalog.
Unauthenticated information disclosure in the Sunshine Photo Cart WordPress plugin (all versions before 3.6.12) allows any internet-connected user to retrieve image comments from private, password-protected, or otherwise access-restricted galleries by exploiting a missing authorization check on an AJAX endpoint. The flaw is classified as CWE-862 (Missing Authorization) and carries a CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N). A publicly available proof-of-concept exists via WPScan, though EPSS at 0.15% (4th percentile) and no CISA KEV listing indicate no confirmed widespread exploitation at time of analysis.
Privilege escalation in Dokan (WordPress multivendor marketplace plugin) versions up to and including 5.0.1 enables any authenticated vendor or seller to read, modify, or delete any WordPress user account - including site administrators - via REST API calls to `/wp-json/dokan/v1/customers/{id}`. The plugin's `CustomersController` re-registers WooCommerce's customer CRUD routes but replaces the native `manage_woocommerce` capability gate with a flawed check that inspects only the requesting user's role and never validates authorization against the target user. Setting the `password` parameter on an administrator's record via a PUT request yields full site takeover. No public exploit identified at time of analysis, though the attack is mechanically trivial for any Vendor-role account holder.
Missing admin authorization on the embedding management API in Odysseus allows any authenticated non-admin user to overwrite or delete the server-wide embedding backend configuration, redirecting all subsequent embedding operations - including chat messages, RAG queries, memory entries, and vault text - in plaintext to an attacker-controlled URL. All deployments running any version prior to commit bf325f6 are affected. A public exploit and detailed write-up are available, and the CVSS 4.0 score of 8.7 (PR:L) reflects the low barrier to exploitation for any account holder.
Unauthorized permanent deletion of chat history in Open WebUI 0.10.x allows any authenticated write-collaborator on a shared folder to destroy the folder owner's chats, messages, and entire subfolder subtree via the DELETE /api/v1/folders/{id} endpoint. The flaw stems from a split authorization check that enforced ownership for root folders but accepted write-grant access for subfolders, while the cascade deletion itself ran under the owner's identity - meaning the collaborator's lower-privilege check granted them the owner's destructive reach. No public exploit has been identified at time of analysis, and exploitation requires a non-default configuration, but the impact is irreversible data destruction with no recovery path.
Improper authorization in ERPNext's CRM module allows authenticated low-privileged users to retrieve CRM opportunity data beyond their permitted scope via the whitelisted API method erpnext.crm.doctype.prospect.prospect.get_opportunities. Versions before 15.115.0 and before 16.26.0 are affected, with patches now available from Frappe. No public exploit code or CISA KEV listing has been identified at time of analysis, though the low-privilege, network-accessible nature of the flaw makes it a realistic insider threat or credential-abuse vector.
OAuth token exchange in Open WebUI 0.8.0-0.10.x enables full, silent account takeover when ENABLE_OAUTH_TOKEN_EXCHANGE=True because the endpoint accepted provider access tokens minted for any OAuth client without verifying the issuing client identity. The endpoint validated tokens exclusively via the provider's userinfo endpoint, which confirms token validity but never returns the client a token was issued to, allowing an attacker who captures a victim's token from any co-registered application to exchange it for a valid Open WebUI session - including administrator sessions with no role gating. A proof-of-concept is confirmed by the upstream advisory; no active exploitation is recorded in CISA KEV, and the CVSS 8.1 score reflects high confidentiality and integrity impact tempered by a required victim interaction step.
Authentication bypass in MaxSite CMS version 109.5 and earlier lets unauthenticated remote attackers reach admin-gated AJAX endpoints by sending any X-Requested-With header alongside a base64-encoded path that resolves to any *-ajax.php file in the codebase. Because the dispatcher never verifies an admin session, attackers can invoke privileged plugin operations - demonstrated by manipulating poll states and vote counts - and can amplify any dangerous action exposed by admin-only AJAX files across the plugin tree. No public exploit identified at time of analysis, but the flaw was reported by VulnCheck and a fixed release (109.6) is available.
Cross-tenant billing manipulation in Flowise's enterprise API allows any authenticated user to perform unauthorized Stripe subscription operations against other organizations by supplying an arbitrary victim subscriptionId to the /update-subscription-plan and /update-additional-seats endpoints. All Flowise enterprise deployments running versions prior to 3.1.3 are affected, with impact including unauthorized plan downgrades, seat-count inflation (inflating victim billing), and service disruption across tenants. No public exploit code or CISA KEV listing exists at time of analysis, but the vulnerability is mechanically straightforward given knowledge of a target organization's Stripe subscription identifier.
Missing authorization middleware on the PUT /api/v1/executions/:id endpoint in Flowise prior to 3.1.3 allows any authenticated workspace member, regardless of assigned RBAC role, to overwrite execution state, data, and metadata for any workflow execution in their workspace. The flaw is a straightforward RBAC enforcement gap - the checkAnyPermission() middleware present on all sibling GET and DELETE routes was omitted from the PUT handler - making privilege escalation trivially reproducible with a single authenticated API call. No confirmed active exploitation (not in CISA KEV), but a working proof-of-concept curl command is published in the vendor's GitHub security advisory, and a vendor-released patch is available in version 3.1.3.
Authentication bypass in Atlas-Livre, a PHP guestbook/livre d'or web application by maximeAmini, lets unauthenticated remote attackers reach admin-only controller endpoints under Espace_admin/controleur/ and trigger destructive actions such as record deletion. The flaw stems from PHP redirect guards that call header() without a following exit/die, so protected code keeps executing regardless of session state. No public exploit is confirmed via KEV, though a referenced GitHub gist may contain proof-of-concept material; there is no active-exploitation listing at time of analysis.
Authenticated low-privilege users in Zammad 7.1.0 can access confidential ticket article attachments beyond their authorization scope via a missing authorization check in the attachment cloning endpoint. The flaw, classified as CWE-862 (Missing Authorization), allows any authenticated user to clone and retrieve attachments from tickets they should not have access to, enabling cross-tenant or cross-ticket data leakage in helpdesk environments. No public exploit code or CISA KEV listing has been identified at time of analysis; a patched release (7.1.2) is available from the vendor.
Cross-workspace OAuth2 credential isolation failure in Flowise prior to version 3.1.3 enables two distinct attack classes: authenticated users can initiate OAuth2 flows against credentials owned by other workspaces, and - more critically - unauthenticated attackers can forge OAuth2 callbacks to overwrite tokens or trigger token refreshes for any credential system-wide by exploiting a whitelist that bypasses all authentication on the /callback and /refresh endpoints. The root cause is that all three OAuth2 handlers query the Credential table by credential ID alone, omitting the workspaceId isolation enforced elsewhere in the codebase. No public exploit has been identified at time of analysis, and the issue is fixed in Flowise 3.1.3.
Cross-workspace IDOR in Flowise's OpenAI Assistants Vector Store API allows authenticated users of one workspace to access, use, and manipulate another workspace's stored OpenAI credentials. Flowise versions up to and including 3.1.2 pass the client-supplied `credential` query parameter directly to a database lookup (`findOneBy({ id: credentialId })`) with no ownership check against the caller's `workspaceId`, violating the multi-tenant isolation guarantee. An attacker with a valid Flowise account and `assistants:*` permissions can cause direct financial harm to victim workspaces via unauthorized OpenAI API billing and can read, modify, or delete the victim's vector stores and files. No public exploit code or CISA KEV listing is identified at time of analysis.
Unauthorized workspace variable disclosure in Flowise (<= 3.1.2) allows any authenticated user or API key - even one explicitly denied the `variables:view` RBAC permission - to exfiltrate all workspace secrets by calling `/api/v1/node-custom-function`. The `$vars` object, populated with static variable values and runtime secrets resolved from `process.env`, is unconditionally injected into every custom JavaScript execution sandbox (utils.ts:1782), while the official `/api/v1/variables` endpoint correctly enforces the permission gate - creating a direct privilege boundary bypass. Depending on workspace configuration, exposed data can include database passwords, JWT signing secrets, SMTP credentials, and cloud provider API keys. No public exploit code has been identified at time of analysis, and this CVE is not listed in CISA KEV.
Insufficient input validation in Amazon Bedrock AgentCore harness allows authenticated remote users to bypass model invocation and associated security controls by submitting crafted content blocks within conversation messages, directly triggering configured tool execution outside the intended agentic pipeline. The vulnerability carries a CVSS 4.0 score of 8.6 with high confidentiality and integrity impact against the vulnerable system (VC:H/VI:H), reflecting the potential for an attacker to invoke tools with whatever permissions those tools hold - such as S3 read access, database queries, or external API calls - without passing through model-layer guardrails. AWS has fully remediated this issue server-side; no public exploit has been identified at time of analysis, and no customer action is required.
Flowise's DELETE /api/v1/chatflows/:id endpoint fails to enforce RBAC boundaries between flow resource types, allowing authenticated workspace members to delete flows they are not permitted to manage. Users holding only agentflows:delete can permanently destroy CHATFLOW resources, and users holding only chatflows:delete can destroy AGENTFLOW resources, in the same workspace. All Flowise installations prior to 3.1.3 are affected; no public standalone exploit tool exists, but the GHSA advisory (GHSA-p5w8-m249-4r4v) supplies a verbatim curl reproduction demonstrating the issue with minimal effort.
Authentication bypass in the REST API interface of HPE Networking (Aruba) EdgeConnect SD-WAN Orchestrator lets an unauthenticated remote attacker circumvent web authentication and reach protected system functions, then view and modify sensitive configuration and data on the orchestrator. HPE reports the flaw as a cluster of multiple REST API weaknesses rated critical (CVSS 9.8). No public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the network-facing, unauthenticated nature makes it a high-priority patch target for any organization running the orchestrator.
Authentication bypass in the REST API of HPE Networking (Aruba) EdgeConnect SD-WAN Orchestrator lets an unauthenticated remote attacker circumvent web authentication and reach protected system functions, then view and modify sensitive configuration and network data. HPE (the reporting vendor) rates it CVSS 9.8 with a fully remote, no-privilege, no-interaction vector. No public exploit identified at time of analysis and it is not in CISA KEV, but the trivial exploitation profile on an internet-facing management plane makes it a high patch priority.
Property injection via the unauthenticated POST /api/v1/prediction/:id endpoint in Flowise allows remote unauthenticated attackers to overwrite session-critical fields (chatId, sessionId, chatHistory) and inject arbitrary values into the $flow.* template variable system of any public chatflow. Flowise versions up to and including 3.1.2 are affected; the fix was released in 3.1.3. Publicly available exploit code exists in the form of detailed curl-based proof-of-concept commands embedded in the public GitHub Security Advisory GHSA-6vh2-wg4h-4vwj, though active exploitation has not been confirmed by CISA KEV.
Quick Facts
- Typical Severity
- CRITICAL
- Category
- auth
- Total CVEs
- 37369