Privilege escalation in the MemberPress Corporate Accounts WordPress plugin (≤1.5.39) allows authenticated subscribers holding a corporate account to create new administrator accounts or hijack existing ones by overwriting their email addresses. The root cause is a mass assignment flaw in the `add_sub_account_user` function, which forwards the raw `userdata` POST array directly to WordPress's `wp_insert_user()` without stripping sensitive keys such as `role` or `ID`. Wordfence reported the vulnerability; a partial patch was released in version 1.5.39, meaning even the latest disclosed version may still be exploitable in some code paths. No public exploit code or CISA KEV listing has been identified at time of analysis.
Local file inclusion and remote code execution in GEO my WP WordPress plugin (≤4.5.5.3) allow unauthenticated attackers to include arbitrary PHP files via the `gmw_posts_locator_ajax_info_window_loader` AJAX handler, which accepted attacker-controlled template paths and passed them to a PHP `require` statement without adequate allowlist enforcement. At minimum this exposes sensitive PHP files such as wp-config.php; when PEAR is installed with `register_argc_argv` enabled, attackers can leverage pearcmd.php to write and execute arbitrary PHP code, achieving full unauthenticated RCE. No public exploit has been identified at time of analysis, though the Wordfence advisory and vulnerable source code are publicly available, substantially reducing the development effort for a proof-of-concept.
Sandbox escape in wasm2c (wabt ≤ 1.0.41) allows an attacker controlling WebAssembly content to achieve arbitrary read/write of host process memory and code execution by exploiting an unchecked calloc() return value during funcref table allocation. When calloc() fails, table->data is left NULL while table->size retains the guest-declared element count, causing bounds checks to pass and element accesses to resolve to absolute low-memory addresses - fully defeating the isolation wasm2c exists to provide. Firefox's RLBox sandboxing of Graphite, Hunspell, Ogg, Expat, and Woff2 libraries is affected, and a public proof-of-concept ('table flip') is available, though exploitation requires specific memory-failure conditions to be present.
Remote code execution is achievable in Tutor LMS WordPress plugin (≤4.0.7) via a PHP Object Injection flaw in the withdrawal account AJAX handler that exploits a subtle interaction between `esc_sql()` percent-escaping and PHP serialized string-length declarations. Authenticated attackers with subscriber-level access — or unauthenticated attackers on sites with user registration enabled, the typical eLearning configuration — can inject an arbitrary serialized object stream and trigger the well-documented `GuzzleHttp\Cookie\FileCookieJar` POP chain to write a webshell to an attacker-specified path. No public exploit or KEV listing is confirmed at time of analysis, but a fix changeset is available and the POP chain is reliably reachable due to the plugin's bundled PayPal Composer autoloader.
Out-of-bounds read in zstd-jni versions 1.2.0 through 1.5.7-13 exposes JVM-based applications to service termination and partial memory disclosure when attacker-controlled offset or length values are passed to the ZstdDictDecompress constructor without bounds validation. The missing guard allows values that exceed the backing byte array, causing the JNI layer to read past the array boundary into native memory, which can abort the JVM process. A vendor-released patch is confirmed in v1.5.7-14; no public exploit code or CISA KEV listing has been identified at time of analysis.
Missing authorization in WWBN AVideo's Scheduler email plugin exposes private subscriber email addresses, live-stream titles, and scheduled job metadata to any unauthenticated network attacker who can supply a valid site-wide daily token. The daily token is obtainable without authentication from publicly accessible Live pages, making the attack effectively unauthenticated for instances with open Live pages. No public exploit code has been identified at time of analysis, but the attack path is mechanically straightforward and the confidentiality impact is high given the exposure of user email addresses.
Unauthenticated stored XSS with missing authorization controls in the BE REST Endpoints WordPress plugin (≤1.0.0) enables persistent script injection across all pages rendering affected widgets. The plugin exposes widget management REST endpoints with no authorization enforcement whatsoever, allowing any unauthenticated network caller to create, update, or delete widgets while injecting arbitrary JavaScript that is stored without sanitization. Every subsequent visitor - including administrators - who loads a page rendering those widgets will execute the injected payload in their browser, making session-theft and site takeover realistic downstream impacts.
Privilege escalation in the Add User Autocomplete WordPress plugin before 1.2 allows any authenticated user - including subscribers - to self-assign the administrator role on a WordPress multisite installation by submitting a crafted site-membership invitation request with an attacker-controlled role parameter. The plugin performs no capability check (no `current_user_can()`) and no nonce validation before accepting and creating the invitation, making the attack trivial for any account holder. No public exploit or CISA KEV listing is identified at time of analysis; EPSS sits at 0.13% (3rd percentile), but the low barrier (subscriber-level auth) makes any multisite deployment with this plugin a meaningful lateral escalation risk.
Out-of-bounds write in snappy-java through 1.1.10.8 allows unauthenticated remote attackers to crash the JVM by supplying valid compressed data whose decompressed size exceeds the caller-provided destination ByteBuffer capacity. The `Snappy.uncompress(ByteBuffer, ByteBuffer)` method passes the destination buffer directly to the native Snappy decompressor via JNI without first asserting that its capacity can accommodate the full decompressed output, causing native-layer writes past the buffer boundary and abrupt JVM process termination. No public exploit code or active exploitation has been identified at time of analysis, but the attack is trivially constructible by any attacker familiar with the Snappy wire format against applications that process untrusted compressed input through this specific API overload.
Unauthenticated SQL injection in the SAMO Forms WordPress plugin (≤1.0.0) allows remote attackers to query the underlying database without any credentials. Multiple plugin endpoints fail to sanitize or escape user-supplied input before incorporating it into SQL queries, enabling classic and potentially blind SQLi attacks. No public exploit code has been identified at time of analysis, and EPSS sits at 0.19% (9th percentile), suggesting no observed widespread exploitation despite the low attack complexity.
Unauthenticated SQL injection in the Album Cover Finder WordPress plugin (≤0.7.0) exposes database contents to remote attackers without any credentials. The CVSS S:C vector indicates the injection can reach data beyond the plugin's own scope - most critically, WordPress core tables containing hashed admin passwords and user data. No public exploit code has been identified and EPSS sits at 0.18% (7th percentile), suggesting low observed exploitation activity despite the severity score; no vendor-released patch has been confirmed at time of analysis.
Unauthenticated arbitrary file read in the Yogeta WP Cloud WordPress plugin (through version 1.0) allows any remote attacker to download arbitrary files from the server, including sensitive credential files such as wp-config.php, database configuration, and OS-level files like /etc/passwd. The plugin exposes a public endpoint that passes a user-supplied file path directly to a file-read function with no path validation and no authorization check, enabling full server-side file disclosure. Reported by WPScan with no patch available at time of analysis; no public exploit is identified at time of analysis, and EPSS stands at a low 0.16%, though the unauthenticated network-accessible nature makes this easily exploitable when the plugin is active.
Remote code execution in vLLM's LlavaOnevision2 processor loader allows an attacker who controls a model repository to execute arbitrary code on systems that load that model, bypassing the trust_remote_code=False safety parameter entirely. All vLLM installations prior to version 0.28.0 are affected when loading LlavaOnevision2-architecture models; the security control that operators rely on to safely evaluate third-party models is silently non-functional for this processor class. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but the attack requires only the ability to publish a model to an accessible registry and social-engineer a user into loading it.
Heap buffer overflow in Freeciv's worklist_load() function allows memory corruption when a crafted savegame file declares a worklist length exceeding the fixed MAX_LEN_WORKLIST bound of 64 entries. Both savegame format v2 (savegame2.c) and v3 (savegame3.c) code paths are vulnerable in all releases before 3.2.6, meaning any user or server operator who loads a malicious .sav file may have heap-adjacent struct fields overwritten, potentially enabling arbitrary code execution. No public exploit has been identified at time of analysis, but the patch diff is publicly available on GitHub, lowering the bar for future weaponization.
PHP Object Injection in the wpstorecart WordPress plugin (through 5.0.7) exposes an unauthenticated deserialization endpoint bundled as an add-on, permitting attackers to inject arbitrary PHP objects without class restrictions. Exploitation to full system compromise (RCE) is contingent on the presence of a suitable POP gadget chain elsewhere in the WordPress environment - a condition that is common on complex WordPress installations running multiple plugins. No public exploit code has been identified at time of analysis, and EPSS sits at 0.16% (5th percentile), reflecting low current exploitation activity.
Stored cross-site scripting in the YayPricing WordPress plugin before 3.5.7 lets any authenticated subscriber-role user inject arbitrary JavaScript into the plugin's pricing rules via an unprotected REST API endpoint that lacks authorization checks. The payload persists server-side and executes in the browser of any WordPress administrator who subsequently opens the YayPricing settings page, enabling session hijacking or full administrative account takeover. No public exploit code has been identified at time of analysis, and the vendor-released fix is available in version 3.5.7.
MCPHub's embedded OAuth 2.0 authorization server before v1.0.32 allows an attacker who intercepts a victim's authorization code to redeem it for valid access tokens without supplying a client secret or PKCE verifier. The root cause is a logic inversion in client authentication: the pre-fix condition checked `if (clientSecret && client.clientSecret)`, meaning that omitting the secret in a token request caused the entire secret-validation block to be skipped, even for confidential clients with a registered secret. Simultaneously, PKCE enforcement was absent for public clients, leaving no proof-of-possession check between code issuance and token exchange. Vendor-released patch v1.0.32 is available; no public exploit or CISA KEV listing has been identified at time of analysis.
Time-based blind SQL injection in rtMedia for WordPress, BuddyPress and bbPress (all versions through 4.7.11) enables unauthenticated remote attackers to exfiltrate arbitrary data from the WordPress database. The flaw stems from RTMediaQuery::query() merging raw $_REQUEST input into internal query parameters while only validating top-level array keys, allowing the nested 'compare' subvalue to bypass input validation and reach an unparameterized SQL sink. Exploitation requires only that a public-facing page exist with an rtMedia shortcode present - no authentication, interaction, or special server configuration is needed. No public exploit code or CISA KEV listing was identified at time of analysis.
Unauthenticated credential token disclosure in the Zonify WordPress plugin before 1.0.5 exposes the site's stored service account login token to any remote attacker without authentication. The plugin fails to perform any WordPress capability check or authentication verification before returning the stored token, allowing retrieval by any network-reachable actor. An attacker who obtains the token can then authenticate to the site owner's linked third-party service account, effectively achieving full account takeover of the integrated service. No public exploit code has been identified at time of analysis, and EPSS stands at 0.18%, but the zero-barrier exploitation profile - unauthenticated, low complexity, network-accessible - makes the vulnerability trivial to abuse once discovered.
Sandbox escape in Flatpak before 1.18.1 allows a malicious sandboxed application to gain arbitrary read and write access to host filesystem paths, with direct escalation to code execution outside the sandbox. The root cause is missing symlink validation in Flatpak's app data directory bind-mount logic: attacker-controlled path components (such as the 'tmp' directory under ~/.var/app/APP_ID/cache/) can be replaced with symlinks pointing to arbitrary host locations, which the Linux kernel resolves when bwrap processes the bind-mount. No public exploit has been identified at time of analysis, and this is catalogued as a separate issue from the related CVE-2026-76925.
Remote code execution against WordPress sites is achievable through the Gpx2Graphics plugin (through version 0.3) by exploiting a missing CSRF token check and absent file-type validation on the plugin's upload handler. An unauthenticated attacker who tricks a logged-in WordPress administrator into visiting a crafted web page can silently deposit an arbitrary PHP webshell in a web-accessible directory, then invoke it to execute OS commands under the web server's identity. No public exploit or active exploitation has been identified at time of analysis; EPSS is 0.14% (4th percentile), indicating low current mass-exploitation probability.
Privilege escalation in the Temporary Login Without Password WordPress plugin (versions 1.5 through 1.9.8) allows a site-level administrator on a WordPress multisite network to elevate their own account or grant a newly provisioned temporary login to network super admin status. The missing authorization check in the account-provisioning and account-promotion logic completely bypasses the multisite privilege boundary, enabling a subordinate site admin to seize control of the entire WordPress network without any additional user interaction. Vendor-released patch is available in version 1.9.9; no public exploit identified at time of analysis, and EPSS is low at 0.14%.
Privilege escalation via IDOR in the Amelia 'Booking for Appointments and Events Calendar' WordPress plugin before 2.4.10 allows users holding plugin-level customer or employee management permissions to overwrite the email address and password of any linked WordPress account, achieving full account takeover of other users including administrators. The flaw stems from missing entitlement verification when editing customer or employee records: the plugin confirms the actor holds management rights within Amelia but never confirms ownership of the underlying WordPress account being modified. No public exploit or active exploitation (CISA KEV) has been identified; EPSS is 0.14% (4th percentile). A vendor-released patch exists at version 2.4.10.
Uncontrolled memory allocation in vLLM's transcription endpoint before 0.28.0 allows authenticated API clients to crash the entire server process by submitting FLAC audio files with forged, inflated sample rate headers. Because vLLM commonly operates as a shared API server across multiple tenants, a single authenticated attacker can deny service to all concurrent users. VulnCheck reported this with a CVSS 4.0 score of 7.1; no public exploit code or CISA KEV listing has been identified at time of analysis.
Stored Cross-Site Scripting in the Export & Import WPBakery Page Builder WordPress plugin (through 1.0.2) is achievable by any remote attacker who can lure a logged-in administrator into visiting a forged page. The plugin's template-import endpoint lacks CSRF protection and fails to sanitize imported template data before persisting and reflecting it, meaning a crafted template injected via a forged POST request stores malicious JavaScript that executes in the administrator's browser session. No public exploit is identified at time of analysis, and EPSS sits at 0.11%, suggesting limited opportunistic targeting.