Stored cross-site scripting in Ghost CMS 6.22.1 through 6.63.x lets an authenticated staff user with upload privileges host a browser-executable file on the site's own domain when the default local storage adapter is in use, potentially compromising other staff members' admin sessions. The flaw arises because the local storage adapter serves uploaded files with a Content-Type derived from the file extension instead of the inert type Ghost applies elsewhere, and it requires a victim staff or admin user to load the uploaded file's URL (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N, base 7.3). Sites using S3 or other cloud storage adapters are not affected, and the issue is fully neutralized in 6.64.0; there is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV).
Local privilege escalation in ClamXAV versions 3.3 through 3.11 allows an attacker who already holds a low-privileged local account on a macOS host to execute arbitrary code with system privileges by winning a race condition in the bundled Privileged Helper Tool that combines with insufficient file validation. Exploitation is timing-dependent (AV:L/AC:H/PR:L/UI:N in the assessed vector, with high confidentiality, integrity, and availability impact) and typically requires repeated attempts rather than a single deterministic trigger, making this a credible but not emergency-tier priority; no public exploit code has been identified at time of analysis, and ClamXAV 3.11.1 fully remediates the flaw.
Authenticated Ghost Administrators on versions 6.10.3 through 6.63.x can achieve remote code execution by installing a crafted theme that abuses how Ghost resolves theme translation (i18n) files, allowing path traversal into attacker-controlled code. Exploitation requires a high-privilege Administrator account (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2) and no victim interaction beyond the attacker's own admin actions; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV). Because the attacker population is limited to trusted or already-compromised admin accounts rather than anonymous remote users, this is a high-severity but access-gated issue rather than a mass-exploitation priority.
Authenticated code execution via media upload in Kunstmaan CMS (KunstmaanBundlesCMS) before 7.3.2: the MediaBundle checks the file-extension blacklist case-sensitively but lowercases the extension before writing the file, so a backend user with media-upload rights can submit a file named e.g. webshell.pHp, slip past the blacklist, and have it stored as webshell.php inside the web-accessible media directory. Impact escalates to full remote code execution, but only where the web server is configured to execute scripts in public/uploads/media/ - the vendor's hardening guidance (disable script execution for that path, send X-Content-Type-Options: nosniff) removes the execution impact. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and the flaw is gated behind a valid media-role account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.2).
Authenticated attackers with high privileges can exploit a PHP Object Injection vulnerability in Product Feed PRO for WooCommerce (versions up to 13.5.7) to potentially execute arbitrary code, delete files, or perform other malicious actions. The flaw stems from deserialization of untrusted data (CWE-502), and successful exploitation hinges on the presence of a reachable POP gadget chain in the targeted site's code; without such a chain, impact may be limited. No public exploit code or active exploitation has been identified at time of analysis, and the CVSS score is 7.2 (High).
PHP object injection in the WP Spell Check WordPress plugin, affecting all versions up to and including 12.1, allows an attacker who already holds administrator-level privileges to pass attacker-controlled data into PHP's deserialization routine and instantiate arbitrary objects. Successful object injection can lead to high-integrity and high-confidentiality impact - including code execution, file manipulation, or privilege abuse - depending on whether a usable POP gadget chain exists in the plugin or the surrounding WordPress environment, which the available data does not confirm. With a CVSS 3.1 base score of 7.2 (High) and PR:H in the vector, the practical attack surface is limited to trusted high-privilege users; no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis.
PHP object injection in the WordPress plugin WP Ultimate Exporter (Smackcoders Inc.) affects all versions up to and including 3.0, allowing an attacker who already holds a high-privilege authenticated account on the target site to submit crafted serialized PHP data to a plugin endpoint and instantiate arbitrary objects. Successful exploitation depends on a usable POP gadget chain being present in the plugin, WordPress core, or a loaded library; without one, the flaw may only yield object injection rather than full code execution. No public exploit code or confirmed active exploitation was identified at time of analysis, and the principal barrier is the CVSS PR:H prerequisite, which limits realistic abuse to privileged insiders or attackers who have already compromised an administrative account.
PHP object injection in the WordPress plugin Sunshine Photo Cart (all versions through 3.7.1) allows an attacker who already holds a high-privilege authenticated WordPress account to submit crafted serialized data to a plugin endpoint, potentially achieving object injection with high confidentiality, integrity and availability impact. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) rates this 7.2 and confirms the attacker must be authenticated with elevated privileges (PR:H), which excludes anonymous internet users and is the primary limiting factor; no user interaction is required. No public exploit code has been identified at time of analysis, and there is no confirmed evidence of active exploitation (not listed in CISA KEV) - realistic impact depends on a usable PHP gadget chain being present in the plugin or the hosting stack, which is not confirmed by the available data.
An out-of-bounds write in Android's wpa_supplicant Robust AV / SCS action-frame handler (wpas_handle_robust_av_scs_recv_action in robust_av.c) can be turned into remote code execution on Android 14 through 17 (including 16-qpr2) devices that receive a crafted SCS action frame. Exploitation is sharply constrained: per the CVSS vector PR:H, the attacker must already hold System-level execution privileges on the target before the malformed frame is processed, and the independently assessed vector (AV:A) places the attacker in Wi-Fi/adjacent range rather than on arbitrary internet-routable paths. User interaction is not required (UI:N), and no public exploit code or CISA KEV entry has been identified at time of analysis; combined with the vendor score of 7.2 and the adjacent-vector reassessment, this rates as a moderate, not emergency, priority.
Incorrect access control in Feehi CMS 2.1.1 allows a low-privilege backend administrator who holds the administrator-update permission to overwrite the password of the built-in super administrator account, achieving full super-admin takeover. The server neither protects the built-in super administrator record from modification nor requires the target account's current password during the update flow, so a single crafted backend request is sufficient. This is an authenticated privilege-escalation issue (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, rated 7.2 High) that requires a pre-existing privileged backend session; no public exploit code or confirmed active exploitation was identified at time of analysis, and no vendor-released patch was identified in the available intelligence.
Authenticated workspace members can tamper with another application's MCP server configuration in Dify versions prior to 1.16.0 by sending a PUT request to /console/api/apps/<app_id>/server with an arbitrary server ID, allowing them to disable or redirect the targeted app's MCP integration. The flaw is a cross-tenant/IDOR access-control gap (CWE-639) rated CVSS 7.1 (PR:L, I:H, A:L) that matters most in multi-tenant or multi-team Dify installations; no public exploit identified at time of analysis.
Cross-tenant file disclosure in Langflow 1.6.8 through 1.9.0 allows any authenticated user who can reach a project-scoped MCP connection to read another user's flow-backed artifacts - uploaded documents, structured data, prompts, and other private flow files - by supplying an arbitrary resource URI to the resources/read handler, which forwarded the caller-controlled URI to storage_service.get_file without verifying that the referenced flow belonged to the caller or the current project (CWE-639). The flaw is read-only, so victim files and stored flows are not modified, but confidentiality impact is high on multi-tenant or multi-user instances where other users' files exist to be read; no public exploit code identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV). The vendor fixed the issue in Langflow 1.9.1.
Cross-tenant deletion of estimate points in Plane (Makeplane) before 1.4.0 allows any authenticated user holding an administrator or member role in one workspace to permanently destroy an estimate point owned by a different workspace, simply by supplying the victim record's UUID in a URL scoped to the attacker's own workspace. The flaw is a destructive cross-tenant IDOR (CWE-639) rated CVSS 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L), requiring only a valid low-privilege account and knowledge of the target's random 128-bit UUID, which must be obtained out-of-band since it is not enumerable through this endpoint. No public exploit code or confirmed active exploitation was identified at time of analysis; the operational risk is moderate-to-high specifically for multi-tenant Plane deployments, while single-tenant installs have no cross-tenant victim.
Denial of service in Moby BuildKit allows a low-privileged remote user to crash the BuildKit daemon by submitting a build that attempts to use a CDI device when the daemon was started with the --cdi-disabled flag. This triggers a null pointer dereference (CWE-476) and daemon panic. The vulnerability requires a non-default configuration and the ability to submit builds; default deployments are not affected. No public exploit has been identified, and the vendor has released a patch in version 0.33.1.
Authenticated low-privilege users can retrieve embedded sensitive data from WordPress sites running the RepairBuddy plugin (versions through 4.1226) due to a missing authorization check. This moderate-severity vulnerability (CVSS 7.1) impacts only confidentiality, requires a valid account with minimal privileges, and has no public exploit code or active exploitation reported.
Authenticated remote users of Langflow can defeat the localhost-only restriction on the MCP configuration install endpoint (POST /api/v1/mcp/project/{project_id}/install) by sending a forged 'X-Forwarded-For: 127.0.0.1' header, causing the server to treat the request as local and allowing the attacker to write or overwrite an MCP client configuration file on the host filesystem. The flaw affects Langflow versions 1.5.0 up to but not including 1.10.3 and carries a CVSS v3.1 score of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L), reflecting a high integrity impact and low availability impact but no confidentiality loss. Authentication is mandatory, no user interaction is required, and no public exploit identified at time of analysis; no EPSS data was supplied for this CVE, so risk is driven by the moderate CVSS score and the requirement for a valid session rather than by observed exploitation.
Reflected cross-site scripting (XSS) in the VillaTheme 'Photo Reviews for WooCommerce' plugin for WordPress affects all versions through 1.2.30, allowing an unauthenticated attacker to inject script into a page viewed by a victim. Exploitation is phishing-driven: the attacker must lure a targeted visitor to a crafted URL, and the payload executes only in that victim's browser session, giving CVSS 3.1 a base score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) rather than server-wide compromise. No public exploit code identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV); the vulnerability was reported by Patchstack and the exact vulnerable parameter or endpoint is not detailed in the available data.
Reflected cross-site scripting (XSS) in the Adsmonetizer WordPress plugin (adsensei-b30) through version 3.2.4 allows remote attackers to inject arbitrary script into a victim's browser by convincing them to click a crafted link. The attacker does not need authentication, but exploitation requires user interaction and the targeted site must have the vulnerable plugin installed and reachable. This is rated CVSS 7.1, and no public exploit has been identified at time of analysis; it is not listed as confirmed actively exploited (CISA KEV).
Cross-Site Request Forgery (CSRF) in the Blubrry PowerPress Podcasting plugin for WordPress up to version 11.17.9 allows remote attackers to force a logged-in user, typically an administrator, to perform unintended actions by tricking them into interacting with a crafted link or malicious page, due to missing CSRF token validation. Exploitation requires user interaction (UI:R) and an active authenticated session, but no public exploit code is currently identified. The vulnerability has a CVSS score of 7.1 (moderate severity per independent assessment) and is tracked as CWE-352.
An insecure direct object reference (IDOR) in Plane prior to 1.4.0 lets an authenticated member of a project reassign ownership of another user's issue attachment by supplying a pk UUID in the V2 issue-attachment PATCH request. Because the endpoint validates only pk, workspace, and project_id while ignoring the issue_id present in the URL, an attacker with project membership (CVSS PR:L, network vector) can target any attachment still in the PENDING, not-yet-confirmed upload state and set created_by to their own account, thereby taking control of it; confirmed attachments are unaffected, and exploitation also requires knowing the victim's unguessable UUID. The flaw is a genuine but moderate-priority authorization issue (CWE-639) with no public exploit identified at time of analysis, and it is fixed in the vendor's 1.4.0 release.
Insecure direct object reference in Plane's public Spaces asset endpoints (all versions prior to 1.4.0) allows an attacker to read, overwrite, or restore arbitrary FileAsset records belonging to other projects and workspaces by supplying a crafted asset ID. The vulnerable code paths - EntityAssetEndpoint and AssetRestoreEndpoint in plane/space/views/asset.py - resolve a DeployBoard from a public anchor but fetch or mutate FileAsset rows scoped only to that board's workspace, with no membership check and no project_id constraint, even though sibling endpoints in plane/app/views/asset/v2.py had already been hardened for two earlier cross-tenant asset IDORs tracked as CVE-2026-27705 and CVE-2026-46558. Exploitation requires that at least one board be published as a public/shared board so an attacker can obtain a valid DeployBoard public anchor; the input CVSS 3.1 vector rates PR:L (7.1, High), while our independent assessment scores PR:N because the affected endpoints are reachable under the unauthenticated /api/public/ namespace, and this difference should be confirmed in the target deployment. No public exploit code or in-the-wild exploitation has been identified for this issue at time of analysis, and it is not listed in CISA KEV.
Code execution in Newell Brands DYMO ID 1.5.1.71 occurs because the application resolves its plugin Modules directory relative to the process working directory, letting an attacker who places a malicious plugin module or DLL alongside a crafted job file load arbitrary code at the victim's privilege level once that job file is opened. The issue is local and file-delivery based rather than network-reachable, requires explicit victim interaction (opening the crafted job), and grants only the privileges the victim already holds, so it cannot self-propagate; no public exploit code and no CISA KEV entry were identified at time of analysis. The vendor has released a fix in DYMO ID 1.6.0.
Code execution via local privilege escalation is possible in Google Android's Bluetooth AVRCP handling (handle_app_val_response in btif_rc.cc) because of a race condition (CWE-362) that can corrupt shared state in the Bluetooth stack. The flaw is rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N) and affects Android 16, Android 16-qpr2, and Android 17; an attacker must already have a low-privilege app installed on the device and must repeatedly drive the AVRCP remote-control code path to win a narrow timing window, with no user interaction required. No public exploit code has been identified and CISA's SSVC assessment records no observed exploitation, so while the technical impact is total if the race is won, the high attack complexity and local-only prerequisites keep this a lower-urgency item than a remotely reachable, deterministic bug.
ApiAdmin 5.0 and earlier allow any logged-in administrator to achieve remote code execution by uploading a .php payload to POST /admin/Index/upload; the handler takes the client-supplied extension verbatim with no whitelist, blacklist, or content inspection, and move_uploaded_file() places the file into the web-served public/upload/Ymd/ directory, where it can be requested directly over HTTP. The attack path is gated by an authenticated admin session (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2), so practical exposure hinges on credential compromise, reuse, or insider access rather than an unauthenticated vector. EPSS is low at 0.35% (26th percentile) and the issue is not listed in CISA KEV; no public exploit code is identified at time of analysis, though a public proof-of-concept write-up is referenced (GitHub fangtang7/CVE) and the European vulnerability entry EUVD-2026-92468 tracks the same CVE.