Information Disclosure
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
How It Works
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security. This happens through multiple channels: verbose error messages that display stack traces revealing internal paths and frameworks, improperly secured debug endpoints left active in production, and misconfigured servers that expose directory listings or version control artifacts like .git folders. APIs often leak excessive data in responses—returning full user objects when only a name is needed, or revealing system internals through metadata fields.
Attackers exploit these exposures systematically. They probe for common sensitive files (.env, config.php, backup archives), trigger error conditions to extract framework details, and analyze response timing or content differences to enumerate valid usernames or resources. Even subtle variations—like "invalid password" versus "user not found"—enable account enumeration. Exposed configuration files frequently contain database credentials, API keys, or internal service URLs that unlock further attack vectors.
The attack flow typically starts with passive reconnaissance: examining HTTP headers, JavaScript bundles, and public endpoints for version information and architecture clues. Active probing follows—testing predictable paths, manipulating parameters to trigger exceptions, and comparing responses across similar requests to identify information leakage patterns.
Impact
- Credential compromise: Exposed configuration files, hardcoded secrets in source code, or API keys enable direct authentication bypass
- Attack surface mapping: Stack traces, framework versions, and internal paths help attackers craft targeted exploits for known vulnerabilities
- Data breach: Direct exposure of user data, payment information, or proprietary business logic through oversharing APIs or accessible backups
- Privilege escalation pathway: Internal URLs, service discovery information, and architecture details facilitate lateral movement and SSRF attacks
- Compliance violations: GDPR, PCI-DSS, and HIPAA penalties for exposing regulated data through preventable disclosures
Real-World Examples
A major Git repository exposure affected thousands of websites when .git folders remained accessible on production servers, allowing attackers to reconstruct entire source code histories including deleted commits containing credentials. Tools like GitDumper automated mass exploitation of this misconfiguration.
Cloud storage misconfigurations have repeatedly exposed sensitive data when companies left S3 buckets or Azure Blob containers publicly readable. One incident exposed 150 million voter records because verbose API error messages revealed the storage URL structure, and no authentication was required.
Framework debug modes left enabled in production have caused numerous breaches. Django's DEBUG=True setting exposed complete stack traces with database queries and environment variables, while Laravel's debug pages revealed encryption keys through the APP_KEY variable in environment dumps.
Mitigation
- Generic error pages: Return uniform error messages to users; log detailed exceptions server-side only
- Disable debug modes: Enforce production configurations that suppress stack traces, verbose logging, and debug endpoints through deployment automation
- Access control audits: Restrict or remove development artifacts (
.git, backup files,phpinfo()) and internal endpoints before deployment - Response minimization: API responses should return only necessary fields; implement allowlists rather than blocklists for data exposure
- Security headers: Deploy
X-Content-Type-Options, remove server version banners, and disable directory indexing - Timing consistency: Ensure authentication and validation responses take uniform time regardless of input validity
Recent CVEs (73549)
XML External Entity (XXE) injection and recursive entity expansion in WSO2's SchemaValidator Mediator expose server-side file contents and enable SSRF across a broad range of WSO2 API management products. Exploitation requires a highly privileged actor - confirmed by PR:H in the CVSS vector - who can supply crafted XML payloads to affected mediator flows, triggering unauthorized outbound requests, server file reads, or resource exhaustion that degrades service availability. Vendor patches are available for all listed affected versions; no public exploit code or CISA KEV listing has been identified at time of analysis.
Use-After-Free in Autodesk Revit's PDF parser allows arbitrary code execution, sensitive data disclosure, or application crash when a user opens a maliciously crafted PDF file. Affected versions span Revit 2026 (prior to 2026.5.0) and Revit 2027 (prior to 2027.2.0), with full high-impact potential across confidentiality, integrity, and availability. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis; a vendor patch is available via advisory ADSK-SA-2026-0011.
Sandbox escape in Google Chrome prior to 151.0.7922.109 enables a remote attacker who has already compromised the renderer process to break out of Chrome's OS-level security sandbox via a crafted HTML page. This is a second-stage, chained vulnerability - not directly exploitable in isolation - making it a high-value component in multi-step browser attacks that pair a renderer exploit with this UI input validation flaw to achieve full OS-level code execution. No public exploit has been identified and SSVC rates exploitation status as none at time of analysis, though the total technical impact and confirmed scope change (S:C) make this a critical priority when chained with any renderer compromise.
Sandbox escape in Google Chrome's Codecs component (versions prior to 151.0.7922.109) allows a remote attacker to break out of the renderer sandbox when a victim views a crafted HTML page, via insufficient validation of untrusted input (CWE-20). Rated CVSS 9.6 with a changed scope, the flaw affects the desktop Stable channel across all platforms and is fixed in 151.0.7922.109. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Sandbox escape in Google Chrome prior to 151.0.7922.109 allows a remote attacker who has already compromised the renderer process to break out of Chrome's isolation boundary via a crafted HTML page exploiting insufficient Navigation policy enforcement (CWE-693). This is a second-stage exploit primitive: it elevates a sandboxed renderer breach into full host OS code execution at browser-process privilege, crossing Chrome's core security boundary as reflected in the CVSS Scope:Changed metric. No public exploit code or CISA KEV listing has been identified at time of analysis; the vendor-confirmed patch shipped in the 151.0.7922.109 stable channel update.
Sandbox escape in Google Chrome on Android prior to 151.0.7922.109 is achievable by a local attacker via a malicious file exploiting insufficient input validation in WebAPK processing. The CVSS scope change (S:C) with high confidentiality, integrity, and availability impacts reflects the potential for full breakout beyond Chrome's sandbox boundary into the broader Android process space. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch is available in the stable channel release.
Supply-chain compromise of the Supsystic Pro WordPress plugin family delivered trojanized plugin updates from the vendor's own compromised update server, giving unauthenticated attackers a foothold on every site that pulled the poisoned release. The embedded malicious code fetches a second-stage payload that harvests credentials and other sensitive data and hands the operator full control of the affected WordPress site. Reported by WPScan; no public exploit is identified and the issue is not listed in CISA KEV at time of analysis, though the delivery mechanism means the implant is effectively pre-planted rather than requiring an active attack against each target.
Price allowlist bypass in WPC Name Your Price for WooCommerce (WordPress plugin before 2.2.5) permits unauthenticated visitors to submit arbitrary below-minimum prices for products configured in "Select" mode, resulting in real completed orders at merchant-disadvantageous amounts and direct revenue loss. The flaw is a distinct business logic failure left unaddressed by the CVE-2025-12115 patch (v2.2.0), which only corrected a related but separate vector involving products with Name Your Price disabled. No public exploit identified at time of analysis, though the attack requires no authentication and is trivially executable against any vulnerable storefront with a Select-mode product.
Unlimited OTP brute-force in the miniOrange 2FA WordPress plugin before 6.2.8 allows a network attacker who already possesses a target user's password to bypass two-factor authentication entirely and achieve full account takeover. The flaw lies in rate-limit tracking being anchored to a client-supplied identifier that is reissued on every login attempt, meaning the attempt counter resets on demand and never accumulates. No public exploit has been identified at time of analysis, and the plugin is not listed in CISA KEV; however, the impact is total authentication bypass for any account protected by the plugin.
Payment bypass in Payment Gateway for Redsys & WooCommerce Lite before version 7.0.2 allows unauthenticated remote attackers to complete WooCommerce orders without actual payment by forging payment-provider callback notifications. The plugin fails to cryptographically verify the authenticity of inbound payment confirmations for at least one of its payment methods, meaning any actor who can reach the callback endpoint can submit a fabricated notification and have orders marked as paid. No public exploit code or CISA KEV listing has been identified at time of analysis, though the attack requires only network access and minimal technical skill.
Supply-chain compromise of MonsterInsights Pro, a widely used WordPress Google Analytics plugin, delivered a malicious file (class-system-check.php) through the vendor's own S3 update bucket (monster-insights.s3.amazonaws.com). Both the current release (10.2.2) and the 10.2.0 build the vendor rolled back to are trojaned, so administrators who updated - or downgraded to remediate - received attacker-controlled PHP that runs with full site privileges. WPScan reports the attacker still holds write access to the bucket and was iterating on three AES-256-GCM payload variants on 2026-06-11; there is no CISA KEV listing and no public exploit code, but the malicious distribution is described as active and ongoing by the reporter.
Out-of-bounds read in Autodesk Revit's PDF parsing engine exposes users to crashes, sensitive memory disclosure, and arbitrary code execution within the Revit process when opening a maliciously crafted PDF file. Affected are users of Autodesk Revit across versions covered by advisory ADSK-SA-2026-0011, with the attack requiring only that a target be socially engineered into opening a weaponized PDF - a realistic threat vector for AEC-industry professionals who routinely exchange PDF documents. No public exploit code has been identified at time of analysis, and no CISA KEV listing exists, though the high C/I/A impact profile makes this a meaningful risk for targeted attacks against Revit users.
Price manipulation in the CoCart WordPress plugin before 4.9.0 allows unauthenticated remote attackers to purchase WooCommerce products at arbitrarily low prices by supplying a manipulated price value through the plugin's public REST API cart endpoint. The server accepts the attacker-controlled price without comparing it to the canonical product price, enabling completed orders at near-zero cost and direct financial loss to store operators. No public exploit code or CISA KEV listing has been identified, but the CVSS:3.1/AV:N/AC:L/PR:N/UI:N vector indicates this is trivially exploitable against any default-configured CoCart deployment.
Quadratic-time denial of service in league/commonmark versions 0.6.0 through 2.8.3 allows remote unauthenticated attackers to exhaust PHP worker processes by submitting a single specially crafted Markdown line. The root cause is a character-vs-byte position mismatch in the UTF-8-aware parser: lines containing non-ASCII characters trigger repeated full-line rescans that scale as O(n²) with line length, and a second independent quadratic path exists in the AutolinkExtension. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the attack fits within a single HTTP request and requires no authentication, making it operationally straightforward once the pattern is known.
Cross-user HTTP response poisoning in Traefik's default reverse proxy allows an unauthenticated remote attacker using HTTP/2 or HTTP/3 to smuggle responses into other clients' backend connections, potentially delivering authenticated or private content from one user to another. All supported Traefik branches through v2.11.52, v3.6.23, and v3.7.8 are affected in default configuration when fronting Go net/http or gunicorn/Flask backends, which are confirmed 'armed' (respond to CONNECT with keep-alive non-2xx without draining the body). A proof-of-concept is publicly available demonstrating reliable cross-user poisoning including a cascade scenario where 8 of 8 sequential victims read responses that were not their own; no CISA KEV listing was present at time of analysis.
Quadratic CPU and memory exhaustion in html_sanitize_ex affects all applications that accept user-supplied HTML for sanitization, regardless of scrubber configuration. The traversal engine's list clause performs a redundant List.flatten over the entire remaining sibling tail at every recursion step, making sanitization cost O(n²) in sibling count rather than O(n). A 160 KB input of 20,000 sibling elements monopolizes a BEAM scheduler for approximately 1.7 seconds per request; no public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV, but the attack requires no authentication and no special server configuration.
Denial of service (and possibly information disclosure) in the Apache Portable Runtime Utility (APR-util) library through version 1.6.3 lets remote attackers crash any consumer that parses attacker-supplied XML via apr_xml_quote_elem(). The flaw is an uncontrolled stack recursion (CWE-674) triggered by deeply nested or malicious XML; no authentication or user interaction is required. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the CISA SSVC framework rates it automatable, so scanning-driven abuse is plausible.
Local File Inclusion in the e2pdf WordPress plugin (versions up to and including 1.32.40) enables unauthenticated remote attackers to include arbitrary PHP files from the server filesystem, potentially yielding full confidentiality, integrity, and availability compromise. Reported by Patchstack and registered under ENISA EUVD-2026-53913, the flaw stems from CWE-98 (PHP file inclusion without proper input sanitization). No public exploit code or CISA KEV entry has been identified at time of analysis, but the network-accessible, zero-authentication attack path makes patching a priority for any WordPress operator running this plugin.
Sensitive subscriber data exposure in the Vimeo WordPress plugin (versions 1.2.2 and earlier) allows unauthenticated remote attackers to retrieve confidential subscriber information via network requests. Reported by Patchstack and tracked as EUVD-2026-53973, the flaw is rooted in CWE-201 (Insertion of Sensitive Information Into Sent Data), meaning the plugin actively includes protected subscriber data in responses that should not be accessible without authorization. No public exploit code has been identified at time of analysis, and the vulnerability has not been listed in the CISA KEV catalog.
Super Socializer plugin for WordPress (versions ≤ 7.14.5) contains a broken authentication vulnerability (CWE-288) that permits unauthenticated remote attackers to bypass the social login authentication mechanism and gain unauthorized access to WordPress user accounts. The CVSS vector (AV:N/AC:L/PR:N/UI:R) indicates low-complexity network exploitation requiring victim interaction, consistent with a social login callback or token-verification bypass where a victim must initiate or interact with the login flow. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the high CVSS score (8.8) and full C/I/A impact reflect the potential for complete account takeover.
Sensitive information disclosure in Dell Virtual Storage Integrator (VSI) for VMware vSphere Client, all versions prior to 10.11.1.0, lets an unauthenticated remote attacker retrieve active session credentials and hijack authenticated sessions, including those of administrators. Because stolen session tokens grant full impersonation of legitimate users, Dell rates this critical (CVSS 9.8); there is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the SSVC framework flags it as automatable with total technical impact. EPSS remains low at 0.39% (32nd percentile), consistent with the absence of observed exploitation to date.
Information disclosure and tampering in Dell RVTools collector versions prior to 4.8.1 stems from improper certificate validation (CWE-295), letting a remote unauthenticated attacker in a machine-in-the-middle position intercept or alter data exchanged between the collector and its target. Rated CVSS 9.1 (C:H/I:H) but with A:N, the flaw affects the popular VMware vSphere inventory-reporting utility. No public exploit is identified at time of analysis; EPSS is low at 0.14% and SSVC lists exploitation as none.
Double-spending of OAuth2 authorization codes in Apache CXF's JCacheCodeDataProvider enables issuance of multiple valid access tokens from a single code. Concurrent requests to the token endpoint during the brief window between code validation and invalidation exploit the TOCTOU race condition (CWE-367), allowing an attacker in possession of a valid authorization code to obtain additional access tokens beyond the one they are entitled to. No public exploit has been identified at time of analysis, and fixed versions are available across all maintained branches.
Authorization scope escalation in Apache CXF's OAuth2 Dynamic Client Registration endpoint allows any registering client to self-assign privileged scopes by supplying arbitrary `scope` values in the registration request, which the authorization server stores verbatim without validating against a server-defined allowlist. Affected versions span the 3.x, 4.1.x, and 4.2.x release lines; patched releases 3.6.12, 4.1.8, and 4.2.3 are available per the Apache advisory. No public exploit or active exploitation has been identified at time of analysis, but the straightforward exploitation path - crafting a single registration request - makes this a meaningful authorization bypass risk for any deployment exposing CXF's OAuth2 AS with Dynamic Client Registration enabled.
Apache CXF's JwtRequestCodeFilter blindly copies all claims from a validly-signed JWT request object into the OAuth2 authorization parameter map, including security-sensitive fields that must not be client-controlled: code_challenge, code_challenge_method, nonce, and state. Affected are all Apache CXF deployments using this filter for OAuth2/OIDC authorization code flows prior to versions 4.2.3, 4.1.8, and 3.6.12. An OAuth2 client with a known or compromised client_secret can craft a signed request JWT that overrides the PKCE parameters established in the outer HTTP request, effectively nullifying PKCE authorization code binding and OIDC replay protection. No public exploit code or CISA KEV listing has been identified at time of analysis.
Apache CXF's DefaultEncryptingCodeDataProvider allows captured OAuth 2.0 authorization codes to be redeemed an unlimited number of times, violating RFC 6749's single-use requirement. The removeCodeGrant() method that should invalidate a code after first exchange fails to do so, meaning any attacker who intercepts or obtains a legitimate authorization code can replay it repeatedly to obtain additional access tokens. No public exploit has been identified at time of analysis, and the issue is addressed in patched releases 4.2.3, 4.1.8, and 3.6.12.
Token revocation bypass in Apache CXF's DefaultEncryptingOAuthDataProvider allows revoked OAuth access and refresh tokens to remain functionally valid indefinitely - the provider continues to decrypt them successfully and TokenIntrospectionService returns active:true in direct violation of RFC 7009 and RFC 7662 mandates. All Apache CXF deployments using this built-in OAuth data provider and relying on token revocation as a security control are affected across the 3.6.x, 4.1.x, and 4.2.x branches. An attacker or suspended user who retains a revoked token can continue accessing protected resources as though revocation never occurred, bypassing intended authorization boundaries. No public exploit has been identified at time of analysis, though the attack requires no tooling beyond a standard HTTP client.
Server-Side Request Forgery in Foxit PDF Services API allows low-privileged remote attackers to bypass local file access restrictions by embedding redirect-chain URLs in PDF creation requests, causing the server to fetch arbitrary internal resources and disclose sensitive information. The CVSS vector (S:C/C:H) confirms the scope change extends to internal backend systems inaccessible to the attacker directly, making this a meaningful lateral-visibility primitive in environments where the API reaches internal network segments. No public exploit identified at time of analysis, and no KEV listing, though the low attack complexity elevates urgency for internet-exposed deployments.
Use-after-free in the Linux kernel ALSA driver for TASCAM US-144MKII USB audio devices allows a local low-privileged attacker to corrupt kernel memory, with potential for privilege escalation. The flaw originates in capture_urb_complete(), where redundant usb_anchor_urb() calls on every URB completion progressively corrupt the anchor's doubly-linked list and inflate the URB reference count; when usb_kill_anchored_urbs() later traverses this list during stream stop, suspend, or device disconnect, it dereferences freed memory. No public exploit or CISA KEV listing exists, and EPSS at 0.17% (6th percentile) reflects the narrow exposure created by the required TASCAM hardware dependency.
Use-after-free in the Linux kernel's Amlogic GXL crypto driver (`crypto/amlogic`) allows a local attacker to trigger memory corruption during driver probe failure, potentially enabling privilege escalation or denial of service on affected kernels (5.5 through pre-patch stable branches). The double-cleanup defect in `meson_crypto_probe()` causes `meson_free_chanlist()` to tear down already-freed per-flow resources - confirmed via KASAN slab-use-after-free in `kthread_destroy_worker()` - when `meson_allocate_chanlist()` fails after partial initialization. No public exploit identified at time of analysis; EPSS is 0.16% (6th percentile), consistent with the narrow hardware footprint and non-trivial triggering conditions.
Memory corruption (double-free) in the Linux kernel's SMB/CIFS client SMB2_close replay path can be triggered when a mounted SMB server returns a replayable error and a subsequent SMB2_close_init() fails, causing the same response buffer to be freed twice. It affects Linux stable kernels across the 6.6.x through 7.x series before the fixed releases; while the CNA-assigned CVSS is 9.8 with no public exploit identified at time of analysis, real-world abuse requires the victim host to communicate with a malicious or compromised SMB server, making this primarily a client-side memory-corruption/DoS concern rather than trivial remote code execution.
Memory ordering data races in the Linux kernel's fuse-uring subsystem expose weakly-ordered architecture systems (ARM64, PowerPC, RISC-V) to kernel-level impacts when the fuse-uring ring initializes. On kernels from commit c2c9af9a through the fix, missing acquire/release semantics around ring->ready and fiq->ops allow a CPU to observe ring->ready == true while reading a stale fiq->ops function pointer table, which could trigger undefined behavior ranging from kernel crashes to potential control-flow hijacking. No public exploit has been identified and EPSS sits at 0.15% (5th percentile), indicating low near-term exploitation probability despite the High CVSS rating; no CISA KEV listing confirms active exploitation.
Race condition in the Linux kernel's ARC EMAC Ethernet driver exposes a use-after-free window during driver probe teardown on ARC processor-based embedded systems. When probe unwinds after devm_request_irq() installs the interrupt handler, stale or firmware-latched EMAC interrupt status bits can fire arc_emac_intr() concurrently with net_device deallocation, potentially corrupting kernel memory. Patched versions are available across all active stable branches (5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.19, 6.19.9, 7.0); no public exploit or CISA KEV entry exists at time of analysis.
Use-after-free in the Linux kernel esd_usb CAN driver exposes local privilege escalation on systems using ESD CAN USB hardware. The esd_usb_disconnect() teardown sequence frees each CAN netdev (and its embedded private struct) before calling unlink_all_urbs(), which then dereferences that already-freed per-netdev memory to kill TX anchors and reset TX contexts. Found by an in-house static analysis tool with no public exploit identified at time of analysis; EPSS is 0.16% (6th percentile), consistent with a niche driver defect rather than a broadly targeted flaw.
Use-after-free in the Linux kernel's USB MIDI gadget driver (f_midi) exposes systems configured as USB MIDI gadgets to local privilege escalation or denial-of-service. The flaw stems from midi->work not being cancelled before struct f_midi is freed in f_midi_free(), allowing a concurrent ALSA rawmidi write via f_midi_in_trigger() to rearm the work item after f_midi_disable() returns but before the object is deallocated - causing f_midi_in_work() to dereference freed kernel memory. No public exploit has been identified and EPSS sits at 0.16% (5th percentile), but the CVSS 7.8 score and kernel-level impact make patching the correct priority on systems deploying USB gadget functionality.
Use-after-free and NULL pointer dereference in the Linux kernel Broadcom BDC USB Device Controller driver expose systems to local privilege escalation during device teardown. The BDC driver's teardown sequence frees DMA-coherent memory and endpoint arrays while a shared IRQ handler remains live - a structural defect introduced when the driver adopted devm_request_irq(), whose LIFO devm release order creates a window where the interrupt handler dereferences freed or NULLed kernel structures. A separately unguarded delayed_work (func_wake_notify) compounds the issue with no cancellation path anywhere in the driver, allowing post-teardown callbacks against freed memory. No public exploit exists and the vulnerability is not in CISA KEV; it was identified by in-house static analysis with EPSS at the 5th percentile (0.16%), indicating negligible current exploitation activity.
Unauthenticated information disclosure in the Gutenberg Essential Blocks WordPress plugin before 6.4.0 exposes published content from custom post types that site administrators deliberately registered as non-public. The plugin's public REST API route queries arbitrary post types supplied by the caller without first verifying their visibility setting, bypassing the access control intent of the post type registration. A publicly available proof-of-concept exists; EPSS sits at 0.14% (4th percentile) suggesting exploitation remains rare despite automatable conditions, and the vulnerability is not currently listed in the CISA KEV catalog.
Unauthenticated information disclosure in Gutenberg Essential Blocks for WordPress (versions before 6.4.0) exposes WooCommerce per-product lifetime sales unit counts to any internet user via an unrestricted public REST API route. The plugin over-fetches a non-public WooCommerce metric and surfaces it in the REST response without access control enforcement, meaning competitors, scrapers, or threat actors can query sales volumes for any published product on affected stores. A publicly available proof-of-concept exploit exists per WPScan, and SSVC assessment confirms the attack is automatable; however, EPSS sits at just 0.14% (4th percentile), indicating limited observed exploitation at time of analysis.
Events Manager WordPress plugin before version 7.4 exposes an unauthenticated REST API endpoint that serves temporarily stored file uploads without any authorization check, enabling an attacker who has obtained a victim's high-entropy temporary upload identifier to retrieve that user's in-progress file submission. Classified as CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), the flaw represents a missing permission_callback on a WordPress REST route - effectively an IDOR variant against ephemeral upload objects. A public POC is available via WPScan; no CISA KEV listing exists, and the EPSS score of 0.14% (4th percentile) reflects the practical constraint imposed by identifier acquisition being the dominant bottleneck.
Unauthenticated CPU exhaustion in Nuxt's island renderer endpoint allows remote attackers to degrade or stall server availability without any credentials or valid hash. Nuxt versions 3.1.0-3.21.9 and 4.0.0-4.5.0 are affected: the `/__nuxt_island/` handler fully buffers, destr-parses, and ohash-hashes attacker-supplied POST bodies before checking the URL-embedded hash token, meaning expensive computation runs on doomed requests. Because Nitro's runtime executes on a single Node.js event loop, a sustained low-rate flood of ~4.6 MB JSON bodies is sufficient to stall all concurrent legitimate requests. No public exploit code or CISA KEV listing exists, but the attack is trivially reproducible from the published advisory description alone.
Authorization gate bypass in Nuxt (npm package, versions 3.21.7-<3.21.10 and 4.4.7-<4.5.1) allows unauthenticated network access to routes protected by appMiddleware auth rules whenever those route-rule keys contain uppercase characters. This is an incomplete fix for CVE-2026-53721: the prior patch case-folded the lookup path before matching route rules, but left the compiled rule keys verbatim, producing a permanent symmetric mismatch that silently drops all app-level protections for any mixed-case route. No public exploit has been identified at time of analysis; however, the vulnerable condition arises automatically in any Nuxt application deriving route rules from PascalCase page files (e.g., pages/Admin.vue) or writing mixed-case routeRules keys explicitly.
Cross-user SSR payload disclosure in Nuxt 4.x allows unauthenticated network attackers to retrieve another authenticated user's full server-side rendered data by fetching `/<page>/_payload.json` after any authenticated user has warmed a cached route. The runtime `cache:nuxt:payload` storage introduced in nuxt 4.4.0 keyed payloads by URL path alone - omitting cookie, authorization header, or `cache.varies` dimensions - causing the renderer to serve one user's SSR data (including `useFetch`/`useAsyncData` results such as profile, tenant, billing, and token-like values) to any subsequent requester. No public exploit identified at time of analysis; vendor-released patch is available as nuxt@4.5.1.
Integrity tampering in Thermo Fisher Applied Biosystems Genetic Analyzers allows any user with local file system access to silently modify .fsa and .hid output files - the raw DNA sequence and fragment analysis data produced by these instruments - because no cryptographic integrity check (CWE-353) is applied to these files. Affected products span eight distinct data collection and analysis software lines, including the forensic-grade GeneMapper ID-X platform, meaning tampered files could propagate falsified DNA profiles into criminal proceedings or clinical diagnostics without detection. No public exploit code has been identified at time of analysis, and exploitation is covered by CISA ICS Medical Advisory ICSMA-26-216-01.
Full unauthenticated access to Livebook 0.19.7-0.19.9 is possible when a Livebook Agent or App Server's deployment group is deleted from Livebook Teams while the agent is temporarily disconnected. A logic error in `Livebook.Hubs.TeamClient.handle_call/3` causes the zero-trust authentication layer to treat an unresolvable cached deployment group identifier identically to one with identity enforcement deliberately disabled, allowing any network-reachable client to read notebooks and secrets, execute code on the server runtime, and disrupt operations without authentication. No public exploit has been identified at time of analysis, and no CISA KEV listing is present, but the high confidentiality, integrity, and availability impact (CVSS 4.0: 7.7) warrants prompt patching for all Teams-connected deployments.
Untrusted JavaScript rendered in Livebook notebook outputs can escape the sandboxed cross-origin iframe and trigger session-wide keyboard shortcuts, causing forced execution of all notebook cells without user consent. Livebook versions 0.5.0-0.18.6 and 0.19.0-0.19.8 are affected; a user who merely opens a third-party or documentation-linked notebook can have its Elixir code automatically evaluated on their runtime. Because cell outputs are mirrored to every connected client, a single malicious notebook load can trigger the exploit simultaneously across all collaborators in the session. No public exploit or CISA KEV listing is identified at time of analysis, but the low-friction attack path - open a notebook, get code executed - represents a meaningful social-engineering risk.
Cross-user chat history disclosure in IBM Langflow OSS 1.0.0-1.10.3 allows any authenticated user to read other users' conversation history by exploiting session_id collision in the MemoryComponent. The MemoryComponent.retrieve_messages and store_message methods validate only session_id when filtering records, omitting flow_id and user_id ownership checks, which exposes multiple REST API endpoints to unauthorized cross-user data access. No public exploit has been identified at time of analysis, but the straightforward exploitation path and High confidentiality impact make this a genuine remediation priority for any multi-user Langflow deployment.
Predictable Fernet encryption keys in IBM Langflow OSS 1.0.0 through 1.10.3 allow attackers to decrypt stored API keys and authentication tokens, because when a user secret is shorter than 32 characters the platform derives keys with Python's non-cryptographic `random` (Mersenne Twister) module. Because the Mersenne Twister PRNG is deterministic, identical seeds reproduce identical keys, so an adversary who can reconstruct the seeding conditions can regenerate the key and read every secret Langflow encrypted with it. No public exploit identified at time of analysis; EPSS is low (0.11%) and CISA SSVC records no known exploitation.
Predictable Fernet encryption key generation in IBM Langflow OSS (versions 1.0.0 through 1.10.3) stems from the ensure_fernet_key() function deriving keys from a cryptographically weak source (CWE-338), letting an attacker reconstruct the symmetric key that protects stored secrets such as API keys, credentials, and connection variables. Because the key is guessable rather than random, an actor who can read Langflow's encrypted data store can decrypt it and, depending on how the key is reused, potentially forge or tamper with protected values. There is no public exploit identified at time of analysis and EPSS is low (0.21%, 11th percentile), but IBM rates the flaw CVSS 9.8 and a vendor patch is available.
Sandboxed iframe popup restriction bypass in Electron allows untrusted iframe content to open new windows or trigger `setWindowOpenHandler` without user interaction, despite the `allow-popups` keyword being absent from the sandbox attribute. Electron versions prior to 42.0.1, 41.10.3, and 39.8.10 are affected. The bypass occurs because `FrameLoader::StartNavigation` and `WebContents::OpenURLFromTab` in the OpenURL code path did not check the iframe's sandbox popup flags, permitting emulated Ctrl+click events from untrusted JavaScript to create new browsing contexts. No public exploit or CISA KEV listing is confirmed at time of analysis, but the patch diff includes a working proof-of-concept test.
Remote availability disruption in Cisco Catalyst SD-WAN Manager and Controller allows a low-privileged authenticated attacker over the network to cause high-availability impact with scope change - affecting resources beyond the directly targeted component. Discovered internally by Cisco's SD-WAN engineering team during a proactive security review and addressed in software hardening releases, this vulnerability is not confirmed as actively exploited (not in CISA KEV) and no public exploit code is known at time of analysis. The CVSS 7.7 (High) score reflects the combination of network accessibility, low authentication bar, no user interaction required, and high availability consequence with scope change.
Host filesystem read and write access in IBM Langflow OSS 1.0.0 through 1.10.3 is achievable by any authenticated low-privilege user via insufficient filtering of Docker volume-mount and device-mapping arguments passed to Docker-based MCP servers. By injecting unsanitized flags such as --volume into MCP server configuration, an attacker can bind-mount arbitrary host directories into a spawned container, exposing or tampering with sensitive files outside the intended Docker isolation boundary. No public exploit code has been identified at time of analysis and no CISA KEV listing exists, but the network-exploitable, low-complexity attack path and full CIA impact score (CVSS 8.8) make this a high-priority patch target for any organization running Langflow in Docker environments with externally accessible or multi-tenant access.
Cleartext storage of sensitive information in Cisco Catalyst SD-WAN Controller and Manager exposes credentials or other security-critical data to authenticated network-accessible attackers, with CVSS 8.8 reflecting the high potential for full system compromise via stolen credentials. Affecting an extraordinarily wide version range spanning 17.2.x through 20.14.x across both the Controller and Manager components, this vulnerability was discovered internally by Cisco's engineering team - a positive signal indicating no known prior adversarial exploitation. No public exploit code exists and the vulnerability is not listed in CISA KEV; however, the SD-WAN control plane sensitivity means exposed credentials could enable broad network infrastructure takeover.
Privileged file manipulation in Cisco Catalyst SD-WAN Manager and SD-WAN Controller allows an authenticated attacker to abuse improper symbolic-link resolution (CWE-59) to read, overwrite, or destroy files outside intended boundaries, with a scope-changing impact that reaches beyond the vulnerable process. The flaw was found during Cisco's internal SD-WAN security review and remediated in hardening releases; it carries a CVSS 9.1 rating driven by network reach, low complexity, and high confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the high base score and management-plane exposure make it a meaningful patching priority.
Privilege escalation and cross-boundary information disclosure in Cisco Catalyst SD-WAN Manager and SD-WAN Controller stems from improper input validation (CWE-20) discovered during Cisco's internal hardening review; an authenticated attacker with low privileges can send crafted input over the network to break out of their intended authorization scope and compromise the confidentiality, integrity, and availability of the management plane. The CVSS 9.9 score is driven by a scope change (S:C), meaning impact extends beyond the vulnerable component to the broader SD-WAN control fabric it orchestrates. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the near-maximal CVSS and the centrality of the affected controllers make this a high-priority patch.
Unauthenticated remote denial-of-service affecting Cisco IOS XE Software across a wide version range results from multiple improper input validation flaws (CWE-20) discovered during Cisco's internal security hardening review. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H) indicates that network-adjacent or internet-facing IOS XE devices can be crashed or rendered unavailable without any credentials or user interaction, with the changed scope (S:C) suggesting impact can extend beyond the directly targeted device to dependent network services. No public exploit code has been identified and this is not listed in CISA KEV, consistent with the internally discovered origin.
Improper neutralization of special elements (CWE-74 injection class) in Cisco IOS XE Software allows remote, unauthenticated attackers to compromise the confidentiality, integrity, and availability of affected network devices, per Cisco's CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, 9.8 Critical). The flaw was found during an internal Cisco security review and fixed via software hardening releases; there is no public exploit identified at time of analysis and it is not listed in CISA KEV. Because the disclosure is a bundled hardening advisory, the exact injection sink and affected feature/protocol are not specified, so the concrete attack surface is not confirmed from available data.
Unauthenticated remote denial-of-service in Cisco IOS XE Software allows network-accessible attackers to crash IOS processes or force full device reloads by exploiting insufficient control flow management flaws (CWE-691), with a scope-changing availability impact rated CVSS 8.6. The vulnerabilities were discovered internally by Cisco's own engineering team as part of a proactive security review and addressed through software hardening releases - no active exploitation or public proof-of-concept has been identified at time of analysis. The affected version range is exceptionally broad, spanning IOS XE 16.6.x through 26.1.x, meaning virtually every Cisco IOS XE device on networks that has not been recently patched is likely running a vulnerable version.
Denial-of-service conditions in Cisco IOS XE Software stem from multiple incorrect calculation flaws (CWE-682) discoverable over the network without authentication, capable of crashing the affected device and disrupting all traffic transiting it. The CVSS scope change (S:C) indicates impact extends beyond the vulnerable component itself, consistent with a network appliance crash affecting downstream routing and switching functions across an enterprise. Internally discovered and disclosed by Cisco as part of a proactive software hardening initiative, no public exploit identified at time of analysis and CISA KEV status is absent.
Unauthenticated remote attackers can cause high availability impact with scope change on Cisco IOS XE Software through improper control of resources across their lifetime (CWE-664), affecting an exceptionally broad version range from 16.6.x through 26.1.x. The vulnerabilities were discovered proactively by Cisco's internal security engineering team and grouped as a software hardening release, meaning patches were prepared before external threat actor awareness. No public exploit exists and the CVE is absent from CISA KEV, but the AV:N/AC:L/PR:N/UI:N CVSS profile means exploitation requires no authentication or special conditions against any network-accessible IOS XE device.
Command injection in Cisco Integrated Management Controller (IMC) allows a remotely authenticated low-privileged attacker to execute arbitrary OS commands and escalate privileges to root on affected Cisco UCS Standalone servers. Exploitation requires only low-level credentials to the IMC web-based management interface - no local access, no user interaction. No public exploit has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog, but the low attack complexity and full system impact make it a meaningful priority for any environment with IMC exposed to internal or management networks.
Cross-origin read bypass in Electron's custom protocol handler exposes sensitive application data to remote pages via fetch() and XMLHttpRequest. Electron apps on any branch prior to 39.8.10, 40.9.3, 41.4.0, or 42.0.0 that register a custom scheme with supportFetchAPI: true but omit corsEnabled: true fail to enforce CORS, allowing a malicious remote page loaded in the renderer to read the full response body of privileged custom-scheme requests. No public exploit code is identified at time of analysis and the vulnerability is not in CISA KEV, but the confidentiality impact is rated high by the vendor given the potential to exfiltrate internal application data.
Unsafe class loading in the ORB (Object Request Broker) component of IBM WebSphere Application Server 8.5, 9.0, and Liberty Continuous Delivery allows a malicious or attacker-controlled IIOP server to force a WebSphere client/server to load and instantiate arbitrary Java classes over the network. Exploitation requires no authentication or user interaction (CVSS 9.8), and successful abuse can lead to loss of confidentiality, integrity, and availability, potentially culminating in remote code execution via dangerous class instantiation. There is no public exploit identified at time of analysis, and EPSS estimates only a 0.44% probability of exploitation in the next 30 days.
Privileged API access in Apache Answer through 2.0.1 persists after an administrator loses their authority: keys issued to an admin stay valid even after the account is demoted, marked inactive, suspended, or deleted, so a former administrator retains full API-level control until the keys are manually purged. This CWE-613 (Insufficient Session Expiration) flaw carries a vendor CVSS of 9.1 and is fixed in 2.0.2. There is no public exploit identified at time of analysis and EPSS is low (0.16%), consistent with an insider/privilege-retention issue rather than mass internet exploitation.
Unauthenticated information disclosure in Apache Answer through 2.0.1 allows any remote user to retrieve deleted or pending answers via the single-answer read API path, provided the parent question remains publicly visible. The flaw bypasses moderation-state access controls, exposing content that was intentionally withheld from public view. No public exploit code or active exploitation has been identified; EPSS at 0.17% (7th percentile) reflects limited real-world exploitation interest despite the high CVSS score.
Privilege escalation in Red Hat Build of Keycloak's Dynamic Client Registration (DCR) grants an attacker with low-privilege client registration credentials full realm administrator access by exploiting a validation bypass in the 'Allowed Protocol Mapper Types' security policy. The policy correctly validates mapper types at initial registration but fails to re-validate the mapper type during a client update when the mapper's surrounding configuration is unchanged, allowing a type-swap from a permitted mapper to a restricted high-privilege mapper (such as a HardcodedRoleMapper that injects realm-admin roles into tokens). No public exploit code has been identified and no CISA KEV listing is present, but the attack is low-complexity, fully network-exploitable, and results in complete confidentiality, integrity, and availability compromise of the Keycloak realm.
Session persistence after password change in Flarum before 1.8.16 allows an attacker who already holds a valid session token to maintain full account access indefinitely, even after the victim resets their password. The `TokensClearer::clearPasswordTokens()` function clears only the `password_tokens` table and never touches the `access_tokens` table, so all active session cookies, API bearer tokens, and long-lived RememberAccessToken entries survive both user-initiated and administrator-forced password resets. No public exploit has been identified at time of analysis; vendor-released patch v1.8.16 resolves the issue.
URI normalization bypass in Keycloak's Authorization Services PathMatcher allows authenticated low-privilege users to reach administrative or restricted endpoints by appending trailing slashes or matrix parameters to request URIs. Affected deployments include Red Hat Build of Keycloak, Red Hat Single Sign-On 7, Red Hat Data Grid 8, and Red Hat JBoss EAP Expansion Pack. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, though the high CVSS confidentiality and integrity impact scores reflect meaningful privilege escalation risk in production environments.
Arbitrary-address memory write in the nanoMODBUS Modbus client library (through v1.23.0) allows a malicious or compromised Modbus server to corrupt the memory of any client that issues a Read Device Identification request. The flaw stems from an unchecked server-supplied object_id used as an array index, ultimately steering a strncpy() destination pointer with attacker-controlled data - a condition that typically leads to remote code execution or crash on embedded/IoT clients. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV; the assigned CVSS is 9.8, though exploitation requires the victim client to communicate with an attacker-controlled server.
Double-free use-after-free in the Linux kernel's xfrm (IPsec) subsystem allows a low-privileged local user to corrupt kernel heap memory, potentially achieving privilege escalation. The race condition in xfrm_user_policy() between a non-atomic sk_dst_cache reset via setsockopt and the UDP fast-path's atomic xchg() reset causes both code paths to observe the same dst pointer and call dst_release() twice, freeing the xfrm_dst bundle while still in use. Critically, the description confirms this is reachable by an unprivileged user via user and network namespaces, making it exploitable on most modern Linux distributions where user namespaces are enabled by default. No public exploit exists and no KEV listing, but the KASAN-confirmed write-to-freed-memory primitive is a classic kernel privilege escalation vector.
Double reference-count release (double netdev_put()) in the Linux kernel's IPv6 XFRM/IPsec policy subsystem allows a local low-privileged user to underflow a net_device refcount, producing kernel ref_tracker warnings and 'unregister_netdevice: waiting for <dev> to become free' hangs that can destabilize or crash the system and potentially enable privilege escalation through kernel memory corruption. The flaw exists in xfrm6_fill_dst() at net/ipv6/xfrm6_policy.c: on the error path where in6_dev_get(dev) returns NULL, netdev_put() is called but xdst->u.dst.dev is not cleared, so dst_destroy() later releases the same reference a second time. No public exploit and no CISA KEV listing have been identified at time of analysis; EPSS is 0.16% (5th percentile), indicating currently low automated exploitation probability.
Remote kernel panic in the Linux kernel's GTP (GPRS Tunneling Protocol) driver allows an unauthenticated network attacker to crash a GTP-enabled host by sending a malformed echo request packet of 16-19 bytes. The vulnerability arises because gtp1u_send_echo_resp() ignores the NULL return from skb_pull_data() on an undersized buffer, causing skb->data to be pushed below skb->head by subsequent header operations, which trips skb_under_panic() and causes an immediate kernel BUG halt. No public exploit has been identified at time of analysis and EPSS of 0.18% (8th percentile) reflects low current exploitation probability, but the unauthenticated network-triggerable DoS against mobile core infrastructure warrants prompt patching for telecom operators.
Uninitialized stack memory dereference in the Linux kernel's IPv4 nexthop subsystem (net/ipv4/nexthop.c) enables local low-privileged attackers to cause kernel panic or leak sensitive stack contents on systems built with CONFIG_INIT_STACK_NONE. Versions from 5.13 through stable branches prior to 6.6.148, 6.12.101, 6.18.42, 7.1.6, and 7.2-rc5 are affected. No public exploit code has been identified and EPSS stands at 0.16% (5th percentile), placing this in the low-urgency tier despite a CVSS 7.1 score driven by dual high-impact outcomes.
Double-release memory corruption in the Linux kernel's BPF TCP iterator (bpf_iter_tcp_batch) allows a local low-privileged user with BPF iterator access to trigger a kernel panic. When batch reallocation fails, the first bpf_iter_tcp_put_batch() call frees socket references and overwrites batch slots with socket cookies; if realloc then fails, the iterator's stop routine executes a second put_batch() and dereferences those cookie integer values as struct sock pointers, causing a KASAN-detected null-pointer dereference and kernel panic. No public exploit identified at time of analysis; EPSS is 0.15% (5th percentile), indicating low current automated exploitation probability.
Use-after-free in the Linux kernel mac80211 MLO (Multi-Link Operation) subsystem allows a local attacker with low privileges to corrupt kernel memory by reading stale debugfs entries after a failed ieee80211_vif_update_links() operation. Systems running kernel 6.4 or later with WiFi 7 (IEEE 802.11be) MLO-capable hardware are within the affected code path; patched releases are available across all active stable branches. No public exploit or CISA KEV listing exists and EPSS is 0.16%, but CVSS impact metrics of C:H/I:H/A:H indicate full kernel compromise potential if the vulnerability is successfully triggered, as confirmed by a KASAN slab-use-after-free trace referencing a task named 'exploit/145'.
Double-free memory corruption in the Linux kernel's mac80211 WiFi subsystem exposes systems running in WiFi 6 AP mode with FILS discovery configured to potential kernel heap corruption and privilege escalation. The flaw in ieee80211_set_fils_discovery() prematurely queues the old template for deferred freeing before confirming the new allocation succeeds; when kzalloc() fails, a stale pointer is retained and freed a second time upon AP teardown or reconfiguration. No public exploit identified at time of analysis; EPSS is 0.19% (8th percentile), consistent with the constrained exploitation prerequisites.
Double-free memory corruption in the Linux kernel's mac80211 WiFi subsystem allows a local attacker with low privileges to corrupt kernel heap memory, potentially leading to privilege escalation or denial of service. The flaw exists in ieee80211_set_unsol_bcast_probe_resp(), where kfree_rcu() is invoked on the old unsolicited broadcast probe response template before a new one is successfully allocated - if kzalloc() then fails, the stale pointer is re-queued for freeing during AP teardown or subsequent configuration updates, triggering a KASAN-detected double-free in softirq context. No public exploit exists and EPSS is extremely low (0.16%, 5th percentile), but the local PR:L CVSS vector and high C/I/A impact scores make this a meaningful kernel hardening target for multi-tenant or shared Linux environments.
Cleartext registration token exposure in Rancher allows a low-privileged user to obtain perpetually valid cluster join tokens and enlist rogue nodes into downstream Kubernetes clusters. The tokens - used to authenticate nodes and agents during cluster bootstrapping - are stored without encryption or expiration and are reachable through at least four distinct channels: the Rancher API, etcd, stored automation artifacts, and direct filesystem access on enrolled nodes. The CVSS scope-change flag (S:C) accurately reflects that successful exploitation extends attacker influence beyond the Rancher management plane into downstream cluster workloads, secrets, and compute. No public exploit has been identified at time of analysis, and no CISA KEV listing exists.
Arbitrary PHP function execution in ShopLentor (woolentor-addons) for WordPress up to and including version 3.3.7 allows authenticated administrators to invoke any PHP callable on the server via the woolentoropt/v1/custom-action REST API endpoint. The root cause is the plugin's handle_action() method passing the user-supplied 'callback' parameter directly into PHP's call_user_func() with no allowlist restriction, enabling full server-side code execution under the web server's privilege context. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the admin-level requirement limits the realistic attacker pool to compromised or malicious site administrators.
Credential brute-forcing against Typemill CMS (versions up to and including 2.25.0) is possible because its primary password-login endpoint (POST /tm/login, ControllerWebAuth::login()) implements no rate-limiting, failed-attempt counting, or account lockout when captcha is disabled - the default state. Any unauthenticated attacker can submit unlimited password guesses against any account, including administrators, enabling account takeover of weakly-protected credentials. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV.
Privilege persistence in Shiori, the self-hosted bookmarks manager (go-shiori/shiori), allows a deleted or demoted owner to continue authenticating with full owner-level privileges for up to 30 days after account revocation. The root cause is that CheckToken in internal/domains/auth.go validates only the JWT HMAC signature and trusts the embedded claims without re-querying the database, and no token revocation or session store mechanism exists anywhere in the codebase. An attacker who previously held an owner-level account - such as a terminated employee - retains full read/write access to all bookmarks and administrative functions until the token's natural expiry. No active exploitation confirmed (no CISA KEV listing); no public exploit code identified at time of analysis.
Memory allocation with excessive size value in Apache Lucy (all versions) enables potential denial-of-service and information disclosure against a retired, unsupported search library. The vulnerability stems from CWE-789, where the library processes externally supplied size values without adequate bounds checking, potentially allowing an attacker to trigger abnormal memory allocation behaviour. No patch will ever be released - the Apache Software Foundation has officially retired Lucy and explicitly recommends migration to an alternative; no public exploit has been identified at time of analysis.
Sensitive information exposure in the Page and Post Restriction WordPress plugin (versions ≤ 1.4.0) allows unauthenticated attackers to read the full rendered content of every published page and post on sites relying on the plugin's global privacy toggles. The plugin's REST API guards - `papr_restrict_page_post_rest_api()` and the `the_posts` filter in `papr_filter_posts()` - consult only per-post/page metabox settings and completely ignore the 'Make all Pages Private' and 'Make all Posts Private' global options, leaving the `/wp-json/wp/v2/pages` and `/wp-json/wp/v2/posts` endpoints unguarded. No public exploit is identified at time of analysis, but the attack is trivially executable with a single unauthenticated HTTP GET request.
Unauthenticated sensitive information exposure in the AI Copilot - Content Generator plugin for WordPress (versions up to and including 1.4.6) allows any remote attacker to retrieve plaintext OpenAI API keys and full AI model configurations. The `getCurrentTaskResults()` method is exposed via `wp_ajax_nopriv_` AJAX hooks with no nonce validation, no authorization checks, and no permission guard - making task results freely accessible to unauthenticated callers. Attackers who enumerate sequential integer task IDs can exfiltrate every stored API key, prompt configuration, and keyword set from the site's database. No active exploitation is confirmed in CISA KEV, and no public exploit code has been identified at time of analysis, though the vulnerability is trivially exploitable given the low attack complexity.
Uncontrolled Recursion in Apache Lucy, a retired full-text search library, enables remote unauthenticated attackers to crash the service via a crafted input, resulting in a complete denial of availability across all versions ever released. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms low-complexity, unauthenticated network exploitation with no confidentiality or integrity impact. No patch exists or will be issued by the Apache Software Foundation, as the project is officially retired; EPSS is low at 0.15% (5th percentile) and no active exploitation (CISA KEV) has been identified at time of analysis.
SQL injection in the Ajax Load More WordPress plugin before 8.0.1 lets unauthenticated attackers inject into an unsanitised parameter used in a database query, enabling time-based blind extraction of sensitive data such as user credentials and secrets. Reported by WPScan with publicly available exploit detail and a vendor patch in 8.0.1; scored CVSS 9.1 with an unauthenticated network vector. EPSS is low (0.19%, 9th percentile), indicating limited observed exploitation despite the critical rating.
Password-protected block content in the Passster WordPress plugin (all versions before 4.3.6) is rendered into the public HTTP response body before the server evaluates the password check, making the gate purely cosmetic. Unauthenticated remote users can retrieve protected content by inspecting the raw response - no password required. A public proof-of-concept exploit is available via WPScan, and the CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N) confirms trivial remote exploitation with full confidentiality impact, though EPSS at 0.16% (5th percentile) and no CISA KEV listing indicate exploitation has not yet become widespread or automated.
Category-locked content in the Passster WordPress plugin (all versions before 4.3.6) is fully exposed through the native WordPress REST API, bypassing the plugin's access controls entirely. Unauthenticated remote users can retrieve the title, full body, and excerpt of any post that site owners intended to restrict using Passster's category-based protection. A publicly available exploit exists per WPScan; no CISA KEV listing and a low EPSS of 0.16% (5th percentile) indicate limited observed in-the-wild exploitation so far, but the trivial exploitation conditions make this an immediate upgrade priority for any site relying on Passster to gate sensitive content.
Unauthenticated content disclosure in the Passster WordPress plugin (versions before 4.3.6) allows any remote user to retrieve the full content of draft, private, and pending posts via a REST API endpoint that skips post-status validation. The flaw is conditional on the target site having a captcha provider configured, which is the typical deployment mode for Passster installations. Publicly available exploit code exists per WPScan reporting, though EPSS sits at only 0.16% (5th percentile), suggesting exploitation remains targeted rather than widespread. No CISA KEV listing has been issued.
Account takeover in the Membership Plugin - Kadence Memberships (formerly Restrict Content) for WordPress affects all versions through 4.0.0 via password-reset link poisoning. The legacy lost-password handler trusts an attacker-controlled rc_redirect POST value, so an unauthenticated attacker can trigger a reset email for any account (including administrators) whose reset link points at an attacker-controlled host carrying a valid key/login; when the victim clicks it, the reset key leaks and can be replayed to seize the account. No public exploit identified at time of analysis, and the flaw is not in CISA KEV, but Wordfence-confirmed root cause and a straightforward primitive make this a high-priority patch (CVSS 9.3).
Remote code execution as root is achievable against H3C NX15 firmware V100R017 via the `/api/esps` Web API endpoint, which exposes the `service.add` function without adequate access controls (CWE-749). Exploitation requires high-privilege authentication, but a post-authentication proof-of-concept script (`postauth_service_add_rce.py`) is publicly available on GitHub, demonstrating a complete root RCE chain. No vendor patch has been identified at time of analysis; no active exploitation is confirmed in CISA KEV.