Authentication Bypass
Monthly
Unrestricted object instantiation in Jenkins 2.575 and earlier (LTS 2.568.1 and earlier) allows users holding Overall/Manage permission to instantiate arbitrary Java types through the project naming strategy configuration, including configuration objects intended exclusively for full administrators. This effectively breaks the permission boundary between Overall/Manage holders and full system administrators, enabling privilege escalation within the Jenkins controller. No public exploit has been identified at time of analysis, but fixed releases (Jenkins 2.576 and LTS 2.568.2) are available and should be applied promptly.
Jenkins 2.575 and earlier (LTS 2.568.1 and earlier) and multiple Jenkins plugins contain a cluster of vulnerabilities ranging from remote code execution via deserialization filter bypass to path traversal, CSRF, permission check failures, and Unicode-based user impersonation. The most critical issue - a bypass of the JEP-200 class filter in the Remoting library - allows authenticated agent operators or principals holding Agent/Connect permission to execute arbitrary code on the Jenkins controller. Three separate avenues for controller-side code execution are present in this advisory: the Remoting deserialization bypass (CVE-2026-70426), a tar archive symlink path traversal (CVE-2026-70427), and a file parameter path traversal (CVE-2026-70428). No public exploit or CISA KEV listing is confirmed at time of analysis, but the severity and variety of attack paths make this advisory high-priority for any Jenkins deployment.
Unauthorized configuration takeover in the Udimi Tools WordPress plugin (≤ 3.2) is possible for any subscriber-level authenticated user due to missing capability checks on both the `ajax_disconnect()` and `ajax_connect()` AJAX handlers. An attacker with a valid low-privilege WordPress account can wipe the site's Udimi API key and connected account settings, then replace them with attacker-controlled credentials - effectively hijacking the site's Udimi solo-ad integration and redirecting lead tracking data. No public exploit code or CISA KEV listing exists at time of analysis; EPSS data was not provided.
Insecure Direct Object Reference in Akaunting's multi-tenant file download route exposes uploaded media records across company boundaries to any authenticated portal customer. The `uploads/{id}/download` endpoint in `app/Http/Controllers/Common/Uploads.php` applies only generic authentication middleware and fetches Media records by raw integer ID without verifying tenant ownership, enabling sequential ID enumeration to exfiltrate invoices, financial statements, and other uploaded documents belonging to unrelated companies on the same instance. No public exploit has been identified and it is not listed in CISA KEV, but the attack is trivially executable by any portal customer given the low complexity of sequential integer enumeration.
Signature forgery in Documenso's V1 sequential-signing workflow allows an authenticated ASSISTANT-role recipient to complete signature fields owned by any co-recipient with an equal or later signing order, bypassing per-field ownership authorization entirely. The flaw resides in sign-field-with-token.ts, which upserts Signature records against the target field's recipientId without validating field type or ownership - a guard that Documenso's own V2 path (sign-envelope-field.ts) explicitly enforces and that the project's test suite comments confirm is absent from the V1 path. No public exploit code has been identified at time of analysis, but exploitation requires only low-privilege authenticated access as a named ASSISTANT recipient within a targeted document envelope.
Authentication bypass in changedetection.io's /settings endpoint silently disables REST API key enforcement when a privileged user or script submits a minimal POST request that omits the api_access_token_enabled checkbox. Because WTForms encodes an unchecked checkbox as False and the settings handler blindly merges all form fields via .update(), the API access token requirement is cleared without any warning, exposing the full watch list, history, and application configuration to unauthenticated REST API callers. No public exploit code or CISA KEV listing has been identified at time of analysis, but the post-exploitation surface - complete unauthenticated API access - is severe.
Unauthenticated retrieval of the full OpenAPI schema is possible in changedetection.io because the /api/v1/full-spec endpoint in changedetectionio/api/Spec.py lacks the @auth.check_token decorator that protects every other /api/v1/* route. Any network-reachable attacker can issue a plain GET request to this path and receive the complete merged schema - all endpoint paths, accepted parameters, and registered processor plugins - even when API key enforcement is active across all sibling routes. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code has been identified, though the attack requires zero prerequisites beyond network access, making opportunistic reconnaissance trivially achievable.
Unauthorized post creation in Xpro Addons - 140+ Widgets for Elementor (WordPress) affects all versions through 1.5.1, allowing any authenticated user with Subscriber-level access to publish arbitrary posts of the custom type `xpro_content` via a missing capability check on the `get_menu_content_editor()` AJAX handler. The created posts are publicly queryable on the front-end, enabling content injection, SEO spam campaigns, and database pollution against any WordPress site running the plugin. No public exploit or CISA KEV listing has been identified at time of analysis, though the low authentication barrier (any registered user) lowers the practical difficulty of abuse.
Insecure Direct Object Reference in the Groundhogg WordPress plugin (all versions through 4.5.2) allows authenticated users holding the view_contacts capability - most notably the built-in Sales Rep role - to enumerate and retrieve any contact record site-wide via the REST API, bypassing the intended ownership restriction that should limit them to their own assigned contacts. The GET /wp-json/gh/v4/contacts/<id> endpoint performs only a role-level capability check and accepts sequential integer IDs, meaning a Sales Rep can trivially iterate through all contact IDs and extract PII, contact metadata, owner identifiers, admin edit URLs, and - for contacts linked to a WordPress account - that user's full capability set. No public exploit code or active exploitation has been identified at time of analysis, but the attack is low-complexity for any attacker who can register or obtain a Sales Rep account.
Unauthenticated SSRF-adjacent resource abuse in Layouts for WPBakery (all versions ≤ 1.1.3) allows any remote attacker to force the WordPress host to issue unlimited outbound HTTP requests to the plugin vendor's external REST API and write the decoded JSON responses directly into the site's wp_options database table. The missing capability check on the wp_ajax_nopriv_handle_sync action (CWE-862) exposes this endpoint to every unauthenticated client with no nonce verification or rate limiting in place. This vulnerability is not listed in CISA KEV and no public exploit code has been identified, but the trivially low attack complexity - unauthenticated, network-reachable, zero prerequisites - makes availability abuse a realistic and automatable threat.
Incorrect authorization in OpenStack Ironic through 38.0.0 allows an authenticated low-privilege project reader to leak Portgroup configuration data belonging to Nodes owned or leased by other tenants via a crafted API request. The flaw breaks multi-tenant isolation - a core security guarantee of shared cloud infrastructure - enabling cross-project enumeration of bare-metal network topology. No public exploit code or CISA KEV listing is identified at time of analysis, but the low attack complexity and wide affected version range (spanning multiple major release series) make this a meaningful risk for multi-tenant OpenStack deployments.
Unauthenticated IDOR in the DHL Shipping Germany for WooCommerce WordPress plugin (versions before 4.0.1) exposes every generated shipping label to any internet visitor. The plugin's label-download endpoint performs no authorization check whatsoever - no capability check, nonce, login requirement, or order-ownership verification - and labels are indexed by predictable sequential IDs, enabling trivial full enumeration. A publicly available exploit exists; successful exploitation leaks customer full names, complete postal addresses, and order references at scale, carrying significant GDPR implications for any German e-commerce operator running the affected plugin.
Insecure Direct Object Reference (IDOR) in the MultiVendorX WordPress plugin before 5.0.11 exposes confidential financial and commission data across vendor accounts. Any authenticated vendor-level user can query a REST API endpoint using an arbitrary store identifier to retrieve another vendor's earnings and commission records, bypassing per-store ownership validation entirely. No active exploitation is confirmed in CISA KEV, but a publicly available exploit exists per WPScan, and the low EPSS score (0.14%, 4th percentile) suggests limited opportunistic scanning activity at this time.
Cost Calculator Builder for WordPress exposes live payment gateway credentials to any authenticated site user through a missing authorization check on its calculator export AJAX endpoint. All plugin versions through 3.6.17 are affected; attackers holding a Subscriber-level WordPress account - the lowest authenticated role - can invoke the `cost-calculator-custom-export-run` AJAX action to receive a full configuration export containing Stripe secret keys, PayPal client secrets, Razorpay secret keys, webhook secret keys, and reCAPTCHA secret keys. No public proof-of-concept exploit or CISA KEV listing has been identified at time of analysis, but the attack requires only a valid site account and basic HTTP knowledge, and an upstream fix has been committed to the plugin's trunk repository.
Cross-tenant object exfiltration in OpenStack Swift through 2.38.0 allows authenticated S3 API users to bypass source-object authorization by injecting Swift-native server-side copy headers (X-Copy-From, X-Copy-From-Account) into a signed S3 PUT request. The S3API middleware authorizes the request against the attacker-controlled destination bucket and then forwards the copy headers to Swift's copy engine, which executes the cross-tenant copy without re-evaluating the source object's ACLs or ownership - a classic confused-deputy flaw (CWE-863). Exploitation is constrained to deployments with the non-default s3_acl=true option enabled, and no public exploit is identified at time of analysis.
OpenStack Swift's S3API middleware through version 2.38.0 fails to enforce SigV4 signature coverage over semantic x-amz-* headers on presigned URL requests, enabling unauthorized server-side object copy operations under the signer's authorization context. An attacker holding a valid presigned PUT URL can inject an unsigned X-Amz-Copy-Source header, redirecting Swift's behavior from a client upload into a server-side copy that reads any object accessible to the URL's original signer - effectively allowing privilege escalation within a delegated authorization context. No public exploit or CISA KEV listing was identified at time of analysis, but all deployments running the S3API middleware under the default s3_acl=false configuration are affected.
Authentication bypass in the My Safetipin Android application version 5.2.1 stems from hardcoded credentials in the authentication module that produce predictable OTP values, letting remote attackers log in as arbitrary users and take over accounts without legitimate credentials. Any personal-safety data stored in a victim's account - location history, safety pins, and profile details - becomes exposed and modifiable. No public exploit has been identified at time of analysis, and the EPSS score of 0.27% (18th percentile) reflects low observed exploitation activity despite the maximal CVSS rating.
Unauthorized access to other users' personal data in SirenGPS Android Application 2.19.44 stems from the backend API failing to verify that a requesting user is authorized to act on the target user identifier supplied in API parameters. An authenticated attacker exploiting this horizontal privilege escalation can read and overwrite arbitrary users' personal information with only low-privilege access. No public exploit identified at time of analysis and EPSS is extremely low (0.15%, 5th percentile), but a detailed researcher advisory is publicly available on GitHub, lowering the bar for replication.
Hardcoded RTSP credentials in Zosi C519M IP camera firmware V4.2.8.823C01450BA expose live video feeds to any network-reachable attacker. The built-in credentials embedded in the RTSP authentication mechanism cannot be changed by the device owner, making every affected unit permanently vulnerable to unauthorized stream access. A public proof-of-concept exists on GitHub, and CISA's SSVC framework rates the attack as automatable with no exploitation preconditions beyond network reachability - no public exploit identified as actively exploited in CISA KEV at time of analysis.
Authorization bypass in the TicketDetailView component of Ehco1996 django-sspanel allows authenticated remote users to access support tickets belonging to other users by manipulating a user-controlled key in requests to apps/sspanel/views.py. All releases through 2023.12.26 are affected per ENISA EUVD-2026-52981. No patch will be issued - the maintainer has abandoned the project and did not respond to disclosure - leaving operators with no vendor remediation path. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Improper authentication in Baserow's 2FA verify endpoint (versions 2.3.0-2.3.2) allows a low-privileged remote attacker to manipulate which user identity the 2FA verification applies to, by supplying a different user identifier in the HTTP request body rather than relying on the authenticated session token. The affected component is the `verify` function in `backend/src/baserow/api/two_factor_auth/views.py`, confirmed by the 2.3.3 release refactor note referencing GitHub issue #5743. Exploitation is characterized as high complexity (CVSS 4.0 AV:N/AC:H/PR:L), and no public exploit or CISA KEV listing has been identified at time of analysis.
Open WebUI's terminal WebSocket route omits the role-state verification gate that all HTTP terminal endpoints enforce, granting `pending`-role accounts - unapproved registrations or deactivated users - interactive shell access that the HTTP plane correctly denies. Affected pip package versions span v0.8.8 through v0.10.x; the flaw was introduced when the terminal WebSocket route was first added in v0.8.8 and persisted because FastAPI dependency injection cannot be applied to WebSocket handshakes, leading to a divergent reimplementation. No public exploit code has been identified at time of analysis, but exploitation requires only a valid pending-role JWT obtainable by design during registration or retained for up to four weeks after deactivation.
Cross-knowledge-base IDOR in Open WebUI 0.9.6-0.10.2 allows any user with write access to one knowledge base to silently delete directories and file embeddings from unrelated knowledge bases they do not control, causing documents to vanish from RAG retrieval results and breaking chat-with-file for targeted files without disclosing their contents. The flaw (CWE-639) sits in the sync cleanup endpoint, which authorized requests based on the URL knowledge base ID but executed destructive operations against object IDs supplied in the request body without verifying those objects belonged to the authorized knowledge base. No public exploit is identified and no CISA KEV listing exists; the vendor released a complete fix in v0.11.0.
Cross-user file content disclosure in Open WebUI versions 0.8.8 through 0.10.2 allows any authenticated user to read indexed chunks from another user's private files by supplying a crafted inline model definition with a known target file UUID. The chat completion, chat completed, and chat action endpoints accepted client-supplied knowledge attachments on inline (non-workspace) model definitions without enforcing the caller's read access, bypassing the access control that saved workspace models correctly enforce. No active exploitation has been confirmed; the vendor released a complete fix in version 0.11.0.
Unauthenticated access to the network setup wizard API in H3C NX15 firmware V100R017 allows remote attackers to interact with the /api/wizard/networkSetup endpoint without presenting valid credentials. The root cause is CWE-306 - missing authentication for a critical function - meaning the device exposes a privileged configuration path with no access control gate. A public proof-of-concept repository exists on GitHub, confirming exploitability; no CISA KEV listing was identified at time of analysis, suggesting exploitation has not yet been confirmed at scale.
Open WebUI versions 0.7.0 through 0.10.x fails to re-validate the `features.image_generation` permission on the legacy chat-completions code path, allowing an authenticated user whose image generation rights were explicitly revoked to bypass the restriction by supplying the feature flag directly in a chat API request. This affects only deployments where an administrator has both enabled ENABLE_IMAGE_GENERATION and explicitly revoked per-user image generation rights - a non-default, deliberately restricted configuration. The result is unauthorized consumption of the operator's configured image provider API credits and quota, and unauthorized writes of generated files to the operator's storage; no public exploit has been identified at time of analysis.
Open WebUI versions 0.9.6 through 0.10.2 contain an authorization-ordering flaw in the DELETE /api/v1/chats/{id} handler that allows any authenticated user to silently cancel another user's active LLM generation tasks - including streaming model responses, title generation, and tag generation - without holding delete permissions on the target chat. The task-cancellation helper executes unconditionally at the top of the handler, before ownership verification, admin checks, or permission gate evaluation, meaning even revoking the chat.delete role permission leaves the cancellation side effect fully reachable. A detailed proof-of-concept is included in the GitHub security advisory; no public exploitation confirmed at time of analysis.
Broken object-level authorization in Open WebUI's standard channel messaging API allows any authenticated channel member with write access to overwrite or permanently delete messages authored by other members. Affected versions are open-webui 0.5.0 through 0.10.2 (pip). The `update_message_by_id` and `delete_message_by_id` route handlers in `channels.py` enforced a write-permission check for standard channels instead of an authorship check, meaning the same credential that grants posting rights silently granted full edit and delete authority over every other member's messages in that channel. A proof-of-concept script demonstrating end-to-end exploitation was included in the report; no public exploit code is independently confirmed at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Incorrect authorization in Veeam ONE's shared report link feature permits a low-privileged authenticated user to retrieve report data beyond the intended scope boundary of that link. Exploitation requires a valid Veeam ONE account but no elevated privileges, and the attack is network-accessible with low complexity. No public exploit code or CISA KEV listing exists at time of analysis, placing this in the medium-priority tier despite the straightforward exploitation path.
Incorrect authorization in NousResearch hermes-agent's Quick Command Handler allows low-privileged remote attackers to bypass slash command access controls via a flaw in the `_check_slash_access` function within `gateway/run.py`. All versions through 2026.6.5 are confirmed affected, with a public proof-of-concept exploit available on GitHub. The vendor did not respond to responsible disclosure, leaving no official patch available at time of analysis.
Session security diagnostics nodes in Eclipse Milo 0.6.0 through 1.1.4 expose sensitive OPC UA session metadata without enforcing any authorization checks, a CWE-862 (Missing Authorization) flaw. An unauthenticated anonymous client connecting over a None/None (no-security) endpoint can enable the diagnostics subsystem with no certificate or credentials whatsoever; separately, a client presenting a trusted application certificate over SignAndEncrypt can read the SessionSecurityDiagnosticsArray for all active server sessions, harvesting usernames, login history, authentication mechanisms, session security modes and policies, and public client certificates. No public exploit code exists and the vulnerability is not listed in CISA KEV, but the zero-authentication path and prevalence of None/None endpoints in legacy OT/IIoT environments meaningfully lower the exploitation barrier.
Broken object-level authorization in the REST API Log WordPress plugin (all versions before 1.7.1) permits unauthenticated attackers who hold any valid log-download token - regardless of which entry it was issued for - to retrieve arbitrary log entries from any other user, exposing stored credentials, authentication tokens, and private REST API payloads. The root cause is twofold: tokens are not cryptographically bound to specific log entry IDs, and the plugin performs no WordPress capability check on the requester. A public exploit PoC is referenced via WPScan, though EPSS at 0.18% and SSVC exploitation status of 'none' indicate no confirmed widespread abuse at time of analysis.
Missing authorization in the Wired Impact Volunteer Management WordPress plugin (versions before 2.8.2) allows any authenticated WordPress user with at least a Subscriber role to remove RSVPs belonging to other users from any volunteer opportunity. The vulnerability stems from an AJAX action handler that neither verifies the requesting user's authorization level nor confirms ownership of the RSVP being deleted, enabling unauthorized data manipulation across the entire volunteer management system. A publicly available proof-of-concept exists via WPScan, though EPSS sits at 0.13% (3rd percentile) and SSVC confirms no active exploitation, suggesting limited real-world attacker interest at this time.
Clearfy Cache WordPress plugin versions before 2.4.3 exposes admin-only settings pages and their contents - including administrative nonces - to any authenticated user at Subscriber level or above due to a missing capability check on an alternate admin-page dispatch path. While the canonical admin URL enforces access controls correctly, the unguarded dispatch path bypasses those restrictions entirely. A publicly available proof-of-concept exists per WPScan reporting, though EPSS sits at 0.13% (3rd percentile), indicating low observed exploitation probability despite POC availability; no confirmed active exploitation (CISA KEV) has been recorded.
Authorization bypass in the Brizy WordPress plugin before 2.8.19 permits authenticated Contributor-level users to hijack template-type metadata on templates owned by other users. The plugin validates authorization against one request parameter while executing the write operation against a different, attacker-controlled parameter - a textbook CWE-639 Insecure Direct Object Reference variant. A publicly available exploit is documented by WPScan; however, no active exploitation is confirmed via CISA KEV, and the EPSS score of 0.13% (3rd percentile) indicates negligible observed in-the-wild activity.
Contest Gallery WordPress plugin (all versions before 30.0.7) exposes the site's complete stored OpenAI prompt history to any authenticated user holding at minimum a Subscriber role, due to a handler that performs neither a capability check nor a nonce verification. An attacker with a basic WordPress account can call the unprotected AJAX endpoint directly to exfiltrate the full prompt history, potentially exposing confidential business logic, AI workflows, or sensitive data embedded in prompts. No active exploitation is confirmed (not in CISA KEV), but a publicly available proof-of-concept exists per WPScan, and EPSS remains low at 0.13% (3rd percentile).
Missing authorization in the miniOrange 2FA WordPress plugin before 6.2.7 allows any authenticated low-privileged user to trigger OTP email delivery to arbitrary email addresses and exhaust the site's metered OTP quota. The plugin's second-factor enrollment endpoint neither restricts which users may invoke it nor binds the OTP recipient to the enrolling user's own address, enabling both unsolicited OTP email delivery and a denial-of-service attack against other users' 2FA flows. No public exploitation or KEV listing has been identified, though a public proof-of-concept is available via WPScan; EPSS stands at 0.13% (3rd percentile), indicating low observed exploitation activity.
Horizontal privilege escalation in the Paid Membership Subscriptions WordPress plugin (all versions before 3.0.8) allows any subscriber-level authenticated user to hijack and overwrite another member's subscription - including plan tier, status, and expiration date - by submitting a crafted change-subscription checkout request with an arbitrary subscription ID. The root cause is a missing ownership verification check at the business logic layer of the checkout flow (CWE-284). A publicly available proof-of-concept exploit has been published by WPScan, though EPSS sits at just 0.13% (3rd percentile), suggesting limited automated exploitation so far. The vulnerability is not listed in CISA KEV at time of analysis.
Unauthenticated consent-record forgery and privacy-queue flooding affect GDPR Framework By Data443 WordPress plugin versions prior to 2.4.0. The plugin fails to verify the identity of the data subject or check authorization when recording cookie-consent choices and processing privacy requests, allowing any unauthenticated remote attacker to submit fraudulent GDPR consent records on behalf of arbitrary email addresses and to inject unlimited entries into the site's privacy-request queue. A publicly available proof-of-concept exists per WPScan; the vulnerability is not listed in the CISA KEV catalog, and EPSS sits at 0.15% (4th percentile), indicating low observed exploitation at time of analysis.
Improper access control in the wpForo Forum WordPress plugin before 3.1.3 permits any subscriber-level authenticated user to write to administrator-controlled profile fields - including account activation status and forum reputation score - during a standard self-service profile update. This allows a banned or pending user to self-activate their own account, bypassing moderator enforcement, and to forge an arbitrarily high reputation score that may unlock elevated forum privileges. No CISA KEV listing exists, but a publicly available exploit is documented by WPScan; the EPSS score of 0.14% (4th percentile) indicates low observed exploitation probability at scale, though the low barrier to attack (any registered user) makes it a meaningful integrity risk for moderated forums.
Signature forgery in the MonsterInsights WordPress plugin before 11.1.0 allows unauthenticated network attackers to overwrite plugin configuration values when the site is not connected to Google Analytics. The root cause is that the HMAC signing key used to authenticate a specific AJAX action defaults to an empty string in that disconnected state, making any forged HMAC trivially valid. The practical impact is limited to disrupting server-side analytics in Manual GA4 mode; no public exploit identified as actively exploited (not in CISA KEV), though a publicly available proof-of-concept exists and the EPSS probability is low at 0.15%.
Improper authorization in diaowen DWSurvey (all versions through 6.14.0) permits authenticated low-privileged users to invoke the Survey Status Handler endpoint beyond their intended access level, enabling unauthorized manipulation of survey state - such as publishing, closing, or altering surveys owned by other accounts. The affected endpoint `/api/dwsurvey/app/survey/up-survey-status.do` is remotely reachable and lacks sufficient authorization enforcement. A public proof-of-concept exploit has been disclosed via Google Drive; no vendor patch exists as the vendor did not respond to responsible disclosure, leaving all current deployments unmitigated.
Authorization bypass in DWSurvey up to version 6.14.0 permits remote authenticated attackers to manipulate user-controlled keys in the Survey Handler's devSurvey function, bypassing access controls on the /api/dwsurvey/app/v6/dw-design-survey/dev-survey.do endpoint. The flaw (CWE-639, Insecure Direct Object Reference class) allows unauthorized read or write access to survey resources belonging to other users. A public proof-of-concept exploit is available and the vendor has not responded to disclosure, leaving no official patch for deployed instances.
Captive portal authentication bypass in Zyxel WAX650S firmware exposes guest or restricted wireless networks to unauthorized access by any WLAN-adjacent attacker. The flaw resides in the social_login.cgi CGI handler, where CWE-287 (Improper Authentication) allows requests to circumvent captive portal enforcement entirely - not just weaken it. All firmware versions through 7.10(ABRM.4)C0 are confirmed affected per the vendor's own advisory. No public exploit code or CISA KEV listing has been identified at time of analysis, though the low attack complexity makes opportunistic exploitation plausible once the mechanism is understood.
Improper authorization in KodBox 1.67 Build 02 allows unauthenticated remote attackers to bypass access controls via the msgWarning plugin endpoint, resulting in limited unauthorized access to confidential data. The CVSS 4.0 vector (PR:N/UI:N) confirms no authentication is required, and a public proof-of-concept exploit has been published on GitHub. The vendor did not respond to responsible disclosure, leaving no confirmed patch available at time of analysis.
Secure boot bypass in Caliptra Core ROM 2.1.0-2.1.1 (subsystem mode) enables a local attacker controlling compromised MCU firmware to silently load unauthorized firmware into ICCM while attestation continues reporting the originally verified image digest, masking the compromise entirely. The TOCTOU race in UpdateResetFlow::run() is compounded by absent validation of the caller-supplied AXI staging address against the strap-configured SS_EXTERNAL_STAGING_AREA_BASE_ADDR, creating a window between verification and ICCM load during which SRAM contents can be swapped. No public exploit has been identified and no CISA KEV listing applies, but the severity lies in the attack's undetectability through standard attestation channels.
Origin validation error in Microsoft Edge (Chromium-based) enables a remote unauthenticated attacker to perform cross-origin spoofing attacks, achieving high confidentiality impact and limited integrity impact against victims who interact with attacker-controlled content. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N) with temporal indicators E:U/RL:O/RC:C indicates an officially patched vulnerability with no publicly proven exploit code and confirmed vendor reporting. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Origin validation error in Microsoft Edge (Chromium-based) allows network-positioned unauthenticated attackers to perform cross-origin tampering when a victim user interacts with malicious web content. The flaw (CWE-346) undermines the browser's origin enforcement logic, enabling integrity and confidentiality compromise at low severity per CVSS 5.4. Tagged as an Authentication Bypass vector, suggesting edge cases where origin-gated auth flows in Edge may be bypassed. No active exploitation confirmed (not in CISA KEV), no public POC identified, and a vendor patch is available via MSRC.
Missing authorization controls in Microsoft Edge (Chromium-based) allow a local attacker without any system privileges to bypass authorization and perform tampering actions against the browser. The flaw (CWE-862) results in high confidentiality impact per the CVSS vector, though the description characterizes the effect as tampering - a discrepancy addressed in confidence notes below. No public exploit code has been identified and Microsoft has released an official patch through the MSRC advisory portal.
Spoofing via origin validation failure in Microsoft Edge (Chromium-based) allows a network-adjacent unauthenticated attacker to deceive users or systems about the true origin of web content or requests. All Chromium-based Edge versions are affected per the wildcard CPE, and a vendor-released patch is confirmed via the Microsoft Security Response Center. No public exploit code exists and active exploitation is not confirmed - the CVSS temporal metric E:U (exploit unproven) and absence of CISA KEV listing reinforce a currently theoretical risk level.
Origin validation error in Microsoft Edge (Chromium-based) enables a local, unauthenticated attacker to bypass cross-origin restrictions and perform data tampering. The CVSS vector (AV:L/PR:N) indicates that any unprivileged local user - including guest or kiosk session users - can trigger this flaw without requiring prior authentication or user interaction. With a high confidentiality impact (C:H) and low integrity impact (I:L), exploitation could expose sensitive browser-held data while also permitting limited content manipulation. No public exploit code has been identified and CISA KEV does not list this CVE; the temporal metric E:U corroborates no known active exploitation at time of analysis.
Draft post creation in Camaleon CMS through 2.9.2 allows any authenticated low-privileged user to create and overwrite draft posts by bypassing role and permission checks on the admin drafts endpoint. The DraftsController's overridden create and update actions omitted the authorize! calls enforced by the parent PostsController, and used global unscoped post lookups that ignore post type and user ownership, enabling cross-post-type draft manipulation and ownership attribution changes on existing drafts. No CISA KEV listing or public exploit code has been identified; the CVSS 4.0 score of 5.3 (PR:L, VI:L) reflects limited integrity impact with no confidentiality or availability consequence.
Insufficient permission checks in Misskey's Direct Messages (Chat) feature expose DM data points to authenticated users who lack authorization to access them, across versions 2025.3.2 through 2026.5.3. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), where the server fails to validate account permissions before returning DM-related data via API. No public exploit or CISA KEV listing exists; the vendor patched this in version 2026.5.4 alongside four additional CVEs.
Unauthorized data disclosure via the Server Announcements API in Misskey affects all instances running versions 2024.5.0 through 2026.5.3, allowing remote callers to read restricted announcement data without appropriate authorization. The flaw stems from CWE-285 (Improper Authorization) - the API endpoint fails to enforce privilege checks before returning data, making restricted content accessible to actors who should not see it. No public exploit code or CISA KEV listing exists at time of analysis, but the network-accessible, no-authentication-required vector makes this straightforwardly reachable on any exposed instance.
Plaintext AWS credential extraction in the DuckDB AWS Extension allows any SQL-privileged database user to bypass the database-wide allow_unredacted_secrets=false security policy by invoking load_aws_credentials(redact_secret=false), returning the full AWS credential chain - access_key_id, secret_access_key, session_token, and region - in cleartext. The bypass is particularly impactful in managed cloud environments where pg_duckdb is preloaded and an ambient AWS credential chain (IMDSv2, IRSA, ECS task role, EC2 instance profile) is automatically reachable from the database host, effectively converting low-privilege SQL access into valid cloud API credentials. No public exploit code or CISA KEV listing has been identified; an upstream fix is confirmed via GitHub commit 7d04119 (PR #156), though a tagged patched release version is not confirmed in available data.
Authorization bypass in Apache NiFi 2.0.0-2.10.0 allows authenticated users holding write access to one Parameter Context to delete Assets belonging to a separate, restricted Parameter Context they are not authorized to modify. The REST API's asset deletion endpoint validated permissions against the caller-supplied Parameter Context Identifier without confirming that the targeted Asset Identifier is actually recorded as belonging to that context - a broken object-level authorization (BOLA/IDOR) flaw. No public exploit code exists and the vulnerability is absent from the CISA KEV catalog; impact is confined to multi-tenant NiFi deployments with differentiated per-context authorization policies.
Missing authorization in Apache NiFi's Parameter Context update REST API allows an authenticated user with write access to a Parameter Context to alter parameter values that affect referencing components the user is not authorized to access. In deployments where parameter values contain executable scripting content, this privilege boundary bypass can trigger code execution during automatic component validation on stopped processors without the attacker needing to start those components. No public exploit has been identified; exploitation is bounded to deployments using component-level authorization policies and is confirmed fixed in Apache NiFi 2.11.0 per NIFI-16148.
Authorization bypass in jeequan jeepay up to version 3.2.9 allows authenticated low-privilege users to circumvent access controls enforced by the PreAuthorize Handler within WebSecurityConfig, specifically targeting the SysLogController component. The flaw stems from CWE-639 (Authorization Bypass Through User-Controlled Key), enabling manipulation of access-control keys to reach system log data or restricted administrative functionality beyond the user's granted permissions. A public proof-of-concept exploit exists; no vendor response has been received and no patch has been confirmed, elevating remediation urgency despite the moderate CVSS score.
Credential recovery is possible on TP-Link Omada network devices - including Gateways, Switches, Access Points, and OLTs - because site credentials are hashed with a legacy algorithm that lacks adequate protection against offline cracking (CWE-759). An attacker who has already obtained privileged access to the device or management environment and extracted stored credential hashes can recover plaintext credentials, enabling unauthorized access to affected Omada infrastructure. No public exploit code has been identified at time of analysis, and the issue is not listed in the CISA KEV catalog, though a vendor patch is available.
Shared embedded certificates across all TP-Link Omada deployments enable impersonation of trusted controllers and managed devices by any attacker who extracts those certificates from a single unit. The CVSS 4.0 vector (AV:A/PR:N/VC:H/SC:H) confirms that an unauthenticated attacker with adjacent network access to the Omada management plane can intercept management communications at high confidentiality impact across both the vulnerable and subsequent systems, with no patch complexity required beyond certificate possession. No public exploit has been identified at time of analysis, and this CVE is not currently listed in the CISA KEV catalog, though the authentication-bypass tagging and the breadth of affected product lines (gateways, switches, access points, controllers, OLTs) give this meaningful real-world weight in environments relying on Omada for network management.
Credential interception in TP-Link Omada's device adoption process exposes site management authentication to offline cracking due to use of a weak, unsalted hash algorithm (CWE-759). An adjacent-network attacker who captures adoption-phase traffic can recover plaintext credentials and authenticate to the Omada controller or managed devices including gateways, switches, access points, and OLTs. No public exploit identified at time of analysis, but a vendor patch is available; the CVSS 4.0 score of 6.9 reflects meaningful real-world constraints including network adjacency, high attack complexity, and a required adoption event.
Improper certificate hostname validation in TP-Link Omada networking devices (gateways, switches, and access points) allows a network-positioned attacker to intercept or modify encrypted management traffic between those devices and their cloud controllers. The flaw - classified as CWE-295 - means the devices do not adequately confirm that a presented TLS certificate belongs to the expected cloud controller hostname, enabling a machine-in-the-middle to substitute a fraudulent certificate and break the trust boundary. No active exploitation is confirmed (not in CISA KEV) and no public proof-of-concept has been identified at time of analysis; vendor has released patched firmware.
Unauthenticated remote access to the /EIP_Com_FileList.aspx endpoint in NewType WebEIP up to version 3.0 exposes file listing functionality to any network-reachable attacker due to improper authentication enforcement (CWE-287). A public proof-of-concept exploit hosted on Google Drive is confirmed available, lowering the exploitation bar significantly. No vendor patch exists as the vendor did not respond to disclosure; organizations must rely entirely on compensating controls.
Channel lifecycle enforcement failure in russh (Rust SSH library, versions <= 0.62.4) allows authenticated clients to invoke server-side handler callbacks - including exec_request, shell_request, subsystem_request, data, channel_eof, and channel_close - for SSH channel IDs that were never opened or confirmed by the transport layer. An authenticated peer can send crafted SSH_MSG_CHANNEL_REQUEST packets without ever issuing SSH_MSG_CHANNEL_OPEN, or after having a channel_open_session request explicitly denied by the application, and still trigger all channel-scoped callbacks. A working Python PoC is publicly available demonstrating 32 exec_request invocations with zero channels ever opened; no active exploitation is confirmed (not in CISA KEV) and a vendor patch exists in v0.62.5.
Authentication bypass in 389 Directory Server (Red Hat Directory Server 11-13) allows a network-connected user holding valid credentials for an administratively locked account to retain an authenticated LDAP session, defeating account-lock as an access-revocation control. The SASL PLAIN bind handler installs connection-level authenticated state before executing the account-lock check; when the lock check fails, only the error is returned to the client while the internal authenticated state on that connection persists unrevertd. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the real-world impact is highest in incident-response and employee-offboarding scenarios that rely on directory lock as the primary revocation mechanism.
Privilege escalation to NT AUTHORITY\SYSTEM is achievable by any local, unprivileged user via Wellbia XIGNCODE3's kernel driver xhunter2.sys version 2026.6.1.192, due to missing access control on the IRP_MJ_WRITE command interface. Beyond SYSTEM-level execution, the flaw enables extraction of credentials from PPL-protected lsass.exe and termination of PPL-protected security processes such as EDR/AV agents, effectively disabling host defenses. No active exploitation is confirmed by CISA KEV, though the primary reference is a researcher blog post (blacksnufkin's 'Hunting the Hunter II') that strongly suggests PoC-grade research material exists.
Insecure Direct Object Reference in Admidio before 5.0.11 allows authenticated low-privilege users to hijack list configurations managed by administrators or other users by manipulating the list_uuid parameter in the save_temporary mode of mylist_function.php. Any user with a valid session can enumerate global list UUIDs and submit crafted requests to overwrite admin-curated global lists or private lists belonging to other users, effectively transferring ownership and demoting shared resources to personal configurations. No public exploit code has been identified at time of analysis, and a vendor-released patch is available in version 5.0.11.
Cross-organization role manipulation in Admidio before 5.0.11 allows authenticated role administrators to delete, activate, deactivate, or edit roles belonging to other organizations hosted on the same instance. The flaw exists because `groups_roles.php` handlers accept role UUIDs without verifying that the target role belongs to the requesting user's organization, enabling cross-tenant privilege structure sabotage. No public exploit has been identified at time of analysis; vendor-released patch version 5.0.11 is available.
Metadata disclosure in SiYuan before v3.7.3 exposes document titles, notebook paths, root IDs, and icons for administrator-restricted documents via the unauthenticated `/api/block/getBlockInfo` endpoint. The publish-access control flag is never checked server-side before returning document root metadata, making this a complete bypass of SiYuan's per-document publish exclusion feature. No public exploit is identified at time of analysis and no KEV listing exists, but the CVSS 4.0 vector (PR:N, AC:L) confirms exploitation requires no credentials and no special conditions against the network-facing API.
Missing granular access control in HCL iControl v3.2.0 exposes administrator-level functionality to unauthorized users over the network. Regular-privilege users can bypass authorization checks to view or access admin-scoped features, resulting in a limited confidentiality impact. No public exploit code exists and no CISA KEV listing is present; however, the 'Authentication Bypass' tag and the network-accessible vector mean the exposure is reachable without physical proximity, though the high attack complexity (AC:H) constrains opportunistic exploitation.
Broken access control in the Unlimited Elements For Elementor WordPress plugin (versions through 2.0.15) permits authenticated low-privileged users to invoke restricted plugin functions without proper authorization. The flaw, rooted in CWE-862 (Missing Authorization), allows a subscriber- or contributor-level WordPress account to perform actions that should be restricted to higher-privileged roles, resulting in low-impact integrity and availability consequences. No public exploit code has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog.
Broken object-level authorization in the Dokan WordPress plugin (versions before 5.0.9) allows any authenticated vendor on a multivendor marketplace to overwrite product attributes and default attributes belonging to other vendors via the plugin's REST API write endpoints. Exploitation requires only a low-privilege vendor account - no admin access needed - making this accessible to any registered seller on the platform. A publicly available proof-of-concept exists per WPScan, though EPSS sits at 0.13% (3rd percentile), indicating limited observed exploitation activity so far; the vulnerability is not listed in CISA KEV.
Order ownership bypass in Dokan Multivendor for WordPress (versions before 5.0.9) allows any authenticated vendor to modify the status of arbitrary WooCommerce orders across the entire marketplace, including orders owned by other vendors and customers. The flaw stems from a REST endpoint handling bulk order-status changes that accepts attacker-supplied order IDs without verifying the requesting vendor's ownership of those orders. No active exploitation is confirmed (not in CISA KEV), but a publicly available proof-of-concept exists and EPSS at 0.13% (3rd percentile) reflects low observed exploitation to date.
Unauthorized lesson content disclosure in Academy LMS WordPress plugin before 3.8.3 allows any subscriber-level authenticated user to read arbitrary lesson content via the REST API - including lessons from paid courses they have not purchased and lessons in unpublished states (draft, pending, private). The root cause is a complete absence of enrollment and publication-status validation in the single-lesson REST API endpoint. A publicly available proof-of-concept exists per WPScan, though EPSS at 0.13% (3rd percentile) and SSVC classification as non-automatable indicate limited observed exploitation activity at the time of analysis.
ProfileGrid WordPress plugin before version 6.0.0.0 exposes pending group membership request data to any authenticated user due to missing authorization checks on the listing endpoint. Any subscriber-level account can enumerate the names and request timestamps of users awaiting approval for any group, including groups configured as private. No active exploitation is confirmed (not in CISA KEV), though a public exploit exists via WPScan; EPSS of 0.13% (3rd percentile) places real-world exploitation probability as very low.
GEO my WP WordPress plugin versions before 4.5.5.3 allows any subscriber-level (or higher) authenticated user to modify or permanently delete geolocation records belonging to other users or posts by supplying arbitrary record IDs to two unprotected AJAX actions. The root cause is a complete absence of ownership and capability checks on these endpoints, a textbook CWE-639 IDOR. A publicly available exploit exists per WPScan; however, no public exploit identified at time of analysis corresponds to confirmed active exploitation (not in CISA KEV), and the EPSS score of 0.13% at the 3rd percentile reflects low observed exploitation activity despite POC availability. A vendor-released patch is available in version 4.5.5.3.
Insecure Direct Object Reference (IDOR) in the Tag, Category, and Taxonomy Manager WordPress plugin before 3.51.0 allows authenticated contributors to disclose content from private or draft posts they do not own. The plugin fails to verify post ownership before processing a referenced post ID and returning derived data, enabling a contributor to enumerate and extract information from restricted content authored by other users. No public exploitation in the wild has been confirmed (no CISA KEV listing), though WPScan has published a publicly available proof-of-concept.
Unauthorized revenue data disclosure in the Classified Listing WordPress plugin (before 5.4.4) allows any authenticated contributor-level user to read daily store revenue figures restricted to administrators and report managers. The flaw stems from a missing capability check (CWE-862) on an AJAX action that aggregates store revenue totals, exposing potentially sensitive business intelligence to lower-privileged users. No public exploit identified at time of analysis per KEV, though a publicly available exploit exists per WPScan reporting; the EPSS score of 0.13% (3rd percentile) suggests limited real-world exploitation interest despite code availability.
The Classified Listing WordPress plugin before version 5.4.4 exposes private, draft, and pending post content to authenticated contributors due to a missing authorization and ownership check on an AJAX endpoint. Any user with contributor-level access or higher can read arbitrary post content belonging to other users, including administrators' unpublished material. A publicly available exploit exists via WPScan, though EPSS at 0.13% (3rd percentile) and the absence of a CISA KEV listing indicate active exploitation is not confirmed at time of analysis.
Post-deletion authorization bypass in the Contest Gallery WordPress plugin before 30.0.7 allows any authenticated Author-level or higher user to permanently delete arbitrary posts, pages, and other WordPress content they do not own. The plugin's post-deletion AJAX handler enforces only a coarse role-membership test, entirely omitting per-object capability verification and nonce validation - the two controls that WordPress's built-in permission model relies on to prevent cross-user destructive actions. A public exploit is available via WPScan, lowering the skill barrier; though EPSS is low at 0.13%, any multi-author site with untrusted Author accounts faces real and irreversible content destruction risk.
Broken access control in Simply Schedule Appointments WordPress plugin before 1.6.12.11 exposes all customer appointment records to any authenticated Contributor-level user site-wide. The administrative appointment-listing shortcode omits a capability check, and the per-user result scoping logic defaults to showing all records when the requesting user is not recognized as staff. Any WordPress user holding the Contributor role or higher - a commonly granted role in multi-author sites - can enumerate names, email addresses, phone numbers, and appointment notes belonging to every customer in the system. A publicly available proof-of-concept exists, though EPSS at 0.13% and SSVC Automatable:No suggest exploitation remains targeted rather than widespread.
Improper authorization in GL.iNet's eSIM LPA API allows adjacent-network unauthenticated attackers to bypass nginx proxy controls on six cellular router models, gaining unauthorized access to eSIM management functions. Affected devices include the E5800, E750, X2000, X3000, XE3000, and XE300 running firmware up to 20260707. The GitHub advisory title explicitly frames this as 'Unauthenticated access to eSIM LPA API via nginx proxy bypass,' indicating the authorization enforcement failure lies in how nginx proxies requests to the /sdk/v1 endpoint. No public exploit code or CISA KEV listing has been identified at time of analysis.
Insecure Direct Object Reference in the better-auth passkey plugin (npm/@better-auth/passkey < 1.4.0) permits any authenticated user to delete arbitrary passkeys belonging to other users via the `POST /passkey/delete-passkey` endpoint. The `ctx.body.id` parameter is implicitly trusted without ownership verification, meaning a valid session - regardless of privilege level - is sufficient to enumerate and destroy other users' passkey credentials. Applications configured with `useNumberId` (auto-incrementing integer IDs) are trivially exploitable by sequential enumeration. No public exploit or CISA KEV listing confirmed at time of analysis; a vendor-released patch exists at version 1.4.0.
Path normalization bypass in Better Auth before v1.4.5 allows unauthenticated remote attackers to circumvent `disabledPaths` security controls and path-based rate limits by submitting requests with extra leading slashes (e.g., `//sign-in/email` instead of `/sign-in/email`). The root cause is in the bundled rou3 router library, which collapses empty path segments before route matching, meaning security rules keyed on canonical paths never match the double-slash variants. No public exploit code has been identified at time of analysis, but the trivially low attack complexity makes exploitation straightforward on unprotected deployments.
Unauthenticated REST API access in the webtoffee-cookie-consent WordPress plugin before 3.5.3 allows any network attacker to export or delete stored visitor consent records, create arbitrary WordPress posts, and alter the plugin's licensing state. All versions prior to 3.5.3 are affected with no special configuration required, as the missing permission callbacks expose endpoints to public access by default. A publicly available exploit exists per WPScan, though EPSS sits at 0.22% (12th percentile), indicating exploitation has not yet reached widespread automated abuse; no public exploit identified at time of analysis for active in-the-wild campaigns.
Broken object-level authorization in the Event Booking Manager for WooCommerce WordPress plugin (all versions before 5.3.7) allows any authenticated user with the Contributor role or higher to modify the title and publication status of arbitrary posts and pages sitewide - including content they do not own. The plugin's quick-edit event handler validates only a global WordPress capability (e.g., edit_posts) without confirming whether the requesting user owns the target object, enabling horizontal and vertical privilege escalation over site content. A publicly available proof-of-concept exists; however, no confirmed active exploitation has been identified and the EPSS score sits at 0.13%, indicating limited real-world adversary interest at time of analysis.
Insecure Direct Object Reference (IDOR) in the ProfileGrid WordPress plugin before 5.9.9.8 allows any authenticated user - including low-privilege Subscribers - to delete arbitrary other users' notifications by enumerating integer notification identifiers. The plugin's notification deletion endpoint fails to verify that the requested notification belongs to the authenticated requester, exposing all users' notifications to deletion by any site member. A publicly available exploit exists per WPScan, though EPSS sits at 0.13% (3rd percentile), indicating low observed exploitation activity at time of analysis.
Cache management actions in the LWS Optimize WordPress plugin before version 3.4 lack authorization checks, permitting any authenticated user - including low-privileged Subscribers - to flush the site's caches and trigger repeated, resource-intensive cache rebuilds. The vulnerability is classified as CWE-862 (Missing Authorization) and carries a CVSS 3.1 score of 4.3 (Medium), with impact limited to availability degradation rather than data exposure or modification. A publicly available proof-of-concept exists per WPScan reporting, though EPSS sits at a very low 0.13% (3rd percentile) and the vulnerability is not listed in CISA KEV, indicating limited observed exploitation interest.
Clever Mega Menu for Visual Composer (WordPress plugin, versions through 1.0.1) allows any authenticated user with as little as Subscriber-level access to overwrite navigation menu item content and settings through an unprotected AJAX endpoint. The plugin fails to perform either a nonce check or a capability check before processing menu item metadata updates, meaning WordPress role-based access control over menu management is completely bypassed. A publicly available exploit exists via WPScan, though EPSS places exploitation probability at 0.14% (4th percentile) with no CISA KEV listing, indicating limited observed exploitation at time of analysis.
Simple Restrict WordPress plugin before 1.2.9 exposes restricted post and page content through the WordPress REST API due to an authorization bypass. The plugin enforces its own permission system on the front-end but falls back to a generic WordPress capability check on REST API routes, allowing any contributor-level or higher WordPress account to read content that was explicitly restricted via the plugin's access controls. No public exploit identified at time of KEV review, though a proof-of-concept is publicly available via WPScan; the EPSS of 0.13% at the 3rd percentile confirms negligible observed exploitation activity.
Unrestricted object instantiation in Jenkins 2.575 and earlier (LTS 2.568.1 and earlier) allows users holding Overall/Manage permission to instantiate arbitrary Java types through the project naming strategy configuration, including configuration objects intended exclusively for full administrators. This effectively breaks the permission boundary between Overall/Manage holders and full system administrators, enabling privilege escalation within the Jenkins controller. No public exploit has been identified at time of analysis, but fixed releases (Jenkins 2.576 and LTS 2.568.2) are available and should be applied promptly.
Jenkins 2.575 and earlier (LTS 2.568.1 and earlier) and multiple Jenkins plugins contain a cluster of vulnerabilities ranging from remote code execution via deserialization filter bypass to path traversal, CSRF, permission check failures, and Unicode-based user impersonation. The most critical issue - a bypass of the JEP-200 class filter in the Remoting library - allows authenticated agent operators or principals holding Agent/Connect permission to execute arbitrary code on the Jenkins controller. Three separate avenues for controller-side code execution are present in this advisory: the Remoting deserialization bypass (CVE-2026-70426), a tar archive symlink path traversal (CVE-2026-70427), and a file parameter path traversal (CVE-2026-70428). No public exploit or CISA KEV listing is confirmed at time of analysis, but the severity and variety of attack paths make this advisory high-priority for any Jenkins deployment.
Unauthorized configuration takeover in the Udimi Tools WordPress plugin (≤ 3.2) is possible for any subscriber-level authenticated user due to missing capability checks on both the `ajax_disconnect()` and `ajax_connect()` AJAX handlers. An attacker with a valid low-privilege WordPress account can wipe the site's Udimi API key and connected account settings, then replace them with attacker-controlled credentials - effectively hijacking the site's Udimi solo-ad integration and redirecting lead tracking data. No public exploit code or CISA KEV listing exists at time of analysis; EPSS data was not provided.
Insecure Direct Object Reference in Akaunting's multi-tenant file download route exposes uploaded media records across company boundaries to any authenticated portal customer. The `uploads/{id}/download` endpoint in `app/Http/Controllers/Common/Uploads.php` applies only generic authentication middleware and fetches Media records by raw integer ID without verifying tenant ownership, enabling sequential ID enumeration to exfiltrate invoices, financial statements, and other uploaded documents belonging to unrelated companies on the same instance. No public exploit has been identified and it is not listed in CISA KEV, but the attack is trivially executable by any portal customer given the low complexity of sequential integer enumeration.
Signature forgery in Documenso's V1 sequential-signing workflow allows an authenticated ASSISTANT-role recipient to complete signature fields owned by any co-recipient with an equal or later signing order, bypassing per-field ownership authorization entirely. The flaw resides in sign-field-with-token.ts, which upserts Signature records against the target field's recipientId without validating field type or ownership - a guard that Documenso's own V2 path (sign-envelope-field.ts) explicitly enforces and that the project's test suite comments confirm is absent from the V1 path. No public exploit code has been identified at time of analysis, but exploitation requires only low-privilege authenticated access as a named ASSISTANT recipient within a targeted document envelope.
Authentication bypass in changedetection.io's /settings endpoint silently disables REST API key enforcement when a privileged user or script submits a minimal POST request that omits the api_access_token_enabled checkbox. Because WTForms encodes an unchecked checkbox as False and the settings handler blindly merges all form fields via .update(), the API access token requirement is cleared without any warning, exposing the full watch list, history, and application configuration to unauthenticated REST API callers. No public exploit code or CISA KEV listing has been identified at time of analysis, but the post-exploitation surface - complete unauthenticated API access - is severe.
Unauthenticated retrieval of the full OpenAPI schema is possible in changedetection.io because the /api/v1/full-spec endpoint in changedetectionio/api/Spec.py lacks the @auth.check_token decorator that protects every other /api/v1/* route. Any network-reachable attacker can issue a plain GET request to this path and receive the complete merged schema - all endpoint paths, accepted parameters, and registered processor plugins - even when API key enforcement is active across all sibling routes. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code has been identified, though the attack requires zero prerequisites beyond network access, making opportunistic reconnaissance trivially achievable.
Unauthorized post creation in Xpro Addons - 140+ Widgets for Elementor (WordPress) affects all versions through 1.5.1, allowing any authenticated user with Subscriber-level access to publish arbitrary posts of the custom type `xpro_content` via a missing capability check on the `get_menu_content_editor()` AJAX handler. The created posts are publicly queryable on the front-end, enabling content injection, SEO spam campaigns, and database pollution against any WordPress site running the plugin. No public exploit or CISA KEV listing has been identified at time of analysis, though the low authentication barrier (any registered user) lowers the practical difficulty of abuse.
Insecure Direct Object Reference in the Groundhogg WordPress plugin (all versions through 4.5.2) allows authenticated users holding the view_contacts capability - most notably the built-in Sales Rep role - to enumerate and retrieve any contact record site-wide via the REST API, bypassing the intended ownership restriction that should limit them to their own assigned contacts. The GET /wp-json/gh/v4/contacts/<id> endpoint performs only a role-level capability check and accepts sequential integer IDs, meaning a Sales Rep can trivially iterate through all contact IDs and extract PII, contact metadata, owner identifiers, admin edit URLs, and - for contacts linked to a WordPress account - that user's full capability set. No public exploit code or active exploitation has been identified at time of analysis, but the attack is low-complexity for any attacker who can register or obtain a Sales Rep account.
Unauthenticated SSRF-adjacent resource abuse in Layouts for WPBakery (all versions ≤ 1.1.3) allows any remote attacker to force the WordPress host to issue unlimited outbound HTTP requests to the plugin vendor's external REST API and write the decoded JSON responses directly into the site's wp_options database table. The missing capability check on the wp_ajax_nopriv_handle_sync action (CWE-862) exposes this endpoint to every unauthenticated client with no nonce verification or rate limiting in place. This vulnerability is not listed in CISA KEV and no public exploit code has been identified, but the trivially low attack complexity - unauthenticated, network-reachable, zero prerequisites - makes availability abuse a realistic and automatable threat.
Incorrect authorization in OpenStack Ironic through 38.0.0 allows an authenticated low-privilege project reader to leak Portgroup configuration data belonging to Nodes owned or leased by other tenants via a crafted API request. The flaw breaks multi-tenant isolation - a core security guarantee of shared cloud infrastructure - enabling cross-project enumeration of bare-metal network topology. No public exploit code or CISA KEV listing is identified at time of analysis, but the low attack complexity and wide affected version range (spanning multiple major release series) make this a meaningful risk for multi-tenant OpenStack deployments.
Unauthenticated IDOR in the DHL Shipping Germany for WooCommerce WordPress plugin (versions before 4.0.1) exposes every generated shipping label to any internet visitor. The plugin's label-download endpoint performs no authorization check whatsoever - no capability check, nonce, login requirement, or order-ownership verification - and labels are indexed by predictable sequential IDs, enabling trivial full enumeration. A publicly available exploit exists; successful exploitation leaks customer full names, complete postal addresses, and order references at scale, carrying significant GDPR implications for any German e-commerce operator running the affected plugin.
Insecure Direct Object Reference (IDOR) in the MultiVendorX WordPress plugin before 5.0.11 exposes confidential financial and commission data across vendor accounts. Any authenticated vendor-level user can query a REST API endpoint using an arbitrary store identifier to retrieve another vendor's earnings and commission records, bypassing per-store ownership validation entirely. No active exploitation is confirmed in CISA KEV, but a publicly available exploit exists per WPScan, and the low EPSS score (0.14%, 4th percentile) suggests limited opportunistic scanning activity at this time.
Cost Calculator Builder for WordPress exposes live payment gateway credentials to any authenticated site user through a missing authorization check on its calculator export AJAX endpoint. All plugin versions through 3.6.17 are affected; attackers holding a Subscriber-level WordPress account - the lowest authenticated role - can invoke the `cost-calculator-custom-export-run` AJAX action to receive a full configuration export containing Stripe secret keys, PayPal client secrets, Razorpay secret keys, webhook secret keys, and reCAPTCHA secret keys. No public proof-of-concept exploit or CISA KEV listing has been identified at time of analysis, but the attack requires only a valid site account and basic HTTP knowledge, and an upstream fix has been committed to the plugin's trunk repository.
Cross-tenant object exfiltration in OpenStack Swift through 2.38.0 allows authenticated S3 API users to bypass source-object authorization by injecting Swift-native server-side copy headers (X-Copy-From, X-Copy-From-Account) into a signed S3 PUT request. The S3API middleware authorizes the request against the attacker-controlled destination bucket and then forwards the copy headers to Swift's copy engine, which executes the cross-tenant copy without re-evaluating the source object's ACLs or ownership - a classic confused-deputy flaw (CWE-863). Exploitation is constrained to deployments with the non-default s3_acl=true option enabled, and no public exploit is identified at time of analysis.
OpenStack Swift's S3API middleware through version 2.38.0 fails to enforce SigV4 signature coverage over semantic x-amz-* headers on presigned URL requests, enabling unauthorized server-side object copy operations under the signer's authorization context. An attacker holding a valid presigned PUT URL can inject an unsigned X-Amz-Copy-Source header, redirecting Swift's behavior from a client upload into a server-side copy that reads any object accessible to the URL's original signer - effectively allowing privilege escalation within a delegated authorization context. No public exploit or CISA KEV listing was identified at time of analysis, but all deployments running the S3API middleware under the default s3_acl=false configuration are affected.
Authentication bypass in the My Safetipin Android application version 5.2.1 stems from hardcoded credentials in the authentication module that produce predictable OTP values, letting remote attackers log in as arbitrary users and take over accounts without legitimate credentials. Any personal-safety data stored in a victim's account - location history, safety pins, and profile details - becomes exposed and modifiable. No public exploit has been identified at time of analysis, and the EPSS score of 0.27% (18th percentile) reflects low observed exploitation activity despite the maximal CVSS rating.
Unauthorized access to other users' personal data in SirenGPS Android Application 2.19.44 stems from the backend API failing to verify that a requesting user is authorized to act on the target user identifier supplied in API parameters. An authenticated attacker exploiting this horizontal privilege escalation can read and overwrite arbitrary users' personal information with only low-privilege access. No public exploit identified at time of analysis and EPSS is extremely low (0.15%, 5th percentile), but a detailed researcher advisory is publicly available on GitHub, lowering the bar for replication.
Hardcoded RTSP credentials in Zosi C519M IP camera firmware V4.2.8.823C01450BA expose live video feeds to any network-reachable attacker. The built-in credentials embedded in the RTSP authentication mechanism cannot be changed by the device owner, making every affected unit permanently vulnerable to unauthorized stream access. A public proof-of-concept exists on GitHub, and CISA's SSVC framework rates the attack as automatable with no exploitation preconditions beyond network reachability - no public exploit identified as actively exploited in CISA KEV at time of analysis.
Authorization bypass in the TicketDetailView component of Ehco1996 django-sspanel allows authenticated remote users to access support tickets belonging to other users by manipulating a user-controlled key in requests to apps/sspanel/views.py. All releases through 2023.12.26 are affected per ENISA EUVD-2026-52981. No patch will be issued - the maintainer has abandoned the project and did not respond to disclosure - leaving operators with no vendor remediation path. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Improper authentication in Baserow's 2FA verify endpoint (versions 2.3.0-2.3.2) allows a low-privileged remote attacker to manipulate which user identity the 2FA verification applies to, by supplying a different user identifier in the HTTP request body rather than relying on the authenticated session token. The affected component is the `verify` function in `backend/src/baserow/api/two_factor_auth/views.py`, confirmed by the 2.3.3 release refactor note referencing GitHub issue #5743. Exploitation is characterized as high complexity (CVSS 4.0 AV:N/AC:H/PR:L), and no public exploit or CISA KEV listing has been identified at time of analysis.
Open WebUI's terminal WebSocket route omits the role-state verification gate that all HTTP terminal endpoints enforce, granting `pending`-role accounts - unapproved registrations or deactivated users - interactive shell access that the HTTP plane correctly denies. Affected pip package versions span v0.8.8 through v0.10.x; the flaw was introduced when the terminal WebSocket route was first added in v0.8.8 and persisted because FastAPI dependency injection cannot be applied to WebSocket handshakes, leading to a divergent reimplementation. No public exploit code has been identified at time of analysis, but exploitation requires only a valid pending-role JWT obtainable by design during registration or retained for up to four weeks after deactivation.
Cross-knowledge-base IDOR in Open WebUI 0.9.6-0.10.2 allows any user with write access to one knowledge base to silently delete directories and file embeddings from unrelated knowledge bases they do not control, causing documents to vanish from RAG retrieval results and breaking chat-with-file for targeted files without disclosing their contents. The flaw (CWE-639) sits in the sync cleanup endpoint, which authorized requests based on the URL knowledge base ID but executed destructive operations against object IDs supplied in the request body without verifying those objects belonged to the authorized knowledge base. No public exploit is identified and no CISA KEV listing exists; the vendor released a complete fix in v0.11.0.
Cross-user file content disclosure in Open WebUI versions 0.8.8 through 0.10.2 allows any authenticated user to read indexed chunks from another user's private files by supplying a crafted inline model definition with a known target file UUID. The chat completion, chat completed, and chat action endpoints accepted client-supplied knowledge attachments on inline (non-workspace) model definitions without enforcing the caller's read access, bypassing the access control that saved workspace models correctly enforce. No active exploitation has been confirmed; the vendor released a complete fix in version 0.11.0.
Unauthenticated access to the network setup wizard API in H3C NX15 firmware V100R017 allows remote attackers to interact with the /api/wizard/networkSetup endpoint without presenting valid credentials. The root cause is CWE-306 - missing authentication for a critical function - meaning the device exposes a privileged configuration path with no access control gate. A public proof-of-concept repository exists on GitHub, confirming exploitability; no CISA KEV listing was identified at time of analysis, suggesting exploitation has not yet been confirmed at scale.
Open WebUI versions 0.7.0 through 0.10.x fails to re-validate the `features.image_generation` permission on the legacy chat-completions code path, allowing an authenticated user whose image generation rights were explicitly revoked to bypass the restriction by supplying the feature flag directly in a chat API request. This affects only deployments where an administrator has both enabled ENABLE_IMAGE_GENERATION and explicitly revoked per-user image generation rights - a non-default, deliberately restricted configuration. The result is unauthorized consumption of the operator's configured image provider API credits and quota, and unauthorized writes of generated files to the operator's storage; no public exploit has been identified at time of analysis.
Open WebUI versions 0.9.6 through 0.10.2 contain an authorization-ordering flaw in the DELETE /api/v1/chats/{id} handler that allows any authenticated user to silently cancel another user's active LLM generation tasks - including streaming model responses, title generation, and tag generation - without holding delete permissions on the target chat. The task-cancellation helper executes unconditionally at the top of the handler, before ownership verification, admin checks, or permission gate evaluation, meaning even revoking the chat.delete role permission leaves the cancellation side effect fully reachable. A detailed proof-of-concept is included in the GitHub security advisory; no public exploitation confirmed at time of analysis.
Broken object-level authorization in Open WebUI's standard channel messaging API allows any authenticated channel member with write access to overwrite or permanently delete messages authored by other members. Affected versions are open-webui 0.5.0 through 0.10.2 (pip). The `update_message_by_id` and `delete_message_by_id` route handlers in `channels.py` enforced a write-permission check for standard channels instead of an authorship check, meaning the same credential that grants posting rights silently granted full edit and delete authority over every other member's messages in that channel. A proof-of-concept script demonstrating end-to-end exploitation was included in the report; no public exploit code is independently confirmed at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Incorrect authorization in Veeam ONE's shared report link feature permits a low-privileged authenticated user to retrieve report data beyond the intended scope boundary of that link. Exploitation requires a valid Veeam ONE account but no elevated privileges, and the attack is network-accessible with low complexity. No public exploit code or CISA KEV listing exists at time of analysis, placing this in the medium-priority tier despite the straightforward exploitation path.
Incorrect authorization in NousResearch hermes-agent's Quick Command Handler allows low-privileged remote attackers to bypass slash command access controls via a flaw in the `_check_slash_access` function within `gateway/run.py`. All versions through 2026.6.5 are confirmed affected, with a public proof-of-concept exploit available on GitHub. The vendor did not respond to responsible disclosure, leaving no official patch available at time of analysis.
Session security diagnostics nodes in Eclipse Milo 0.6.0 through 1.1.4 expose sensitive OPC UA session metadata without enforcing any authorization checks, a CWE-862 (Missing Authorization) flaw. An unauthenticated anonymous client connecting over a None/None (no-security) endpoint can enable the diagnostics subsystem with no certificate or credentials whatsoever; separately, a client presenting a trusted application certificate over SignAndEncrypt can read the SessionSecurityDiagnosticsArray for all active server sessions, harvesting usernames, login history, authentication mechanisms, session security modes and policies, and public client certificates. No public exploit code exists and the vulnerability is not listed in CISA KEV, but the zero-authentication path and prevalence of None/None endpoints in legacy OT/IIoT environments meaningfully lower the exploitation barrier.
Broken object-level authorization in the REST API Log WordPress plugin (all versions before 1.7.1) permits unauthenticated attackers who hold any valid log-download token - regardless of which entry it was issued for - to retrieve arbitrary log entries from any other user, exposing stored credentials, authentication tokens, and private REST API payloads. The root cause is twofold: tokens are not cryptographically bound to specific log entry IDs, and the plugin performs no WordPress capability check on the requester. A public exploit PoC is referenced via WPScan, though EPSS at 0.18% and SSVC exploitation status of 'none' indicate no confirmed widespread abuse at time of analysis.
Missing authorization in the Wired Impact Volunteer Management WordPress plugin (versions before 2.8.2) allows any authenticated WordPress user with at least a Subscriber role to remove RSVPs belonging to other users from any volunteer opportunity. The vulnerability stems from an AJAX action handler that neither verifies the requesting user's authorization level nor confirms ownership of the RSVP being deleted, enabling unauthorized data manipulation across the entire volunteer management system. A publicly available proof-of-concept exists via WPScan, though EPSS sits at 0.13% (3rd percentile) and SSVC confirms no active exploitation, suggesting limited real-world attacker interest at this time.
Clearfy Cache WordPress plugin versions before 2.4.3 exposes admin-only settings pages and their contents - including administrative nonces - to any authenticated user at Subscriber level or above due to a missing capability check on an alternate admin-page dispatch path. While the canonical admin URL enforces access controls correctly, the unguarded dispatch path bypasses those restrictions entirely. A publicly available proof-of-concept exists per WPScan reporting, though EPSS sits at 0.13% (3rd percentile), indicating low observed exploitation probability despite POC availability; no confirmed active exploitation (CISA KEV) has been recorded.
Authorization bypass in the Brizy WordPress plugin before 2.8.19 permits authenticated Contributor-level users to hijack template-type metadata on templates owned by other users. The plugin validates authorization against one request parameter while executing the write operation against a different, attacker-controlled parameter - a textbook CWE-639 Insecure Direct Object Reference variant. A publicly available exploit is documented by WPScan; however, no active exploitation is confirmed via CISA KEV, and the EPSS score of 0.13% (3rd percentile) indicates negligible observed in-the-wild activity.
Contest Gallery WordPress plugin (all versions before 30.0.7) exposes the site's complete stored OpenAI prompt history to any authenticated user holding at minimum a Subscriber role, due to a handler that performs neither a capability check nor a nonce verification. An attacker with a basic WordPress account can call the unprotected AJAX endpoint directly to exfiltrate the full prompt history, potentially exposing confidential business logic, AI workflows, or sensitive data embedded in prompts. No active exploitation is confirmed (not in CISA KEV), but a publicly available proof-of-concept exists per WPScan, and EPSS remains low at 0.13% (3rd percentile).
Missing authorization in the miniOrange 2FA WordPress plugin before 6.2.7 allows any authenticated low-privileged user to trigger OTP email delivery to arbitrary email addresses and exhaust the site's metered OTP quota. The plugin's second-factor enrollment endpoint neither restricts which users may invoke it nor binds the OTP recipient to the enrolling user's own address, enabling both unsolicited OTP email delivery and a denial-of-service attack against other users' 2FA flows. No public exploitation or KEV listing has been identified, though a public proof-of-concept is available via WPScan; EPSS stands at 0.13% (3rd percentile), indicating low observed exploitation activity.
Horizontal privilege escalation in the Paid Membership Subscriptions WordPress plugin (all versions before 3.0.8) allows any subscriber-level authenticated user to hijack and overwrite another member's subscription - including plan tier, status, and expiration date - by submitting a crafted change-subscription checkout request with an arbitrary subscription ID. The root cause is a missing ownership verification check at the business logic layer of the checkout flow (CWE-284). A publicly available proof-of-concept exploit has been published by WPScan, though EPSS sits at just 0.13% (3rd percentile), suggesting limited automated exploitation so far. The vulnerability is not listed in CISA KEV at time of analysis.
Unauthenticated consent-record forgery and privacy-queue flooding affect GDPR Framework By Data443 WordPress plugin versions prior to 2.4.0. The plugin fails to verify the identity of the data subject or check authorization when recording cookie-consent choices and processing privacy requests, allowing any unauthenticated remote attacker to submit fraudulent GDPR consent records on behalf of arbitrary email addresses and to inject unlimited entries into the site's privacy-request queue. A publicly available proof-of-concept exists per WPScan; the vulnerability is not listed in the CISA KEV catalog, and EPSS sits at 0.15% (4th percentile), indicating low observed exploitation at time of analysis.
Improper access control in the wpForo Forum WordPress plugin before 3.1.3 permits any subscriber-level authenticated user to write to administrator-controlled profile fields - including account activation status and forum reputation score - during a standard self-service profile update. This allows a banned or pending user to self-activate their own account, bypassing moderator enforcement, and to forge an arbitrarily high reputation score that may unlock elevated forum privileges. No CISA KEV listing exists, but a publicly available exploit is documented by WPScan; the EPSS score of 0.14% (4th percentile) indicates low observed exploitation probability at scale, though the low barrier to attack (any registered user) makes it a meaningful integrity risk for moderated forums.
Signature forgery in the MonsterInsights WordPress plugin before 11.1.0 allows unauthenticated network attackers to overwrite plugin configuration values when the site is not connected to Google Analytics. The root cause is that the HMAC signing key used to authenticate a specific AJAX action defaults to an empty string in that disconnected state, making any forged HMAC trivially valid. The practical impact is limited to disrupting server-side analytics in Manual GA4 mode; no public exploit identified as actively exploited (not in CISA KEV), though a publicly available proof-of-concept exists and the EPSS probability is low at 0.15%.
Improper authorization in diaowen DWSurvey (all versions through 6.14.0) permits authenticated low-privileged users to invoke the Survey Status Handler endpoint beyond their intended access level, enabling unauthorized manipulation of survey state - such as publishing, closing, or altering surveys owned by other accounts. The affected endpoint `/api/dwsurvey/app/survey/up-survey-status.do` is remotely reachable and lacks sufficient authorization enforcement. A public proof-of-concept exploit has been disclosed via Google Drive; no vendor patch exists as the vendor did not respond to responsible disclosure, leaving all current deployments unmitigated.
Authorization bypass in DWSurvey up to version 6.14.0 permits remote authenticated attackers to manipulate user-controlled keys in the Survey Handler's devSurvey function, bypassing access controls on the /api/dwsurvey/app/v6/dw-design-survey/dev-survey.do endpoint. The flaw (CWE-639, Insecure Direct Object Reference class) allows unauthorized read or write access to survey resources belonging to other users. A public proof-of-concept exploit is available and the vendor has not responded to disclosure, leaving no official patch for deployed instances.
Captive portal authentication bypass in Zyxel WAX650S firmware exposes guest or restricted wireless networks to unauthorized access by any WLAN-adjacent attacker. The flaw resides in the social_login.cgi CGI handler, where CWE-287 (Improper Authentication) allows requests to circumvent captive portal enforcement entirely - not just weaken it. All firmware versions through 7.10(ABRM.4)C0 are confirmed affected per the vendor's own advisory. No public exploit code or CISA KEV listing has been identified at time of analysis, though the low attack complexity makes opportunistic exploitation plausible once the mechanism is understood.
Improper authorization in KodBox 1.67 Build 02 allows unauthenticated remote attackers to bypass access controls via the msgWarning plugin endpoint, resulting in limited unauthorized access to confidential data. The CVSS 4.0 vector (PR:N/UI:N) confirms no authentication is required, and a public proof-of-concept exploit has been published on GitHub. The vendor did not respond to responsible disclosure, leaving no confirmed patch available at time of analysis.
Secure boot bypass in Caliptra Core ROM 2.1.0-2.1.1 (subsystem mode) enables a local attacker controlling compromised MCU firmware to silently load unauthorized firmware into ICCM while attestation continues reporting the originally verified image digest, masking the compromise entirely. The TOCTOU race in UpdateResetFlow::run() is compounded by absent validation of the caller-supplied AXI staging address against the strap-configured SS_EXTERNAL_STAGING_AREA_BASE_ADDR, creating a window between verification and ICCM load during which SRAM contents can be swapped. No public exploit has been identified and no CISA KEV listing applies, but the severity lies in the attack's undetectability through standard attestation channels.
Origin validation error in Microsoft Edge (Chromium-based) enables a remote unauthenticated attacker to perform cross-origin spoofing attacks, achieving high confidentiality impact and limited integrity impact against victims who interact with attacker-controlled content. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N) with temporal indicators E:U/RL:O/RC:C indicates an officially patched vulnerability with no publicly proven exploit code and confirmed vendor reporting. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Origin validation error in Microsoft Edge (Chromium-based) allows network-positioned unauthenticated attackers to perform cross-origin tampering when a victim user interacts with malicious web content. The flaw (CWE-346) undermines the browser's origin enforcement logic, enabling integrity and confidentiality compromise at low severity per CVSS 5.4. Tagged as an Authentication Bypass vector, suggesting edge cases where origin-gated auth flows in Edge may be bypassed. No active exploitation confirmed (not in CISA KEV), no public POC identified, and a vendor patch is available via MSRC.
Missing authorization controls in Microsoft Edge (Chromium-based) allow a local attacker without any system privileges to bypass authorization and perform tampering actions against the browser. The flaw (CWE-862) results in high confidentiality impact per the CVSS vector, though the description characterizes the effect as tampering - a discrepancy addressed in confidence notes below. No public exploit code has been identified and Microsoft has released an official patch through the MSRC advisory portal.
Spoofing via origin validation failure in Microsoft Edge (Chromium-based) allows a network-adjacent unauthenticated attacker to deceive users or systems about the true origin of web content or requests. All Chromium-based Edge versions are affected per the wildcard CPE, and a vendor-released patch is confirmed via the Microsoft Security Response Center. No public exploit code exists and active exploitation is not confirmed - the CVSS temporal metric E:U (exploit unproven) and absence of CISA KEV listing reinforce a currently theoretical risk level.
Origin validation error in Microsoft Edge (Chromium-based) enables a local, unauthenticated attacker to bypass cross-origin restrictions and perform data tampering. The CVSS vector (AV:L/PR:N) indicates that any unprivileged local user - including guest or kiosk session users - can trigger this flaw without requiring prior authentication or user interaction. With a high confidentiality impact (C:H) and low integrity impact (I:L), exploitation could expose sensitive browser-held data while also permitting limited content manipulation. No public exploit code has been identified and CISA KEV does not list this CVE; the temporal metric E:U corroborates no known active exploitation at time of analysis.
Draft post creation in Camaleon CMS through 2.9.2 allows any authenticated low-privileged user to create and overwrite draft posts by bypassing role and permission checks on the admin drafts endpoint. The DraftsController's overridden create and update actions omitted the authorize! calls enforced by the parent PostsController, and used global unscoped post lookups that ignore post type and user ownership, enabling cross-post-type draft manipulation and ownership attribution changes on existing drafts. No CISA KEV listing or public exploit code has been identified; the CVSS 4.0 score of 5.3 (PR:L, VI:L) reflects limited integrity impact with no confidentiality or availability consequence.
Insufficient permission checks in Misskey's Direct Messages (Chat) feature expose DM data points to authenticated users who lack authorization to access them, across versions 2025.3.2 through 2026.5.3. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), where the server fails to validate account permissions before returning DM-related data via API. No public exploit or CISA KEV listing exists; the vendor patched this in version 2026.5.4 alongside four additional CVEs.
Unauthorized data disclosure via the Server Announcements API in Misskey affects all instances running versions 2024.5.0 through 2026.5.3, allowing remote callers to read restricted announcement data without appropriate authorization. The flaw stems from CWE-285 (Improper Authorization) - the API endpoint fails to enforce privilege checks before returning data, making restricted content accessible to actors who should not see it. No public exploit code or CISA KEV listing exists at time of analysis, but the network-accessible, no-authentication-required vector makes this straightforwardly reachable on any exposed instance.
Plaintext AWS credential extraction in the DuckDB AWS Extension allows any SQL-privileged database user to bypass the database-wide allow_unredacted_secrets=false security policy by invoking load_aws_credentials(redact_secret=false), returning the full AWS credential chain - access_key_id, secret_access_key, session_token, and region - in cleartext. The bypass is particularly impactful in managed cloud environments where pg_duckdb is preloaded and an ambient AWS credential chain (IMDSv2, IRSA, ECS task role, EC2 instance profile) is automatically reachable from the database host, effectively converting low-privilege SQL access into valid cloud API credentials. No public exploit code or CISA KEV listing has been identified; an upstream fix is confirmed via GitHub commit 7d04119 (PR #156), though a tagged patched release version is not confirmed in available data.
Authorization bypass in Apache NiFi 2.0.0-2.10.0 allows authenticated users holding write access to one Parameter Context to delete Assets belonging to a separate, restricted Parameter Context they are not authorized to modify. The REST API's asset deletion endpoint validated permissions against the caller-supplied Parameter Context Identifier without confirming that the targeted Asset Identifier is actually recorded as belonging to that context - a broken object-level authorization (BOLA/IDOR) flaw. No public exploit code exists and the vulnerability is absent from the CISA KEV catalog; impact is confined to multi-tenant NiFi deployments with differentiated per-context authorization policies.
Missing authorization in Apache NiFi's Parameter Context update REST API allows an authenticated user with write access to a Parameter Context to alter parameter values that affect referencing components the user is not authorized to access. In deployments where parameter values contain executable scripting content, this privilege boundary bypass can trigger code execution during automatic component validation on stopped processors without the attacker needing to start those components. No public exploit has been identified; exploitation is bounded to deployments using component-level authorization policies and is confirmed fixed in Apache NiFi 2.11.0 per NIFI-16148.
Authorization bypass in jeequan jeepay up to version 3.2.9 allows authenticated low-privilege users to circumvent access controls enforced by the PreAuthorize Handler within WebSecurityConfig, specifically targeting the SysLogController component. The flaw stems from CWE-639 (Authorization Bypass Through User-Controlled Key), enabling manipulation of access-control keys to reach system log data or restricted administrative functionality beyond the user's granted permissions. A public proof-of-concept exploit exists; no vendor response has been received and no patch has been confirmed, elevating remediation urgency despite the moderate CVSS score.
Credential recovery is possible on TP-Link Omada network devices - including Gateways, Switches, Access Points, and OLTs - because site credentials are hashed with a legacy algorithm that lacks adequate protection against offline cracking (CWE-759). An attacker who has already obtained privileged access to the device or management environment and extracted stored credential hashes can recover plaintext credentials, enabling unauthorized access to affected Omada infrastructure. No public exploit code has been identified at time of analysis, and the issue is not listed in the CISA KEV catalog, though a vendor patch is available.
Shared embedded certificates across all TP-Link Omada deployments enable impersonation of trusted controllers and managed devices by any attacker who extracts those certificates from a single unit. The CVSS 4.0 vector (AV:A/PR:N/VC:H/SC:H) confirms that an unauthenticated attacker with adjacent network access to the Omada management plane can intercept management communications at high confidentiality impact across both the vulnerable and subsequent systems, with no patch complexity required beyond certificate possession. No public exploit has been identified at time of analysis, and this CVE is not currently listed in the CISA KEV catalog, though the authentication-bypass tagging and the breadth of affected product lines (gateways, switches, access points, controllers, OLTs) give this meaningful real-world weight in environments relying on Omada for network management.
Credential interception in TP-Link Omada's device adoption process exposes site management authentication to offline cracking due to use of a weak, unsalted hash algorithm (CWE-759). An adjacent-network attacker who captures adoption-phase traffic can recover plaintext credentials and authenticate to the Omada controller or managed devices including gateways, switches, access points, and OLTs. No public exploit identified at time of analysis, but a vendor patch is available; the CVSS 4.0 score of 6.9 reflects meaningful real-world constraints including network adjacency, high attack complexity, and a required adoption event.
Improper certificate hostname validation in TP-Link Omada networking devices (gateways, switches, and access points) allows a network-positioned attacker to intercept or modify encrypted management traffic between those devices and their cloud controllers. The flaw - classified as CWE-295 - means the devices do not adequately confirm that a presented TLS certificate belongs to the expected cloud controller hostname, enabling a machine-in-the-middle to substitute a fraudulent certificate and break the trust boundary. No active exploitation is confirmed (not in CISA KEV) and no public proof-of-concept has been identified at time of analysis; vendor has released patched firmware.
Unauthenticated remote access to the /EIP_Com_FileList.aspx endpoint in NewType WebEIP up to version 3.0 exposes file listing functionality to any network-reachable attacker due to improper authentication enforcement (CWE-287). A public proof-of-concept exploit hosted on Google Drive is confirmed available, lowering the exploitation bar significantly. No vendor patch exists as the vendor did not respond to disclosure; organizations must rely entirely on compensating controls.
Channel lifecycle enforcement failure in russh (Rust SSH library, versions <= 0.62.4) allows authenticated clients to invoke server-side handler callbacks - including exec_request, shell_request, subsystem_request, data, channel_eof, and channel_close - for SSH channel IDs that were never opened or confirmed by the transport layer. An authenticated peer can send crafted SSH_MSG_CHANNEL_REQUEST packets without ever issuing SSH_MSG_CHANNEL_OPEN, or after having a channel_open_session request explicitly denied by the application, and still trigger all channel-scoped callbacks. A working Python PoC is publicly available demonstrating 32 exec_request invocations with zero channels ever opened; no active exploitation is confirmed (not in CISA KEV) and a vendor patch exists in v0.62.5.
Authentication bypass in 389 Directory Server (Red Hat Directory Server 11-13) allows a network-connected user holding valid credentials for an administratively locked account to retain an authenticated LDAP session, defeating account-lock as an access-revocation control. The SASL PLAIN bind handler installs connection-level authenticated state before executing the account-lock check; when the lock check fails, only the error is returned to the client while the internal authenticated state on that connection persists unrevertd. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the real-world impact is highest in incident-response and employee-offboarding scenarios that rely on directory lock as the primary revocation mechanism.
Privilege escalation to NT AUTHORITY\SYSTEM is achievable by any local, unprivileged user via Wellbia XIGNCODE3's kernel driver xhunter2.sys version 2026.6.1.192, due to missing access control on the IRP_MJ_WRITE command interface. Beyond SYSTEM-level execution, the flaw enables extraction of credentials from PPL-protected lsass.exe and termination of PPL-protected security processes such as EDR/AV agents, effectively disabling host defenses. No active exploitation is confirmed by CISA KEV, though the primary reference is a researcher blog post (blacksnufkin's 'Hunting the Hunter II') that strongly suggests PoC-grade research material exists.
Insecure Direct Object Reference in Admidio before 5.0.11 allows authenticated low-privilege users to hijack list configurations managed by administrators or other users by manipulating the list_uuid parameter in the save_temporary mode of mylist_function.php. Any user with a valid session can enumerate global list UUIDs and submit crafted requests to overwrite admin-curated global lists or private lists belonging to other users, effectively transferring ownership and demoting shared resources to personal configurations. No public exploit code has been identified at time of analysis, and a vendor-released patch is available in version 5.0.11.
Cross-organization role manipulation in Admidio before 5.0.11 allows authenticated role administrators to delete, activate, deactivate, or edit roles belonging to other organizations hosted on the same instance. The flaw exists because `groups_roles.php` handlers accept role UUIDs without verifying that the target role belongs to the requesting user's organization, enabling cross-tenant privilege structure sabotage. No public exploit has been identified at time of analysis; vendor-released patch version 5.0.11 is available.
Metadata disclosure in SiYuan before v3.7.3 exposes document titles, notebook paths, root IDs, and icons for administrator-restricted documents via the unauthenticated `/api/block/getBlockInfo` endpoint. The publish-access control flag is never checked server-side before returning document root metadata, making this a complete bypass of SiYuan's per-document publish exclusion feature. No public exploit is identified at time of analysis and no KEV listing exists, but the CVSS 4.0 vector (PR:N, AC:L) confirms exploitation requires no credentials and no special conditions against the network-facing API.
Missing granular access control in HCL iControl v3.2.0 exposes administrator-level functionality to unauthorized users over the network. Regular-privilege users can bypass authorization checks to view or access admin-scoped features, resulting in a limited confidentiality impact. No public exploit code exists and no CISA KEV listing is present; however, the 'Authentication Bypass' tag and the network-accessible vector mean the exposure is reachable without physical proximity, though the high attack complexity (AC:H) constrains opportunistic exploitation.
Broken access control in the Unlimited Elements For Elementor WordPress plugin (versions through 2.0.15) permits authenticated low-privileged users to invoke restricted plugin functions without proper authorization. The flaw, rooted in CWE-862 (Missing Authorization), allows a subscriber- or contributor-level WordPress account to perform actions that should be restricted to higher-privileged roles, resulting in low-impact integrity and availability consequences. No public exploit code has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog.
Broken object-level authorization in the Dokan WordPress plugin (versions before 5.0.9) allows any authenticated vendor on a multivendor marketplace to overwrite product attributes and default attributes belonging to other vendors via the plugin's REST API write endpoints. Exploitation requires only a low-privilege vendor account - no admin access needed - making this accessible to any registered seller on the platform. A publicly available proof-of-concept exists per WPScan, though EPSS sits at 0.13% (3rd percentile), indicating limited observed exploitation activity so far; the vulnerability is not listed in CISA KEV.
Order ownership bypass in Dokan Multivendor for WordPress (versions before 5.0.9) allows any authenticated vendor to modify the status of arbitrary WooCommerce orders across the entire marketplace, including orders owned by other vendors and customers. The flaw stems from a REST endpoint handling bulk order-status changes that accepts attacker-supplied order IDs without verifying the requesting vendor's ownership of those orders. No active exploitation is confirmed (not in CISA KEV), but a publicly available proof-of-concept exists and EPSS at 0.13% (3rd percentile) reflects low observed exploitation to date.
Unauthorized lesson content disclosure in Academy LMS WordPress plugin before 3.8.3 allows any subscriber-level authenticated user to read arbitrary lesson content via the REST API - including lessons from paid courses they have not purchased and lessons in unpublished states (draft, pending, private). The root cause is a complete absence of enrollment and publication-status validation in the single-lesson REST API endpoint. A publicly available proof-of-concept exists per WPScan, though EPSS at 0.13% (3rd percentile) and SSVC classification as non-automatable indicate limited observed exploitation activity at the time of analysis.
ProfileGrid WordPress plugin before version 6.0.0.0 exposes pending group membership request data to any authenticated user due to missing authorization checks on the listing endpoint. Any subscriber-level account can enumerate the names and request timestamps of users awaiting approval for any group, including groups configured as private. No active exploitation is confirmed (not in CISA KEV), though a public exploit exists via WPScan; EPSS of 0.13% (3rd percentile) places real-world exploitation probability as very low.
GEO my WP WordPress plugin versions before 4.5.5.3 allows any subscriber-level (or higher) authenticated user to modify or permanently delete geolocation records belonging to other users or posts by supplying arbitrary record IDs to two unprotected AJAX actions. The root cause is a complete absence of ownership and capability checks on these endpoints, a textbook CWE-639 IDOR. A publicly available exploit exists per WPScan; however, no public exploit identified at time of analysis corresponds to confirmed active exploitation (not in CISA KEV), and the EPSS score of 0.13% at the 3rd percentile reflects low observed exploitation activity despite POC availability. A vendor-released patch is available in version 4.5.5.3.
Insecure Direct Object Reference (IDOR) in the Tag, Category, and Taxonomy Manager WordPress plugin before 3.51.0 allows authenticated contributors to disclose content from private or draft posts they do not own. The plugin fails to verify post ownership before processing a referenced post ID and returning derived data, enabling a contributor to enumerate and extract information from restricted content authored by other users. No public exploitation in the wild has been confirmed (no CISA KEV listing), though WPScan has published a publicly available proof-of-concept.
Unauthorized revenue data disclosure in the Classified Listing WordPress plugin (before 5.4.4) allows any authenticated contributor-level user to read daily store revenue figures restricted to administrators and report managers. The flaw stems from a missing capability check (CWE-862) on an AJAX action that aggregates store revenue totals, exposing potentially sensitive business intelligence to lower-privileged users. No public exploit identified at time of analysis per KEV, though a publicly available exploit exists per WPScan reporting; the EPSS score of 0.13% (3rd percentile) suggests limited real-world exploitation interest despite code availability.
The Classified Listing WordPress plugin before version 5.4.4 exposes private, draft, and pending post content to authenticated contributors due to a missing authorization and ownership check on an AJAX endpoint. Any user with contributor-level access or higher can read arbitrary post content belonging to other users, including administrators' unpublished material. A publicly available exploit exists via WPScan, though EPSS at 0.13% (3rd percentile) and the absence of a CISA KEV listing indicate active exploitation is not confirmed at time of analysis.
Post-deletion authorization bypass in the Contest Gallery WordPress plugin before 30.0.7 allows any authenticated Author-level or higher user to permanently delete arbitrary posts, pages, and other WordPress content they do not own. The plugin's post-deletion AJAX handler enforces only a coarse role-membership test, entirely omitting per-object capability verification and nonce validation - the two controls that WordPress's built-in permission model relies on to prevent cross-user destructive actions. A public exploit is available via WPScan, lowering the skill barrier; though EPSS is low at 0.13%, any multi-author site with untrusted Author accounts faces real and irreversible content destruction risk.
Broken access control in Simply Schedule Appointments WordPress plugin before 1.6.12.11 exposes all customer appointment records to any authenticated Contributor-level user site-wide. The administrative appointment-listing shortcode omits a capability check, and the per-user result scoping logic defaults to showing all records when the requesting user is not recognized as staff. Any WordPress user holding the Contributor role or higher - a commonly granted role in multi-author sites - can enumerate names, email addresses, phone numbers, and appointment notes belonging to every customer in the system. A publicly available proof-of-concept exists, though EPSS at 0.13% and SSVC Automatable:No suggest exploitation remains targeted rather than widespread.
Improper authorization in GL.iNet's eSIM LPA API allows adjacent-network unauthenticated attackers to bypass nginx proxy controls on six cellular router models, gaining unauthorized access to eSIM management functions. Affected devices include the E5800, E750, X2000, X3000, XE3000, and XE300 running firmware up to 20260707. The GitHub advisory title explicitly frames this as 'Unauthenticated access to eSIM LPA API via nginx proxy bypass,' indicating the authorization enforcement failure lies in how nginx proxies requests to the /sdk/v1 endpoint. No public exploit code or CISA KEV listing has been identified at time of analysis.
Insecure Direct Object Reference in the better-auth passkey plugin (npm/@better-auth/passkey < 1.4.0) permits any authenticated user to delete arbitrary passkeys belonging to other users via the `POST /passkey/delete-passkey` endpoint. The `ctx.body.id` parameter is implicitly trusted without ownership verification, meaning a valid session - regardless of privilege level - is sufficient to enumerate and destroy other users' passkey credentials. Applications configured with `useNumberId` (auto-incrementing integer IDs) are trivially exploitable by sequential enumeration. No public exploit or CISA KEV listing confirmed at time of analysis; a vendor-released patch exists at version 1.4.0.
Path normalization bypass in Better Auth before v1.4.5 allows unauthenticated remote attackers to circumvent `disabledPaths` security controls and path-based rate limits by submitting requests with extra leading slashes (e.g., `//sign-in/email` instead of `/sign-in/email`). The root cause is in the bundled rou3 router library, which collapses empty path segments before route matching, meaning security rules keyed on canonical paths never match the double-slash variants. No public exploit code has been identified at time of analysis, but the trivially low attack complexity makes exploitation straightforward on unprotected deployments.
Unauthenticated REST API access in the webtoffee-cookie-consent WordPress plugin before 3.5.3 allows any network attacker to export or delete stored visitor consent records, create arbitrary WordPress posts, and alter the plugin's licensing state. All versions prior to 3.5.3 are affected with no special configuration required, as the missing permission callbacks expose endpoints to public access by default. A publicly available exploit exists per WPScan, though EPSS sits at 0.22% (12th percentile), indicating exploitation has not yet reached widespread automated abuse; no public exploit identified at time of analysis for active in-the-wild campaigns.
Broken object-level authorization in the Event Booking Manager for WooCommerce WordPress plugin (all versions before 5.3.7) allows any authenticated user with the Contributor role or higher to modify the title and publication status of arbitrary posts and pages sitewide - including content they do not own. The plugin's quick-edit event handler validates only a global WordPress capability (e.g., edit_posts) without confirming whether the requesting user owns the target object, enabling horizontal and vertical privilege escalation over site content. A publicly available proof-of-concept exists; however, no confirmed active exploitation has been identified and the EPSS score sits at 0.13%, indicating limited real-world adversary interest at time of analysis.
Insecure Direct Object Reference (IDOR) in the ProfileGrid WordPress plugin before 5.9.9.8 allows any authenticated user - including low-privilege Subscribers - to delete arbitrary other users' notifications by enumerating integer notification identifiers. The plugin's notification deletion endpoint fails to verify that the requested notification belongs to the authenticated requester, exposing all users' notifications to deletion by any site member. A publicly available exploit exists per WPScan, though EPSS sits at 0.13% (3rd percentile), indicating low observed exploitation activity at time of analysis.
Cache management actions in the LWS Optimize WordPress plugin before version 3.4 lack authorization checks, permitting any authenticated user - including low-privileged Subscribers - to flush the site's caches and trigger repeated, resource-intensive cache rebuilds. The vulnerability is classified as CWE-862 (Missing Authorization) and carries a CVSS 3.1 score of 4.3 (Medium), with impact limited to availability degradation rather than data exposure or modification. A publicly available proof-of-concept exists per WPScan reporting, though EPSS sits at a very low 0.13% (3rd percentile) and the vulnerability is not listed in CISA KEV, indicating limited observed exploitation interest.
Clever Mega Menu for Visual Composer (WordPress plugin, versions through 1.0.1) allows any authenticated user with as little as Subscriber-level access to overwrite navigation menu item content and settings through an unprotected AJAX endpoint. The plugin fails to perform either a nonce check or a capability check before processing menu item metadata updates, meaning WordPress role-based access control over menu management is completely bypassed. A publicly available exploit exists via WPScan, though EPSS places exploitation probability at 0.14% (4th percentile) with no CISA KEV listing, indicating limited observed exploitation at time of analysis.
Simple Restrict WordPress plugin before 1.2.9 exposes restricted post and page content through the WordPress REST API due to an authorization bypass. The plugin enforces its own permission system on the front-end but falls back to a generic WordPress capability check on REST API routes, allowing any contributor-level or higher WordPress account to read content that was explicitly restricted via the plugin's access controls. No public exploit identified at time of KEV review, though a proof-of-concept is publicly available via WPScan; the EPSS of 0.13% at the 3rd percentile confirms negligible observed exploitation activity.