Authentication Bypass
Monthly
Authentication bypass in the Newsletters WordPress plugin (all versions before 4.16) allows remote unauthenticated attackers to gain privileged API access via PHP type juggling against a non-strict key comparison. Exploitation is conditional on the plugin's optional API being enabled, but when active, attackers can modify subscriber records and send bulk emails without any credentials. A publicly available proof-of-concept is documented by WPScan; EPSS at 0.19% (9th percentile) suggests limited automated exploitation to date, and no CISA KEV listing has been issued.
Ghostfolio's Stripe checkout callback endpoint unconditionally grants a one-year Premium subscription to any authenticated user who supplies a valid Stripe Checkout Session ID, regardless of whether payment was completed. Versions prior to 3.4.0 retrieve the session object by ID and immediately create a subscription using the session's `client_reference_id` without ever asserting `session.payment_status === 'paid'` or `session.status === 'complete'`. Any registered user of an affected Ghostfolio instance can self-grant Premium access at zero cost, with no public exploit identified at time of analysis but trivial exploitability given the complete description of the missing check.
Authorization bypass in the kata-agent's ttRPC API allows an untrusted host to invoke two mem-agent methods unconditionally, circumventing the OPA/Rego-based AgentPolicy that forms the security boundary in Confidential Containers (CoCo) deployments. Affected are kata-containers versions prior to 4.0.0 when the mem-agent feature is explicitly enabled (disabled by default). The untrusted host can force in-guest memory operations - swap, aggressive eviction, or compaction - causing attacker-controlled availability and performance degradation of the confidential workload; the description explicitly rules out memory disclosure and code execution. No public exploit or CISA KEV listing has been identified at time of analysis, but the bypass is architecturally significant because it violates the CoCo threat model's fundamental assumption that the host is untrusted.
MCP resource and prompt wrappers in HKUDS nanobot 0.2.0 and 0.2.1 bypass operator-defined `enabledTools` access restrictions, allowing MCP servers to register capabilities beyond the intended scope. Operators who configure a specific tool allowlist to restrict what an MCP server can contribute to a nanobot agent find that resources and prompts from that server are registered unconditionally, exposing capabilities that were explicitly intended to be blocked. A public proof-of-concept exploit exists; this CVE is not in the CISA KEV catalog, so confirmed widespread active exploitation is not established.
Adobe Genuine Software Integrity Service on local systems exposes an Incorrect Authorization flaw (CWE-863) enabling any local attacker - without elevated privileges - to bypass the service's integrity-verification controls and obtain unauthorized limited write access to areas the service is designed to protect. All tracked versions of the service are affected per the open-ended CPE range published by Adobe. No public exploit or CISA KEV listing has been identified at time of analysis, and exploitation is constrained to the local environment, reducing mass-exploitation risk while remaining a realistic threat from malware, shared-account misuse, or low-privileged insider scenarios.
L7 intention authorization bypass in HashiCorp Consul Community and Enterprise editions 1.20.1 through 2.0.2 allows an authenticated mesh workload to reach HTTP paths that are explicitly blocked by path-based deny intentions, when the service proxy is configured with a custom public listener. The flaw undermines a core service mesh security control - path-based L7 intentions - without requiring unauthenticated access or elevated privileges beyond mesh workload enrollment. No public exploit code has been identified and this CVE is not listed in CISA KEV; the CVSS 4.2 Medium score accurately reflects the configuration-dependent, authenticated nature of the attack.
Partial arbitrary file read in HashiCorp Consul Community Edition and Enterprise 1.18.21 through 2.0.2 allows a network-accessible, highly-privileged attacker to exfiltrate sensitive credential files from the Consul server host. The flaw is scoped to configurations using the Vault Connect CA provider with JWT or AppRole authentication - a non-default but production-relevant deployment pattern - and requires operator:write permission to exploit. No public exploit or active exploitation has been identified at time of analysis; a vendor-released patch is available in Consul 2.0.3 and corresponding Enterprise builds.
Unauthenticated remote attackers can trigger operator-configured scheduled jobs in Grav CMS when the scheduler-webhook plugin is installed and misconfigured, due to a compound-conditional short-circuit (CWE-303) that skips token validation entirely when no webhookToken is set. The primitive is job-triggering rather than attacker-controlled command injection: RCE is only achievable when an administrator has separately configured a scheduled job that shells out, a condition the attacker cannot influence. No public exploit has been identified at time of analysis, and the vendor-released fix is available in Grav v2.0.9.
Missing authentication in VHF Data Link (VDL) CPDLC (Controller-Pilot Data Link Communications) enables rogue ground stations to inject unauthorized clearance messages into cockpit avionics over radio frequency. Pilots receiving spoofed CPDLC messages may follow misleading ATC instructions - altitude changes, heading redirections, or route modifications - with no indication the messages are inauthentic. This ICS-CERT advisory (ICSA-26-219-01) exposes a systemic protocol-level authentication gap with no public exploit identified at time of analysis.
Stale permission enforcement in Frappe's Document Follow subsystem allows authenticated users whose document access has been revoked or downgraded to continue receiving document-level data via scheduled email notifications. Affecting all Frappe v15 releases prior to 15.112.0 and v16 releases prior to 16.23.0, the flaw arises because notification generation never re-evaluates whether recipients still hold current read permission on subscribed documents at dispatch time. No public exploit code exists and no active exploitation has been confirmed; the vendor-assigned CVSS 4.0 score of 2.3 accurately reflects the narrow exposure window and the prerequisite that access revocation must have already occurred before the notification job fires.
Unrestricted access to the Document Follow API (update_follow) in Frappe framework allows any authenticated user to follow or unfollow arbitrary documents without authorization checks, constituting an Insecure Direct Object Reference (IDOR) flaw classified under CWE-639. Frappe versions prior to 16.20.0 (v16 branch) and 15.112.0 (v15 branch) are affected, enabling authenticated attackers to subscribe to change notifications for documents outside their authorization scope. No public exploit code exists and no active exploitation has been identified at time of analysis.
Field-level permissions bypass in Frappe framework allows authenticated users to read restricted DocType field values via the document follow timeline feature. Frappe deployments on the v16 branch prior to 16.23.0 and the v15 branch prior to 15.112.0 are affected, including ERPNext and other applications built on Frappe. An authenticated low-privileged user can access historical change values for fields protected by Frappe's permlevel system simply by viewing the document follow timeline - no public exploit has been identified and the vulnerability is not listed in CISA KEV.
Tenant isolation bypass in SuperTokens Core v6.0.0 through v11.4.0 enables an authenticated user in one tenant to access sessions, data, and API endpoints belonging to separate tenants on the same instance. The flaw represents a failure of authorization enforcement at the multi-tenancy boundary layer - the core authentication service does not adequately scope API operations to the requesting tenant's namespace. No public exploit code has been identified at time of analysis, but the confidentiality impact is rated high given that cross-tenant session hijacking and user data exfiltration are within scope for a successful attacker.
Unauthenticated log file exposure in the Webbox component of Tobit Laboratories AG TeamDavid allows remote attackers to retrieve sensitive error messages and internal application details without any credentials. All TeamDavid versions through Rollout 524 are affected per CPE cpe:2.3:a:tobit_laboratories_ag:teamdavid:*:*:*:*:*:*:*:*. No public exploit code or active exploitation has been identified; this vulnerability was disclosed as part of a batch of 22 CVEs uncovered by InfoGuard researchers during a systematic security audit of the platform.
Cross-package resource and model poisoning in NLTK's downloader (versions <= 3.9.4) allows an attacker who can influence what packages a user downloads to silently overwrite trusted corpora and model files with adversarial replacements. The root cause is that nltk.downloader extracts archives into shared namespaces (corpora/, taggers/) rather than package-isolated directories, and performs integrity validation only after extraction is complete - a classic TOCTOU-like design flaw. Poisoned resources survive interpreter restarts and propagate silently into ML pipelines, making this particularly dangerous in reproducibility-sensitive or automated NLP workflows. No public exploit code has been identified at time of analysis and this vulnerability is not listed in CISA KEV.
Broken Object Level Authorization in MStore API WordPress plugin (all versions before 4.21.0) exposes every WooCommerce order and associated customer PII to any authenticated WordPress user, including low-privileged Subscribers. The vendor-orders endpoint performs no caller-scoping check, meaning a Subscriber can enumerate the entire store's order history. Publicly available exploit code exists per WPScan, though EPSS at 0.13% (3rd percentile) indicates exploitation has not become widespread at time of analysis; no CISA KEV listing confirms active exploitation.
Unauthenticated cloud credential hijacking in the Templately WordPress plugin (all versions before 3.7.1) allows any remote attacker to overwrite the site administrator's stored cloud service connection with an account under their control. This severs the legitimate administrator's access to the cloud template library and redirects the site's template source to attacker-controlled infrastructure, enabling supply-chain-style content injection against the WordPress admin. A publicly available proof-of-concept exists per WPScan, though EPSS remains very low (0.14%, 3rd percentile), and no CISA KEV listing confirms active widespread exploitation at time of analysis.
Insecure Direct Object Reference (IDOR) in the Subscriptions for WooCommerce WordPress plugin before 2.0.1 allows any authenticated customer to read subscription records belonging to other customers by supplying an arbitrary subscription ID. The plugin fails to enforce ownership checks before returning subscription details - subscribed product, status, and date fields - exposing sensitive order metadata across tenant boundaries. A publicly available proof-of-concept exists per WPScan, but with an EPSS of 0.13% (3rd percentile) and no CISA KEV listing, mass exploitation is not currently observed.
Authorization bypass in the Stream - Activity Log & Audit Trail WordPress plugin (versions through 4.2.0) exposes the full site audit trail to any authenticated user holding a subscriber-level account or higher. The flaw resides in the plugin's Heartbeat API live-update handler, which returns activity records without verifying the requesting user holds the privileges required to view them (CWE-862). No public exploit or CISA KEV listing exists at time of analysis, but the low exploitation bar - any registered user account suffices - makes this a credible insider or low-effort attacker risk on sites with open registration.
Sigstore attestation verification in GitHub CLI prior to 2.97.0 can be defeated when an attacker registers a lookalike repository whose name contains dot characters that function as regex wildcards - for example, github/artifact.attestations-workflows matching a matcher intended solely for github/artifact-attestations-workflows. The `gh attestation verify` command in pkg/cmd/attestation/verify/policy.go constructed Certificate Subject Alternative Name (SAN) matchers by interpolating `--signer-repo` and `--signer-workflow` flag values directly into regex patterns without calling regexp.QuoteMeta(), allowing any dot or other metacharacter in a GitHub-permitted name to act as a wildcard. No public exploit has been identified at time of analysis; the CVSS 4.0 AT:P designator confirms exploitation requires the attacker to first position a valid lookalike repository with legitimate Sigstore attestations, making this a targeted rather than opportunistic threat.
Unauthenticated read access to appointment records in OpenReception appointment-booking-software (versions prior to 1.1.0) exposes scheduling metadata and AES-GCM cryptographic components - including encryptedPayload, iv, authTag, and dataKey - to any caller who possesses a valid appointment UUID. The GET handler at /api/tenants/{id}/appointments/{appointmentId} omits the checkPermission() call that the DELETE handler on the same file correctly enforces, and neither the apiAuthHandle nor authGuard middleware compensates because API paths bypass authGuard entirely and apiAuthHandle does not block unauthenticated requests on non-admin routes. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms zero-friction remote exploitation against any unpatched instance.
Unauthorized booking injection into private channels affects OpenReception appointment-booking-software ≤ 1.0.1 via a missing isPublic authorization check in the new-client booking path. An unauthenticated remote attacker solves a trivial 16-bit proof-of-work challenge, obtains a valid bearer token, and then supplies any private channelId in the create-new-client payload - bypassing the access control that protects the standard appointment path. When chained with companion finding V-10 (unauthenticated schedule endpoint leaking all private channel IDs), the entire attack requires only two unauthenticated HTTP sequences, no public exploit code identified at time of analysis.
Unauthenticated appointment injection in OpenReception appointment-booking-software prior to version 1.0.5 allows any remote caller to insert CONFIRMED appointments into arbitrary client tunnels by exploiting a missing authorization gate on the `add-to-tunnel` endpoint. The endpoint accepted any POST supplying a valid `emailHash` - used only as a tenant existence check - alongside an unrelated valid `tunnelId`, writing attacker-controlled appointment fields (ciphertext content, date, duration, agent) without a session, Authorization header, booking access token, or proof-of-work. No CISA KEV listing or public POC is identified at time of analysis, but the exploit pattern is structurally straightforward once valid identifiers are obtained.
Cross-tenant invite deletion in OpenReception's appointment booking software (prior to 1.0.6) allows an authenticated TENANT_ADMIN to destroy pending onboarding invites belonging to unrelated tenants on the same platform instance. The flaw exists because the invite cleanup query inside `StaffService.deleteStaffMember()` matches only on email address without constraining to the acting tenant's ID, causing any staff deletion to silently cascade-delete matching invites across all tenants. No active exploitation has been identified and no public exploit code exists; the issue is fully remediated in version 1.0.6 via a single ORM predicate addition.
The billing controller in Postiz (postiz-app) before v2.21.10 allows exploitation of an unauthenticated or lightly authenticated API endpoint to activate permanent top-tier paid subscriptions without financial transaction, by forging or replaying lifetime-deal redemption codes against a backend that performs no cryptographic validation or single-use enforcement. The vulnerable `/lifetime` POST endpoint passed user-supplied codes directly into the Stripe-integrated `lifetimeDeal` service with no server-side state verification, a textbook CWE-345 (Insufficient Verification of Data Authenticity) failure. No public exploit has been identified and this CVE is not listed in CISA KEV; the fix in v2.21.10 was complete endpoint removal, confirmed via the upstream GitHub commit.
Authorization bypass in SourceCodester Online Examination & Learning Management System 1.0 exposes student records to unauthorized authenticated users by failing to validate the `class_group` parameter in `view_students.php`. The CVSS 4.0 vector (PR:L) confirms that at least low-privilege authentication is required, limiting the attack surface but still enabling lateral access to student data across class groups the attacker should not be permitted to view. No public exploit code has been identified and the product is not listed in the CISA KEV catalog at time of analysis.
Unrestricted file upload in SourceCodester Online Examination & Learning Management System 1.0 exposes the server to arbitrary file upload via the upload_files.php endpoint, which lacks adequate file type or extension enforcement. The CVSS 4.0 vector indicates low-privilege authentication is required (PR:L) over a network vector with low complexity, and the 'Authentication Bypass' tag raises the possibility that this authentication gate may itself be circumventable. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the attack class is well-understood and trivially weaponizable against affected deployments.
Authorization bypass in SourceCodester Online Examination & Learning Management System 1.0 allows authenticated low-privilege users to access records belonging to other users by manipulating the `id` parameter in the `/view.php` endpoint without proper ownership verification. The CVSS 4.0 vector (PR:L, AV:N, VC:L) confirms the flaw is remotely reachable but requires prior authentication, and impact is limited to confidentiality disclosure of a single record type. No public exploit code and no active exploitation (CISA KEV) have been identified at time of analysis.
Payment authorization token reuse in Events Made Easy WordPress plugin before 3.1.2 enables unauthenticated financial fraud against event organizers. An attacker exploits an absent binding between payment tokens and booking records to pay minimally for a cheap registration, then apply that valid token to a separate, higher-priced booking - having it marked as fully paid. No public exploit is identified at time of analysis, but CVSS:3.1/AV:N/AC:L/PR:N/UI:N confirms the attack requires no authentication and no user interaction, making it trivially accessible to non-technical threat actors targeting paid event registrations.
Tutor LMS WordPress plugin before 3.9.14 fails to correctly scope enrollment checks when gating access to protected course content, meaning any authenticated subscriber enrolled in at least one course can freely access paid lessons, quizzes, and assignments from courses they never purchased. This breaks the revenue model of any site selling course content through the plugin, as a single free or low-cost enrollment grants lateral access across the entire content library. No public exploit code has been identified at time of analysis, and the issue is not listed in the CISA KEV catalog.
Security Optimizer WordPress plugin versions 1.5.8 through 1.6.4 expose a bypass in its optional IP-based login restriction feature, allowing unauthenticated remote users from non-allowlisted IP addresses to reach the WordPress login form despite administrator-configured access controls. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial network exploitability with no authentication or user interaction required to perform the bypass. No public exploit has been identified at time of analysis and this vulnerability is not listed in CISA KEV; however, sites relying on the IP restriction as a primary login protection layer face elevated credential attack exposure.
Payment logic bypass in the Formidable Forms WordPress plugin before 6.32.1 enables unauthenticated remote attackers to complete PayPal subscription flows without being charged. The plugin fails to properly validate PayPal subscription payment status before marking it complete, allowing attackers to trigger all downstream paid-form actions - including digital content delivery, license key issuance, and membership activation - without a valid transaction. No public exploit or KEV listing exists at time of analysis, but the business logic nature of the flaw and its zero-authentication requirement make it accessible to motivated, non-technical attackers once the code path is understood.
Passster WordPress plugin before 4.3.7 allows any authenticated Contributor or higher to bypass global password protection and read protected content via the WordPress core REST API without supplying the protection password. When global protection is enabled, the plugin enforces its access controls only on direct front-end page requests, leaving the REST API path unrestricted for users holding the edit_posts capability. No public exploit has been identified at time of analysis; the CVSS score of 2.7 reflects realistic low risk, constrained to sites with untrusted registered contributors.
Broken tenant isolation in WSO2 API Manager's Publisher REST APIs lets a privileged user in one tenant reach across tenant boundaries in multi-tenant deployments. Because the APIs do not correctly scope operations to the caller's tenant, an authenticated publisher-level account can enumerate, expose, or modify API metadata belonging to entirely separate tenant environments. No public exploit identified at time of analysis, but the vendor-assigned 9.0 (Critical) score and CVSS scope-change flag reflect the cross-tenant reach of the flaw.
Token invalidation failure in WSO2 products allows authenticated users whose internal roles have been revoked to retain those privileges until their existing tokens naturally expire. The flaw means that administrative role-removal actions have no immediate security effect - a revoked user continues to hold a valid, exploitable credential granting access to resources they are no longer authorized to reach. No public exploit code has been identified at time of analysis, and this is not listed in CISA KEV, but the business impact of failed privilege revocation can be significant in environments where timely access termination is a compliance requirement.
Unauthorized entry disclosure in Statamic CMS exposes restricted content to any authenticated Control Panel user, regardless of their assigned role permissions. Any CP account - even one holding only the 'access cp' permission - can read entry content, custom field values, and unpublished drafts from any collection by querying the navigation pages endpoint. No data can be modified. Vendor-released patches exist for both active branches (5.74.1 and 6.24.0); no public exploit or active exploitation has been identified at time of analysis.
Namespace isolation bypass in Traefik's Kubernetes CRD provider allows a tenant confined by RBAC to a single namespace to bind their own router to a `TraefikService` owned by a different namespace, exposing or rerouting that namespace's backend services - defeating the isolation boundary that `allowCrossNamespace=false` (the default) is meant to enforce. All Traefik v2 releases through 2.11.53, v3.0.0-3.6.24, and v3.7.0-3.7.9 are affected; patches are available at v2.11.54, v3.6.25, and v3.7.10. A proof-of-concept test harness accompanies the advisory confirming the bypass; the vulnerability has not been added to CISA KEV at time of analysis.
Traefik's BasicAuth middleware in versions 3.6.11-3.6.24 and 3.7.0-3.7.9 permits an authenticated low-privilege user to forge arbitrary backend identities via a singleflight key collision race condition. By concatenating their known valid password with a retrieved stored bcrypt hash, an attacker crafts a singleflight deduplication key identical to a legitimate in-flight request's key; the middleware returns the legitimate request's successful authentication result to the attacker's request, then propagates the attacker's chosen unconfigured username to the backend as a trusted identity. A fully working proof-of-concept achieving 25-of-25 successful identity forgeries under default bcrypt cost is publicly available in the GitHub security advisory; no CISA KEV listing has been identified at time of analysis.
Authorization bypass in eScriptorium through version 26.04.1 enables any authenticated remote user to overwrite other users' document parts by supplying arbitrary part primary keys to misconfigured serializer endpoints. The flaw is a Django REST Framework IDOR (CWE-639): queryset access restrictions were applied to the ManyRelatedField wrapper instead of its child_relation, rendering them completely inoperative. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; the integrity impact is high in collaborative archival workflows where document content corruption is irreversible without backup.
Missing authorization in eScriptorium's WebSocket consumer (all versions through 26.04.1) allows any authenticated user to subscribe to arbitrary document event streams without access verification. By supplying a target document's object_cls and object_pk in a join-room WebSocket message, an attacker's connection is added to that document's channel group via group_add with no permission check, exposing real-time segmentation, transcription, import, export, and AI training activity belonging to other users. No public exploit code and no CISA KEV listing have been identified at time of analysis; EPSS data was not provided in the available intelligence.
Unauthenticated broken access control in the Profile Builder WordPress plugin (versions up to and including 3.16.5) allows remote, unauthenticated attackers to perform unauthorized write operations against plugin functionality - bypassing intended access restrictions without any credentials. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) confirms full network exploitability with no prerequisites, though impact is limited to low-severity integrity modifications with no confidentiality or availability consequences. No public exploit code or active exploitation has been identified at time of analysis.
Broken access control in the Dokan WordPress multi-vendor marketplace plugin (all versions through 5.0.10) allows network-accessible exploitation of its custom role permission system, enabling unauthorized integrity-affecting actions. The flaw stems from CWE-862 (Missing Authorization), where the plugin fails to verify whether a requester holds the appropriate capability before executing role-gated operations. No public exploit code or CISA KEV listing exists at time of analysis; CVSS rates this medium severity (5.3), with the original vector asserting no privileges required and no user interaction.
Insecure Direct Object Reference (IDOR) in the Colissimo Officiel WooCommerce shipping plugin (≤2.10.0) enables authenticated low-privileged customers to access shipping or order objects belonging to other users by manipulating controllable object references in plugin requests. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) confirms network-exploitable, low-complexity exploitation limited to authenticated WooCommerce customer accounts, with impact confined to limited confidentiality exposure of delivery data. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Broken access control in the Advanced Custom Fields: Font Awesome Field WordPress plugin (versions up to and including 6.1.1) permits contributor-level authenticated users to perform privileged operations beyond their intended role. The CWE-862 root cause indicates the plugin fails to enforce proper authorization checks before executing certain functionality, allowing lower-privileged users to read data or invoke actions restricted to higher roles. No public exploit code or CISA KEV listing has been identified at time of analysis, but the network-accessible attack vector and low privilege requirement make this exploitable by any user with a contributor account on affected WordPress installations.
Broken access control in the IT-Recht Kanzlei Legal Text Connector WordPress plugin (versions <= 1.0.13) allows unauthenticated remote attackers to perform unauthorized actions against the plugin's endpoints, resulting in low-severity integrity and availability impact. The root cause is CWE-862 (Missing Authorization), meaning the plugin fails to verify that a requestor has permission before executing sensitive operations. No public exploit has been identified at time of analysis and this vulnerability is not listed in the CISA KEV catalog.
CAPTCHA bypass in Element Pack Elementor Addons (WordPress plugin by BDThemes) versions up to and including 8.7.13 allows unauthenticated remote attackers to circumvent CAPTCHA verification on protected forms. Classified under CWE-290 (Authentication Bypass by Spoofing), the flaw enables automated or scripted clients to submit forms without completing the CAPTCHA challenge, undermining bot-protection controls. No public exploit code or active exploitation has been identified at time of analysis; CVSS rates this Medium (5.3) with integrity-only impact.
Broken access control in the SureCart WordPress e-commerce plugin through version 4.6.2 permits unauthenticated remote attackers to access protected resources without credentials or user interaction, as confirmed by the CVSS:3.1/AV:N/AC:L/PR:N/UI:N vector and CWE-862 (Missing Authorization) classification. The impact is scoped to limited confidentiality exposure (C:L/I:N/A:N), consistent with unauthorized read access to restricted data such as order or customer records rather than write or execution capability. No public exploit code has been identified at time of analysis, and the vulnerability does not appear in the CISA KEV catalog, though the zero-friction exploitation conditions mean any unpatched internet-facing SureCart installation is trivially reachable.
CAPTCHA 4WP WordPress plugin (versions up to and including 7.6.0) allows unauthenticated remote attackers to bypass CAPTCHA verification entirely, undermining bot-protection controls on any form the plugin secures. Classified under CWE-290 (Authentication Bypass by Spoofing), the flaw suggests the verification logic can be defeated without completing the human challenge - enabling automated abuse of protected endpoints. The CVSS:3.1/AV:N/AC:L/PR:N/UI:N vector confirms trivially exploitable, zero-prerequisite network access; no public exploit code and no CISA KEV listing are identified at time of analysis.
Unauthenticated IDOR in Mercado Pago payments for WooCommerce plugin (≤8.9.0) exposes order or payment objects to remote attackers without any authentication requirement. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms network-accessible exploitation at low complexity with no credentials needed, resulting in limited confidentiality breach (C:L). No public exploit code or CISA KEV listing has been identified at time of analysis, but the zero-barrier entry point makes enumeration of payment and order references realistic for opportunistic actors targeting WooCommerce storefronts.
Broken access control in Ultimate Store Kit Elementor Addons versions up to and including 3.0.5 allows unauthenticated remote attackers to perform unauthorized read and write operations against WordPress store functionality. The vulnerability stems from missing authorization checks (CWE-862) on one or more plugin endpoints or AJAX actions, enabling bypass of intended access restrictions without any credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, but the zero-barrier entry (PR:N, AC:L) makes opportunistic exploitation straightforward once the specific vulnerable endpoint is identified.
Unauthorized plugin installation in the ThemeGrill Accelerate WordPress theme (versions up to and including 1.5.3) is possible because the enqueue_scripts() function performs no WordPress capability check before triggering ThemeGrill Demo Importer plugin installation. Any user holding at least a Subscriber-level account on the affected site can exploit this to install and activate an additional plugin, expanding the attack surface. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis.
Authorization bypass in the Ad Inserter WordPress plugin (all versions through 2.8.16) allows unauthenticated remote attackers to read ad block contents that administrators have restricted to administrator-only visibility, by invoking the unguarded `ai_ajax` AJAX function. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial unauthenticated network exploitation with no user interaction required. No public exploit has been identified at time of analysis, but two upstream WordPress plugin repository changesets (3583409, 3567905) indicate a fix has been committed.
CatchPulse's named pipe IPC interface exposes internal security functions without adequate caller authentication, enabling a low-privileged local attacker to invoke privileged operations within the endpoint security product. The vulnerability carries a CVSS 3.1 score of 5.2 (Medium) with a scope change component, indicating the attacker can affect the higher-privileged CatchPulse service process from a low-privilege context. No public exploit code or CISA KEV listing exists at time of analysis; impact is bounded by the vendor description to operations that apply more restrictive security policies, limiting the severity.
Apache Polaris incorrectly enforces storage location boundaries during Iceberg table and view registration, enabling an authenticated principal with registration privileges to cause the catalog service to read S3 objects outside the configured allowed storage perimeter. Exploitation depends on a deployment running S3 credential vending where the catalog's underlying credentials can access objects beyond the allowed boundary - a constrained but realistic enterprise configuration. The demonstrated impact is limited to partial confidentiality disclosure of out-of-bounds objects; no unauthorized write or availability impact has been demonstrated, and no public exploit or active exploitation has been identified at time of analysis.
Authentication bypass in WSO2 Identity Server and multiple WSO2 platform products (API Manager, Open Banking AM/IAM/KM, Traffic Manager, Universal Gateway, API Control Plane, Identity Server as Key Manager) lets an attacker skip intermediate multi-factor challenges when the Conditional (Adaptive) Authentication script is configured with a particular multi-step callback/re-execution pattern, resulting in unauthorized takeover of a targeted user account. The flaw stems from the adaptive script failing to enforce completion of all required steps, and carries a high CVSS of 9.4 (C:H/I:H). There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the affected components underpin enterprise SSO/MFA and open-banking IAM, making impact severe where the vulnerable flow exists.
Sensitive information disclosure in WSO2's Carbon Event Publisher Core affects nine WSO2 platform products, including API Manager, Identity Server, and Open Banking components. When an Event Publisher output adapter is misconfigured with extraneous or irrelevant properties, those property values - which may include user credentials or confidential data - are written to the wso2carbon log files without sanitization or masking (CWE-532). A local, high-privileged actor with read access to those log files can extract the inadvertently logged secrets and leverage them for unauthorized access. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Tenant isolation failure in WSO2 Identity Server allows authenticated low-privilege users to disclose personally identifiable information belonging to users in separate tenants. The vulnerability exists specifically when Email OTP, SMS OTP, or Magic Link are configured as first-factor authenticators - authentication requests processed through these flows lack sufficient validation to enforce organizational tenant boundaries, exposing data such as mobile numbers. No public exploit code or CISA KEV listing exists at time of analysis, but the low-complexity, network-accessible attack vector (CVSS PR:L/AV:N/AC:L) makes this a credible insider threat and compromised-account scenario for multi-tenant deployments.
WSO2 Identity Server's implicit-association resolver incorrectly initializes from a secondary user store rather than the primary store when multiple user stores are configured, causing identity confusion during external IDP authentication flows. When the same lookup claim - such as a username or email address - exists in both the primary and a secondary store, an external IDP subject is silently associated with the wrong local account, either denying legitimate users their expected access level or, in adversarially constructed scenarios, potentially hijacking an IDP association intended for a primary-store user. The vulnerability is only triggered when secondary user stores are active, implicit association is enabled, and duplicate claim values exist across stores - deployments not meeting all three conditions are unaffected. No public exploit code has been identified at time of analysis and the issue is not listed in the CISA KEV catalog.
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Avoid WARNING in sva unbind path The Intel IOMMU driver allows SVA on devices even if they do not support PCI/PRI. Commit 39c20c4e83b9 ("iommu/vt-d: Only handle IOPF for SVA when PRI is supported") modified the SVA bind path to allow this configuration by skipping IOPF enablement when PRI is missing. However, it failed to update the unbind path. This creates an imbalance: the unbind path attempts to disable IOPF for a device that never had it enabled, triggering a WARNING in intel_iommu_disable_iopf(): WARNING: drivers/iommu/intel/iommu.c:3475 at intel_iommu_disable_iopf+0x4f/0x90d Call Trace: <TASK> blocking_domain_set_dev_pasid+0x50/0x70 iommu_detach_device_pasid+0x89/0xc0 iommu_sva_unbind_device+0x73/0x150 xe_vm_close_and_put+0x4d2/0x1200 [xe] Fix this by bypassing IOPF operations for SVA domains on non-PRI hardware in both the bind and unbind paths.
Missing authorization in TinyAGI 0.0.20's Message API Endpoint allows remote unauthenticated attackers to invoke the processMessage function without any access control enforcement, yielding limited but real confidentiality, integrity, and availability impact. A publicly available proof-of-concept exploit is referenced in GitHub issue #284, and the project maintainer has not responded to the responsible disclosure, leaving no patch available at time of analysis. The combination of unauthenticated network exploitability, live POC, and vendor silence makes this a material risk for any deployment exposing the endpoint to untrusted networks.
Missing capability check in the SEO Redirection Plugin for WordPress (versions before 9.19) exposes authenticated AJAX endpoints to any logged-in user, regardless of role. A subscriber-level account - the lowest WordPress user tier - can invoke the unprotected action to enumerate all configured 301 redirect rules, revealing source and destination URLs that may disclose internal site architecture, campaign tracking patterns, or sensitive path structures. No public exploitation in the wild has been confirmed by CISA KEV, but a proof-of-concept is publicly available per WPScan, raising the probability of opportunistic abuse against unpatched sites.
Incorrect authorization in openclaw-cn 2026.2.5 allows authenticated remote attackers to bypass the Gateway Exec Approval Flow, circumventing the intended control that governs bash command execution through the agent gateway. The flaw resides in src/agents/bash-tools.exec.ts and is classified as CWE-863 (Incorrect Authorization). No public exploit identified at time of analysis is incorrect here - a proof-of-concept is publicly available via GitHub issue #563, though CISA KEV listing is absent, indicating no confirmed mass exploitation at time of analysis.
ProfileGrid WordPress plugin (all versions before 6.0.0.0) exposes group member lists and member identifiers to unauthenticated visitors due to a handler registered without any authorization checks, completely bypassing the plugin's member-visibility settings for private and closed groups. Any unauthenticated visitor who can reach the WordPress site can enumerate group members and their identifiers across all group types, including those the site owner intended to restrict. A publicly available exploit exists per WPScan, and the SSVC classification flags this as automatable - though EPSS at 0.14% (4th percentile) indicates exploitation has not become widespread despite the low barrier to entry.
Open email relay in the Estatik Real Estate Plugin for WordPress (before 4.3.3) allows unauthenticated remote attackers to send arbitrary emails through any affected WordPress site by submitting crafted property inquiry form requests with controlled recipient address, subject, body, and Reply-To header. The plugin's anti-spam check is trivially bypassed and provides no constraint on recipient routing, effectively turning victim sites into spam or phishing infrastructure. A publicly available exploit exists per WPScan; EPSS sits at 0.14% (3rd percentile) and CISA KEV does not list active exploitation, suggesting limited but plausible abuse given SSVC confirms the attack is automatable.
Improper authorization in cosmicstack-labs mercury-agent's delegate_task tool allows a remotely authenticated low-privilege attacker to invoke SubAgent.run operations beyond their permitted scope in all versions through 1.1.12. No vendor patch has been released - the project was notified via issue report but has not responded. A public proof-of-concept exploit exists (GitHub issue #74), lowering the bar for exploitation in any exposed deployment.
Incorrect authorization in cosmicstack-labs mercury-agent through version 1.1.12 allows remote authenticated attackers to bypass access controls via the bg Command Handler. The flaw (CWE-863) resides in Agent.handleBgCommand within src/core/agent.ts, where a present-but-flawed authorization check can be manipulated to execute unauthorized background commands. A proof-of-concept exploit is publicly available via GitHub issue #73; the vendor has not responded to responsible disclosure and no patch exists at time of analysis.
Improper access control in NousResearch hermes-agent up to 0.16.0 allows low-privileged authenticated users to invoke the Memory Toolset even when it has been explicitly disabled by an operator via the `disabled_toolsets` configuration. The root cause is a missing guard in `init_agent()` within `agent/agent_init.py`, which unconditionally injected the Memory Toolset regardless of operator-level restrictions. A public proof-of-concept exploit exists (GitHub issue #48181), and a vendor patch is available via pull request #46185.
Incorrect authorization in zhayujie CowAgent up to version 2.1.1 allows low-privilege authenticated remote attackers to bypass access controls in the Self-Evolution Review Agent component. The flaw resides in the _select_tools function of agent/evolution/executor.py (CWE-863), where authorization logic is implemented incorrectly, potentially permitting access to tools or agent capabilities outside the caller's intended permission scope. Publicly available exploit code exists (E:P in CVSS 4.0 vector), though active exploitation has not been confirmed by CISA KEV.
Authentication bypass in letta-ai LettaBot 0.2.0 exposes the API Status Route in src/api/server.ts to unauthenticated remote access, allowing any network-reachable attacker to interact with the endpoint without credentials. The root cause is missing authentication enforcement (CWE-287) on what should be a protected API handler, with confidentiality, integrity, and availability each assessed at low impact per the CVSS 4.0 vector. A public proof-of-concept exploit exists (GitHub Gist, corroborated by CVSS 4.0 E:P), and the vendor did not respond to responsible disclosure, leaving no patch available at time of analysis.
Unauthenticated file upload in Rongzhitong Visual Integrated Command and Dispatch Platform (versions through 20260617) allows remote attackers to upload arbitrary files - including web shells - to the server via the /dm/dispatch/userinfo/upload endpoint without any authentication. The 'Authentication Bypass' tag confirms that access controls on this endpoint are entirely absent, not merely weak. A public proof-of-concept exploit exists and is circulating, and the vendor has not responded to disclosure contact, meaning no patch is forthcoming. No public exploit identified as confirmed actively exploited (CISA KEV), but PoC availability and zero remediation response substantially raise real-world risk.
Unauthenticated guild membership enumeration in Spacebar Server (before commit 51da17c) exposes complete member user ID lists for any guild on an instance to any bearer-token holder. The GET /guilds/{guild_id}/roles/{role_id}/member-ids route handler omits the IsInGuildOrFail authorization check present in sibling endpoints, meaning an attacker with any valid account can query membership of guilds they do not belong to. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified; real-world impact is privacy-sensitive membership enumeration enabling targeted social engineering or account correlation.
Write operation bypass in the AWS Labs DocumentDB MCP Server before version 1.0.12 allows an authenticated MCP client to execute unauthorized database writes while the server operates in read-only mode. The aggregation pipeline tool failed to block write-capable stages - specifically $out and $merge - enabling low-privilege MCP clients to modify DocumentDB data in direct violation of the configured read-only policy. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; a vendor-confirmed fix is available in release 2026.04.20260408085348.
External protocol handler bypass in Electron allows sandboxed iframes to launch OS-registered external applications, circumventing iframe sandbox enforcement in all Electron versions below 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3. The root cause is that Electron's HandleExternalProtocolInUI function in electron_browser_client.cc failed to inspect WebSandboxFlags before processing external protocol navigation requests, and critically did not forward the frame's sandbox state to the app's permission handler - so even a custom handler could not make an informed allow/deny decision. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis, but the attack is network-deliverable with no authentication required against apps relying on Electron's default permission configuration.
Firewall rule inheritance bypass in Cisco Terminal Services (TS) Agent allows an authenticated remote attacker to escape their own firewall policy and operate under the network access rules of a different user account. Affected versions span TSAgent-1.0 through TSAgent-1.4.2 per EUVD-2026-53447. No public exploit code has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog, but the low attack complexity and network-accessible vector make it straightforward to attempt for any credentialed user in an affected deployment.
Path validation bypass in Electron's shell.openPath() allows an attacker-controlled file to be opened in place of one that passed string-based extension validation, due to embedded null bytes not being rejected before OS-level path resolution. Electron-based desktop applications that accept untrusted file paths, validate them using only JavaScript string methods (e.g., endsWith(), regex extension checks), and then pass them to shell.openPath() are affected; apps using Node.js fs APIs (fs.existsSync(), fs.stat()) prior to the call are explicitly not vulnerable. Fixed in versions 39.8.6, 40.9.0, 41.1.1, and 42.0.0-beta.1; no public exploit identified at time of analysis.
Session isolation bypass in Electron allows a malicious or compromised Chrome extension loaded into one session to cross session boundaries and access, navigate, and script windows belonging to a completely separate session. Affected are Electron applications prior to versions 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3 that invoke session.loadExtension and rely on multi-session architecture as a security boundary - a narrowly scoped but architecturally significant trust boundary violation. No public exploit code or CISA KEV listing exists at time of analysis; exploitation requires attacker control of an extension the application has explicitly loaded.
Parent process code-sign spoofing in Electron on macOS allows a local low-privileged attacker to bypass fuse-based hardening controls restricting ELECTRON_RUN_AS_NODE and NODE_OPTIONS, injecting code inside the signed Electron application and inheriting its TCC permissions and keychain access. Only macOS deployments of Electron apps that have explicitly enabled same-signed-parent fuse restrictions are exposed; applications without this hardening are unaffected. No public exploit has been identified at time of analysis, and CVSS AC:H reflects the PID-reuse race-condition timing requirement inherent to the attack.
Improper authorization in Apache Answer through version 2.0.1 allows any authenticated user to reject arbitrary pending edit-revisions without holding review permissions. The missing authorization check on the reject operation means content moderation controls are effectively bypassed by ordinary users, enabling disruption of the peer-review workflow. No public exploit code exists and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
Insecure Direct Object Reference (IDOR) in Apache Answer through version 2.0.1 allows any authenticated user to delete uploaded files belonging to other users by supplying arbitrary file URLs to the avatar-cleanup endpoint. The root cause is a missing ownership check in the file-deletion logic (CWE-639), meaning the application accepts a user-controlled file URL and acts on it without verifying the requesting user has authority over that resource. No public exploit has been identified at time of analysis, but the attack requires only a valid account, making it low-friction once an attacker has registered or compromised any user.
Header injection in openshift/oauth-proxy allows unauthenticated network attackers to impersonate arbitrary users on upstream applications by exploiting authentication-bypass paths. When skip-auth-regex rules are configured, the proxy forwards client-controlled identity headers (X-Forwarded-User, X-Forwarded-Email, X-Forwarded-Access-Token) to upstream services without stripping them, enabling forged identity claims. Affecting Red Hat OpenShift Container Platform 4, this vulnerability is classified under CWE-345 (Insufficient Verification of Data Authenticity) with a CVSS 6.5 base score; no public exploit code or CISA KEV listing has been identified at time of analysis.
Missing permission check in a Jenkins plugin (SECURITY-3888) exposes one or more HTTP endpoints to attackers without adequate authorization enforcement. The vulnerability is one of a paired finding alongside CVE-2026-70434 (CSRF), suggesting the same endpoint lacks both CSRF protection and proper access controls. The full description is truncated in the available source data, so the specific plugin and endpoint are not independently confirmed, but fixes are included in the August 5, 2026 Jenkins security advisory. No public exploit is identified at time of analysis.
Missing permission checks in HCL AppScan Plugin 1.8.3 and earlier expose multiple Jenkins HTTP endpoints to any authenticated user holding Overall/Read permission, enabling enumeration of credentials IDs stored in Jenkins. Credential ID disclosure is a stepping-stone attack: while the raw secrets are not returned, knowledge of credential IDs can be combined with a separate vulnerability to capture those credentials. No public exploit or active exploitation has been confirmed. A patched release (1.8.4) is available.
Jenkins 2.575 and LTS 2.568.1 and earlier, along with a broad set of Jenkins plugins, are affected by a batch of security vulnerabilities disclosed in the 2026-08-05 advisory. CVE-2026-70438 is one of the CVEs issued under this advisory batch; based on sequential numbering (the described CVEs run from 70426 through approximately 70435+), it likely corresponds to one of the eleven plugins listed as carrying unresolved security issues without a fix at time of publication - including AWS CodeBuild, CodeSonar, Google Chat Notification, Horreum, Ivy Report, Parameterized Remote Trigger, Qualys Container Scanning Connector, Sauce OnDemand, Summary Display, Violation Comments to GitLab, and XML Job to Job DSL. No public exploit has been identified for CVE-2026-70438 specifically, and it does not appear in CISA KEV. The broader advisory includes critical issues such as a Remoting deserialization filter bypass enabling controller-side code execution from agent processes, path traversal enabling arbitrary file write, and CSRF or missing permission checks across multiple plugins.
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.
CVE-2026-70439 is part of the Jenkins multi-CVE security advisory published August 5, 2026, covering vulnerabilities across Jenkins core and multiple plugins. The advisory batch includes critical issues such as a Remoting deserialization filter bypass enabling controller code execution (CVE-2026-70426), arbitrary file write via crafted tar archives (CVE-2026-70427), and path traversal enabling script deployment (CVE-2026-70428). The specific technical details for CVE-2026-70439 are not present in the available data - the oss-security disclosure is truncated and covers only CVE-2026-70426 through the beginning of CVE-2026-70435 before cutting off. No public exploit or CISA KEV listing is confirmed for CVE-2026-70439 at time of analysis.
CVE-2026-70445 is one of multiple security vulnerabilities disclosed in the Jenkins security advisory published 2026-08-05, affecting Jenkins core and a range of Jenkins plugins. The specific vulnerability details for this CVE ID were not included in the provided input data - the oss-security disclosure text was truncated before reaching the description of CVE-2026-70445, which falls beyond CVE-2026-70435 in the sequential numbering. Based on the advisory structure, this CVE likely pertains to one of the Jenkins plugins listed either as patched (External Workspace Manager, HCL AppScan, Multijob, SCM-Manager, Webhook Secret Credentials Provider) or as containing unresolved issues (AWS CodeBuild, CodeSonar, Google Chat Notification, Horreum, Ivy Report, Parameterized Remote Trigger, Qualys Container Scanning Connector, Sauce OnDemand, Summary Display, Violation Comments to GitLab, XML Job to Job DSL). No public exploit, KEV listing, or EPSS score was provided.
Remote code execution and privilege escalation are the headline risks in this Jenkins advisory covering multiple vulnerabilities in Jenkins core (versions 2.575/LTS 2.568.1 and earlier) and eleven plugins. The most critical flaw (CVE-2026-70426) bypasses the JEP-200 deserialization class filter via a fallback path in the Remoting library, allowing an agent process or a user with Agent/Connect permission to execute arbitrary code on the Jenkins controller. A companion archive-extraction vulnerability (CVE-2026-70427) enables arbitrary file writes to the controller filesystem - including into init.groovy.d or the plugins directory - through crafted tar/tar.gz archives delivered from an agent; no public exploits or CISA KEV listing were identified for any issue in this advisory at time of analysis.
The August 2026 Jenkins security advisory discloses multiple severe vulnerabilities across Jenkins core (2.575/LTS 2.568.1 and earlier) and several plugins, with the most critical being a JEP-200 deserialization class filter bypass (CVE-2026-70426) enabling remote code execution on the Jenkins controller from agent processes, and a symlink-based path traversal in tar archive extraction (CVE-2026-70427) permitting arbitrary file writes that achieve controller RCE via init scripts or plugin deployment. Additional high-severity issues include a second path traversal via file parameter names (CVE-2026-70428), Unicode-based user identity impersonation (CVE-2026-70429), arbitrary type instantiation by privileged users (CVE-2026-70430), and unsandboxed Groovy RCE in the Multijob Plugin (CVE-2026-70431/70432). No active exploitation is confirmed at time of analysis, but the exploitability of agent-to-controller RCE paths in Jenkins is a well-understood and historically targeted vulnerability class warranting immediate remediation.
Remote code execution, arbitrary file write, and privilege escalation vulnerabilities in Jenkins 2.575 and earlier (LTS 2.568.1 and earlier) expose the Jenkins controller to full compromise via agent-initiated attacks. The most critical paths - a JEP-200 deserialization filter bypass (CVE-2026-70426) and a symlink-based arbitrary file write through tar archive handling (CVE-2026-70427) - both allow attacker-controlled agent processes to execute code on the Jenkins controller JVM. Additional vulnerabilities in Multijob, HCL AppScan, and SCM-Manager plugins introduce unauthenticated Groovy RCE, CSRF-triggered code execution, and credential enumeration. No EPSS data or CISA KEV listing is present in available intelligence; no public exploit code is noted at time of analysis.
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.
Authentication bypass in the Newsletters WordPress plugin (all versions before 4.16) allows remote unauthenticated attackers to gain privileged API access via PHP type juggling against a non-strict key comparison. Exploitation is conditional on the plugin's optional API being enabled, but when active, attackers can modify subscriber records and send bulk emails without any credentials. A publicly available proof-of-concept is documented by WPScan; EPSS at 0.19% (9th percentile) suggests limited automated exploitation to date, and no CISA KEV listing has been issued.
Ghostfolio's Stripe checkout callback endpoint unconditionally grants a one-year Premium subscription to any authenticated user who supplies a valid Stripe Checkout Session ID, regardless of whether payment was completed. Versions prior to 3.4.0 retrieve the session object by ID and immediately create a subscription using the session's `client_reference_id` without ever asserting `session.payment_status === 'paid'` or `session.status === 'complete'`. Any registered user of an affected Ghostfolio instance can self-grant Premium access at zero cost, with no public exploit identified at time of analysis but trivial exploitability given the complete description of the missing check.
Authorization bypass in the kata-agent's ttRPC API allows an untrusted host to invoke two mem-agent methods unconditionally, circumventing the OPA/Rego-based AgentPolicy that forms the security boundary in Confidential Containers (CoCo) deployments. Affected are kata-containers versions prior to 4.0.0 when the mem-agent feature is explicitly enabled (disabled by default). The untrusted host can force in-guest memory operations - swap, aggressive eviction, or compaction - causing attacker-controlled availability and performance degradation of the confidential workload; the description explicitly rules out memory disclosure and code execution. No public exploit or CISA KEV listing has been identified at time of analysis, but the bypass is architecturally significant because it violates the CoCo threat model's fundamental assumption that the host is untrusted.
MCP resource and prompt wrappers in HKUDS nanobot 0.2.0 and 0.2.1 bypass operator-defined `enabledTools` access restrictions, allowing MCP servers to register capabilities beyond the intended scope. Operators who configure a specific tool allowlist to restrict what an MCP server can contribute to a nanobot agent find that resources and prompts from that server are registered unconditionally, exposing capabilities that were explicitly intended to be blocked. A public proof-of-concept exploit exists; this CVE is not in the CISA KEV catalog, so confirmed widespread active exploitation is not established.
Adobe Genuine Software Integrity Service on local systems exposes an Incorrect Authorization flaw (CWE-863) enabling any local attacker - without elevated privileges - to bypass the service's integrity-verification controls and obtain unauthorized limited write access to areas the service is designed to protect. All tracked versions of the service are affected per the open-ended CPE range published by Adobe. No public exploit or CISA KEV listing has been identified at time of analysis, and exploitation is constrained to the local environment, reducing mass-exploitation risk while remaining a realistic threat from malware, shared-account misuse, or low-privileged insider scenarios.
L7 intention authorization bypass in HashiCorp Consul Community and Enterprise editions 1.20.1 through 2.0.2 allows an authenticated mesh workload to reach HTTP paths that are explicitly blocked by path-based deny intentions, when the service proxy is configured with a custom public listener. The flaw undermines a core service mesh security control - path-based L7 intentions - without requiring unauthenticated access or elevated privileges beyond mesh workload enrollment. No public exploit code has been identified and this CVE is not listed in CISA KEV; the CVSS 4.2 Medium score accurately reflects the configuration-dependent, authenticated nature of the attack.
Partial arbitrary file read in HashiCorp Consul Community Edition and Enterprise 1.18.21 through 2.0.2 allows a network-accessible, highly-privileged attacker to exfiltrate sensitive credential files from the Consul server host. The flaw is scoped to configurations using the Vault Connect CA provider with JWT or AppRole authentication - a non-default but production-relevant deployment pattern - and requires operator:write permission to exploit. No public exploit or active exploitation has been identified at time of analysis; a vendor-released patch is available in Consul 2.0.3 and corresponding Enterprise builds.
Unauthenticated remote attackers can trigger operator-configured scheduled jobs in Grav CMS when the scheduler-webhook plugin is installed and misconfigured, due to a compound-conditional short-circuit (CWE-303) that skips token validation entirely when no webhookToken is set. The primitive is job-triggering rather than attacker-controlled command injection: RCE is only achievable when an administrator has separately configured a scheduled job that shells out, a condition the attacker cannot influence. No public exploit has been identified at time of analysis, and the vendor-released fix is available in Grav v2.0.9.
Missing authentication in VHF Data Link (VDL) CPDLC (Controller-Pilot Data Link Communications) enables rogue ground stations to inject unauthorized clearance messages into cockpit avionics over radio frequency. Pilots receiving spoofed CPDLC messages may follow misleading ATC instructions - altitude changes, heading redirections, or route modifications - with no indication the messages are inauthentic. This ICS-CERT advisory (ICSA-26-219-01) exposes a systemic protocol-level authentication gap with no public exploit identified at time of analysis.
Stale permission enforcement in Frappe's Document Follow subsystem allows authenticated users whose document access has been revoked or downgraded to continue receiving document-level data via scheduled email notifications. Affecting all Frappe v15 releases prior to 15.112.0 and v16 releases prior to 16.23.0, the flaw arises because notification generation never re-evaluates whether recipients still hold current read permission on subscribed documents at dispatch time. No public exploit code exists and no active exploitation has been confirmed; the vendor-assigned CVSS 4.0 score of 2.3 accurately reflects the narrow exposure window and the prerequisite that access revocation must have already occurred before the notification job fires.
Unrestricted access to the Document Follow API (update_follow) in Frappe framework allows any authenticated user to follow or unfollow arbitrary documents without authorization checks, constituting an Insecure Direct Object Reference (IDOR) flaw classified under CWE-639. Frappe versions prior to 16.20.0 (v16 branch) and 15.112.0 (v15 branch) are affected, enabling authenticated attackers to subscribe to change notifications for documents outside their authorization scope. No public exploit code exists and no active exploitation has been identified at time of analysis.
Field-level permissions bypass in Frappe framework allows authenticated users to read restricted DocType field values via the document follow timeline feature. Frappe deployments on the v16 branch prior to 16.23.0 and the v15 branch prior to 15.112.0 are affected, including ERPNext and other applications built on Frappe. An authenticated low-privileged user can access historical change values for fields protected by Frappe's permlevel system simply by viewing the document follow timeline - no public exploit has been identified and the vulnerability is not listed in CISA KEV.
Tenant isolation bypass in SuperTokens Core v6.0.0 through v11.4.0 enables an authenticated user in one tenant to access sessions, data, and API endpoints belonging to separate tenants on the same instance. The flaw represents a failure of authorization enforcement at the multi-tenancy boundary layer - the core authentication service does not adequately scope API operations to the requesting tenant's namespace. No public exploit code has been identified at time of analysis, but the confidentiality impact is rated high given that cross-tenant session hijacking and user data exfiltration are within scope for a successful attacker.
Unauthenticated log file exposure in the Webbox component of Tobit Laboratories AG TeamDavid allows remote attackers to retrieve sensitive error messages and internal application details without any credentials. All TeamDavid versions through Rollout 524 are affected per CPE cpe:2.3:a:tobit_laboratories_ag:teamdavid:*:*:*:*:*:*:*:*. No public exploit code or active exploitation has been identified; this vulnerability was disclosed as part of a batch of 22 CVEs uncovered by InfoGuard researchers during a systematic security audit of the platform.
Cross-package resource and model poisoning in NLTK's downloader (versions <= 3.9.4) allows an attacker who can influence what packages a user downloads to silently overwrite trusted corpora and model files with adversarial replacements. The root cause is that nltk.downloader extracts archives into shared namespaces (corpora/, taggers/) rather than package-isolated directories, and performs integrity validation only after extraction is complete - a classic TOCTOU-like design flaw. Poisoned resources survive interpreter restarts and propagate silently into ML pipelines, making this particularly dangerous in reproducibility-sensitive or automated NLP workflows. No public exploit code has been identified at time of analysis and this vulnerability is not listed in CISA KEV.
Broken Object Level Authorization in MStore API WordPress plugin (all versions before 4.21.0) exposes every WooCommerce order and associated customer PII to any authenticated WordPress user, including low-privileged Subscribers. The vendor-orders endpoint performs no caller-scoping check, meaning a Subscriber can enumerate the entire store's order history. Publicly available exploit code exists per WPScan, though EPSS at 0.13% (3rd percentile) indicates exploitation has not become widespread at time of analysis; no CISA KEV listing confirms active exploitation.
Unauthenticated cloud credential hijacking in the Templately WordPress plugin (all versions before 3.7.1) allows any remote attacker to overwrite the site administrator's stored cloud service connection with an account under their control. This severs the legitimate administrator's access to the cloud template library and redirects the site's template source to attacker-controlled infrastructure, enabling supply-chain-style content injection against the WordPress admin. A publicly available proof-of-concept exists per WPScan, though EPSS remains very low (0.14%, 3rd percentile), and no CISA KEV listing confirms active widespread exploitation at time of analysis.
Insecure Direct Object Reference (IDOR) in the Subscriptions for WooCommerce WordPress plugin before 2.0.1 allows any authenticated customer to read subscription records belonging to other customers by supplying an arbitrary subscription ID. The plugin fails to enforce ownership checks before returning subscription details - subscribed product, status, and date fields - exposing sensitive order metadata across tenant boundaries. A publicly available proof-of-concept exists per WPScan, but with an EPSS of 0.13% (3rd percentile) and no CISA KEV listing, mass exploitation is not currently observed.
Authorization bypass in the Stream - Activity Log & Audit Trail WordPress plugin (versions through 4.2.0) exposes the full site audit trail to any authenticated user holding a subscriber-level account or higher. The flaw resides in the plugin's Heartbeat API live-update handler, which returns activity records without verifying the requesting user holds the privileges required to view them (CWE-862). No public exploit or CISA KEV listing exists at time of analysis, but the low exploitation bar - any registered user account suffices - makes this a credible insider or low-effort attacker risk on sites with open registration.
Sigstore attestation verification in GitHub CLI prior to 2.97.0 can be defeated when an attacker registers a lookalike repository whose name contains dot characters that function as regex wildcards - for example, github/artifact.attestations-workflows matching a matcher intended solely for github/artifact-attestations-workflows. The `gh attestation verify` command in pkg/cmd/attestation/verify/policy.go constructed Certificate Subject Alternative Name (SAN) matchers by interpolating `--signer-repo` and `--signer-workflow` flag values directly into regex patterns without calling regexp.QuoteMeta(), allowing any dot or other metacharacter in a GitHub-permitted name to act as a wildcard. No public exploit has been identified at time of analysis; the CVSS 4.0 AT:P designator confirms exploitation requires the attacker to first position a valid lookalike repository with legitimate Sigstore attestations, making this a targeted rather than opportunistic threat.
Unauthenticated read access to appointment records in OpenReception appointment-booking-software (versions prior to 1.1.0) exposes scheduling metadata and AES-GCM cryptographic components - including encryptedPayload, iv, authTag, and dataKey - to any caller who possesses a valid appointment UUID. The GET handler at /api/tenants/{id}/appointments/{appointmentId} omits the checkPermission() call that the DELETE handler on the same file correctly enforces, and neither the apiAuthHandle nor authGuard middleware compensates because API paths bypass authGuard entirely and apiAuthHandle does not block unauthenticated requests on non-admin routes. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms zero-friction remote exploitation against any unpatched instance.
Unauthorized booking injection into private channels affects OpenReception appointment-booking-software ≤ 1.0.1 via a missing isPublic authorization check in the new-client booking path. An unauthenticated remote attacker solves a trivial 16-bit proof-of-work challenge, obtains a valid bearer token, and then supplies any private channelId in the create-new-client payload - bypassing the access control that protects the standard appointment path. When chained with companion finding V-10 (unauthenticated schedule endpoint leaking all private channel IDs), the entire attack requires only two unauthenticated HTTP sequences, no public exploit code identified at time of analysis.
Unauthenticated appointment injection in OpenReception appointment-booking-software prior to version 1.0.5 allows any remote caller to insert CONFIRMED appointments into arbitrary client tunnels by exploiting a missing authorization gate on the `add-to-tunnel` endpoint. The endpoint accepted any POST supplying a valid `emailHash` - used only as a tenant existence check - alongside an unrelated valid `tunnelId`, writing attacker-controlled appointment fields (ciphertext content, date, duration, agent) without a session, Authorization header, booking access token, or proof-of-work. No CISA KEV listing or public POC is identified at time of analysis, but the exploit pattern is structurally straightforward once valid identifiers are obtained.
Cross-tenant invite deletion in OpenReception's appointment booking software (prior to 1.0.6) allows an authenticated TENANT_ADMIN to destroy pending onboarding invites belonging to unrelated tenants on the same platform instance. The flaw exists because the invite cleanup query inside `StaffService.deleteStaffMember()` matches only on email address without constraining to the acting tenant's ID, causing any staff deletion to silently cascade-delete matching invites across all tenants. No active exploitation has been identified and no public exploit code exists; the issue is fully remediated in version 1.0.6 via a single ORM predicate addition.
The billing controller in Postiz (postiz-app) before v2.21.10 allows exploitation of an unauthenticated or lightly authenticated API endpoint to activate permanent top-tier paid subscriptions without financial transaction, by forging or replaying lifetime-deal redemption codes against a backend that performs no cryptographic validation or single-use enforcement. The vulnerable `/lifetime` POST endpoint passed user-supplied codes directly into the Stripe-integrated `lifetimeDeal` service with no server-side state verification, a textbook CWE-345 (Insufficient Verification of Data Authenticity) failure. No public exploit has been identified and this CVE is not listed in CISA KEV; the fix in v2.21.10 was complete endpoint removal, confirmed via the upstream GitHub commit.
Authorization bypass in SourceCodester Online Examination & Learning Management System 1.0 exposes student records to unauthorized authenticated users by failing to validate the `class_group` parameter in `view_students.php`. The CVSS 4.0 vector (PR:L) confirms that at least low-privilege authentication is required, limiting the attack surface but still enabling lateral access to student data across class groups the attacker should not be permitted to view. No public exploit code has been identified and the product is not listed in the CISA KEV catalog at time of analysis.
Unrestricted file upload in SourceCodester Online Examination & Learning Management System 1.0 exposes the server to arbitrary file upload via the upload_files.php endpoint, which lacks adequate file type or extension enforcement. The CVSS 4.0 vector indicates low-privilege authentication is required (PR:L) over a network vector with low complexity, and the 'Authentication Bypass' tag raises the possibility that this authentication gate may itself be circumventable. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the attack class is well-understood and trivially weaponizable against affected deployments.
Authorization bypass in SourceCodester Online Examination & Learning Management System 1.0 allows authenticated low-privilege users to access records belonging to other users by manipulating the `id` parameter in the `/view.php` endpoint without proper ownership verification. The CVSS 4.0 vector (PR:L, AV:N, VC:L) confirms the flaw is remotely reachable but requires prior authentication, and impact is limited to confidentiality disclosure of a single record type. No public exploit code and no active exploitation (CISA KEV) have been identified at time of analysis.
Payment authorization token reuse in Events Made Easy WordPress plugin before 3.1.2 enables unauthenticated financial fraud against event organizers. An attacker exploits an absent binding between payment tokens and booking records to pay minimally for a cheap registration, then apply that valid token to a separate, higher-priced booking - having it marked as fully paid. No public exploit is identified at time of analysis, but CVSS:3.1/AV:N/AC:L/PR:N/UI:N confirms the attack requires no authentication and no user interaction, making it trivially accessible to non-technical threat actors targeting paid event registrations.
Tutor LMS WordPress plugin before 3.9.14 fails to correctly scope enrollment checks when gating access to protected course content, meaning any authenticated subscriber enrolled in at least one course can freely access paid lessons, quizzes, and assignments from courses they never purchased. This breaks the revenue model of any site selling course content through the plugin, as a single free or low-cost enrollment grants lateral access across the entire content library. No public exploit code has been identified at time of analysis, and the issue is not listed in the CISA KEV catalog.
Security Optimizer WordPress plugin versions 1.5.8 through 1.6.4 expose a bypass in its optional IP-based login restriction feature, allowing unauthenticated remote users from non-allowlisted IP addresses to reach the WordPress login form despite administrator-configured access controls. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial network exploitability with no authentication or user interaction required to perform the bypass. No public exploit has been identified at time of analysis and this vulnerability is not listed in CISA KEV; however, sites relying on the IP restriction as a primary login protection layer face elevated credential attack exposure.
Payment logic bypass in the Formidable Forms WordPress plugin before 6.32.1 enables unauthenticated remote attackers to complete PayPal subscription flows without being charged. The plugin fails to properly validate PayPal subscription payment status before marking it complete, allowing attackers to trigger all downstream paid-form actions - including digital content delivery, license key issuance, and membership activation - without a valid transaction. No public exploit or KEV listing exists at time of analysis, but the business logic nature of the flaw and its zero-authentication requirement make it accessible to motivated, non-technical attackers once the code path is understood.
Passster WordPress plugin before 4.3.7 allows any authenticated Contributor or higher to bypass global password protection and read protected content via the WordPress core REST API without supplying the protection password. When global protection is enabled, the plugin enforces its access controls only on direct front-end page requests, leaving the REST API path unrestricted for users holding the edit_posts capability. No public exploit has been identified at time of analysis; the CVSS score of 2.7 reflects realistic low risk, constrained to sites with untrusted registered contributors.
Broken tenant isolation in WSO2 API Manager's Publisher REST APIs lets a privileged user in one tenant reach across tenant boundaries in multi-tenant deployments. Because the APIs do not correctly scope operations to the caller's tenant, an authenticated publisher-level account can enumerate, expose, or modify API metadata belonging to entirely separate tenant environments. No public exploit identified at time of analysis, but the vendor-assigned 9.0 (Critical) score and CVSS scope-change flag reflect the cross-tenant reach of the flaw.
Token invalidation failure in WSO2 products allows authenticated users whose internal roles have been revoked to retain those privileges until their existing tokens naturally expire. The flaw means that administrative role-removal actions have no immediate security effect - a revoked user continues to hold a valid, exploitable credential granting access to resources they are no longer authorized to reach. No public exploit code has been identified at time of analysis, and this is not listed in CISA KEV, but the business impact of failed privilege revocation can be significant in environments where timely access termination is a compliance requirement.
Unauthorized entry disclosure in Statamic CMS exposes restricted content to any authenticated Control Panel user, regardless of their assigned role permissions. Any CP account - even one holding only the 'access cp' permission - can read entry content, custom field values, and unpublished drafts from any collection by querying the navigation pages endpoint. No data can be modified. Vendor-released patches exist for both active branches (5.74.1 and 6.24.0); no public exploit or active exploitation has been identified at time of analysis.
Namespace isolation bypass in Traefik's Kubernetes CRD provider allows a tenant confined by RBAC to a single namespace to bind their own router to a `TraefikService` owned by a different namespace, exposing or rerouting that namespace's backend services - defeating the isolation boundary that `allowCrossNamespace=false` (the default) is meant to enforce. All Traefik v2 releases through 2.11.53, v3.0.0-3.6.24, and v3.7.0-3.7.9 are affected; patches are available at v2.11.54, v3.6.25, and v3.7.10. A proof-of-concept test harness accompanies the advisory confirming the bypass; the vulnerability has not been added to CISA KEV at time of analysis.
Traefik's BasicAuth middleware in versions 3.6.11-3.6.24 and 3.7.0-3.7.9 permits an authenticated low-privilege user to forge arbitrary backend identities via a singleflight key collision race condition. By concatenating their known valid password with a retrieved stored bcrypt hash, an attacker crafts a singleflight deduplication key identical to a legitimate in-flight request's key; the middleware returns the legitimate request's successful authentication result to the attacker's request, then propagates the attacker's chosen unconfigured username to the backend as a trusted identity. A fully working proof-of-concept achieving 25-of-25 successful identity forgeries under default bcrypt cost is publicly available in the GitHub security advisory; no CISA KEV listing has been identified at time of analysis.
Authorization bypass in eScriptorium through version 26.04.1 enables any authenticated remote user to overwrite other users' document parts by supplying arbitrary part primary keys to misconfigured serializer endpoints. The flaw is a Django REST Framework IDOR (CWE-639): queryset access restrictions were applied to the ManyRelatedField wrapper instead of its child_relation, rendering them completely inoperative. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; the integrity impact is high in collaborative archival workflows where document content corruption is irreversible without backup.
Missing authorization in eScriptorium's WebSocket consumer (all versions through 26.04.1) allows any authenticated user to subscribe to arbitrary document event streams without access verification. By supplying a target document's object_cls and object_pk in a join-room WebSocket message, an attacker's connection is added to that document's channel group via group_add with no permission check, exposing real-time segmentation, transcription, import, export, and AI training activity belonging to other users. No public exploit code and no CISA KEV listing have been identified at time of analysis; EPSS data was not provided in the available intelligence.
Unauthenticated broken access control in the Profile Builder WordPress plugin (versions up to and including 3.16.5) allows remote, unauthenticated attackers to perform unauthorized write operations against plugin functionality - bypassing intended access restrictions without any credentials. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) confirms full network exploitability with no prerequisites, though impact is limited to low-severity integrity modifications with no confidentiality or availability consequences. No public exploit code or active exploitation has been identified at time of analysis.
Broken access control in the Dokan WordPress multi-vendor marketplace plugin (all versions through 5.0.10) allows network-accessible exploitation of its custom role permission system, enabling unauthorized integrity-affecting actions. The flaw stems from CWE-862 (Missing Authorization), where the plugin fails to verify whether a requester holds the appropriate capability before executing role-gated operations. No public exploit code or CISA KEV listing exists at time of analysis; CVSS rates this medium severity (5.3), with the original vector asserting no privileges required and no user interaction.
Insecure Direct Object Reference (IDOR) in the Colissimo Officiel WooCommerce shipping plugin (≤2.10.0) enables authenticated low-privileged customers to access shipping or order objects belonging to other users by manipulating controllable object references in plugin requests. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) confirms network-exploitable, low-complexity exploitation limited to authenticated WooCommerce customer accounts, with impact confined to limited confidentiality exposure of delivery data. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Broken access control in the Advanced Custom Fields: Font Awesome Field WordPress plugin (versions up to and including 6.1.1) permits contributor-level authenticated users to perform privileged operations beyond their intended role. The CWE-862 root cause indicates the plugin fails to enforce proper authorization checks before executing certain functionality, allowing lower-privileged users to read data or invoke actions restricted to higher roles. No public exploit code or CISA KEV listing has been identified at time of analysis, but the network-accessible attack vector and low privilege requirement make this exploitable by any user with a contributor account on affected WordPress installations.
Broken access control in the IT-Recht Kanzlei Legal Text Connector WordPress plugin (versions <= 1.0.13) allows unauthenticated remote attackers to perform unauthorized actions against the plugin's endpoints, resulting in low-severity integrity and availability impact. The root cause is CWE-862 (Missing Authorization), meaning the plugin fails to verify that a requestor has permission before executing sensitive operations. No public exploit has been identified at time of analysis and this vulnerability is not listed in the CISA KEV catalog.
CAPTCHA bypass in Element Pack Elementor Addons (WordPress plugin by BDThemes) versions up to and including 8.7.13 allows unauthenticated remote attackers to circumvent CAPTCHA verification on protected forms. Classified under CWE-290 (Authentication Bypass by Spoofing), the flaw enables automated or scripted clients to submit forms without completing the CAPTCHA challenge, undermining bot-protection controls. No public exploit code or active exploitation has been identified at time of analysis; CVSS rates this Medium (5.3) with integrity-only impact.
Broken access control in the SureCart WordPress e-commerce plugin through version 4.6.2 permits unauthenticated remote attackers to access protected resources without credentials or user interaction, as confirmed by the CVSS:3.1/AV:N/AC:L/PR:N/UI:N vector and CWE-862 (Missing Authorization) classification. The impact is scoped to limited confidentiality exposure (C:L/I:N/A:N), consistent with unauthorized read access to restricted data such as order or customer records rather than write or execution capability. No public exploit code has been identified at time of analysis, and the vulnerability does not appear in the CISA KEV catalog, though the zero-friction exploitation conditions mean any unpatched internet-facing SureCart installation is trivially reachable.
CAPTCHA 4WP WordPress plugin (versions up to and including 7.6.0) allows unauthenticated remote attackers to bypass CAPTCHA verification entirely, undermining bot-protection controls on any form the plugin secures. Classified under CWE-290 (Authentication Bypass by Spoofing), the flaw suggests the verification logic can be defeated without completing the human challenge - enabling automated abuse of protected endpoints. The CVSS:3.1/AV:N/AC:L/PR:N/UI:N vector confirms trivially exploitable, zero-prerequisite network access; no public exploit code and no CISA KEV listing are identified at time of analysis.
Unauthenticated IDOR in Mercado Pago payments for WooCommerce plugin (≤8.9.0) exposes order or payment objects to remote attackers without any authentication requirement. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms network-accessible exploitation at low complexity with no credentials needed, resulting in limited confidentiality breach (C:L). No public exploit code or CISA KEV listing has been identified at time of analysis, but the zero-barrier entry point makes enumeration of payment and order references realistic for opportunistic actors targeting WooCommerce storefronts.
Broken access control in Ultimate Store Kit Elementor Addons versions up to and including 3.0.5 allows unauthenticated remote attackers to perform unauthorized read and write operations against WordPress store functionality. The vulnerability stems from missing authorization checks (CWE-862) on one or more plugin endpoints or AJAX actions, enabling bypass of intended access restrictions without any credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, but the zero-barrier entry (PR:N, AC:L) makes opportunistic exploitation straightforward once the specific vulnerable endpoint is identified.
Unauthorized plugin installation in the ThemeGrill Accelerate WordPress theme (versions up to and including 1.5.3) is possible because the enqueue_scripts() function performs no WordPress capability check before triggering ThemeGrill Demo Importer plugin installation. Any user holding at least a Subscriber-level account on the affected site can exploit this to install and activate an additional plugin, expanding the attack surface. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis.
Authorization bypass in the Ad Inserter WordPress plugin (all versions through 2.8.16) allows unauthenticated remote attackers to read ad block contents that administrators have restricted to administrator-only visibility, by invoking the unguarded `ai_ajax` AJAX function. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms trivial unauthenticated network exploitation with no user interaction required. No public exploit has been identified at time of analysis, but two upstream WordPress plugin repository changesets (3583409, 3567905) indicate a fix has been committed.
CatchPulse's named pipe IPC interface exposes internal security functions without adequate caller authentication, enabling a low-privileged local attacker to invoke privileged operations within the endpoint security product. The vulnerability carries a CVSS 3.1 score of 5.2 (Medium) with a scope change component, indicating the attacker can affect the higher-privileged CatchPulse service process from a low-privilege context. No public exploit code or CISA KEV listing exists at time of analysis; impact is bounded by the vendor description to operations that apply more restrictive security policies, limiting the severity.
Apache Polaris incorrectly enforces storage location boundaries during Iceberg table and view registration, enabling an authenticated principal with registration privileges to cause the catalog service to read S3 objects outside the configured allowed storage perimeter. Exploitation depends on a deployment running S3 credential vending where the catalog's underlying credentials can access objects beyond the allowed boundary - a constrained but realistic enterprise configuration. The demonstrated impact is limited to partial confidentiality disclosure of out-of-bounds objects; no unauthorized write or availability impact has been demonstrated, and no public exploit or active exploitation has been identified at time of analysis.
Authentication bypass in WSO2 Identity Server and multiple WSO2 platform products (API Manager, Open Banking AM/IAM/KM, Traffic Manager, Universal Gateway, API Control Plane, Identity Server as Key Manager) lets an attacker skip intermediate multi-factor challenges when the Conditional (Adaptive) Authentication script is configured with a particular multi-step callback/re-execution pattern, resulting in unauthorized takeover of a targeted user account. The flaw stems from the adaptive script failing to enforce completion of all required steps, and carries a high CVSS of 9.4 (C:H/I:H). There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the affected components underpin enterprise SSO/MFA and open-banking IAM, making impact severe where the vulnerable flow exists.
Sensitive information disclosure in WSO2's Carbon Event Publisher Core affects nine WSO2 platform products, including API Manager, Identity Server, and Open Banking components. When an Event Publisher output adapter is misconfigured with extraneous or irrelevant properties, those property values - which may include user credentials or confidential data - are written to the wso2carbon log files without sanitization or masking (CWE-532). A local, high-privileged actor with read access to those log files can extract the inadvertently logged secrets and leverage them for unauthorized access. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Tenant isolation failure in WSO2 Identity Server allows authenticated low-privilege users to disclose personally identifiable information belonging to users in separate tenants. The vulnerability exists specifically when Email OTP, SMS OTP, or Magic Link are configured as first-factor authenticators - authentication requests processed through these flows lack sufficient validation to enforce organizational tenant boundaries, exposing data such as mobile numbers. No public exploit code or CISA KEV listing exists at time of analysis, but the low-complexity, network-accessible attack vector (CVSS PR:L/AV:N/AC:L) makes this a credible insider threat and compromised-account scenario for multi-tenant deployments.
WSO2 Identity Server's implicit-association resolver incorrectly initializes from a secondary user store rather than the primary store when multiple user stores are configured, causing identity confusion during external IDP authentication flows. When the same lookup claim - such as a username or email address - exists in both the primary and a secondary store, an external IDP subject is silently associated with the wrong local account, either denying legitimate users their expected access level or, in adversarially constructed scenarios, potentially hijacking an IDP association intended for a primary-store user. The vulnerability is only triggered when secondary user stores are active, implicit association is enabled, and duplicate claim values exist across stores - deployments not meeting all three conditions are unaffected. No public exploit code has been identified at time of analysis and the issue is not listed in the CISA KEV catalog.
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Avoid WARNING in sva unbind path The Intel IOMMU driver allows SVA on devices even if they do not support PCI/PRI. Commit 39c20c4e83b9 ("iommu/vt-d: Only handle IOPF for SVA when PRI is supported") modified the SVA bind path to allow this configuration by skipping IOPF enablement when PRI is missing. However, it failed to update the unbind path. This creates an imbalance: the unbind path attempts to disable IOPF for a device that never had it enabled, triggering a WARNING in intel_iommu_disable_iopf(): WARNING: drivers/iommu/intel/iommu.c:3475 at intel_iommu_disable_iopf+0x4f/0x90d Call Trace: <TASK> blocking_domain_set_dev_pasid+0x50/0x70 iommu_detach_device_pasid+0x89/0xc0 iommu_sva_unbind_device+0x73/0x150 xe_vm_close_and_put+0x4d2/0x1200 [xe] Fix this by bypassing IOPF operations for SVA domains on non-PRI hardware in both the bind and unbind paths.
Missing authorization in TinyAGI 0.0.20's Message API Endpoint allows remote unauthenticated attackers to invoke the processMessage function without any access control enforcement, yielding limited but real confidentiality, integrity, and availability impact. A publicly available proof-of-concept exploit is referenced in GitHub issue #284, and the project maintainer has not responded to the responsible disclosure, leaving no patch available at time of analysis. The combination of unauthenticated network exploitability, live POC, and vendor silence makes this a material risk for any deployment exposing the endpoint to untrusted networks.
Missing capability check in the SEO Redirection Plugin for WordPress (versions before 9.19) exposes authenticated AJAX endpoints to any logged-in user, regardless of role. A subscriber-level account - the lowest WordPress user tier - can invoke the unprotected action to enumerate all configured 301 redirect rules, revealing source and destination URLs that may disclose internal site architecture, campaign tracking patterns, or sensitive path structures. No public exploitation in the wild has been confirmed by CISA KEV, but a proof-of-concept is publicly available per WPScan, raising the probability of opportunistic abuse against unpatched sites.
Incorrect authorization in openclaw-cn 2026.2.5 allows authenticated remote attackers to bypass the Gateway Exec Approval Flow, circumventing the intended control that governs bash command execution through the agent gateway. The flaw resides in src/agents/bash-tools.exec.ts and is classified as CWE-863 (Incorrect Authorization). No public exploit identified at time of analysis is incorrect here - a proof-of-concept is publicly available via GitHub issue #563, though CISA KEV listing is absent, indicating no confirmed mass exploitation at time of analysis.
ProfileGrid WordPress plugin (all versions before 6.0.0.0) exposes group member lists and member identifiers to unauthenticated visitors due to a handler registered without any authorization checks, completely bypassing the plugin's member-visibility settings for private and closed groups. Any unauthenticated visitor who can reach the WordPress site can enumerate group members and their identifiers across all group types, including those the site owner intended to restrict. A publicly available exploit exists per WPScan, and the SSVC classification flags this as automatable - though EPSS at 0.14% (4th percentile) indicates exploitation has not become widespread despite the low barrier to entry.
Open email relay in the Estatik Real Estate Plugin for WordPress (before 4.3.3) allows unauthenticated remote attackers to send arbitrary emails through any affected WordPress site by submitting crafted property inquiry form requests with controlled recipient address, subject, body, and Reply-To header. The plugin's anti-spam check is trivially bypassed and provides no constraint on recipient routing, effectively turning victim sites into spam or phishing infrastructure. A publicly available exploit exists per WPScan; EPSS sits at 0.14% (3rd percentile) and CISA KEV does not list active exploitation, suggesting limited but plausible abuse given SSVC confirms the attack is automatable.
Improper authorization in cosmicstack-labs mercury-agent's delegate_task tool allows a remotely authenticated low-privilege attacker to invoke SubAgent.run operations beyond their permitted scope in all versions through 1.1.12. No vendor patch has been released - the project was notified via issue report but has not responded. A public proof-of-concept exploit exists (GitHub issue #74), lowering the bar for exploitation in any exposed deployment.
Incorrect authorization in cosmicstack-labs mercury-agent through version 1.1.12 allows remote authenticated attackers to bypass access controls via the bg Command Handler. The flaw (CWE-863) resides in Agent.handleBgCommand within src/core/agent.ts, where a present-but-flawed authorization check can be manipulated to execute unauthorized background commands. A proof-of-concept exploit is publicly available via GitHub issue #73; the vendor has not responded to responsible disclosure and no patch exists at time of analysis.
Improper access control in NousResearch hermes-agent up to 0.16.0 allows low-privileged authenticated users to invoke the Memory Toolset even when it has been explicitly disabled by an operator via the `disabled_toolsets` configuration. The root cause is a missing guard in `init_agent()` within `agent/agent_init.py`, which unconditionally injected the Memory Toolset regardless of operator-level restrictions. A public proof-of-concept exploit exists (GitHub issue #48181), and a vendor patch is available via pull request #46185.
Incorrect authorization in zhayujie CowAgent up to version 2.1.1 allows low-privilege authenticated remote attackers to bypass access controls in the Self-Evolution Review Agent component. The flaw resides in the _select_tools function of agent/evolution/executor.py (CWE-863), where authorization logic is implemented incorrectly, potentially permitting access to tools or agent capabilities outside the caller's intended permission scope. Publicly available exploit code exists (E:P in CVSS 4.0 vector), though active exploitation has not been confirmed by CISA KEV.
Authentication bypass in letta-ai LettaBot 0.2.0 exposes the API Status Route in src/api/server.ts to unauthenticated remote access, allowing any network-reachable attacker to interact with the endpoint without credentials. The root cause is missing authentication enforcement (CWE-287) on what should be a protected API handler, with confidentiality, integrity, and availability each assessed at low impact per the CVSS 4.0 vector. A public proof-of-concept exploit exists (GitHub Gist, corroborated by CVSS 4.0 E:P), and the vendor did not respond to responsible disclosure, leaving no patch available at time of analysis.
Unauthenticated file upload in Rongzhitong Visual Integrated Command and Dispatch Platform (versions through 20260617) allows remote attackers to upload arbitrary files - including web shells - to the server via the /dm/dispatch/userinfo/upload endpoint without any authentication. The 'Authentication Bypass' tag confirms that access controls on this endpoint are entirely absent, not merely weak. A public proof-of-concept exploit exists and is circulating, and the vendor has not responded to disclosure contact, meaning no patch is forthcoming. No public exploit identified as confirmed actively exploited (CISA KEV), but PoC availability and zero remediation response substantially raise real-world risk.
Unauthenticated guild membership enumeration in Spacebar Server (before commit 51da17c) exposes complete member user ID lists for any guild on an instance to any bearer-token holder. The GET /guilds/{guild_id}/roles/{role_id}/member-ids route handler omits the IsInGuildOrFail authorization check present in sibling endpoints, meaning an attacker with any valid account can query membership of guilds they do not belong to. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified; real-world impact is privacy-sensitive membership enumeration enabling targeted social engineering or account correlation.
Write operation bypass in the AWS Labs DocumentDB MCP Server before version 1.0.12 allows an authenticated MCP client to execute unauthorized database writes while the server operates in read-only mode. The aggregation pipeline tool failed to block write-capable stages - specifically $out and $merge - enabling low-privilege MCP clients to modify DocumentDB data in direct violation of the configured read-only policy. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; a vendor-confirmed fix is available in release 2026.04.20260408085348.
External protocol handler bypass in Electron allows sandboxed iframes to launch OS-registered external applications, circumventing iframe sandbox enforcement in all Electron versions below 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3. The root cause is that Electron's HandleExternalProtocolInUI function in electron_browser_client.cc failed to inspect WebSandboxFlags before processing external protocol navigation requests, and critically did not forward the frame's sandbox state to the app's permission handler - so even a custom handler could not make an informed allow/deny decision. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis, but the attack is network-deliverable with no authentication required against apps relying on Electron's default permission configuration.
Firewall rule inheritance bypass in Cisco Terminal Services (TS) Agent allows an authenticated remote attacker to escape their own firewall policy and operate under the network access rules of a different user account. Affected versions span TSAgent-1.0 through TSAgent-1.4.2 per EUVD-2026-53447. No public exploit code has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog, but the low attack complexity and network-accessible vector make it straightforward to attempt for any credentialed user in an affected deployment.
Path validation bypass in Electron's shell.openPath() allows an attacker-controlled file to be opened in place of one that passed string-based extension validation, due to embedded null bytes not being rejected before OS-level path resolution. Electron-based desktop applications that accept untrusted file paths, validate them using only JavaScript string methods (e.g., endsWith(), regex extension checks), and then pass them to shell.openPath() are affected; apps using Node.js fs APIs (fs.existsSync(), fs.stat()) prior to the call are explicitly not vulnerable. Fixed in versions 39.8.6, 40.9.0, 41.1.1, and 42.0.0-beta.1; no public exploit identified at time of analysis.
Session isolation bypass in Electron allows a malicious or compromised Chrome extension loaded into one session to cross session boundaries and access, navigate, and script windows belonging to a completely separate session. Affected are Electron applications prior to versions 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3 that invoke session.loadExtension and rely on multi-session architecture as a security boundary - a narrowly scoped but architecturally significant trust boundary violation. No public exploit code or CISA KEV listing exists at time of analysis; exploitation requires attacker control of an extension the application has explicitly loaded.
Parent process code-sign spoofing in Electron on macOS allows a local low-privileged attacker to bypass fuse-based hardening controls restricting ELECTRON_RUN_AS_NODE and NODE_OPTIONS, injecting code inside the signed Electron application and inheriting its TCC permissions and keychain access. Only macOS deployments of Electron apps that have explicitly enabled same-signed-parent fuse restrictions are exposed; applications without this hardening are unaffected. No public exploit has been identified at time of analysis, and CVSS AC:H reflects the PID-reuse race-condition timing requirement inherent to the attack.
Improper authorization in Apache Answer through version 2.0.1 allows any authenticated user to reject arbitrary pending edit-revisions without holding review permissions. The missing authorization check on the reject operation means content moderation controls are effectively bypassed by ordinary users, enabling disruption of the peer-review workflow. No public exploit code exists and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
Insecure Direct Object Reference (IDOR) in Apache Answer through version 2.0.1 allows any authenticated user to delete uploaded files belonging to other users by supplying arbitrary file URLs to the avatar-cleanup endpoint. The root cause is a missing ownership check in the file-deletion logic (CWE-639), meaning the application accepts a user-controlled file URL and acts on it without verifying the requesting user has authority over that resource. No public exploit has been identified at time of analysis, but the attack requires only a valid account, making it low-friction once an attacker has registered or compromised any user.
Header injection in openshift/oauth-proxy allows unauthenticated network attackers to impersonate arbitrary users on upstream applications by exploiting authentication-bypass paths. When skip-auth-regex rules are configured, the proxy forwards client-controlled identity headers (X-Forwarded-User, X-Forwarded-Email, X-Forwarded-Access-Token) to upstream services without stripping them, enabling forged identity claims. Affecting Red Hat OpenShift Container Platform 4, this vulnerability is classified under CWE-345 (Insufficient Verification of Data Authenticity) with a CVSS 6.5 base score; no public exploit code or CISA KEV listing has been identified at time of analysis.
Missing permission check in a Jenkins plugin (SECURITY-3888) exposes one or more HTTP endpoints to attackers without adequate authorization enforcement. The vulnerability is one of a paired finding alongside CVE-2026-70434 (CSRF), suggesting the same endpoint lacks both CSRF protection and proper access controls. The full description is truncated in the available source data, so the specific plugin and endpoint are not independently confirmed, but fixes are included in the August 5, 2026 Jenkins security advisory. No public exploit is identified at time of analysis.
Missing permission checks in HCL AppScan Plugin 1.8.3 and earlier expose multiple Jenkins HTTP endpoints to any authenticated user holding Overall/Read permission, enabling enumeration of credentials IDs stored in Jenkins. Credential ID disclosure is a stepping-stone attack: while the raw secrets are not returned, knowledge of credential IDs can be combined with a separate vulnerability to capture those credentials. No public exploit or active exploitation has been confirmed. A patched release (1.8.4) is available.
Jenkins 2.575 and LTS 2.568.1 and earlier, along with a broad set of Jenkins plugins, are affected by a batch of security vulnerabilities disclosed in the 2026-08-05 advisory. CVE-2026-70438 is one of the CVEs issued under this advisory batch; based on sequential numbering (the described CVEs run from 70426 through approximately 70435+), it likely corresponds to one of the eleven plugins listed as carrying unresolved security issues without a fix at time of publication - including AWS CodeBuild, CodeSonar, Google Chat Notification, Horreum, Ivy Report, Parameterized Remote Trigger, Qualys Container Scanning Connector, Sauce OnDemand, Summary Display, Violation Comments to GitLab, and XML Job to Job DSL. No public exploit has been identified for CVE-2026-70438 specifically, and it does not appear in CISA KEV. The broader advisory includes critical issues such as a Remoting deserialization filter bypass enabling controller-side code execution from agent processes, path traversal enabling arbitrary file write, and CSRF or missing permission checks across multiple plugins.
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.
CVE-2026-70439 is part of the Jenkins multi-CVE security advisory published August 5, 2026, covering vulnerabilities across Jenkins core and multiple plugins. The advisory batch includes critical issues such as a Remoting deserialization filter bypass enabling controller code execution (CVE-2026-70426), arbitrary file write via crafted tar archives (CVE-2026-70427), and path traversal enabling script deployment (CVE-2026-70428). The specific technical details for CVE-2026-70439 are not present in the available data - the oss-security disclosure is truncated and covers only CVE-2026-70426 through the beginning of CVE-2026-70435 before cutting off. No public exploit or CISA KEV listing is confirmed for CVE-2026-70439 at time of analysis.
CVE-2026-70445 is one of multiple security vulnerabilities disclosed in the Jenkins security advisory published 2026-08-05, affecting Jenkins core and a range of Jenkins plugins. The specific vulnerability details for this CVE ID were not included in the provided input data - the oss-security disclosure text was truncated before reaching the description of CVE-2026-70445, which falls beyond CVE-2026-70435 in the sequential numbering. Based on the advisory structure, this CVE likely pertains to one of the Jenkins plugins listed either as patched (External Workspace Manager, HCL AppScan, Multijob, SCM-Manager, Webhook Secret Credentials Provider) or as containing unresolved issues (AWS CodeBuild, CodeSonar, Google Chat Notification, Horreum, Ivy Report, Parameterized Remote Trigger, Qualys Container Scanning Connector, Sauce OnDemand, Summary Display, Violation Comments to GitLab, XML Job to Job DSL). No public exploit, KEV listing, or EPSS score was provided.
Remote code execution and privilege escalation are the headline risks in this Jenkins advisory covering multiple vulnerabilities in Jenkins core (versions 2.575/LTS 2.568.1 and earlier) and eleven plugins. The most critical flaw (CVE-2026-70426) bypasses the JEP-200 deserialization class filter via a fallback path in the Remoting library, allowing an agent process or a user with Agent/Connect permission to execute arbitrary code on the Jenkins controller. A companion archive-extraction vulnerability (CVE-2026-70427) enables arbitrary file writes to the controller filesystem - including into init.groovy.d or the plugins directory - through crafted tar/tar.gz archives delivered from an agent; no public exploits or CISA KEV listing were identified for any issue in this advisory at time of analysis.
The August 2026 Jenkins security advisory discloses multiple severe vulnerabilities across Jenkins core (2.575/LTS 2.568.1 and earlier) and several plugins, with the most critical being a JEP-200 deserialization class filter bypass (CVE-2026-70426) enabling remote code execution on the Jenkins controller from agent processes, and a symlink-based path traversal in tar archive extraction (CVE-2026-70427) permitting arbitrary file writes that achieve controller RCE via init scripts or plugin deployment. Additional high-severity issues include a second path traversal via file parameter names (CVE-2026-70428), Unicode-based user identity impersonation (CVE-2026-70429), arbitrary type instantiation by privileged users (CVE-2026-70430), and unsandboxed Groovy RCE in the Multijob Plugin (CVE-2026-70431/70432). No active exploitation is confirmed at time of analysis, but the exploitability of agent-to-controller RCE paths in Jenkins is a well-understood and historically targeted vulnerability class warranting immediate remediation.
Remote code execution, arbitrary file write, and privilege escalation vulnerabilities in Jenkins 2.575 and earlier (LTS 2.568.1 and earlier) expose the Jenkins controller to full compromise via agent-initiated attacks. The most critical paths - a JEP-200 deserialization filter bypass (CVE-2026-70426) and a symlink-based arbitrary file write through tar archive handling (CVE-2026-70427) - both allow attacker-controlled agent processes to execute code on the Jenkins controller JVM. Additional vulnerabilities in Multijob, HCL AppScan, and SCM-Manager plugins introduce unauthenticated Groovy RCE, CSRF-triggered code execution, and credential enumeration. No EPSS data or CISA KEV listing is present in available intelligence; no public exploit code is noted at time of analysis.
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.