Stored cross-site scripting in the Advanced Woo Labels - Product Labels & Badges for WooCommerce plugin (all versions up to and including 2.51) lets an authenticated attacker with Contributor-level access or higher create product labels whose content is written to the database and later rendered without proper output escaping. When a victim - an editor, administrator, or any site visitor viewing a page that renders the label - loads the affected page, the injected script executes in their browser session, enabling session theft, privilege escalation, or content manipulation within the WordPress context; the scoring is moderate (CVSS 5.4, adjusted to scope-changed at 5.x-class impact by this assessment) and no public exploit code or confirmed active exploitation was identified at time of analysis. Note that version 2.46 contained only a partial fix, so installs in the 2.47-2.51 range remain exposed.
Physical attackers who can obtain, disassemble and hardware-modify a TP-Link Kasa EC70 v4 or EC71 v4 smart plug can restore the manufacturing-severed debug traces, interrupt the boot process and manipulate boot parameters to reach a non-standard initialization path that spawns an unauthenticated root shell during startup, giving full root-level control over the device (high confidentiality, integrity and availability impact to the device itself). The root cause is improper access control on the on-chip debug interface (CWE-1191): the production debug interface is not logically disabled at the firmware or chip level and the bootloader is not locked, so the physical cut of the debug traces is the only barrier. The attacker path is purely physical (CVSS 4.0 AV:P/AC:L/AT:P, assessed as CVSS 3.1 AV:P/AC:H), with no remote or over-the-air vector, and exploitation demands disassembly, trace rework (resoldering/bridging) and boot-timing manipulation; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, while vendor firmware updates are available per the TP-Link release notes.
HTML injection in JetBrains YouTrack's VCS command failure notifications (before 2026.2.19422) allows an authenticated attacker with high privileges to inject arbitrary HTML into notifications, potentially leading to content spoofing or script execution, but a victim must view the crafted notification. The vulnerability requires high attack complexity, and no public exploit code or active exploitation has been identified. Despite the low CVSS score of 2.0, it is a genuine XSS flaw that should be remediated by upgrading to version 2026.2.19422 or later.
Authenticated broken access control in the Magepeople WpTravelly (tour-booking-manager) WordPress plugin, affecting versions through 2.3.1, allows any logged-in low-privilege user to invoke plugin functionality that should be restricted to higher-privileged roles, weakening site integrity and availability. The assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L confirms a valid authenticated session is mandatory (PR:L, unauthenticated attackers are excluded), no user interaction is needed, and there is no confidentiality impact. There is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), so this presents as a moderate-priority, authenticated authorization gap whose real-world weight rises on sites that permit open registration or host many subscriber-level accounts.
Authenticated users of JetBrains YouTrack before version 2026.2.19422 can read notifications belonging to other users by directly referencing inbox thread identifiers that lack a proper per-user ownership check. The flaw is a classic insecure direct object reference (CWE-639) reachable over the network with low complexity and no user interaction, but it requires a valid low-privilege account, so it is not exploitable by unauthenticated outsiders. Impact is limited to confidentiality - disclosure of other users' notification contents - with no evidence of modification, service disruption, active exploitation, or publicly available exploit code at time of analysis; EPSS and KEV data were not provided, and the vendor has released a fix.
Missing capability checks in the WP Fusion Lite WordPress plugin before version 3.48.0 allow any authenticated subscriber-level user to read other users' email addresses and to trigger cross-user CRM re-syncs through two exposed admin AJAX handlers. The CVSS vector indicates the attacker must hold a valid logged-in account (PR:L, so authenticated, not unauthenticated), and sites that allow open or self-service user registration are the most exposed, since no user interaction or administrative privilege is needed. Impact is confined to information disclosure of email addresses and unintended CRM synchronisation activity rather than full site takeover, and no public exploit code was identified at time of analysis.
Information disclosure in Apache HTTP Server 2.4.0 through 2.4.68 arises from a path-equivalence flaw (CWE-55, '/./' single-dot directory) in the mod_userdir module, which mishandles the single-dot directory segment when the UserDir directive is configured with an absolute, non-wildcard path. Only deployments that load mod_userdir and use that specific second syntax form (for example 'UserDir /some/absolute/path') are exposed; servers on the default wildcard/username form, or without mod_userdir loaded, are unaffected regardless of version, so the practical exposure surface is a non-default configuration. The issue is network-reachable over HTTP and is assessed as low-confidentiality impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N); no public exploit code or confirmed active exploitation has been identified at time of analysis, and no patch version is specified in the available advisory data.
Unauthenticated information disclosure in WP Popular Posts (all versions up to and including 7.4.2) lets any remote attacker read sensitive edit-context fields - raw title, raw content body, password, meta, status, and guid - from non-public post objects such as drafts, private or password-protected posts, and wp_block synced patterns that WordPress core itself refuses to expose to anonymous callers. Scoring CVSS 3.1 as AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (5.3 Medium), the flaw requires no authentication, user interaction, or non-default configuration because the plugin's REST route is registered with a permission_callback of __return_true and passes the caller-supplied context parameter (for example context=edit) directly into WP_REST_Posts_Controller::prepare_item_for_response() while the underlying query accepts an arbitrary post_type without enforcing public or show_in_rest visibility. The practical limit is data-dependent rather than access-dependent - a site with no sensitive non-public content leaks little - and no public exploit code or confirmed active exploitation was identified at time of analysis.
Information disclosure in Apache HTTP Server 2.4.0 through 2.4.68 allows an unauthenticated remote client to read WebDAV dead properties of resources it cannot author by sending an HTTP GET request to the module's internal .DAV state directory. The flaw is in mod_dav_fs (CWE-552, files or directories accessible to external parties) and is reachable only when mod_dav and mod_dav_fs are loaded with WebDAV enabled and the .DAV state directory is web-accessible, so no default configuration is affected. No public exploit identified at time of analysis, and there is no CISA KEV listing; the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) reflects a read-only, low-confidentiality leak of client-set metadata with no integrity, availability, or code-execution impact.
An exposed API endpoint in HCL BigFix Service Management returns sensitive internal database information to remote, unauthenticated callers (CVSS 5.3, AV:N/AC:L/PR:N/UI:N), giving attackers reconnaissance material that could support follow-on targeted database attacks. Impact is limited to confidentiality (C:L) with no integrity or availability effect, and no public exploit code or confirmed active exploitation has been identified at time of analysis; exploitation is assessed as network-reachable and automatable, so the practical risk depends heavily on whether the management interface is internet-facing or confined to a trusted internal segment.
Information disclosure in HCL BigFix Service Management allows unauthenticated remote attackers to retrieve sensitive data from two exposed API endpoints, with no user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N = 5.3, MEDIUM). Only confidentiality is affected at a low level; the flaw does not permit data modification or cause denial of service on its own, but the leaked data can be used to stage follow-on attacks against the platform. There is no vendor-released fix identified in the available data, no public exploit code identified at time of analysis, and no confirmed active exploitation (not listed in CISA KEV); the practical risk is driven primarily by whether the BigFix Service Management API tier is reachable from untrusted networks.
Inspection of publicly served JavaScript in BigFix Service Management lets unauthenticated remote users discover hidden administrative API endpoint paths, a low-severity reconnaissance issue that leaks endpoint names without exposing sensitive data, altering data, or causing denial of service. The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N confirms no authentication or user interaction is required, but impact is limited to low confidentiality loss; no public exploit code or active exploitation has been identified at time of analysis. The disclosure is only useful if the discovered endpoints have separate exploitable flaws, which this CVE does not provide.
Authenticated staff-level users of Ghost CMS (versions 5.42.2 up to but not including 6.58.0) can infer other staff users' password hashes by supplying Admin API bulk post and page edit/delete filters that reference restricted fields such as authors.password. Because the bulk operation code paths fail to reject these restricted-field filters, the match/no-match behaviour acts as a boolean oracle that leaks information about the stored hash, which an attacker can then attack with offline password-guessing (cracking) - it does not hand over credentials directly. This is a genuine but modest-priority authenticated information disclosure (CVSS 5.3, assessed CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, CWE-203); there is no CISA KEV entry and no public exploit identified at time of analysis, and the issue is fully remediated in Ghost 6.58.0.
Team-scoped users in Fleet DM before 4.89.0 can read MDM command results for hosts on other teams via the commands/results endpoint when a shared command UUID targets hosts across multiple teams, exposing host UUIDs, command payloads, and device responses. Exploitation requires an authenticated low-privileged team-scoped account on an instance with MDM features in use, and the disclosure is limited to results tied to such cross-team command UUIDs; there is no public exploit identified at time of analysis. CVSS 4.0 base score is 5.3, with an assessed CVSS 3.1 base score of 4.3 reflecting read-only low confidentiality impact.
Server-side request forgery in Ghost 3.20.2 through 6.50.x allows authenticated staff users to trigger outbound HTTP requests to arbitrary URLs via the image dimension refetching feature. Attackers can point image cards at internal network endpoints or cloud metadata services (e.g., 169.254.169.254) to access resources unavailable from the public internet. No public exploit code identified at time of analysis; the vendor has released a patch in Ghost 6.51.0.
Cleartext 802.11 session traffic between Teledyne FLIR Aware2 (versions through 6.9.0.2) and PackBot robots can be sniffed, hijacked, or modified by an adjacent unauthenticated attacker who is within radio range of the robot's wireless network, giving limited confidentiality, integrity, and availability impact (assessed CVSS 3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L; CVSS 4.0 base 5.3). The flaw is CWE-319 (cleartext transmission of sensitive information) and stems from the absence of transport encryption on the robot control link rather than from a software logic error, so exploitation requires RF proximity to an operating robot on the same 802.11 network and does not need credentials or user interaction. No public exploit code or confirmed in-the-wild exploitation has been identified at time of analysis (not listed in CISA KEV), and the practical risk is bounded mainly by the mandatory adjacency requirement, which narrows realistic exposure to active fielded deployments; the issue was disclosed by Mandiant as MNDT-2026-0030 and tracked in the EU as EUVD-2026-91051.
Cleartext transmission of application traffic in the Joyland AI Android app exposes data to on-path attackers positioned on the same LAN or Wi-Fi segment, because the app explicitly opts into cleartext HTTP on Android 9+ where the platform default blocks it. Only data the app actually sends over plain HTTP is exposed, and the exposure is passive disclosure - no code execution, account takeover, or data modification results - with authentication not required (CVSS vector PR:N) and confidentiality impact scored low. No public exploit code has been identified at time of analysis (no public exploit identified at time of analysis), and no CISA KEV listing or EPSS signal was provided; the practical attack prerequisite is an adjacent-network or on-path foothold, which excludes remote internet-only attackers.
Unauthenticated devices on the same local network segment as a TP-Link Tapo C120 v1 or Tapo C200 V5 camera can invoke the HTTPS onboarding scan function and pull back metadata about nearby wireless access points, including SSIDs, BSSIDs, authentication and encryption modes, and signal-strength readings (CWE-306, missing authentication for a critical function). The flaw is only reachable after the camera has completed initial setup and requires the attacker to already have adjacent-network access (CVSS:4.0 AV:A/PR:N/UI:N, base 5.3; our own assessment scores it CVSS:3.1 3.1 AV:A/AC:L/PR:N/UI:N with C:L only), so it is not internet-exploitable and yields reconnaissance-grade wireless topology data rather than code execution, credential theft, or camera/video access. There is no KEV listing and no public exploit identified at time of analysis, and TP-Link has published firmware updates for both hardware revisions. This is a genuine but low-to-moderate priority issue, not a critical one, and the practical risk depends entirely on how hostile or shared the camera's LAN/Wi-Fi segment is.
Bypassing the CAPTCHA protection in the hCaptcha for WP plugin (hcaptcha-for-forms-and-more) up to version 5.3.0 allows unauthenticated remote attackers to submit forms without solving the challenge, defeating the anti-bot gate on login, registration, comment, WooCommerce, or contact forms. This authentication bypass by spoofing (CWE-290) is rated CVSS 5.3 and has limited impact, as it does not directly compromise data or the site. No public exploit code has been identified at time of analysis, and exploitation requires hCaptcha to be actively enabled on at least one form.
Unauthenticated information disclosure in the WPExperts CF7 Apps WordPress plugin (slug contact-form-7-honeypot) at version 3.7.2 and earlier lets a remote attacker retrieve sensitive data that the plugin inserts into data it sends out, typically form submission payloads or notification content. Per the assessed vector (AV:N/AC:L/PR:N/UI:N) no authentication or user interaction is required and default configurations are affected, but the flaw is confidentiality-only and low impact (C:L, no integrity or availability effect), so real-world severity depends on what a given site's forms and configuration actually expose. No public exploit identified at time of analysis, and CR7 Apps is not listed as confirmed actively exploited (CISA KEV); the risk is best characterized as a low-to-medium priority information disclosure rather than a critical incident.
Unauthenticated remote attackers can read data that should be access-controlled on WordPress sites running the Metagauss ProfileGrid plugin (profilegrid-user-profiles-groups-and-communities) through version 6.0.0.2 by supplying or guessing an object/user identifier that the plugin fails to validate against the requester's ownership or privileges. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) indicates no authentication, privilege, or user interaction is required, but impact is limited to confidentiality (C:L), with the practical constraint that the attacker must know or be able to enumerate a valid identifier. No confirmed active exploitation (KEV) and no public exploit code have been identified from the available data, and the independent assessment rates the overall priority as modest rather than urgent.
Sensitive information disclosure in Pie Register WordPress plugin versions through 3.8.4.13 allows remote, unauthenticated attackers to retrieve embedded data from affected sites. The vulnerability (CWE-201) has a CVSS score of 5.3 and requires no special conditions beyond the plugin being active, though the specific data exposed is not detailed in the advisory; this is a genuine but low-urgency issue. No public exploit code has been identified at time of analysis, and the impact is confined to confidentiality (C:L) with no integrity or availability effects.
Unauthorized affiliate action execution is possible in AFFI - Affiliate Marketing for WooCommerce through version 1.0.9 because an access-control check is missing, allowing unauthenticated remote attackers to perform a low-integrity action per CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N. No public exploit code or CISA KEV entry was identified at time of analysis, so this is assessed as a modest-severity, integrity-only issue rather than an actively exploited urgent threat. The practical risk is abuse of the plugin's affiliate functionality on sites running the affected version.
Majestic Support plugin through 1.2.0 for WordPress allows remote unauthenticated attackers to perform unauthorized low-integrity actions because a plugin endpoint omits an authorization check. Only integrity is affected, with no confidentiality or availability impact expected, and no public exploit identified at time of analysis.
Unauthenticated remote attackers can exploit missing authorization checks in the Unlimited Elements for Elementor (Free Widgets, Addons, Templates) WordPress plugin, affecting all versions through 2.0.20. Because the vulnerable endpoint performs no proper access-control validation, a request sent without authentication can reach restricted functionality or data, though the assessed impact is limited to low confidentiality loss with no integrity or availability effect, giving a CVSS 3.1 base score of 5.3. There is no indication of confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; the primary prerequisite is simply that an affected, active installation of the plugin be reachable over the network.
Missing authorization in Gemini Labs Site Reviews WordPress plugin through 8.3.2 lets unauthenticated remote attackers trigger an improperly access-controlled action, potentially modifying site data with limited integrity-only impact; confidentiality and availability are not affected per the assessed CVSS vector. The flaw is CWE-862 and requires no authentication, no user interaction, and no special privileges in default configurations, making it remotely reachable on sites where the plugin is active. No public exploit or confirmed active exploitation is indicated by the available data, and no fixed version is named in the provided intelligence; Patchstack reported the issue.
WP Ultimate CSV Importer plugin for WordPress, through version 9.1, exposes embedded sensitive data to unauthenticated network attackers. The plugin inserts sensitive information into sent data, allowing retrieval of partial confidential information without authentication, user interaction, or special configuration. The impact is confidentiality-only and low-to-moderate, with no public exploit code identified at time of analysis.
Authenticated users on MISP instances before 2.5.48 can read restricted discussion thread titles and quoted post content, and can inject new posts into threads they are not authorized to participate in, because PostsController::add validated only the thread's organization-only distribution flag instead of the full thread access control list (sharing-group membership and associated event visibility). Exploitation requires a valid MISP account (the CVSS vector shows PR:L, so it is not exploitable unauthenticated) plus knowledge or enumeration of a target thread ID, but no user interaction. No public exploit code has been identified at the time of analysis, and the impact is confined to confidentiality and integrity of discussion content, making this a genuine but modest-severity authorization flaw rather than a critical one.
Authorization scope leakage in Apache APISIX 2.3.0 through versions before 3.7.0 allows an authenticated attacker to have a prior request's Keycloak authorization scope bleed into a later request on the same route, producing unintended authorization expansion and inconsistent access-control decisions. Exploitation requires the route to be running the authz-keycloak plugin in a supported configuration and depends on request timing/ordering across a shared route state rather than a single self-contained request, which keeps this a modest-severity access-control defect rather than a broad compromise path. The vendor has released a fix in 3.7.0; no public exploit code was identified and the issue is not confirmed as actively exploited (no CISA KEV listing) at time of analysis.
FluentForm WordPress plugin versions through 6.2.14 allow a remote, unauthenticated attacker to remove or alter intended client-side form functionality due to an incorrect behavior order flaw (CWE-696). The assessed impact is limited to integrity of client-side behavior (I:L) with no data disclosure, server compromise, or availability loss, and no public exploit or active exploitation has been identified at time of analysis.
Cross-site request forgery in the post feedback function of Ghost CMS lets an attacker submit feedback on behalf of any logged-in member who visits a crafted link, affecting versions 5.19.0 up to (but not including) 6.57.1. The attacker needs no account on the target site, but the attack only works against a victim who is an authenticated member with an active session and who follows the malicious page, and the resulting impact is integrity-only - unwanted feedback entries with no confidentiality or availability effect (CVSS 3.1: 5.3). No public exploit code was identified at time of analysis, and the vendor has released a fix in Ghost 6.57.1.
Information disclosure in Ghost CMS affects versions 5.125.1 up to but not including 6.57.1, where the Admin Feedback endpoint omits a proper authorization check and lets an authenticated staff user retrieve member records they should not be able to see. The flaw is credential-gated (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), needs no user interaction, and is limited to confidentiality of member data with no integrity or availability impact, which is why the published 5.3 base score reflects a moderate rather than emergency-level risk. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, so realistic exposure depends mainly on how many staff accounts an instance provisions and how sensitive its member records are.
A race condition in Ghost CMS's staff invitation acceptance flow (affecting versions 0.5.0 through 6.22.x) allows someone holding a valid invitation token to create more than one user account from that single-use invite by firing concurrent acceptance requests before the token is marked consumed. The impact is integrity-only and low (independent assessment: CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, matching the published 5.3), since exploitation is opportunistic rather than deterministic and requires a legitimately issued staff invite token; no public exploit code or confirmed active exploitation was identified at time of analysis. Ghost 6.23.0 contains the vendor fix.
Authenticated low-privilege staff users on Ghost sites can read Admin API keys that should only be visible to higher-privileged accounts, handing them credentials intended for trusted integrations. The exposure affects the Ghost npm package from 3.23.0 through 6.22.x and is resolved in 6.23.0, with the CVSS vector (PR:L, AV:N, no UI) confirming that a valid staff login on a remote instance is the only prerequisite. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the independent assessment rates this as a genuine but modest-severity information-disclosure and privilege-escalation risk driven by insider or compromised-staff scenarios rather than unauthenticated remote attack.
Authenticated low-privilege staff users on Ghost CMS versions 4.3.0 through 6.57.x can abuse staff tokens to modify posts beyond the permissions granted to their role, effectively bypassing the post-editing restrictions that separate Authors and Contributors from higher-privileged editors. Exploitation requires a valid, already-provisioned staff account (PR:L in both the reported and independently assessed vectors), so it is not reachable by anonymous internet users, and the impact is confined to unauthorized content modification (integrity) with no data disclosure or availability loss. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so this is a moderate, authenticated-only authorization flaw rather than a widespread-exploitation priority; a vendor patch is available from Ghost in version 6.58.0.
Staff invite acceptance in Ghost before 6.62.0 allows the holder of a valid invite token to create their account with an arbitrary, attacker-chosen email address instead of the address the invite was issued to, breaking the binding between an invited identity and the resulting staff account. Exploitation is authenticated (CVSS PR:L) and depends on a legitimate invite token already existing and having been leaked, forwarded, or otherwise exposed - a remote unauthenticated attacker cannot mint an invite and trigger this on their own - and the assessed impact is integrity-only with no confidentiality or availability loss (CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), making this a low-to-moderate risk issue despite the 'authentication bypass' label. No public exploit identified at time of analysis; the vendor has released a fix in Ghost 6.62.0.
Order payment integrity in the Payments for Hubtel WordPress plugin before 1.0.2 can be bypassed because the plugin's payment callback/notification (IPN) handler does not verify that incoming notifications actually originate from the payment provider, allowing unauthenticated remote attackers to mark arbitrary orders as paid without any money changing hands. Any WordPress site running the affected plugin is exposed by default, since the callback endpoint must remain network-reachable for the legitimate provider; the only practical prerequisite is referencing a valid or guessable pending order ID. Rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), this is a moderate integrity-only flaw - no CISA KEV listing, no public exploit identified at time of analysis, and EPSS data was not supplied; the vendor has released a fix in 1.0.2.
Unauthenticated information disclosure in the Payments for Hubtel WordPress plugin (all versions before 1.0.2) allows remote attackers to retrieve the order key of an arbitrary order through the plugin's public payment-callback request and then view that order's contents. The flaw is an authorization bypass through user-controlled key (CWE-639): the callback handler redirects the requester without verifying they are permitted to view the order, so an attacker needs only to reach the callback endpoint and reference or guess a valid order identifier. It is a genuine but modest-severity issue (CVSS 3.1 base 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), with no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the practical limit is that it grants read-only exposure of one order at a time and does not permit modification, privilege escalation, or service disruption.
Unauthenticated attackers who obtain a valid signed click-tracking URL from the Newsletter - Send awesome emails from WordPress plugin (all versions up to and including 9.3.9) can receive a subscriber's permanent raw authentication token in a Set-Cookie response header and use it to export that subscriber's full PII record, rewrite their stored profile, or silently unsubscribe them. Exploitation requires possession of one leaked signed link - such links are embedded in every external link of every newsletter, carry no timestamp, and never expire until the site's relink key rotates - but no nonce, password, authentication, or email challenge is needed once the URL is observed. Rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N, with confidentiality and integrity impact of Low per independent assessment); no CISA KEV listing and no public exploit code identified at time of analysis, making this a bounded data-privacy and account-manipulation issue rather than a server-compromise emergency.
Path traversal in David-Crty databasement up to 1.7.1 lets a high-privileged authenticated user escape the intended backup volume by supplying a crafted schema_name to the database-servers restore API endpoint, reaching filesystem locations outside the restore target. The attack is network-reachable but rated high-complexity and difficult to exploit, and its assessed impact is limited to low confidentiality, integrity and availability with no scope change. Publicly available exploit code exists, though there is no confirmed evidence of active exploitation; the issue is fixed in 1.7.2.
Server-side request forgery in Ghost (TryGhost) versions 1.18.0 through 6.27.0 allows an authenticated staff-level user with permission to create or edit webhooks to make the Ghost server send requests to internal network resources, including cloud metadata services. Vendor scoring is CVSS 5.1 with PR:H, reflecting that the attacker must already hold privileged access; no public exploit code was identified at time of analysis and there is no CISA KEV listing.
Prototype replacement in stream-json before 3.6.0 lets a JSON key literally named __proto__ overwrite the prototype of an assembled object, because Assembler and FlexAssembler wrote properties with plain assignment and thereby invoked the inherited setter instead of creating an own data property. Applications that read authorization, feature-flag, or control-flow values through prototype inheritance from a parsed object - or that call Object.prototype methods on it - can consume attacker-controlled inherited properties or hit runtime errors when the prototype is null; the global Object.prototype is never polluted, so impact is confined to the individual parsed object (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L, low integrity and availability impact only). No public exploit code was identified at time of analysis and the issue is not in CISA KEV, but the flaw is genuine and its real-world exposure hinges on a disputed threat model: the maintainer documents intended input as locally owned dumps, exports, and logs (AV:L) while the reporter treats untrusted JSON parsing as part of the library contract, and no authentication or user interaction is required once hostile JSON reaches the parser (PR:N/UI:N).
Stack-based buffer overflow in OpenSC's SetCOS smart-card driver (setcos_construct_fci_44 in src/libopensc/card-setcos.c) lets attacker-influenced file attribute data overwrite a fixed-size stack buffer during a file-creation operation. OpenSC builds through 0.27.1 that compile in the SetCOS driver are affected; per the assessed CVSS:3.1 vector (AV:L/PR:L/UI:R) this is a local, low-privilege issue that requires user interaction, such as a user running OpenSC tooling against a malicious or manipulated SetCOS card, with limited confidentiality, integrity and availability impact. Although the upstream fix is publicly visible as a GitHub commit and pull request, no public exploit code or confirmed active exploitation was identified at time of analysis.
Stored cross-site scripting in the Prime Mover WordPress plugin before 2.2.1 allows an authenticated low-privilege attacker who can write a crafted package into the plugin's prime-mover-export-files directory to execute arbitrary JavaScript in an administrator's browser. The malicious site_title value inside a package's footprint.json is rendered unescaped by the column_site_title() method in PrimeMoverBackupMenuListTable.php whenever an admin opens the Prime Mover Packages list table, and no package restoration is required for the payload to fire. Exploitation is bounded rather than drive-by: the attacker needs a prior write foothold on that directory and the payload is inert until a privileged user views the specific admin screen; no public exploit code has been identified at time of analysis, there is no CISA KEV listing, and no EPSS score was supplied in the available data.
Improper issuer validation in Apache APISIX 3.12.0 through 3.18.0 lets an attacker who already holds a valid token for one issuer get that token accepted on an API route restricted to a different issuer, when the openid-connect plugin is configured for remote introspection against an authorization server that serves multiple issuers. The exposure is configuration-dependent: single-issuer auth servers, routes that do not use the openid-connect plugin, and deployments using local JWT validation instead of remote introspection are not affected, and versions 3.19.0 and later are patched. No public exploit code has been identified at time of analysis, and there is no confirmed active exploitation (CISA KEV); the CVSS 4.0 base score is 5.1 with subsequent-system confidentiality impact, reflecting a genuine but conditional authentication-boundary weakness rather than a widespread emergency.
Path traversal in the Ghost CMS ImageSize service (versions 6.14.0 through releases prior to 6.27.0) lets an authenticated staff user with elevated privileges read arbitrary local files from the server outside the intended data/storage directories. Exploitation is network-reachable and requires no user interaction, but is gated behind valid staff credentials, so the impact is bounded to file disclosure (confidentiality only, with no integrity or availability effect). No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV), making this a moderate, authentication-gated risk (CVSS 5.1) that the vendor has fixed in Ghost 6.27.0.
Reflected cross-site scripting in MISP before 2.5.48 lets an attacker execute arbitrary JavaScript in an authenticated site administrator's browser by luring that admin to a crafted URL whose taxonomy tag name parameter is echoed unescaped into the legacy add_tag and disable_tag confirmation views. Exploitation requires no credentials or prior access to the instance (PR:N), but it cannot be self-triggered: the payload only fires in the victim admin's session after active user interaction with a malicious link (UI:A), so convincing phishing is the decisive limiting factor. There is no CISA KEV listing and no public exploit code identified at time of analysis, and the vendor has released a patch (fixed in 2.5.48, commit 9619083c8), making this a genuine but low-to-moderate priority issue rather than an exploitable-at-scale flaw.
Hard-coded credentials in Johnson Controls EasyIO FS32 firmware before 3.0b63 allow an attacker with adjacent-network access to use embedded login secrets and cause a high availability impact on the controller; the assessed CVSS 3.1 vector is AV:A/AC:L/PR:N/UI:N with only availability affected (C:N/I:N/A:H). This is not remotely internet-exploitable, the vendor notes an additional precondition (CVSS 4.0 AT:P), and no public exploit identified at time of analysis, making it a moderate, context-dependent risk. Johnson Controls lists the fix as EasyIO FS32 firmware 3.0b63 and later, with the advisory at its trust center.
Revoking runtime permissions from other apps is possible on Motorola devices running Motorola Setup App versions before the 2026-01-01 fixed release, because an exported Setup App component lacks a guarding permission (CWE-862). A local, low-privilege malicious app already installed on the same device can trigger this without user interaction (CVSS 4.8, PR:L/UI:N); remote exploitation is not possible, and there is no data disclosure. No public exploit code identified at time of analysis, and the vendor has made a patch available.
Predictable machine-account passwords produced by the adjoin utility in Fortra BoKS Server Agent can be guessed by a remote, unauthenticated attacker who can estimate when the password was generated, because the utility's generation routine yields significantly less entropy than intended. Rated CVSS 4.8 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N), the exposure is limited to AD-integrated deployments that ran an Active Directory join or machine-account password renewal through adjoin; the timing dependency required to narrow the password space is the principal barrier, reflected in the high attack-complexity metric. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, and the impact is confined to predicting that specific machine-account credential rather than achieving direct host compromise.