Authentication Bypass
Monthly
Authentication bypass in SiYuan's publish layer exposes password-protected attribute view data to unauthenticated remote users across all versions before v3.7.4. The FilterViewByPublishAccess filter omits its password enforcement on the renderAttributeView code path, allowing arbitrary callers to retrieve structured database rows - including document titles, block IDs, and column values - from documents the owner intended to gate with a publish password. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis; vendor patch is available at v3.7.4.
Unauthorized information disclosure in SiYuan exposes protected document metadata and content snippets via three unenforced API endpoints - getBlockBreadcrumb, getRefText, and getBlockTreeInfos - in all versions before v3.7.4. Unauthenticated network actors or low-privilege RoleReader accounts can bypass publish-access controls on documents explicitly marked as publish-forbidden or password-protected, retrieving titles, ancestor block content snippets, reference text, and path metadata by supplying block IDs. No public exploit has been identified at time of analysis; vendor patch is available in v3.7.4.
Unauthenticated information disclosure in SiYuan versions before 3.7.4 allows retrieval of block attributes - names, aliases, memos, and custom fields - from documents protected by publish-access controls. The `getBlockAttrs` and `batchGetBlockAttrs` API endpoints accept POST requests with block IDs without verifying the caller's authorization against the parent document's access policy, directly bypassing the publish-access restriction (CWE-862). No active exploitation has been confirmed and no public proof-of-concept has been identified; impact is bounded to metadata exposure rather than full document content, but the unauthenticated network vector warrants prompt patching for internet-exposed instances.
Information disclosure in SiYuan before v3.7.4 allows unauthenticated remote attackers to retrieve the server's absolute filesystem workspace path, operating-system username, and installation layout by querying the resolveAssetPath endpoint with relative asset paths harvested from published documents. The endpoint enforces only a lightweight CheckAuth gate rather than full authentication, satisfying CWE-639's authorization bypass pattern, and returns raw absolute paths to any network-reachable caller. Vendor patch v3.7.4 has been released; no active exploitation has been confirmed and no public proof-of-concept code has been identified at time of analysis.
Missing authorization controls on three internal API endpoints in SiYuan before v3.7.4 allow callers operating within the publish context to retrieve database column schemas, template expressions, select vocabularies, and workspace-wide block identifiers that were never intended to cross publish access boundaries. The affected endpoints - getAttributeViewKeysByID, getBlockDefIDsByRefText, and getBlockRelevantIDs - perform their operations without consulting publish-scoped permission checks, constituting a CWE-862 (Missing Authorization) flaw. A vendor patch is available at v3.7.4, no public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Five path-resolution API endpoints in SiYuan's publish mode fail to enforce access controls, allowing unauthenticated or minimally-authenticated readers to enumerate the complete private document tree. Affected versions are all SiYuan releases up to and including v3.7.2; v3.7.4 contains the fix. An attacker targeting a SiYuan instance running in publish mode with Publish.Auth.Enable set to false can call getFullHPathByID, getHPathByID, getPathByID, getIDsByHPath, and getHPathByPath without any credentials to recover notebook names, folder hierarchies, document titles, and document IDs - including for content explicitly marked hidden, password-protected, or publish-forbidden. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Unauthenticated information disclosure in SiYuan before v3.7.4 exposes encrypted notebook identifiers, names, and memory-resident unlock states via the getEncryptedNotebookStatus API endpoint without enforcing publish-access filtering. Any anonymous or publish-mode client that can reach the instance can enumerate the full list of encrypted notebooks and determine which are actively decrypted in server memory, leaking sensitive organizational metadata. No public exploit has been identified and no CISA KEV listing exists; a vendor-released patch is available in v3.7.4.
Static-route access control bypass in SiYuan before v3.7.4 allows attackers to read sensitive workspace data by directly accessing file-serving routes that skip the authorization checks enforced on the REST API. Affected deployments include any SiYuan instance operating in disabled-auth mode (anonymous access) or where publish reader tokens have been issued, as those token holders can reach templates, snippets, and export artifacts without restriction. No public exploit or active exploitation has been identified at time of analysis, but the patch to v3.7.4 is available and should be applied promptly given the unauthenticated attack vector in disabled-auth configurations.
SiYuan's /api/tag/getTag endpoint leaks tag labels and occurrence counts from password-protected documents to any unauthenticated network caller, constituting an authorization bypass under CWE-863. All SiYuan versions before 3.7.4 are affected, as confirmed by a vendor GitHub Security Advisory (GHSA-mp7r-57w4-5qm3) and the EUVD entry EUVD-2026-57452. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog; however, the zero-friction network exploitability (PR:N, AC:L, UI:N) means any attacker with network reach can enumerate protected document vocabulary with a single API call.
Information disclosure in SiYuan v3.7.4-alpha.1 (pre-release only) permits any caller who passes basic authentication to retrieve complete database view metadata - including view names, icons, layout types, and per-field Hidden flags - for arbitrary database blocks by supplying an avID, regardless of their access level. The `/api/av/getAttributeViewFieldViews` endpoint introduced in commit acfc02ee8 applies `CheckAuth` middleware but omits any ownership or publish-access filter, producing a CWE-862 Missing Authorization condition. The vulnerability was corrected in the v3.7.4 stable release; no public exploit or active exploitation has been identified at time of analysis.
Unauthenticated information disclosure in SiYuan before v3.7.4 exposes notebook metadata - including names, document counts, storage sizes, and timestamps - for closed and non-published notebooks via the /api/notebook/getNotebookInfo endpoint, which performs no authorization check. Any attacker with network access to the SiYuan API can enumerate structural information that the application's access control model explicitly intends to hide from readers. No public exploit or CISA KEV listing has been identified at time of analysis, but the zero-friction, unauthenticated attack path makes this trivially exploitable wherever the API is internet- or network-exposed.
Information disclosure in SiYuan before v3.7.4 exposes administrator workspace state to unauthenticated network attackers via an improperly protected getConf API endpoint. The UILayout filter fails to enforce authorization boundaries between publish readers and the administrative configuration layer, leaking open document names, recent search terms, notebook directory paths, and private asset locations. No public exploit code or CISA KEV listing exists at time of analysis; however, the unauthenticated network vector makes the flaw trivially reachable on any internet-exposed SiYuan instance with publish features active.
Unauthorized disclosure of external status check configuration in GitLab Enterprise Edition allows any authenticated user holding a developer-role to read merge request API data that should be restricted to higher-privileged roles (maintainer or owner), due to a missing authorization check on the affected endpoint. Versions spanning 16.0 through 19.2.x are affected across a wide installation base. A publicly available proof-of-concept was disclosed via HackerOne (report #3622861), and GitLab has confirmed and remediated the issue; no confirmed active exploitation (CISA KEV) has been reported at time of analysis.
IP-based access restriction bypass in GitLab Enterprise Edition exposes private project merge request metadata to authenticated users who would otherwise be blocked by network-level controls. Affecting all EE versions from 12.0 up to 19.0.6, 19.1.4, and 19.2.2, the flaw stems from a missing authorization check in a merge requests API endpoint that fails to enforce configured IP allowlists. A publicly available exploit exists via HackerOne, and while the confidentiality impact is scoped to limited merge request information, the bypass of a deliberate security boundary elevates practical risk for organizations relying on IP restrictions as a compensating control.
Incorrect authorization in GitLab Enterprise Edition's GraphQL layer allows authenticated users to read policy configurations belonging to namespaces they have no authorized access to. Affected versions span GitLab EE 19.1 before 19.1.4 and 19.2 before 19.2.2. A publicly available proof-of-concept exploit exists (HackerOne report #3776182), though no active exploitation has been confirmed by CISA KEV, making this a medium-severity information disclosure risk for organizations running GitLab EE at affected patch levels.
SPIFFE identity impersonation in Kong Mesh universal mode allows an authenticated dataplane operator to assume another workload's mTLS identity by exploiting an incomplete workload-binding enforcement in the XDS authenticator. The kuma-cp authenticator validates the kuma.io/workload label only when a dataplane token is explicitly bound to a workload; because workload binding is optional, a tags-only-bound token can register any kuma.io/workload label value and receive the corresponding SPIFFE ID, bypassing MeshIdentity-enforced access controls. No public exploit has been identified at time of analysis; vendor-confirmed patches are available via upstream Kuma PRs.
Missing RBAC middleware on Budibase's GET /api/global/groups API endpoint allows any authenticated BASIC-role user to enumerate all tenant groups, role-to-application mappings, member user lists, builder permission flags, and default-group designations that should be restricted to builders and administrators. All Budibase versions prior to 3.39.25 are affected across both self-hosted and cloud deployments. No active exploitation is confirmed in CISA KEV, but a complete proof-of-concept with Docker-based reproduction steps is publicly disclosed in GitHub Security Advisory GHSA-4qcj-m5wp-jmf4, reducing exploitation effort to near zero for any tenant user with a valid session.
Package registry metadata modification in GitLab CE/EE exposes an improper authorization flaw (CWE-863) that permits authenticated developer-role users to alter package registry metadata normally restricted to maintainers, across all instances running versions 17.6 through 19.2.1. A publicly available exploit has been disclosed via HackerOne (report 3598070), making this immediately actionable for insider or contractor threat scenarios. No active exploitation has been confirmed by CISA KEV, but the combination of wide version range, broad GitLab deployment footprint, and public exploit code elevates practical risk beyond the moderate CVSS 4.3 score alone.
Improper authorization checks on a GitLab Enterprise Edition group settings page allow any authenticated user to view restricted configuration settings they should not have access to. GitLab EE versions from 17.7 through 19.0.5, 19.1.0 through 19.1.3, and 19.2.0 through 19.2.1 are affected; patched releases (19.0.6, 19.1.4, 19.2.2) are available. No public exploit code and no confirmed active exploitation exist at time of analysis.
Session token validation bypass in IBM i versions 7.3 through 7.6 enables a remote low-privileged attacker to circumvent security restrictions by exploiting improper session token handling (CWE-294). The CVSS vector confirms network reachability but mandates high attack complexity and an existing authenticated foothold, capping the score at 6.8 Medium. No public exploit code or CISA KEV listing has been identified at time of analysis, and IBM has issued a vendor patch.
Security restriction bypass in IBM i 7.3 through 7.6 exploits an interpretation conflict in the multipart parser, enabling a remote attacker with high administrative privileges to circumvent configured access controls with low integrity impact. The flaw (CWE-436) arises when the security enforcement layer and the processing layer disagree on how to interpret multipart message boundaries, allowing carefully crafted requests to evade security checks. No public exploit code and no CISA KEV listing have been identified at time of analysis; IBM has released a patch via its support portal.
Improper authorization in IBM i versions 7.3 through 7.6 allows remote authenticated attackers to bypass security restrictions and perform unauthorized write operations on protected objects or data. The flaw, rooted in CWE-285, requires only low-privilege credentials and no user interaction, making it accessible to any authenticated user on the platform. IBM has released patches via their support advisory, and no active exploitation or public proof-of-concept has been identified at time of analysis.
Unauthorized artifact access in JFrog Artifactory allows unauthenticated network attackers to retrieve restricted artifacts under specific, high-complexity conditions. The flaw stems from a missing authorization check (CWE-862) that can be triggered without credentials, directly exposing confidential build artifacts, proprietary binaries, or sensitive packages stored in the repository. No public exploit code or active exploitation has been identified at time of analysis, and the high attack complexity requirement (AC:H) limits opportunistic mass exploitation.
Cross-team DAG authorization bypass in Apache Airflow versions prior to 3.3.1 allows authenticated users in one team to trigger DAG runs and read XCom values belonging to other teams. The asset materialization endpoint (POST /api/v2/assets/{asset_id}/materialize) and the XCom check in wait_dag_run_until_finished both passed DagDetails without resolving the DAG's team_name, causing team-aware auth managers (e.g., Keycloak) to evaluate the permission against the global DAG resource instead of the team-scoped DAG:<team> resource. This is a missing authorization flaw (CWE-862) affecting only deployments running multi-team mode with a team-aware auth manager; FAB auth manager deployments are explicitly unaffected. No public exploit code or CISA KEV listing has been identified at time of analysis.
Cross-team credential access in Apache Airflow before 3.3.1 allows authenticated members of one team to invoke another team's Connection credentials through the POST /api/v2/connections/test API endpoint, exploiting a broken namespace-isolation guard in the environment-variable secrets backend. The flaw-confirmed by Apache with patches in PRs #70736 and #70902-combines a guard that only triggered on unscoped (global) requests with a regex incapable of matching team names containing underscores, even though underscores are explicitly permitted in Airflow team name validation. Exploitation requires a precise configuration alignment of multi_team mode, an explicitly enabled test_connection endpoint, and environment-variable-provisioned team secrets; no public exploit has been identified at time of analysis.
Improper authorization in WhatsUp Gold's Scheduled Reports API allows any authenticated user to invoke actions that should be restricted to privileged roles. Affecting all versions prior to 2026.0.2, the flaw (CWE-862, Missing Authorization) means the API enforces authentication but performs no role-based access check on sensitive operations, enabling horizontal or vertical privilege escalation within the application. No public exploit has been identified at time of analysis, and a vendor-released patch is available as of version 2026.0.2.
Package metadata authorization bypass in JFrog Artifactory 7.161.0 through 7.161.15 allows authenticated low-privileged users to read package metadata from repositories they are explicitly denied read access to, under specific undisclosed conditions. The flaw is a missing authorization check (CWE-862) in the metadata access path, creating an unintended privilege boundary crossing within Artifactory's permission model. No active exploitation has been confirmed (no CISA KEV listing) and no public exploit code has been identified, but the network-accessible attack vector with no user interaction required makes this relevant for any multi-tenant or externally accessible Artifactory deployment.
Broken access control in Winter CMS (composer/winter/wn-cms-module ≤ 1.2.12) allows any authenticated backend user holding at least one Theme Editor permission to pivot beyond their authorized scope via crafted AJAX requests. The Cms\Controllers\Index controller gated section access with OR-logic across five permissions but individual handlers - onSave(), onDelete(), onDeleteTemplates(), and AssetList.onUpload() - performed no per-template-type authorization check, enabling cross-template actions such as deleting layouts, modifying partials, reading content files, and uploading arbitrary files to the active theme asset directory. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; vendor-released fix is v1.2.13.
Information disclosure in JFrog Artifactory exposes private Release Bundle metadata to unauthorized parties under two conditions: when anonymous access is globally enabled, or when a low-privilege authenticated account is used. Affected users can enumerate the names and versions of private Release Bundles provided they already know the bundle name, bypassing expected access controls. No public exploit code has been identified and the vulnerability carries a low CVSS score of 3.1, but the missing authorization check (CWE-862) represents a genuine access control gap in sensitive artifact delivery pipelines.
Unauthorized access to restricted support information in JFrog Artifactory allows a low-privileged authenticated user to read sensitive support data under specific, undisclosed conditions. The vulnerability stems from missing authorization controls (CWE-862) on support-related endpoints, exposing information that should be restricted to administrative roles. No public exploit has been identified at time of analysis, and no CISA KEV listing was found.
Authentication bypass in JFrog Artifactory exposes protected repository resources to unauthenticated remote users when specific cache conditions are met. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms exploitation requires no credentials, no user interaction, and no special network position - any user who can reach the Artifactory instance over the network can potentially trigger this condition. No public exploit code exists and this CVE is not listed in the CISA KEV catalog at time of analysis, but the unauthenticated network attack vector elevates real-world concern for internet-facing deployments.
JFrog Artifactory exposes private Puppet module metadata to authenticated users who lack repository read access, constituting a missing authorization control on a specific metadata retrieval endpoint. Any low-privilege user with a valid Artifactory account can silently enumerate Puppet module metadata from repositories they are explicitly denied access to, potentially revealing module names, versions, dependencies, and authorship details. No public exploit code has been identified at time of analysis, and this vulnerability has not been listed in the CISA KEV catalog, though the CVSS 4.3 score reflects a real, network-exploitable authorization bypass with limited but concrete confidentiality impact.
Unauthorized NuGet metadata exposure in JFrog Artifactory allows an authenticated user who lacks repository read permission to read private NuGet feed metadata under specific conditions, constituting a missing authorization control (CWE-862). All versions covered by the CPE wildcard (cpe:2.3:a:jfrog:artifactory:*) appear affected. An attacker with any valid Artifactory account can potentially enumerate or read package metadata from private NuGet repositories they should not have visibility into, leading to information disclosure of internal package names, versions, or dependency structures. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
Unauthorized repository information disclosure in JFrog Artifactory allows unauthenticated remote users to read restricted repository content under specific deployment conditions. Rooted in CWE-862 (Missing Authorization), the flaw bypasses access controls without credentials, confirmed by a PR:N/AV:N CVSS vector. No public exploit code and no CISA KEV listing exist at time of analysis, and the 'specific conditions' qualifier in the vendor's own description limits the realistic attack surface compared to the raw CVSS score suggests.
Incorrect authorization (CWE-863) in JFrog Artifactory allows an authenticated bundle writer to generate misleading release promotion metadata under specific operating conditions, undermining the integrity of the software release pipeline. Affected scope spans all Artifactory versions per the wildcard CPE string, impacting both self-managed and potentially cloud deployments where the bundle writer role is in use. No public exploit code exists and this vulnerability has not been added to the CISA KEV catalog, though the supply-chain integrity risk in production DevSecOps pipelines may exceed the moderate CVSS score.
Insufficient authorization in JFrog Artifactory allows an authenticated user lacking repository read permissions to access private OCI referrer metadata under specific conditions. The flaw maps to CWE-862 (Missing Authorization), meaning the access control check for OCI referrer metadata is absent or bypassed rather than misconfigured. No public exploit or active exploitation has been identified at time of analysis, but the information disclosure could expose artifact relationship graphs and supply chain metadata that organizations intend to keep private.
JFrog Artifactory contains a missing authorization flaw that allows an authenticated user holding a publisher role - but explicitly denied delete permissions - to modify protected package content under specific conditions. This integrity bypass (CWE-862) is reachable over the network without elevated privileges, making it a supply chain risk for organizations using Artifactory as their artifact repository. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Unauthorized read access to restricted JFrog Artifactory content is possible when a credentialed remote repository is configured in a specific non-default manner, triggering a missing authorization check (CWE-862). The flaw affects all Artifactory versions per the CPE wildcard, exposing proprietary artifacts such as internal libraries, Docker images, or build dependencies to network-accessible requests without credential validation. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the high confidentiality impact (C:H in CVSS) means successful exploitation results in full read exposure of the targeted restricted repository.
Docker Sandboxes (sbx) fails to enforce read-only semantics on virtio-fs host mounts: the in-guest bind correctly receives the read-only flag, but the underlying host-edge grant omitted from the policy-share allowlist carries no access mode, leaving the shared-export path fully writable at the host level. Low-privileged code executing inside the sandbox can enumerate or derive the virtio-fs export path and write to host directories the operator explicitly attached as read-only, breaking the isolation guarantee that is the product's core security promise. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Object version metadata exposure in RustFS allows anonymous HTTP clients to enumerate all stored object versions via GET /<bucket>?versions= even after an operator enables RestrictPublicBuckets. The authorization fallback in rustfs/src/storage/access.rs grants listing through an s3:ListBucket check but returns before applying the public-access block controls, silently contradicting the operator's intent to restrict anonymous access. No public exploit has been identified and the vulnerability is not listed in CISA KEV; the vendor-released fix is available in 1.0.0-beta.12.
Authorization bypass in RustFS FTPS MKD handler allows authenticated FTPS users to create S3 buckets in violation of enforced IAM-style policies. All RustFS releases prior to 1.0.0-beta.12 are affected via the `FtpsDriver::mkd` function in `crates/protocols/src/ftps/driver.rs`, which calls `storage.create_bucket` without invoking `authorize_operation` for `S3Action::CreateBucket`. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Versioned object access control bypass in RustFS allows authenticated principals holding only s3:GetObject permission to read historical object versions by supplying an explicit versionId parameter on GetObject, CopyObject source, or UploadPartCopy source requests. The authorization boundary in access.rs conflated two distinct IAM actions - s3:GetObject and s3:GetObjectVersion - by always evaluating versioned reads against the former, effectively collapsing a privileged historical-version operation into an ordinary current-object read. No active exploitation has been confirmed (not in CISA KEV), and no public exploit code has been identified; however, the bypass is trivial to exercise for any valid IAM credential with bucket read access.
Inconsistent authorization enforcement in Vulnerability-Lookup's SSE streaming interface allows self-registered but unconfirmed or inactive accounts to subscribe to Pub/Sub event streams, accessing pre-moderation data that the REST API correctly restricts. The platform's self-registration flow issues an API key before account confirmation is complete, and the token_required decorator on /pubsub/subscribe/<topic> validated only that the key matched a known user - not that the account was active or confirmed. No public exploit has been identified at time of analysis, and a vendor-released patch correcting the authorization gap is confirmed available via upstream commit.
Unauthenticated comment creation in SP Page Builder for Joomla (versions prior to 6.8.0) allows remote attackers to bypass the disabled guest commenting restriction by supplying crafted user input that overrides the server-side access control setting. The vulnerability stems from improper access control (CWE-284), where a client-influenced parameter can override a site administrator's explicit configuration decision to disable public commenting. No public exploit or active exploitation has been identified at time of analysis, and the CVSS 4.0 score of 6.3 reflects limited integrity impact with no confidentiality or availability consequence.
Improper access control in the Cotton Cloud Joomla extension (versions prior to 2.0.3) enables horizontal privilege escalation across user accounts within a shared Joomla installation. Any authenticated user - regardless of privilege level - can read, delete, overwrite, or reassign permissions on files owned by other users, bypassing the extension's intended ACL enforcement. No public exploit code or CISA KEV listing has been identified at time of analysis, though the low attack complexity makes exploitation straightforward for any credentialed user.
Incorrect authorization in Velociraptor's hunt_delete() VQL function grants investigator-role users the ability to permanently delete hunt results, a privilege that should be restricted to administrators holding the DELETE_RESULTS permission. The platform misapplied the COLLECT_CLIENT permission check in place of the DELETE_RESULTS gate, enabling lateral privilege abuse within authenticated sessions. No public exploit or active exploitation has been identified, but the integrity impact is high because hunt data represents forensic evidence collected during incident response operations.
Cross-tenant data exposure in Velociraptor's multi-tenant GUI allows authenticated root-org users to read Stacked result sets belonging to child organizations by bypassing the prefix deny list that enforces datastore path isolation. The GUI endpoint that serves result sets does not correctly validate requested paths against the deny list, so a crafted request can resolve to a sub-org datastore directory the requester should not have access to. No public exploit has been identified and exploitation requires existing high-privilege authenticated access, but the confidentiality impact is significant in shared DFIR environments where tenant isolation is a core security guarantee.
Improper access control in the Cotton Cloud Joomla extension (versions below 2.0.2) by tabaoca.org exposes a broken ACL implementation that allows unauthenticated remote attackers to perform arbitrary file operations - reading, deleting, overwriting, and reassigning permissions - on every file managed within the extension. The network-accessible, zero-authentication attack vector (CVSS 4.0 AV:N/AC:L/PR:N/UI:N) makes exploitation trivially low-effort against any Joomla site running an unpatched Cotton Cloud installation. No public exploit code or active exploitation has been identified at time of analysis, though the attack surface is broad enough that no specialized tooling is required.
Missing authorization on two administrative AJAX endpoints in ProSolution WP Client WordPress plugin before 2.0.9 allows any low-privileged authenticated user - including subscribers - to trigger administrative data synchronization and erase the plugin's activity log. The security nonce protecting these endpoints is exposed in the public-facing frontend, effectively nullifying WordPress's built-in CSRF protection and reducing the attack bar to any account with login access. A public exploit exists via WPScan, though CISA KEV lists no active exploitation and SSVC rates technical impact as only partial.
Insufficient authorization in WP Photo Album Plus (all versions before 9.2.09.002) allows any authenticated WordPress user-including low-privilege Subscriber accounts-to upload files into photo albums owned by other users or administrators. The flaw is rooted in CWE-639 (Authorization Bypass Through User-Controlled Key): the plugin's front-end upload endpoint accepts a caller-supplied album identifier without verifying ownership, enabling cross-user content injection. A publicly available POC exists via WPScan; no active exploitation is confirmed in CISA KEV, and the attack surface is constrained by a non-default configuration prerequisite.
Incorrect authorization in the Cookie Consent WordPress plugin (versions before 0.0.10) allows any authenticated user - including low-privilege roles such as subscribers - to overwrite the plugin's stored geolocation service license key via a REST API route that fails its intended administrator-only capability check and falls back to a weaker authentication-only gate. The practical consequence is silent disruption of geolocation-based consent banner targeting, which can undermine GDPR and regional cookie-consent compliance workflows. Publicly available exploit code exists (no confirmed CISA KEV listing), and an EPSS score of 17% indicates above-average real-world exploitation interest relative to this severity class.
User Access Manager WordPress plugin before version 2.3.15 exposes restricted content to unauthenticated attackers via the WordPress REST API, which the plugin fails to protect with its own access control logic. Any post, page, or custom post type configured to be visible only to specific user groups can be silently read through standard REST API endpoints without credentials. A publicly available proof-of-concept exists (WPScan), and with an EPSS of 15% and automatable exploitation, this is a realistic risk for any WordPress site using this plugin to gate premium or sensitive content.
Reflected Cross-Site Scripting in the WP Photo Album Plus WordPress plugin (all versions before 9.2.07.002) allows unauthenticated attackers to inject arbitrary JavaScript into a victim's browser by reflecting an unsanitized parameter directly into an inline script block on gallery pages. Exploitation requires social engineering - the victim must open a crafted link - but no attacker credentials are needed. A publicly available proof-of-concept exists, reported by WPScan, and EPSS places exploitation probability at 17%, a notably elevated figure for a reflected XSS in a plugin.
Unauthenticated IDOR in WP Travel Engine WordPress plugin before 6.8.5 exposes all customer booking records and stored billing information to any unauthenticated attacker who supplies a valid booking identifier to an unprotected cart action. The root cause is a complete absence of authorization and ownership checks - the plugin accepts a caller-supplied booking ID and processes it without verifying the requestor's identity or entitlement. Beyond disclosure, attackers can overwrite any customer's booking record with their own data, enabling fraud, booking manipulation, or data corruption at travel agencies. A publicly available proof-of-concept exists, and at 15% EPSS this vulnerability is elevated for its CVSS 5.3 rating - warranting prompt attention.
Broken authorization in the Cookie Consent WordPress plugin before 0.0.10 allows any authenticated user - including a subscriber - to invoke administrator-intended REST API endpoints that control consent settings. Affected sites on the vendor's paid plan face an additional confidentiality exposure: the same misconfigured routes permit low-privileged users to read stored visitor consent logs, data that may carry GDPR compliance significance. A publicly available exploit exists, and an EPSS of 18% signals meaningful near-term exploitation probability despite the moderate CVSS score.
WP Crowdfunding WordPress plugin before version 2.2.1 allows any subscriber-level authenticated user to create crowdfunding campaign posts by exploiting a missing capability check in an AJAX action endpoint. The plugin fails to verify whether the requesting user holds the campaign-submission permission, allowing low-privilege WordPress roles to perform actions reserved for higher-privileged users. A publicly available exploit exists via WPScan, and an elevated EPSS of 14% signals meaningful real-world exploitation interest despite no CISA KEV listing.
Insecure Direct Object Reference in WP Crowdfunding (WordPress plugin, all versions before 2.2.1) allows any authenticated user with Subscriber-level access to read personal data from arbitrary WooCommerce orders and enumerate the store's complete order history. The flaw stems from missing order ownership verification, meaning low-privilege accounts - freely obtainable on sites with open registration - can harvest customer PII at scale. A publicly available exploit documented by WPScan exists, and the 14% EPSS score indicates meaningful real-world exploitation interest beyond what the mid-range CVSS score alone suggests.
Broken object-level authorization in the WP Crowdfunding WordPress plugin before 2.2.1 allows any authenticated user - including low-privilege Subscribers - to modify the update history of campaigns they do not own and trigger notification emails to that campaign's backers. The vulnerability stems from missing ownership verification on campaign update endpoints, enabling horizontal privilege escalation across all campaigns on the affected site. A publicly available proof-of-concept exists (reported by WPScan), and the EPSS score of 14% is notably elevated relative to most WordPress plugin flaws, warranting prompt patching on sites hosting active crowdfunding campaigns.
Insecure Direct Object Reference (IDOR) in KiviCare WordPress plugin before 4.5.2 allows any authenticated patient-level user to retrieve bills, invoices, and appointment records belonging to other patients without authorization. The plugin fails to verify record ownership server-side, meaning a low-privilege patient account is sufficient to enumerate and access sensitive healthcare and financial records of arbitrary other patients. A publicly available proof-of-concept exists via WPScan, and the EPSS score of 14% indicates meaningful near-term exploitation probability.
Eventin WordPress plugin versions from 4.1.9 through 4.1.19 exposes customer order records - including personal information - to any contributor-level or higher WordPress user via an Insecure Direct Object Reference (IDOR) flaw. Authenticated users can enumerate order identifiers sequentially to read arbitrary customers' purchase data without authorization. A public proof-of-concept is available via WPScan, and an EPSS score of 14% places this notably above the median for WordPress plugin vulnerabilities, indicating active interest from threat actors even without a CISA KEV listing.
Cross-namespace Secret manipulation in the multicloud-operators-channel component of Red Hat Advanced Cluster Management for Kubernetes 2 (RHACM) enables an authenticated low-privileged user holding specific channel-related permissions to read or modify Kubernetes Secrets outside their authorized namespace scope. The CVSS S:C (Changed Scope) metric confirms the flaw crosses namespace trust boundaries - a critical boundary in multi-tenant Kubernetes environments - potentially exposing credentials, service account tokens, or application secrets belonging to other tenants, and enabling privilege escalation. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Boot partition authentication bypass in CPSD CryptoPro Secure Disk for BitLocker before v7.7.4 allows an attacker who can manipulate disk partition layout to redirect boot-time code execution to a crafted Linux partition. The product fails to cryptographically verify the integrity of the intended boot partition and instead selects the first partition whose type matches a hardcoded value - a logic flaw that allows a spoofed partition to preempt the legitimate boot target and execute arbitrary code at elevated privilege. No public exploit or CISA KEV listing is confirmed at time of analysis, though a Black Hat USA 2026 research presentation by Burch ('The Cost of Obscurity') describes the finding, suggesting detailed technical disclosure has occurred.
Unauthenticated access to Micronaut management endpoints in Kestra prior to 2.0.0-rc6 allows any network-reachable attacker to read fully resolved configuration via GET /env or manipulate runtime log levels via POST /loggers/{name}, bypassing the Basic Auth controls that protect only the primary API on port 8080. The management port (8081) is configured in application.yml with no equivalent authentication gate, making this a structural authentication bypass rather than a misconfiguration edge case. No active exploitation is confirmed (not in CISA KEV) and no public proof-of-concept has been identified at time of analysis.
Authorization bypass in Snipe-IT before 8.6.0 allows any authenticated low-privileged user to cancel other users' pending asset checkout requests by supplying arbitrary values in URL path segments. The checkout-request cancellation endpoint reads `cancel_by_admin` and `requestingUser` directly from user-controlled URL segments without server-side ownership validation, enabling any logged-in user to bypass request-ownership checks. Because asset and user identifiers are sequential integers, a determined attacker can enumerate the full ID space and systematically cancel every pending checkout request platform-wide, disrupting the asset-management workflow. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog; a vendor patch is confirmed in v8.6.0, reported by Tenable (TRA-2026-54).
Path traversal in Red Hat insights-client allows a compromised spoke (managed cluster) to inject unencoded sequences into the Insights API URL path by manipulating the ClusterID value it controls, redirecting authenticated hub-side requests to unintended API endpoints. Affected deployments include any multi-cluster Red Hat Insights configuration where a spoke cluster could be under adversary control. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Bearer token reuse in the acm-search-v2-api-rhel9 component of Red Hat Advanced Cluster Management exposes federated hub search results to unauthorized authenticated users. The `getFederationConfig` cache refresh incorrectly retains one user's token and applies it to all subsequent federated queries until TTL expiry, enabling cross-tenant information disclosure across remote managed hubs. No public exploit has been identified at time of analysis, and the CVSS High Confidentiality rating is tempered by the AC:H timing dependency required for successful exploitation.
Remote code execution in Microsoft Edge (Chromium-based) below version 151.0.4129.78 stems from a type confusion flaw (CWE-843) in the browser engine, exploitable over the network when a user visits or interacts with attacker-controlled content. The vendor has confirmed patch availability and the flaw is tagged as causing memory corruption, which aligns with the typical consequence of type confusion in browser engines. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis, though the unauthenticated network vector with low attack complexity warrants prioritized patching in enterprise environments.
MongoDB Server's sharded cluster transaction coordination is vulnerable to an authorization bypass that allows an authenticated, low-privileged user with direct adjacent-network access to a shard process to illegitimately commit or abort in-progress prepared transactions - actions that are normally reserved for the designated transaction coordinator. Exploitation can produce cross-shard data inconsistency, cluster clock corruption, and broken atomicity guarantees across the distributed database. No public exploit code exists and SSVC confirms no active exploitation; however, successful abuse could silently corrupt application-layer data integrity across the cluster.
Insufficient privilege enforcement in MongoDB Server allows an authenticated user holding only a limited database-scoped role to operate against protected system collections normally restricted to higher-privilege roles. Affected versions span the 7.0, 8.0, and 8.3 release lines. Depending on deployment configuration, exploitation can expose collection metadata or enable unauthorized modification of system collection data. No public exploit has been identified at time of analysis, and SSVC assessment confirms no observed exploitation.
MongoDB Server 8.3.x through 8.3.7 permits certificate-based authentication to succeed for a client holding a valid x.509 certificate and a corresponding user account, even when the administrator has explicitly configured the server to restrict allowable authentication mechanisms to other methods such as SCRAM. The vulnerability undermines deliberate access-control policy decisions rather than enabling unauthenticated access, meaning the attacker must already possess legitimate credential material. With a CVSS 4.0 score of 2.3, CISA SSVC exploitation status of 'none', and no public exploit identified at time of analysis, this is a low-urgency compliance and policy-integrity issue rather than an imminent exploitation threat.
Broken object-level authorization in CVAT's lambda annotation API allows authenticated Worker-role users to exploit predictable task-based request IDs to read automatic annotation requests for tasks they are not permitted to access and to cancel annotation requests submitted by other users. All CVAT deployments running versions 2.17.0 through 2.71.x are affected per cpe:2.3:a:cvat-ai:cvat. No public exploit exists and this vulnerability is not listed in CISA KEV; SSVC assessment confirms no current exploitation, but multi-tenant environments with mixed-trust Worker accounts face meaningful workflow disruption risk.
IPv6 denied-peer-ip bypass in Coturn before 4.16.0 allows an authenticated TURN client to relay traffic to internal IPv6 hosts that fall within a configured blocked range, enabling a TURN-specific server-side request forgery. The root cause is a component-wise (rectangular-box) comparison in addr_less_eq() that fails to enforce the contiguous numerical span [min,max] for non-prefix-aligned IPv6 ranges, so addresses like 2001:db8::1ff are incorrectly classified as outside a denied range of 2001:db8::100-2001:db8::200. No active exploitation is confirmed in CISA KEV, but the flaw carries high subsequent-system impact (CVSS 4.0 SC:H/SI:H/SA:H) and a public GitHub advisory and commit diff are available.
Coturn TURN/STUN server prior to version 4.13.1 exposes an IPv4 access control bypass through incomplete IPv6 address canonicalization, allowing authenticated RFC 6062 TCP CONNECT relay clients to reach peer addresses that administrators intended to block via denied-peer-ip rules. The bypass exploits three IPv4-in-IPv6 encoding formats - IPv4-compatible (::/96), 6to4 (2002::/16), and NAT64 (64:ff9b::/96) - that the peer address validation function failed to normalize before comparing against configured ACL ranges. No active exploitation has been confirmed (not in CISA KEV) and a vendor-released patch is available as version 4.13.1.
Broken access control in Cap v0.3.1's POST /api/video/comment endpoint allows any authenticated user to post comments on arbitrary private videos owned by other users by supplying an attacker-chosen videoId in the request body. Beyond unauthorized commenting, attackers can trigger notification emails to the video owner and enumerate valid private video IDs through response differences, constituting both a confidentiality and integrity breach. No public exploit code or CISA KEV listing has been identified at time of analysis, and the upstream fix has been committed to the Cap GitHub repository.
Privilege escalation in Adobe Commerce and Magento Open Source exposes restricted resources to authenticated high-privilege users through a flawed authorization check (CWE-863). Affected products span the full 2.4.x series of Adobe Commerce and Magento Open Source, plus the 1.3.x-1.5.x Adobe Commerce B2B extension. No public exploits are known, CISA SSVC rates exploitation as none, and vendor-released August 2026 patches are available across all affected release lines per advisory APSB26-92.
Incorrect Authorization in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B allows a network-accessible, high-privileged attacker to bypass platform security controls and gain unauthorized write access, resulting in high integrity and availability impacts. Affected are Adobe Commerce through 2.4.9-2026-jul, Magento Open Source through 2.4.9-2026-jul, and Adobe Commerce B2B through 1.5.3-2026-jul, with August 2026 patches available per Adobe APSB26-92. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Improper input validation in Adobe's Content Credentials ecosystem (Rust SDK, JS SDK, and CLI tool) allows local attackers to bypass C2PA content authenticity security controls and gain unauthorized limited write access to credential metadata. Affected are c2pa-v0.90.5 and earlier, @contentauth/c2pa-web@0.12.0 and earlier, and c2patool-v0.27.5 and earlier. No user interaction is required, but the local attack vector (AV:L) and SSVC automation rating of 'no' constrain realistic exploitation to targeted scenarios rather than mass exploitation.
Information disclosure in Azure CycleCloud allows an authenticated network attacker to bypass authorization checks and read sensitive data. Rooted in CWE-862 (Missing Authorization), the flaw affects versions up to 8.9.2 and is exploitable by any authorized user who can reach the service over a network without elevated privileges. No public exploit or CISA KEV listing has been identified at time of analysis, and Microsoft has released a patch.
Inadequate encryption strength in Windows Active Directory enables a low-privileged authenticated network attacker to bypass a security feature, resulting in a high-integrity impact. Affected platforms span Windows Server 2022, Windows Server 2025, and multiple Windows 11 release channels (23H2 through 26H1). No public exploit identified at time of analysis; SSVC assessment confirms no observed exploitation and the attack is not automatable, placing this in a lower operational urgency tier despite the high integrity impact rating.
Security feature bypass in Microsoft Visual Studio Code Copilot Chat Extension (versions 0.27.0 through pre-1.132.1) enables network-based attackers to circumvent a protective control without authentication, resulting in high integrity impact and low availability impact. The attack requires user interaction - consistent with a scenario where a victim must engage with crafted content delivered over the network. No public exploit code has been identified at time of analysis, and a vendor patch (1.132.1) is available via the Microsoft Security Response Center.
Incorrect authorization in Microsoft SharePoint Server exposes authenticated network attackers to unrestrained content tampering across three supported product lines. The flaw, rooted in CWE-863 (Incorrect Authorization), allows a low-privileged but authenticated user to perform write or modification operations that server-side access controls should restrict to higher-privileged roles. Microsoft has released patches for all three affected versions; no public exploit code or CISA KEV listing exists at time of analysis.
Missing authorization in Microsoft Exchange Server allows authenticated low-privilege network users to bypass a security feature, achieving high-integrity impact without requiring elevated credentials or user interaction. Rooted in CWE-862, Exchange fails to enforce a required authorization check on at least one network-accessible endpoint, enabling unauthorized high-integrity modifications - such as changes to mailbox permissions, transport rules, or security policy - by any valid account holder. No active exploitation is confirmed by CISA KEV, no public exploit code is identified, and Microsoft has released patches across all affected cumulative update tracks.
HTTP request smuggling in System.Net.HttpListener across .NET 8.0, 9.0, and 10.0 enables unauthenticated remote attackers to bypass security features on Linux and macOS deployments. The flaw stems from inconsistent HTTP request interpretation (CWE-444), allowing crafted requests to circumvent authentication or access controls with high confidentiality impact. Exploitation carries high attack complexity (AC:H), no public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV, placing this in a monitored-but-not-emergency posture for most organizations.
Insufficiently protected credentials in Microsoft Office Outlook expose authentication material over network connections, enabling unauthenticated network-positioned attackers to perform spoofing attacks contingent on victim user interaction. The flaw affects Outlook 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, and Microsoft 365 Apps for Enterprise - collectively spanning nearly the entire current Outlook product line. Microsoft has released a patch; no public exploit or active exploitation (CISA KEV) has been identified at time of analysis.
Incorrect authorization in the Windows Container Isolation FS Filter Driver (unionfs.sys) allows a local authenticated attacker on Windows 11 26H1 to disclose sensitive information beyond their authorized filesystem scope. The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) confirms high confidentiality impact confined to the local system, with no integrity or availability consequence. No public exploit code exists and SSVC rates exploitation as none, placing this as a routine patching priority rather than an emergency response item.
Authentication bypass in Windows Schannel allows a network-based attacker to circumvent cryptographic signature validation, achieving high-integrity impact without requiring prior privileges. Schannel, Microsoft's TLS/SSL security provider, fails to properly verify cryptographic signatures - tagged as a JWT attack vector - enabling forged or malformed tokens to pass validation and bypass security feature enforcement. No active exploitation is confirmed (SSVC: exploitation=none; not listed in CISA KEV), and the high attack complexity and required user interaction constrain opportunistic mass exploitation despite the broad Windows version footprint.
Tampering via partial string comparison in the Windows HTTP Protocol Stack (http.sys) exposes a broad range of Windows client and server editions to integrity compromise by unauthenticated adjacent-network attackers. Affected platforms span Windows 10 1607 through Windows 11 26H1 and Windows Server 2012 through Server 2025, with Microsoft tagging the issue as an authentication bypass rooted in CWE-187. No public exploit has been identified at time of analysis, and Microsoft has released patched builds across all affected product lines.
Windows Defender Firewall Service across Windows 10, Windows 11, and Windows Server 2019 through 2025 contains a missing authorization flaw (CWE-862) that enables a locally authenticated low-privileged attacker to bypass firewall security controls and manipulate firewall rules without the required authorization. The vulnerability carries a CVSS score of 5.5 with High integrity impact, reflecting the attacker's ability to fully undermine the local firewall enforcement boundary from a standard user session. No public exploit code or CISA KEV listing has been identified at time of analysis, though the post-exploitation value as a lateral movement enabler is notable given the breadth of affected Windows versions.
Certificate validation bypass in Adobe's Content Credentials SDK undermines the C2PA provenance chain across three SDK variants - JavaScript/WASM (@contentauth/c2pa-web through 0.12.0), Rust (c2pa through v0.90.5), and CLI (c2patool through v0.27.5) - allowing an attacker-controlled certificate to be accepted as legitimate when a victim visits a malicious URL or interacts with a compromised web page. Successful exploitation grants unauthorized write access to content credentials, enabling an attacker to forge provenance metadata and defeat the product's core integrity guarantee. No public exploit has been identified at time of analysis; vendor-released patches exist for all three affected SDK variants.
Improper input validation across Adobe's Content Credentials JS SDK, Rust SDK, and command-line tool allows a remote unauthenticated attacker to bypass integrity verification and gain unauthorized write access to C2PA-signed content metadata. All three SDK components prior to their respective patch releases are affected, and exploitation requires a victim to visit a maliciously crafted URL or interact with a compromised web page. No public exploit code or active exploitation has been identified at time of analysis, though the write-impact on content authenticity signals carries meaningful trust implications for downstream consumers.
Authentication bypass in SiYuan's publish layer exposes password-protected attribute view data to unauthenticated remote users across all versions before v3.7.4. The FilterViewByPublishAccess filter omits its password enforcement on the renderAttributeView code path, allowing arbitrary callers to retrieve structured database rows - including document titles, block IDs, and column values - from documents the owner intended to gate with a publish password. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis; vendor patch is available at v3.7.4.
Unauthorized information disclosure in SiYuan exposes protected document metadata and content snippets via three unenforced API endpoints - getBlockBreadcrumb, getRefText, and getBlockTreeInfos - in all versions before v3.7.4. Unauthenticated network actors or low-privilege RoleReader accounts can bypass publish-access controls on documents explicitly marked as publish-forbidden or password-protected, retrieving titles, ancestor block content snippets, reference text, and path metadata by supplying block IDs. No public exploit has been identified at time of analysis; vendor patch is available in v3.7.4.
Unauthenticated information disclosure in SiYuan versions before 3.7.4 allows retrieval of block attributes - names, aliases, memos, and custom fields - from documents protected by publish-access controls. The `getBlockAttrs` and `batchGetBlockAttrs` API endpoints accept POST requests with block IDs without verifying the caller's authorization against the parent document's access policy, directly bypassing the publish-access restriction (CWE-862). No active exploitation has been confirmed and no public proof-of-concept has been identified; impact is bounded to metadata exposure rather than full document content, but the unauthenticated network vector warrants prompt patching for internet-exposed instances.
Information disclosure in SiYuan before v3.7.4 allows unauthenticated remote attackers to retrieve the server's absolute filesystem workspace path, operating-system username, and installation layout by querying the resolveAssetPath endpoint with relative asset paths harvested from published documents. The endpoint enforces only a lightweight CheckAuth gate rather than full authentication, satisfying CWE-639's authorization bypass pattern, and returns raw absolute paths to any network-reachable caller. Vendor patch v3.7.4 has been released; no active exploitation has been confirmed and no public proof-of-concept code has been identified at time of analysis.
Missing authorization controls on three internal API endpoints in SiYuan before v3.7.4 allow callers operating within the publish context to retrieve database column schemas, template expressions, select vocabularies, and workspace-wide block identifiers that were never intended to cross publish access boundaries. The affected endpoints - getAttributeViewKeysByID, getBlockDefIDsByRefText, and getBlockRelevantIDs - perform their operations without consulting publish-scoped permission checks, constituting a CWE-862 (Missing Authorization) flaw. A vendor patch is available at v3.7.4, no public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Five path-resolution API endpoints in SiYuan's publish mode fail to enforce access controls, allowing unauthenticated or minimally-authenticated readers to enumerate the complete private document tree. Affected versions are all SiYuan releases up to and including v3.7.2; v3.7.4 contains the fix. An attacker targeting a SiYuan instance running in publish mode with Publish.Auth.Enable set to false can call getFullHPathByID, getHPathByID, getPathByID, getIDsByHPath, and getHPathByPath without any credentials to recover notebook names, folder hierarchies, document titles, and document IDs - including for content explicitly marked hidden, password-protected, or publish-forbidden. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Unauthenticated information disclosure in SiYuan before v3.7.4 exposes encrypted notebook identifiers, names, and memory-resident unlock states via the getEncryptedNotebookStatus API endpoint without enforcing publish-access filtering. Any anonymous or publish-mode client that can reach the instance can enumerate the full list of encrypted notebooks and determine which are actively decrypted in server memory, leaking sensitive organizational metadata. No public exploit has been identified and no CISA KEV listing exists; a vendor-released patch is available in v3.7.4.
Static-route access control bypass in SiYuan before v3.7.4 allows attackers to read sensitive workspace data by directly accessing file-serving routes that skip the authorization checks enforced on the REST API. Affected deployments include any SiYuan instance operating in disabled-auth mode (anonymous access) or where publish reader tokens have been issued, as those token holders can reach templates, snippets, and export artifacts without restriction. No public exploit or active exploitation has been identified at time of analysis, but the patch to v3.7.4 is available and should be applied promptly given the unauthenticated attack vector in disabled-auth configurations.
SiYuan's /api/tag/getTag endpoint leaks tag labels and occurrence counts from password-protected documents to any unauthenticated network caller, constituting an authorization bypass under CWE-863. All SiYuan versions before 3.7.4 are affected, as confirmed by a vendor GitHub Security Advisory (GHSA-mp7r-57w4-5qm3) and the EUVD entry EUVD-2026-57452. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog; however, the zero-friction network exploitability (PR:N, AC:L, UI:N) means any attacker with network reach can enumerate protected document vocabulary with a single API call.
Information disclosure in SiYuan v3.7.4-alpha.1 (pre-release only) permits any caller who passes basic authentication to retrieve complete database view metadata - including view names, icons, layout types, and per-field Hidden flags - for arbitrary database blocks by supplying an avID, regardless of their access level. The `/api/av/getAttributeViewFieldViews` endpoint introduced in commit acfc02ee8 applies `CheckAuth` middleware but omits any ownership or publish-access filter, producing a CWE-862 Missing Authorization condition. The vulnerability was corrected in the v3.7.4 stable release; no public exploit or active exploitation has been identified at time of analysis.
Unauthenticated information disclosure in SiYuan before v3.7.4 exposes notebook metadata - including names, document counts, storage sizes, and timestamps - for closed and non-published notebooks via the /api/notebook/getNotebookInfo endpoint, which performs no authorization check. Any attacker with network access to the SiYuan API can enumerate structural information that the application's access control model explicitly intends to hide from readers. No public exploit or CISA KEV listing has been identified at time of analysis, but the zero-friction, unauthenticated attack path makes this trivially exploitable wherever the API is internet- or network-exposed.
Information disclosure in SiYuan before v3.7.4 exposes administrator workspace state to unauthenticated network attackers via an improperly protected getConf API endpoint. The UILayout filter fails to enforce authorization boundaries between publish readers and the administrative configuration layer, leaking open document names, recent search terms, notebook directory paths, and private asset locations. No public exploit code or CISA KEV listing exists at time of analysis; however, the unauthenticated network vector makes the flaw trivially reachable on any internet-exposed SiYuan instance with publish features active.
Unauthorized disclosure of external status check configuration in GitLab Enterprise Edition allows any authenticated user holding a developer-role to read merge request API data that should be restricted to higher-privileged roles (maintainer or owner), due to a missing authorization check on the affected endpoint. Versions spanning 16.0 through 19.2.x are affected across a wide installation base. A publicly available proof-of-concept was disclosed via HackerOne (report #3622861), and GitLab has confirmed and remediated the issue; no confirmed active exploitation (CISA KEV) has been reported at time of analysis.
IP-based access restriction bypass in GitLab Enterprise Edition exposes private project merge request metadata to authenticated users who would otherwise be blocked by network-level controls. Affecting all EE versions from 12.0 up to 19.0.6, 19.1.4, and 19.2.2, the flaw stems from a missing authorization check in a merge requests API endpoint that fails to enforce configured IP allowlists. A publicly available exploit exists via HackerOne, and while the confidentiality impact is scoped to limited merge request information, the bypass of a deliberate security boundary elevates practical risk for organizations relying on IP restrictions as a compensating control.
Incorrect authorization in GitLab Enterprise Edition's GraphQL layer allows authenticated users to read policy configurations belonging to namespaces they have no authorized access to. Affected versions span GitLab EE 19.1 before 19.1.4 and 19.2 before 19.2.2. A publicly available proof-of-concept exploit exists (HackerOne report #3776182), though no active exploitation has been confirmed by CISA KEV, making this a medium-severity information disclosure risk for organizations running GitLab EE at affected patch levels.
SPIFFE identity impersonation in Kong Mesh universal mode allows an authenticated dataplane operator to assume another workload's mTLS identity by exploiting an incomplete workload-binding enforcement in the XDS authenticator. The kuma-cp authenticator validates the kuma.io/workload label only when a dataplane token is explicitly bound to a workload; because workload binding is optional, a tags-only-bound token can register any kuma.io/workload label value and receive the corresponding SPIFFE ID, bypassing MeshIdentity-enforced access controls. No public exploit has been identified at time of analysis; vendor-confirmed patches are available via upstream Kuma PRs.
Missing RBAC middleware on Budibase's GET /api/global/groups API endpoint allows any authenticated BASIC-role user to enumerate all tenant groups, role-to-application mappings, member user lists, builder permission flags, and default-group designations that should be restricted to builders and administrators. All Budibase versions prior to 3.39.25 are affected across both self-hosted and cloud deployments. No active exploitation is confirmed in CISA KEV, but a complete proof-of-concept with Docker-based reproduction steps is publicly disclosed in GitHub Security Advisory GHSA-4qcj-m5wp-jmf4, reducing exploitation effort to near zero for any tenant user with a valid session.
Package registry metadata modification in GitLab CE/EE exposes an improper authorization flaw (CWE-863) that permits authenticated developer-role users to alter package registry metadata normally restricted to maintainers, across all instances running versions 17.6 through 19.2.1. A publicly available exploit has been disclosed via HackerOne (report 3598070), making this immediately actionable for insider or contractor threat scenarios. No active exploitation has been confirmed by CISA KEV, but the combination of wide version range, broad GitLab deployment footprint, and public exploit code elevates practical risk beyond the moderate CVSS 4.3 score alone.
Improper authorization checks on a GitLab Enterprise Edition group settings page allow any authenticated user to view restricted configuration settings they should not have access to. GitLab EE versions from 17.7 through 19.0.5, 19.1.0 through 19.1.3, and 19.2.0 through 19.2.1 are affected; patched releases (19.0.6, 19.1.4, 19.2.2) are available. No public exploit code and no confirmed active exploitation exist at time of analysis.
Session token validation bypass in IBM i versions 7.3 through 7.6 enables a remote low-privileged attacker to circumvent security restrictions by exploiting improper session token handling (CWE-294). The CVSS vector confirms network reachability but mandates high attack complexity and an existing authenticated foothold, capping the score at 6.8 Medium. No public exploit code or CISA KEV listing has been identified at time of analysis, and IBM has issued a vendor patch.
Security restriction bypass in IBM i 7.3 through 7.6 exploits an interpretation conflict in the multipart parser, enabling a remote attacker with high administrative privileges to circumvent configured access controls with low integrity impact. The flaw (CWE-436) arises when the security enforcement layer and the processing layer disagree on how to interpret multipart message boundaries, allowing carefully crafted requests to evade security checks. No public exploit code and no CISA KEV listing have been identified at time of analysis; IBM has released a patch via its support portal.
Improper authorization in IBM i versions 7.3 through 7.6 allows remote authenticated attackers to bypass security restrictions and perform unauthorized write operations on protected objects or data. The flaw, rooted in CWE-285, requires only low-privilege credentials and no user interaction, making it accessible to any authenticated user on the platform. IBM has released patches via their support advisory, and no active exploitation or public proof-of-concept has been identified at time of analysis.
Unauthorized artifact access in JFrog Artifactory allows unauthenticated network attackers to retrieve restricted artifacts under specific, high-complexity conditions. The flaw stems from a missing authorization check (CWE-862) that can be triggered without credentials, directly exposing confidential build artifacts, proprietary binaries, or sensitive packages stored in the repository. No public exploit code or active exploitation has been identified at time of analysis, and the high attack complexity requirement (AC:H) limits opportunistic mass exploitation.
Cross-team DAG authorization bypass in Apache Airflow versions prior to 3.3.1 allows authenticated users in one team to trigger DAG runs and read XCom values belonging to other teams. The asset materialization endpoint (POST /api/v2/assets/{asset_id}/materialize) and the XCom check in wait_dag_run_until_finished both passed DagDetails without resolving the DAG's team_name, causing team-aware auth managers (e.g., Keycloak) to evaluate the permission against the global DAG resource instead of the team-scoped DAG:<team> resource. This is a missing authorization flaw (CWE-862) affecting only deployments running multi-team mode with a team-aware auth manager; FAB auth manager deployments are explicitly unaffected. No public exploit code or CISA KEV listing has been identified at time of analysis.
Cross-team credential access in Apache Airflow before 3.3.1 allows authenticated members of one team to invoke another team's Connection credentials through the POST /api/v2/connections/test API endpoint, exploiting a broken namespace-isolation guard in the environment-variable secrets backend. The flaw-confirmed by Apache with patches in PRs #70736 and #70902-combines a guard that only triggered on unscoped (global) requests with a regex incapable of matching team names containing underscores, even though underscores are explicitly permitted in Airflow team name validation. Exploitation requires a precise configuration alignment of multi_team mode, an explicitly enabled test_connection endpoint, and environment-variable-provisioned team secrets; no public exploit has been identified at time of analysis.
Improper authorization in WhatsUp Gold's Scheduled Reports API allows any authenticated user to invoke actions that should be restricted to privileged roles. Affecting all versions prior to 2026.0.2, the flaw (CWE-862, Missing Authorization) means the API enforces authentication but performs no role-based access check on sensitive operations, enabling horizontal or vertical privilege escalation within the application. No public exploit has been identified at time of analysis, and a vendor-released patch is available as of version 2026.0.2.
Package metadata authorization bypass in JFrog Artifactory 7.161.0 through 7.161.15 allows authenticated low-privileged users to read package metadata from repositories they are explicitly denied read access to, under specific undisclosed conditions. The flaw is a missing authorization check (CWE-862) in the metadata access path, creating an unintended privilege boundary crossing within Artifactory's permission model. No active exploitation has been confirmed (no CISA KEV listing) and no public exploit code has been identified, but the network-accessible attack vector with no user interaction required makes this relevant for any multi-tenant or externally accessible Artifactory deployment.
Broken access control in Winter CMS (composer/winter/wn-cms-module ≤ 1.2.12) allows any authenticated backend user holding at least one Theme Editor permission to pivot beyond their authorized scope via crafted AJAX requests. The Cms\Controllers\Index controller gated section access with OR-logic across five permissions but individual handlers - onSave(), onDelete(), onDeleteTemplates(), and AssetList.onUpload() - performed no per-template-type authorization check, enabling cross-template actions such as deleting layouts, modifying partials, reading content files, and uploading arbitrary files to the active theme asset directory. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; vendor-released fix is v1.2.13.
Information disclosure in JFrog Artifactory exposes private Release Bundle metadata to unauthorized parties under two conditions: when anonymous access is globally enabled, or when a low-privilege authenticated account is used. Affected users can enumerate the names and versions of private Release Bundles provided they already know the bundle name, bypassing expected access controls. No public exploit code has been identified and the vulnerability carries a low CVSS score of 3.1, but the missing authorization check (CWE-862) represents a genuine access control gap in sensitive artifact delivery pipelines.
Unauthorized access to restricted support information in JFrog Artifactory allows a low-privileged authenticated user to read sensitive support data under specific, undisclosed conditions. The vulnerability stems from missing authorization controls (CWE-862) on support-related endpoints, exposing information that should be restricted to administrative roles. No public exploit has been identified at time of analysis, and no CISA KEV listing was found.
Authentication bypass in JFrog Artifactory exposes protected repository resources to unauthenticated remote users when specific cache conditions are met. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms exploitation requires no credentials, no user interaction, and no special network position - any user who can reach the Artifactory instance over the network can potentially trigger this condition. No public exploit code exists and this CVE is not listed in the CISA KEV catalog at time of analysis, but the unauthenticated network attack vector elevates real-world concern for internet-facing deployments.
JFrog Artifactory exposes private Puppet module metadata to authenticated users who lack repository read access, constituting a missing authorization control on a specific metadata retrieval endpoint. Any low-privilege user with a valid Artifactory account can silently enumerate Puppet module metadata from repositories they are explicitly denied access to, potentially revealing module names, versions, dependencies, and authorship details. No public exploit code has been identified at time of analysis, and this vulnerability has not been listed in the CISA KEV catalog, though the CVSS 4.3 score reflects a real, network-exploitable authorization bypass with limited but concrete confidentiality impact.
Unauthorized NuGet metadata exposure in JFrog Artifactory allows an authenticated user who lacks repository read permission to read private NuGet feed metadata under specific conditions, constituting a missing authorization control (CWE-862). All versions covered by the CPE wildcard (cpe:2.3:a:jfrog:artifactory:*) appear affected. An attacker with any valid Artifactory account can potentially enumerate or read package metadata from private NuGet repositories they should not have visibility into, leading to information disclosure of internal package names, versions, or dependency structures. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
Unauthorized repository information disclosure in JFrog Artifactory allows unauthenticated remote users to read restricted repository content under specific deployment conditions. Rooted in CWE-862 (Missing Authorization), the flaw bypasses access controls without credentials, confirmed by a PR:N/AV:N CVSS vector. No public exploit code and no CISA KEV listing exist at time of analysis, and the 'specific conditions' qualifier in the vendor's own description limits the realistic attack surface compared to the raw CVSS score suggests.
Incorrect authorization (CWE-863) in JFrog Artifactory allows an authenticated bundle writer to generate misleading release promotion metadata under specific operating conditions, undermining the integrity of the software release pipeline. Affected scope spans all Artifactory versions per the wildcard CPE string, impacting both self-managed and potentially cloud deployments where the bundle writer role is in use. No public exploit code exists and this vulnerability has not been added to the CISA KEV catalog, though the supply-chain integrity risk in production DevSecOps pipelines may exceed the moderate CVSS score.
Insufficient authorization in JFrog Artifactory allows an authenticated user lacking repository read permissions to access private OCI referrer metadata under specific conditions. The flaw maps to CWE-862 (Missing Authorization), meaning the access control check for OCI referrer metadata is absent or bypassed rather than misconfigured. No public exploit or active exploitation has been identified at time of analysis, but the information disclosure could expose artifact relationship graphs and supply chain metadata that organizations intend to keep private.
JFrog Artifactory contains a missing authorization flaw that allows an authenticated user holding a publisher role - but explicitly denied delete permissions - to modify protected package content under specific conditions. This integrity bypass (CWE-862) is reachable over the network without elevated privileges, making it a supply chain risk for organizations using Artifactory as their artifact repository. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Unauthorized read access to restricted JFrog Artifactory content is possible when a credentialed remote repository is configured in a specific non-default manner, triggering a missing authorization check (CWE-862). The flaw affects all Artifactory versions per the CPE wildcard, exposing proprietary artifacts such as internal libraries, Docker images, or build dependencies to network-accessible requests without credential validation. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the high confidentiality impact (C:H in CVSS) means successful exploitation results in full read exposure of the targeted restricted repository.
Docker Sandboxes (sbx) fails to enforce read-only semantics on virtio-fs host mounts: the in-guest bind correctly receives the read-only flag, but the underlying host-edge grant omitted from the policy-share allowlist carries no access mode, leaving the shared-export path fully writable at the host level. Low-privileged code executing inside the sandbox can enumerate or derive the virtio-fs export path and write to host directories the operator explicitly attached as read-only, breaking the isolation guarantee that is the product's core security promise. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Object version metadata exposure in RustFS allows anonymous HTTP clients to enumerate all stored object versions via GET /<bucket>?versions= even after an operator enables RestrictPublicBuckets. The authorization fallback in rustfs/src/storage/access.rs grants listing through an s3:ListBucket check but returns before applying the public-access block controls, silently contradicting the operator's intent to restrict anonymous access. No public exploit has been identified and the vulnerability is not listed in CISA KEV; the vendor-released fix is available in 1.0.0-beta.12.
Authorization bypass in RustFS FTPS MKD handler allows authenticated FTPS users to create S3 buckets in violation of enforced IAM-style policies. All RustFS releases prior to 1.0.0-beta.12 are affected via the `FtpsDriver::mkd` function in `crates/protocols/src/ftps/driver.rs`, which calls `storage.create_bucket` without invoking `authorize_operation` for `S3Action::CreateBucket`. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Versioned object access control bypass in RustFS allows authenticated principals holding only s3:GetObject permission to read historical object versions by supplying an explicit versionId parameter on GetObject, CopyObject source, or UploadPartCopy source requests. The authorization boundary in access.rs conflated two distinct IAM actions - s3:GetObject and s3:GetObjectVersion - by always evaluating versioned reads against the former, effectively collapsing a privileged historical-version operation into an ordinary current-object read. No active exploitation has been confirmed (not in CISA KEV), and no public exploit code has been identified; however, the bypass is trivial to exercise for any valid IAM credential with bucket read access.
Inconsistent authorization enforcement in Vulnerability-Lookup's SSE streaming interface allows self-registered but unconfirmed or inactive accounts to subscribe to Pub/Sub event streams, accessing pre-moderation data that the REST API correctly restricts. The platform's self-registration flow issues an API key before account confirmation is complete, and the token_required decorator on /pubsub/subscribe/<topic> validated only that the key matched a known user - not that the account was active or confirmed. No public exploit has been identified at time of analysis, and a vendor-released patch correcting the authorization gap is confirmed available via upstream commit.
Unauthenticated comment creation in SP Page Builder for Joomla (versions prior to 6.8.0) allows remote attackers to bypass the disabled guest commenting restriction by supplying crafted user input that overrides the server-side access control setting. The vulnerability stems from improper access control (CWE-284), where a client-influenced parameter can override a site administrator's explicit configuration decision to disable public commenting. No public exploit or active exploitation has been identified at time of analysis, and the CVSS 4.0 score of 6.3 reflects limited integrity impact with no confidentiality or availability consequence.
Improper access control in the Cotton Cloud Joomla extension (versions prior to 2.0.3) enables horizontal privilege escalation across user accounts within a shared Joomla installation. Any authenticated user - regardless of privilege level - can read, delete, overwrite, or reassign permissions on files owned by other users, bypassing the extension's intended ACL enforcement. No public exploit code or CISA KEV listing has been identified at time of analysis, though the low attack complexity makes exploitation straightforward for any credentialed user.
Incorrect authorization in Velociraptor's hunt_delete() VQL function grants investigator-role users the ability to permanently delete hunt results, a privilege that should be restricted to administrators holding the DELETE_RESULTS permission. The platform misapplied the COLLECT_CLIENT permission check in place of the DELETE_RESULTS gate, enabling lateral privilege abuse within authenticated sessions. No public exploit or active exploitation has been identified, but the integrity impact is high because hunt data represents forensic evidence collected during incident response operations.
Cross-tenant data exposure in Velociraptor's multi-tenant GUI allows authenticated root-org users to read Stacked result sets belonging to child organizations by bypassing the prefix deny list that enforces datastore path isolation. The GUI endpoint that serves result sets does not correctly validate requested paths against the deny list, so a crafted request can resolve to a sub-org datastore directory the requester should not have access to. No public exploit has been identified and exploitation requires existing high-privilege authenticated access, but the confidentiality impact is significant in shared DFIR environments where tenant isolation is a core security guarantee.
Improper access control in the Cotton Cloud Joomla extension (versions below 2.0.2) by tabaoca.org exposes a broken ACL implementation that allows unauthenticated remote attackers to perform arbitrary file operations - reading, deleting, overwriting, and reassigning permissions - on every file managed within the extension. The network-accessible, zero-authentication attack vector (CVSS 4.0 AV:N/AC:L/PR:N/UI:N) makes exploitation trivially low-effort against any Joomla site running an unpatched Cotton Cloud installation. No public exploit code or active exploitation has been identified at time of analysis, though the attack surface is broad enough that no specialized tooling is required.
Missing authorization on two administrative AJAX endpoints in ProSolution WP Client WordPress plugin before 2.0.9 allows any low-privileged authenticated user - including subscribers - to trigger administrative data synchronization and erase the plugin's activity log. The security nonce protecting these endpoints is exposed in the public-facing frontend, effectively nullifying WordPress's built-in CSRF protection and reducing the attack bar to any account with login access. A public exploit exists via WPScan, though CISA KEV lists no active exploitation and SSVC rates technical impact as only partial.
Insufficient authorization in WP Photo Album Plus (all versions before 9.2.09.002) allows any authenticated WordPress user-including low-privilege Subscriber accounts-to upload files into photo albums owned by other users or administrators. The flaw is rooted in CWE-639 (Authorization Bypass Through User-Controlled Key): the plugin's front-end upload endpoint accepts a caller-supplied album identifier without verifying ownership, enabling cross-user content injection. A publicly available POC exists via WPScan; no active exploitation is confirmed in CISA KEV, and the attack surface is constrained by a non-default configuration prerequisite.
Incorrect authorization in the Cookie Consent WordPress plugin (versions before 0.0.10) allows any authenticated user - including low-privilege roles such as subscribers - to overwrite the plugin's stored geolocation service license key via a REST API route that fails its intended administrator-only capability check and falls back to a weaker authentication-only gate. The practical consequence is silent disruption of geolocation-based consent banner targeting, which can undermine GDPR and regional cookie-consent compliance workflows. Publicly available exploit code exists (no confirmed CISA KEV listing), and an EPSS score of 17% indicates above-average real-world exploitation interest relative to this severity class.
User Access Manager WordPress plugin before version 2.3.15 exposes restricted content to unauthenticated attackers via the WordPress REST API, which the plugin fails to protect with its own access control logic. Any post, page, or custom post type configured to be visible only to specific user groups can be silently read through standard REST API endpoints without credentials. A publicly available proof-of-concept exists (WPScan), and with an EPSS of 15% and automatable exploitation, this is a realistic risk for any WordPress site using this plugin to gate premium or sensitive content.
Reflected Cross-Site Scripting in the WP Photo Album Plus WordPress plugin (all versions before 9.2.07.002) allows unauthenticated attackers to inject arbitrary JavaScript into a victim's browser by reflecting an unsanitized parameter directly into an inline script block on gallery pages. Exploitation requires social engineering - the victim must open a crafted link - but no attacker credentials are needed. A publicly available proof-of-concept exists, reported by WPScan, and EPSS places exploitation probability at 17%, a notably elevated figure for a reflected XSS in a plugin.
Unauthenticated IDOR in WP Travel Engine WordPress plugin before 6.8.5 exposes all customer booking records and stored billing information to any unauthenticated attacker who supplies a valid booking identifier to an unprotected cart action. The root cause is a complete absence of authorization and ownership checks - the plugin accepts a caller-supplied booking ID and processes it without verifying the requestor's identity or entitlement. Beyond disclosure, attackers can overwrite any customer's booking record with their own data, enabling fraud, booking manipulation, or data corruption at travel agencies. A publicly available proof-of-concept exists, and at 15% EPSS this vulnerability is elevated for its CVSS 5.3 rating - warranting prompt attention.
Broken authorization in the Cookie Consent WordPress plugin before 0.0.10 allows any authenticated user - including a subscriber - to invoke administrator-intended REST API endpoints that control consent settings. Affected sites on the vendor's paid plan face an additional confidentiality exposure: the same misconfigured routes permit low-privileged users to read stored visitor consent logs, data that may carry GDPR compliance significance. A publicly available exploit exists, and an EPSS of 18% signals meaningful near-term exploitation probability despite the moderate CVSS score.
WP Crowdfunding WordPress plugin before version 2.2.1 allows any subscriber-level authenticated user to create crowdfunding campaign posts by exploiting a missing capability check in an AJAX action endpoint. The plugin fails to verify whether the requesting user holds the campaign-submission permission, allowing low-privilege WordPress roles to perform actions reserved for higher-privileged users. A publicly available exploit exists via WPScan, and an elevated EPSS of 14% signals meaningful real-world exploitation interest despite no CISA KEV listing.
Insecure Direct Object Reference in WP Crowdfunding (WordPress plugin, all versions before 2.2.1) allows any authenticated user with Subscriber-level access to read personal data from arbitrary WooCommerce orders and enumerate the store's complete order history. The flaw stems from missing order ownership verification, meaning low-privilege accounts - freely obtainable on sites with open registration - can harvest customer PII at scale. A publicly available exploit documented by WPScan exists, and the 14% EPSS score indicates meaningful real-world exploitation interest beyond what the mid-range CVSS score alone suggests.
Broken object-level authorization in the WP Crowdfunding WordPress plugin before 2.2.1 allows any authenticated user - including low-privilege Subscribers - to modify the update history of campaigns they do not own and trigger notification emails to that campaign's backers. The vulnerability stems from missing ownership verification on campaign update endpoints, enabling horizontal privilege escalation across all campaigns on the affected site. A publicly available proof-of-concept exists (reported by WPScan), and the EPSS score of 14% is notably elevated relative to most WordPress plugin flaws, warranting prompt patching on sites hosting active crowdfunding campaigns.
Insecure Direct Object Reference (IDOR) in KiviCare WordPress plugin before 4.5.2 allows any authenticated patient-level user to retrieve bills, invoices, and appointment records belonging to other patients without authorization. The plugin fails to verify record ownership server-side, meaning a low-privilege patient account is sufficient to enumerate and access sensitive healthcare and financial records of arbitrary other patients. A publicly available proof-of-concept exists via WPScan, and the EPSS score of 14% indicates meaningful near-term exploitation probability.
Eventin WordPress plugin versions from 4.1.9 through 4.1.19 exposes customer order records - including personal information - to any contributor-level or higher WordPress user via an Insecure Direct Object Reference (IDOR) flaw. Authenticated users can enumerate order identifiers sequentially to read arbitrary customers' purchase data without authorization. A public proof-of-concept is available via WPScan, and an EPSS score of 14% places this notably above the median for WordPress plugin vulnerabilities, indicating active interest from threat actors even without a CISA KEV listing.
Cross-namespace Secret manipulation in the multicloud-operators-channel component of Red Hat Advanced Cluster Management for Kubernetes 2 (RHACM) enables an authenticated low-privileged user holding specific channel-related permissions to read or modify Kubernetes Secrets outside their authorized namespace scope. The CVSS S:C (Changed Scope) metric confirms the flaw crosses namespace trust boundaries - a critical boundary in multi-tenant Kubernetes environments - potentially exposing credentials, service account tokens, or application secrets belonging to other tenants, and enabling privilege escalation. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Boot partition authentication bypass in CPSD CryptoPro Secure Disk for BitLocker before v7.7.4 allows an attacker who can manipulate disk partition layout to redirect boot-time code execution to a crafted Linux partition. The product fails to cryptographically verify the integrity of the intended boot partition and instead selects the first partition whose type matches a hardcoded value - a logic flaw that allows a spoofed partition to preempt the legitimate boot target and execute arbitrary code at elevated privilege. No public exploit or CISA KEV listing is confirmed at time of analysis, though a Black Hat USA 2026 research presentation by Burch ('The Cost of Obscurity') describes the finding, suggesting detailed technical disclosure has occurred.
Unauthenticated access to Micronaut management endpoints in Kestra prior to 2.0.0-rc6 allows any network-reachable attacker to read fully resolved configuration via GET /env or manipulate runtime log levels via POST /loggers/{name}, bypassing the Basic Auth controls that protect only the primary API on port 8080. The management port (8081) is configured in application.yml with no equivalent authentication gate, making this a structural authentication bypass rather than a misconfiguration edge case. No active exploitation is confirmed (not in CISA KEV) and no public proof-of-concept has been identified at time of analysis.
Authorization bypass in Snipe-IT before 8.6.0 allows any authenticated low-privileged user to cancel other users' pending asset checkout requests by supplying arbitrary values in URL path segments. The checkout-request cancellation endpoint reads `cancel_by_admin` and `requestingUser` directly from user-controlled URL segments without server-side ownership validation, enabling any logged-in user to bypass request-ownership checks. Because asset and user identifiers are sequential integers, a determined attacker can enumerate the full ID space and systematically cancel every pending checkout request platform-wide, disrupting the asset-management workflow. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog; a vendor patch is confirmed in v8.6.0, reported by Tenable (TRA-2026-54).
Path traversal in Red Hat insights-client allows a compromised spoke (managed cluster) to inject unencoded sequences into the Insights API URL path by manipulating the ClusterID value it controls, redirecting authenticated hub-side requests to unintended API endpoints. Affected deployments include any multi-cluster Red Hat Insights configuration where a spoke cluster could be under adversary control. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Bearer token reuse in the acm-search-v2-api-rhel9 component of Red Hat Advanced Cluster Management exposes federated hub search results to unauthorized authenticated users. The `getFederationConfig` cache refresh incorrectly retains one user's token and applies it to all subsequent federated queries until TTL expiry, enabling cross-tenant information disclosure across remote managed hubs. No public exploit has been identified at time of analysis, and the CVSS High Confidentiality rating is tempered by the AC:H timing dependency required for successful exploitation.
Remote code execution in Microsoft Edge (Chromium-based) below version 151.0.4129.78 stems from a type confusion flaw (CWE-843) in the browser engine, exploitable over the network when a user visits or interacts with attacker-controlled content. The vendor has confirmed patch availability and the flaw is tagged as causing memory corruption, which aligns with the typical consequence of type confusion in browser engines. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis, though the unauthenticated network vector with low attack complexity warrants prioritized patching in enterprise environments.
MongoDB Server's sharded cluster transaction coordination is vulnerable to an authorization bypass that allows an authenticated, low-privileged user with direct adjacent-network access to a shard process to illegitimately commit or abort in-progress prepared transactions - actions that are normally reserved for the designated transaction coordinator. Exploitation can produce cross-shard data inconsistency, cluster clock corruption, and broken atomicity guarantees across the distributed database. No public exploit code exists and SSVC confirms no active exploitation; however, successful abuse could silently corrupt application-layer data integrity across the cluster.
Insufficient privilege enforcement in MongoDB Server allows an authenticated user holding only a limited database-scoped role to operate against protected system collections normally restricted to higher-privilege roles. Affected versions span the 7.0, 8.0, and 8.3 release lines. Depending on deployment configuration, exploitation can expose collection metadata or enable unauthorized modification of system collection data. No public exploit has been identified at time of analysis, and SSVC assessment confirms no observed exploitation.
MongoDB Server 8.3.x through 8.3.7 permits certificate-based authentication to succeed for a client holding a valid x.509 certificate and a corresponding user account, even when the administrator has explicitly configured the server to restrict allowable authentication mechanisms to other methods such as SCRAM. The vulnerability undermines deliberate access-control policy decisions rather than enabling unauthenticated access, meaning the attacker must already possess legitimate credential material. With a CVSS 4.0 score of 2.3, CISA SSVC exploitation status of 'none', and no public exploit identified at time of analysis, this is a low-urgency compliance and policy-integrity issue rather than an imminent exploitation threat.
Broken object-level authorization in CVAT's lambda annotation API allows authenticated Worker-role users to exploit predictable task-based request IDs to read automatic annotation requests for tasks they are not permitted to access and to cancel annotation requests submitted by other users. All CVAT deployments running versions 2.17.0 through 2.71.x are affected per cpe:2.3:a:cvat-ai:cvat. No public exploit exists and this vulnerability is not listed in CISA KEV; SSVC assessment confirms no current exploitation, but multi-tenant environments with mixed-trust Worker accounts face meaningful workflow disruption risk.
IPv6 denied-peer-ip bypass in Coturn before 4.16.0 allows an authenticated TURN client to relay traffic to internal IPv6 hosts that fall within a configured blocked range, enabling a TURN-specific server-side request forgery. The root cause is a component-wise (rectangular-box) comparison in addr_less_eq() that fails to enforce the contiguous numerical span [min,max] for non-prefix-aligned IPv6 ranges, so addresses like 2001:db8::1ff are incorrectly classified as outside a denied range of 2001:db8::100-2001:db8::200. No active exploitation is confirmed in CISA KEV, but the flaw carries high subsequent-system impact (CVSS 4.0 SC:H/SI:H/SA:H) and a public GitHub advisory and commit diff are available.
Coturn TURN/STUN server prior to version 4.13.1 exposes an IPv4 access control bypass through incomplete IPv6 address canonicalization, allowing authenticated RFC 6062 TCP CONNECT relay clients to reach peer addresses that administrators intended to block via denied-peer-ip rules. The bypass exploits three IPv4-in-IPv6 encoding formats - IPv4-compatible (::/96), 6to4 (2002::/16), and NAT64 (64:ff9b::/96) - that the peer address validation function failed to normalize before comparing against configured ACL ranges. No active exploitation has been confirmed (not in CISA KEV) and a vendor-released patch is available as version 4.13.1.
Broken access control in Cap v0.3.1's POST /api/video/comment endpoint allows any authenticated user to post comments on arbitrary private videos owned by other users by supplying an attacker-chosen videoId in the request body. Beyond unauthorized commenting, attackers can trigger notification emails to the video owner and enumerate valid private video IDs through response differences, constituting both a confidentiality and integrity breach. No public exploit code or CISA KEV listing has been identified at time of analysis, and the upstream fix has been committed to the Cap GitHub repository.
Privilege escalation in Adobe Commerce and Magento Open Source exposes restricted resources to authenticated high-privilege users through a flawed authorization check (CWE-863). Affected products span the full 2.4.x series of Adobe Commerce and Magento Open Source, plus the 1.3.x-1.5.x Adobe Commerce B2B extension. No public exploits are known, CISA SSVC rates exploitation as none, and vendor-released August 2026 patches are available across all affected release lines per advisory APSB26-92.
Incorrect Authorization in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B allows a network-accessible, high-privileged attacker to bypass platform security controls and gain unauthorized write access, resulting in high integrity and availability impacts. Affected are Adobe Commerce through 2.4.9-2026-jul, Magento Open Source through 2.4.9-2026-jul, and Adobe Commerce B2B through 1.5.3-2026-jul, with August 2026 patches available per Adobe APSB26-92. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Improper input validation in Adobe's Content Credentials ecosystem (Rust SDK, JS SDK, and CLI tool) allows local attackers to bypass C2PA content authenticity security controls and gain unauthorized limited write access to credential metadata. Affected are c2pa-v0.90.5 and earlier, @contentauth/c2pa-web@0.12.0 and earlier, and c2patool-v0.27.5 and earlier. No user interaction is required, but the local attack vector (AV:L) and SSVC automation rating of 'no' constrain realistic exploitation to targeted scenarios rather than mass exploitation.
Information disclosure in Azure CycleCloud allows an authenticated network attacker to bypass authorization checks and read sensitive data. Rooted in CWE-862 (Missing Authorization), the flaw affects versions up to 8.9.2 and is exploitable by any authorized user who can reach the service over a network without elevated privileges. No public exploit or CISA KEV listing has been identified at time of analysis, and Microsoft has released a patch.
Inadequate encryption strength in Windows Active Directory enables a low-privileged authenticated network attacker to bypass a security feature, resulting in a high-integrity impact. Affected platforms span Windows Server 2022, Windows Server 2025, and multiple Windows 11 release channels (23H2 through 26H1). No public exploit identified at time of analysis; SSVC assessment confirms no observed exploitation and the attack is not automatable, placing this in a lower operational urgency tier despite the high integrity impact rating.
Security feature bypass in Microsoft Visual Studio Code Copilot Chat Extension (versions 0.27.0 through pre-1.132.1) enables network-based attackers to circumvent a protective control without authentication, resulting in high integrity impact and low availability impact. The attack requires user interaction - consistent with a scenario where a victim must engage with crafted content delivered over the network. No public exploit code has been identified at time of analysis, and a vendor patch (1.132.1) is available via the Microsoft Security Response Center.
Incorrect authorization in Microsoft SharePoint Server exposes authenticated network attackers to unrestrained content tampering across three supported product lines. The flaw, rooted in CWE-863 (Incorrect Authorization), allows a low-privileged but authenticated user to perform write or modification operations that server-side access controls should restrict to higher-privileged roles. Microsoft has released patches for all three affected versions; no public exploit code or CISA KEV listing exists at time of analysis.
Missing authorization in Microsoft Exchange Server allows authenticated low-privilege network users to bypass a security feature, achieving high-integrity impact without requiring elevated credentials or user interaction. Rooted in CWE-862, Exchange fails to enforce a required authorization check on at least one network-accessible endpoint, enabling unauthorized high-integrity modifications - such as changes to mailbox permissions, transport rules, or security policy - by any valid account holder. No active exploitation is confirmed by CISA KEV, no public exploit code is identified, and Microsoft has released patches across all affected cumulative update tracks.
HTTP request smuggling in System.Net.HttpListener across .NET 8.0, 9.0, and 10.0 enables unauthenticated remote attackers to bypass security features on Linux and macOS deployments. The flaw stems from inconsistent HTTP request interpretation (CWE-444), allowing crafted requests to circumvent authentication or access controls with high confidentiality impact. Exploitation carries high attack complexity (AC:H), no public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV, placing this in a monitored-but-not-emergency posture for most organizations.
Insufficiently protected credentials in Microsoft Office Outlook expose authentication material over network connections, enabling unauthenticated network-positioned attackers to perform spoofing attacks contingent on victim user interaction. The flaw affects Outlook 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, and Microsoft 365 Apps for Enterprise - collectively spanning nearly the entire current Outlook product line. Microsoft has released a patch; no public exploit or active exploitation (CISA KEV) has been identified at time of analysis.
Incorrect authorization in the Windows Container Isolation FS Filter Driver (unionfs.sys) allows a local authenticated attacker on Windows 11 26H1 to disclose sensitive information beyond their authorized filesystem scope. The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) confirms high confidentiality impact confined to the local system, with no integrity or availability consequence. No public exploit code exists and SSVC rates exploitation as none, placing this as a routine patching priority rather than an emergency response item.
Authentication bypass in Windows Schannel allows a network-based attacker to circumvent cryptographic signature validation, achieving high-integrity impact without requiring prior privileges. Schannel, Microsoft's TLS/SSL security provider, fails to properly verify cryptographic signatures - tagged as a JWT attack vector - enabling forged or malformed tokens to pass validation and bypass security feature enforcement. No active exploitation is confirmed (SSVC: exploitation=none; not listed in CISA KEV), and the high attack complexity and required user interaction constrain opportunistic mass exploitation despite the broad Windows version footprint.
Tampering via partial string comparison in the Windows HTTP Protocol Stack (http.sys) exposes a broad range of Windows client and server editions to integrity compromise by unauthenticated adjacent-network attackers. Affected platforms span Windows 10 1607 through Windows 11 26H1 and Windows Server 2012 through Server 2025, with Microsoft tagging the issue as an authentication bypass rooted in CWE-187. No public exploit has been identified at time of analysis, and Microsoft has released patched builds across all affected product lines.
Windows Defender Firewall Service across Windows 10, Windows 11, and Windows Server 2019 through 2025 contains a missing authorization flaw (CWE-862) that enables a locally authenticated low-privileged attacker to bypass firewall security controls and manipulate firewall rules without the required authorization. The vulnerability carries a CVSS score of 5.5 with High integrity impact, reflecting the attacker's ability to fully undermine the local firewall enforcement boundary from a standard user session. No public exploit code or CISA KEV listing has been identified at time of analysis, though the post-exploitation value as a lateral movement enabler is notable given the breadth of affected Windows versions.
Certificate validation bypass in Adobe's Content Credentials SDK undermines the C2PA provenance chain across three SDK variants - JavaScript/WASM (@contentauth/c2pa-web through 0.12.0), Rust (c2pa through v0.90.5), and CLI (c2patool through v0.27.5) - allowing an attacker-controlled certificate to be accepted as legitimate when a victim visits a malicious URL or interacts with a compromised web page. Successful exploitation grants unauthorized write access to content credentials, enabling an attacker to forge provenance metadata and defeat the product's core integrity guarantee. No public exploit has been identified at time of analysis; vendor-released patches exist for all three affected SDK variants.
Improper input validation across Adobe's Content Credentials JS SDK, Rust SDK, and command-line tool allows a remote unauthenticated attacker to bypass integrity verification and gain unauthorized write access to C2PA-signed content metadata. All three SDK components prior to their respective patch releases are affected, and exploitation requires a victim to visit a maliciously crafted URL or interact with a compromised web page. No public exploit code or active exploitation has been identified at time of analysis, though the write-impact on content authenticity signals carries meaningful trust implications for downstream consumers.