Stored cross-site scripting in the Motors - Car Dealership & Classified Listings WordPress plugin (versions up to and including 1.4.123) allows authenticated attackers with Subscriber-level access to inject arbitrary web scripts via the 'stm_f_s' parameter. The CSRF nonce protecting the stm_ajax_add_a_car AJAX handler is emitted in wp_footer on every page, so any logged-in user can retrieve it, removing the usual barrier to exploitation. This is a moderate-risk issue (CVSS 6.4) and no public exploit has been identified at the time of analysis.
Stored cross-site scripting in the HivePress WordPress plugin (Business Directory, Listings & Classified Ads) affects all versions up to and including 1.7.31 and allows authenticated users with subscriber-level accounts or higher to inject arbitrary JavaScript that executes when other users view the affected listing page. Exploitation is conditional, not universal: the site must permit subscriber-level registration or listing submission, and an administrator must have configured a HivePress Text attribute whose display format places the %value% token inside an HTML attribute (for example title="%value%"), which is a documented but non-default HivePress pattern - a default configuration that renders %value% as normal element text is not exploitable. The vendor has released 1.7.32, which includes the fix for escaping field and token values; no public exploit code has been identified at time of analysis, and the flaw is not confirmed actively exploited (CISA KEV). Independent assessment rates the practical severity as moderate and conditionally exploitable, with attack complexity assessed as High (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N) rather than the published AC:L rating.
Stored cross-site scripting in the Sonaar MP3 Audio Player - Music Player, Podcast Player & Radio plugin for WordPress (all versions up to and including 5.14.2) allows authenticated users holding contributor-level access or higher to inject arbitrary JavaScript through the plugin's shortcode attributes, which then executes in the browser of any user who later loads the affected page. The payload survives WordPress's save-time wp_kses_post sanitization because it is carried in a shortcode attribute rather than raw post HTML, so the unescaped value reaches render time intact. The flaw is authentication-gated and rated CVSS 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), and no public exploit was identified at time of analysis; there is no CISA KEV listing for this CVE.
Stored cross-site scripting in the Download Manager WordPress plugin (all versions up to and including 3.3.71) allows an authenticated attacker holding contributor-level access or above to inject arbitrary JavaScript into pages via the 'regurl' parameter, which then executes for logged-out site visitors who load the affected page. Because the vulnerable login-form.php template branch is gated on !is_user_logged_in(), the payload only fires for anonymous traffic and never for authenticated viewers, which confines the impact despite the CVSS 6.4 score. No public exploit code has been identified and the issue is not flagged as actively exploited, so urgency is moderate and concentrated on sites that grant contributor roles or open registration to low-trust users.
Stored cross-site scripting in the GeoDirectory WordPress plugin (all versions up to and including 2.8.188) allows authenticated users with subscriber-level access or above to plant arbitrary JavaScript in listing data via the 'Contact Email' custom field, which then executes in the browser of anyone viewing the affected public single-listing page. Exploitation is not a default-configuration issue: the site administrator must first have added and configured the Contact Email custom field (htmlvar_name 'email') to render on public single-listing output and must subsequently approve the attacker's submitted listing before the payload becomes live, which is why the independent assessment rates the vector AC:H and describes this as conditionally exploitable rather than broadly reachable. There is no public exploit code or confirmed active exploitation at time of analysis, and no EPSS or KEV signal accompanies this record; residual risk is concentrated in sites that permit low-privilege registration, accept untrusted listing submissions, and expose the Contact Email field publicly.
Stored cross-site scripting in the Advanced Classifieds & Directory Pro WordPress plugin (versions up to and including 3.4.4) allows an authenticated attacker holding a 'custom-level' account or higher to inject arbitrary JavaScript through the 'phone' parameter of a listing, which then executes for any user viewing the poisoned page. Exploitation is gated behind two non-default operator choices: the 'Force Bootstrap' miscellaneous setting must be enabled and the 'ACADP Listing Address' widget must be placed in a sidebar rendered on single listing pages, so default-configured sites are not exposed. No public exploit code or confirmed in-the-wild exploitation (CISA KEV) was identified at time of analysis, and the reported CVSS 6.4 score is softened by our reassessment to AC:H given the stacked prerequisite chain.
Stored cross-site scripting in the WordPress plugin Team - Team Members Showcase (slug 'tlp-team', vendor techlabpro1) affects all versions up to and including 6.0.2 and lets authenticated attackers with contributor-level privileges or above persist arbitrary JavaScript via the 'ttp_filter_taxonomy' taxonomy-meta value of an attacker-chosen post. The script then executes in the browser of any user - including higher-privileged users such as editors or administrators - who views a page where the plugin's shortcode renders that taxonomy filter output, giving a CVSS 6.4 impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N). No public exploit identified at time of analysis, and there is no CISA KEV confirmation of active exploitation, so risk is concentrated on sites that grant contributor access to untrusted users; there is no unauthenticated path (PR:L).
Stored cross-site scripting in the Table Field Add-on for ACF and SCF (WordPress plugin slug advanced-custom-fields-table-field, vendor jonua) affects all versions up to and including 1.4.1-RC2, allowing an authenticated attacker with subscriber-level access or above to inject arbitrary scripts into table field values that execute when a victim views a page rendering that field. The issue carries a CVSS 3.1 base score of 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), reflecting the low privilege bar and scope change typical of stored XSS inside the WordPress rendering context, though exploitation stops short of RCE and depends on a victim viewing the poisoned content. No public exploit identified at time of analysis, and no evidence of active exploitation; vendor-released patch: 1.4.1.
Stored cross-site scripting in the PeproDev Ultimate Profile Solutions WordPress plugin (all versions up to and including 8.2.36) allows an authenticated attacker holding contributor-level privileges or higher to inject arbitrary JavaScript into a page via the 'button' attribute of the shortcode, which is stored without sanitization and rendered without output escaping. The payload executes in the browser of any user who later views the injected page, and because the injected content lives in persistent post data it can trigger against administrators and other privileged viewers. Rated CVSS 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N); no public exploit code has been identified at time of analysis and there is no indication of active exploitation, so this should be treated as a moderate-priority issue rather than an emergency.
Stored cross-site scripting in the Graphene theme for WordPress through version 2.9.4 allows any authenticated user holding Subscriber-level access or above to plant persistent JavaScript in the theme's 'Current location' and 'Author profile image URL' profile fields, which then executes in the browser of every user who loads a page rendering that author data - including administrators. The flaw stems from insufficient input sanitization and output escaping (CWE-79) and was reported by Wordfence; the CVSS 3.1 score is 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), reflecting that the attacker needs only a low-privilege account but the injected script can run in a scope beyond the vulnerable component. There is no KEV listing and no public exploit code identified at time of analysis, and the fixes appear in the WordPress theme Trac changesets comparing 2.9.4 against 2.9.6.
Stored cross-site scripting in the GamiPress WordPress gamification plugin (all versions up to and including 7.9.4) allows any authenticated user with subscriber-level access or higher to inject arbitrary JavaScript through the 'video_id' parameter processed by the plugin's YouTube integration, which then executes in the browser of any user viewing the poisoned page. Exploitation requires a valid low-privilege account on the affected site plus a victim loading the injected content; the impact is most serious when the victim is an administrator, since the script runs in the site's origin and can be used to hijack sessions or perform privileged actions. There is no public exploit identified at time of analysis and the issue is not confirmed as actively exploited, making this a moderate-severity (CVSS 6.4) but credible priority for sites that allow open registration and use the YouTube integration.
Stored cross-site scripting in the Frontend Admin by DynamiApps WordPress plugin through version 3.28.36 lets authenticated users with Contributor-level or higher access inject arbitrary web scripts by exploiting a kses/mutation-XSS bypass in the get_dynamic_values function, which performs text-level find-and-replace on post content without HTML-aware parsing. The stored payload executes when another user views the affected page, and the CVE carries a CVSS 3.1 score of 6.4 with scope change. This is a moderate-priority issue rather than a top-tier emergency, and no public exploit identified at time of analysis; practical risk is limited to sites that grant untrusted users Contributor-or-higher roles and have the plugin active.
Stored cross-site scripting in the Avada theme for WordPress (versions up to and including 7.16.1) allows authenticated attackers with Subscriber-level access or higher to inject javascript: URLs into author social link profile fields, which execute when a victim visits the attacker's author archive page and clicks the affected social icon. Exploitation is constrained by required user interaction and by the Avada option 'Open Social Icons in a New Window' being set to Off so the browser does not block the javascript: URL in a new tab. This is a moderate-severity issue (CVSS 6.4) that does not rise to emergency priority, and no public exploit was identified at time of analysis.
Stored cross-site scripting in the Brizy - Page Builder WordPress plugin, affecting all versions up to and including 2.8.18, lets an authenticated attacker with contributor-level access or higher inject arbitrary JavaScript through the 'brizy-compiled-sections' parameter when creating or editing page content. Because the payload is persisted and rendered without adequate escaping, the script executes in the browser of any user - including higher-privileged editors or administrators - who subsequently views the injected page, and the CVSS scope-change (S:C) reflects that the code runs in the victim's session context rather than the attacker's. Rated CVSS 6.4 and reported by Wordfence, there is no public exploit code and no confirmed active exploitation (CISA KEV) at time of analysis, making this a routine patch-management priority rather than an emergency.
Stored cross-site scripting in the Data Tables Generator by Supsystic WordPress plugin (all versions up to and including 1.12.03) allows an authenticated attacker holding contributor-level access or higher to inject arbitrary script into a table's id attribute, which is then stored and executed in the browser of any user - including an administrator - who views the affected page. The issue is rated CVSS 6.4 with a scope change (S:C) because the injected script executes in the security context of the hosting site rather than merely the plugin, giving the attacker a path to session theft, content tampering, or administrative action on behalf of the victim. No public exploit code and no confirmed active exploitation were identified at time of analysis, and an upstream fix has been committed to the plugin repository (changeset 3608322).
Stored cross-site scripting in the Embed Any Document WordPress plugin (all versions through 2.7.13) lets authenticated users with contributor-level access or above plant arbitrary JavaScript in post content through the plugin's 'embeddoc' shortcode; the script lies dormant until any visitor - commonly a higher-privileged editor or administrator reviewing the page - loads the affected content. The issue carries a CVSS 3.1 score of 6.4 (medium), with a vector of AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N that confirms remote reachability but an authenticated (PR:L) prerequisite and a scope change indicating execution in the context of the site. No public exploit code identified at time of analysis, and real-world exposure is limited to sites that run the vulnerable plugin, permit the 'embeddoc' shortcode in author-controllable content, and grant contributor accounts to untrusted parties.
Stored cross-site scripting in the Getwid - Gutenberg Blocks plugin for WordPress (all versions up to and including 3.0.1) allows authenticated attackers with contributor-level privileges or higher to inject arbitrary web scripts through the 'data-image-points' parameter, which are then stored and executed whenever another user - an editor, administrator, or site visitor - accesses the affected page. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N confirms the attacker needs a low-privileged authenticated account but requires no victim interaction to trigger the payload beyond viewing the injected page, and the changed scope indicates the script executes in the context of the broader site rather than the attacker's own content. No public exploit code has been identified at the time of analysis and there is no indication of confirmed active exploitation (CISA KEV), so practical exposure is concentrated on sites that provision contributor accounts to untrusted users or allow open registration; a site with only a single administrator and no contributor roles faces minimal real-world risk.
Stored cross-site scripting in the Church Admin plugin for WordPress (all versions up to and including 5.1.2) lets an authenticated attacker with subscriber-level access or above inject arbitrary script through the plugin's 'email' parameter, which is neither sanitized on input nor escaped on output. The injected payload persists in the database and executes in the browser of any user who later views the affected page - typically an administrator or other privileged staff member reviewing church member records - making it a low-complexity path from a throwaway subscriber account to privileged session compromise. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (no CISA KEV listing); with a CVSS base of 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) this should be treated as a patch-when-convenient issue rather than an emergency. Sites that permit open self-registration are meaningfully more exposed, since the attacker must first hold a valid low-privilege account.
Stored cross-site scripting in the Table Field Add-on for ACF and SCF (WordPress plugin, all versions up to and including 1.3.35) lets an authenticated attacker holding Contributor-level privileges or higher inject arbitrary JavaScript through table cell content, which then executes in the browser of any user who later views the affected page. The flaw is a classic CWE-79 defect: cell content is insufficiently sanitized on input and insufficiently escaped on output, so payloads persist in post data and are served back to victims. Rated CVSS 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) with scope change because the script runs in the security context of the site and can reach higher-privileged viewers; no public exploit code and no confirmed active exploitation were identified at time of analysis, so this is a moderate-priority hardening item rather than an emergency.
Stored cross-site scripting in the WordPress Download Manager plugin (codename065, versions up to and including 3.3.58) lets authenticated attackers with Contributor-level access or higher inject arbitrary JavaScript through the 'not_found' parameter processed by the plugin's shortcode handler; the stored script then runs in the browser of any user who views the injected page. The flaw is rooted in insufficient input sanitization and output escaping (CWE-79), has a CVSS 3.1 base score of 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), and is corrected in version 3.3.59. Unauthenticated and Subscriber-only users cannot trigger it, and no public exploit code was identified at time of analysis.
Missing authorization checks in the Upcasted S3 Offload plugin (published as 'AWS S3 for WordPress Plugin - Upcasted') through version 3.1.0 let any authenticated user holding only the Subscriber role invoke plugin functionality that should be reserved for higher-privileged accounts, yielding limited confidentiality, integrity, and availability impact rather than full site takeover. The attack is network-reachable and requires no user interaction, but the PR:L rating means an attacker must first possess a valid low-privilege WordPress account - most commonly obtained through open or self-service user registration - which is the principal limiting factor on real-world exposure. There is no public exploit code identified at time of analysis and no indication of active exploitation, and the moderate CVSS score of 6.3 reflects the constrained, low-impact actions that the missing check exposes.
Reflected cross-site scripting in the Filter Everything - WordPress & WooCommerce Filters plugin (versions up to and including 1.9.6) lets unauthenticated remote attackers inject arbitrary web scripts via the flrt_elementor_load_more_anchor() output, which execute when a victim clicks a crafted link that reaches the Elementor load-more code path. The flaw is rated CVSS 6.1 (Medium) with vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N and requires both victim interaction (UI:R) and the Elementor-integrated load-more/AJAX filtering feature to be reachable on the target page; no public exploit identified at time of analysis.
Reflected cross-site scripting (XSS) in the Payment Plugins for Stripe WooCommerce WordPress plugin, affecting all versions up to and including 4.0.17, enables unauthenticated attackers to inject arbitrary web scripts through the '#response' URL fragment when a victim opens a crafted link. Exploitation is further conditional on the plugin's 'Generic Errors' setting being unchecked, which causes raw Stripe error strings to be reflected into the page; there is no public exploit identified at time of analysis and no CISA KEV listing. The vendor-provided CVSS 3.1 score is 6.1 (moderate), and the independent assessment raises attack complexity to High given the required non-default configuration and mandatory user interaction.
Reflected cross-site scripting (XSS) in the Form Maker by 10Web WordPress plugin (versions up to and including 1.15.48) allows unauthenticated attackers to inject arbitrary web scripts via the 'inputs' array key parameter. Exploitation requires tricking a user into clicking a crafted link while a vulnerable form page is reachable; the impact escalates if an authenticated administrator is the victim. No public exploit identified at time of analysis, and the vendor released a patch in version 1.15.49.
Reflected cross-site scripting in the Favicon Rotator plugin for WordPress (all versions up to and including 1.2.11) allows unauthenticated attackers to inject arbitrary JavaScript through any request parameter prefixed with 'fvrt_', which the plugin reflects back into a page without adequate sanitization or output escaping. Exploitation is not direct: because the CVSS vector is AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, the attacker must deliver a crafted link and convince a victim to click it, after which the script executes only in that victim's browser, potentially stealing session data, altering page content, or acting as the victim - with an administrator victim yielding the greatest impact. This is a moderate-severity reflected XSS that warrants routine, lower-priority patching; no public exploit code was identified at time of analysis, and the vendor's 1.2.12 release addresses the flaw.
Reflected cross-site scripting in the WordPress Download Manager plugin (codename065, all versions up to and including 3.3.57) lets unauthenticated attackers inject arbitrary JavaScript that executes in a victim's browser when they load a crafted link containing a malicious payload in the 'REFERRER' parameter. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, 6.1) confirms no authentication is required but a successful attack depends on victim interaction, making phishing or social-engineering delivery the realistic path rather than silent mass exploitation; the scope is changed (S:C), so script execution can reach beyond the plugin's own page context. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so this is best treated as a moderate-severity, high-prevalence-product hygiene fix rather than an emergency.
Information exposure in mini-swe-agent versions 1.10.0 through 2.4.6 allows remote attackers to read sensitive environment variables, such as API keys, from the host system when the BubblewrapEnvironment sandbox is used. The sandbox fails to clear the environment (missing --clearenv), so sandboxed commands inherit the host environment. An attacker can leverage prompt injection in processed task content to direct the agent to exfiltrate these secrets over the network. Exploitation requires the use of BubblewrapEnvironment, presence of sensitive variables in the environment, and attacker-controlled task content; it is a moderate, context-dependent risk, and no public exploit has been identified at the time of analysis.
Authenticated users of OpenLIT 2.1.0 can read telemetry belonging to other projects - including captured LLM prompts and completions - by forging the x-openlit-project-id header against the trace read API, because the server trusts the client-supplied project identifier without re-checking that the caller actually owns the referenced project. Exploitation requires a valid account on the target instance plus prior knowledge of both the victim's project id and its corresponding database config id, which restricts meaningful impact to multi-tenant or shared deployments where projects cross trust boundaries; a single-tenant installation has no cross-tenant victim to reach. The effect is confidentiality-only (no modification or availability impact), and no public exploit code or confirmed active exploitation (no CISA KEV listing) was identified at time of analysis, so this is assessed as a medium-severity authorization bypass rather than an emergency.
Sub-agent spawning in the Phi AI agent (versions 0.3.0 through 0.28.4) accepts an unchecked workdir argument, allowing a spawned worker to be rooted outside the intended workspace and thereby bypass the workspace_only_writes and readonly protection modes. Untrusted or attacker-influenced content processed by the agent can carry prompt-injected instructions that trigger a spawn with an alternate working directory, resulting in unapproved file writes anywhere the user running Phi already has write permission. The flaw is rated CVSS 4.0 6.0 (CWE-863 incorrect authorization), is remotely reachable without credentials but requires passive user interaction and a pre-existing agent deployment; no public exploit identified at time of analysis, and impact is bounded to integrity (no confidentiality or availability loss) with no privilege gain beyond the invoking user.
Arbitrary file write in the Cohere Python SDK 5.11.0 through 7.2.0 arises from unvalidated tar archive extraction in the _s3_models_dir_to_tarfile helper used by the SDK's cohere_aws SageMaker integration. An attacker who can place a crafted model archive into the S3 prefix the SDK reads from can embed absolute paths or ../ traversal members that, once tarfile.extractall runs on the victim host, overwrite files outside the intended model directory. Exploitation is precondition-heavy: it requires the affected SageMaker model-archive flow to be in use, attacker write access to the victim's S3 model location, and the victim to trigger the extraction (passive user interaction); there is no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status. EPSS and KEV data were not provided, and the impact is scored as integrity-only (no confidentiality or availability effect), making this a medium-severity, precondition-dependent flaw.
Authenticated InnoShop 0.9.2 administrators who hold the files_create permission can read arbitrary server files and have their contents written to the publicly served media disk by abusing the AI Core MCP file_upload tool's source argument, exposing the application's .env file with APP_KEY and database credentials. Because exploitation requires a high-privilege admin account plus MCP/AI Core being enabled and reachable (CVSS 4.0 5.9; independently assessed as CVSS 3.1 AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N), this is a moderate - not high - priority issue whose realistic threat model is a malicious or compromised administrator escalating to theft of application secrets rather than an unauthenticated outsider. No public exploit code was flagged in the provided intelligence and there is no confirmation of active exploitation (not in CISA KEV), although a public technical writeup describing the stream-wrapper technique is referenced.
Unauthenticated sensitive data exposure in the WordPress plugin Swish Migrate and Backup (versions 1.4.0 and earlier) lets remote attackers retrieve data the plugin should have kept private, with the impact confined to confidentiality (CVSS 5.9, C:H/I:N/A:N). Exploitation is not trivial: the CVSS vector (AV:N/AC:H/PR:N/UI:N) marks high attack complexity, meaning a specific transient or plugin-operation condition - such as a backup or migration in progress, or an exposed backup artifact - must be met before the leak occurs, and the available data does not identify the exact trigger. At time of analysis no public exploit code has been identified, the issue was reported by Patchstack, and it is a moderate-priority information disclosure rather than a top-tier emergency; the niche deployment of this plugin further limits realistic exploitation.
Unauthenticated remote attackers can retrieve embedded sensitive information from WordPress sites running the WP Rollback plugin through version 3.1.2, because the plugin places sensitive data into data it sends back to the client (CWE-201). The flaw is rated CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), meaning no credentials or user interaction are needed but attack complexity is high, so success depends on conditions the attacker does not control - such as the specific sensitive data being present in the affected responses or a particular plugin state. There is no public exploit code identified at time of analysis and no confirmation of active exploitation (CISA KEV); the exposure is limited to confidentiality, with no integrity or availability impact, and the exact data exposed is not described in the available advisory and should be confirmed with the vendor/Patchstack.
Read-only mode bypass in Tabularis through 0.27.0 lets prompt-injected AI agents or untrusted MCP clients execute data-modifying SQL that the run_query safety gate misclassifies as read-only, allowing side-effecting statements such as setval, nextval, or PostgreSQL query_to_xml with an embedded DELETE to alter or destroy data without triggering an approval prompt. The issue is a local, MCP-channel authorization flaw (assessed CVSS:3.1 AV:L/AC:L/PR:N/UI:R, C:N/I:H/A:H; CVSS 4.0 base 5.8) that only matters when read-only mode is relied upon as a security control against a backend exposing such functions, and the provided CVSS vector indicates no privileges are required (PR:N) while the operator still must interact with the agent (UI:P). No public exploit code was identified at time of analysis and there is no CISA KEV listing, so risk is driven by preconditions-an exposed MCP run_query connection to PostgreSQL-rather than by active exploitation.
Symlink-based workspace escape in phi 0.1.1 through 0.28.4 lets a malicious repository bypass the agent's workspace_only_writes permission gate and cause the write tool to modify files outside the workspace. The gate compares only the lexical path string, so a symlink committed in the repository that resolves outside the workspace passes validation once prompt injection steers the agent's write tool at that path; the resulting impact is integrity-only (unauthorized out-of-workspace writes) with no confidentiality or availability loss, consistent with the assessed CVSS:3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N and the reported CVSS 4.0 base of 5.7. Exploitation is local and requires the victim to run the agent against an attacker-influenced repository with workspace_only_writes active, making this a medium-severity sandbox escape rather than a remote threat; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Information disclosure in ZTE Z80 Ultra (nubia Z80 Ultra) smartphones allows a local app to reflectively invoke a system interface that lacks the necessary access-control check and read otherwise-protected information, with no integrity or availability impact. The vendor rates this CVE-2026-108501 at CVSS 5.7 (AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), while the independent assessment treats it as a local, unauthenticated information-disclosure issue (CVSS 3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) that requires code execution on the device via an attacker-controlled app. No public exploit code or confirmed active exploitation was identified at time of analysis, and the issue is confined to the ZTE Z80 Ultra model.
Sandbox escape in open-multi-agent's @open-multi-agent/core 1.5.0 through 1.21.2 lets an attacker write attacker-influenced files anywhere the agent process has write permission by planting a dangling symlink inside the agent workspace and using prompt injection to steer the file_write built-in tool toward that symlink path. Impact is integrity-only in the assessed vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N), and exploitation is gated on two preconditions combining: attacker-controlled symlink placement in the workspace plus prompt-injection influence over the agent, so this is a genuine but moderate-priority issue rather than a remote, default-configuration exploit. No public exploit code or active exploitation was identified at time of analysis, and the flaw requires local reachability with no privileges required per the assessed vector.
Information disclosure in ZTE Z80 Ultra allows a malicious or compromised third-party app installed on the device to invoke system interfaces through reflection and retrieve sensitive information, because those interfaces lack robust invocation authentication and access control. Exploitation is local and requires user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), with confidentiality impact only and no integrity or availability effect. No public exploit identified at time of analysis; the issue is classified under CWE-269 and tagged as privilege escalation, but the assessed impact is a moderate, local-only information-disclosure flaw rather than a high-priority remote threat.
Information disclosure in ZTE Z80 Ultra allows a locally installed application to read device-related information by invoking framework methods that have insufficient access control. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, score 5.5) means an attacker needs local access and must persuade or trick the user into installing or interacting with a malicious app, with impact limited to confidentiality; there is no integrity or availability impact and no privilege gain, despite the 'Privilege Escalation' tag. No public exploit code is identified at time of analysis, and the issue is assessed as moderate and locally scoped.
Stored cross-site scripting (XSS) in the Noptin Newsletter WordPress plugin up to version 4.3.10 allows unauthenticated attackers to inject malicious scripts that execute in the browser of a privileged user. Exploitation requires a published campaign post containing a [[subscriber.*]] merge tag and social engineering of an admin to visit a crafted preview URL; the independent assessment rates this as medium severity (CVSS 5.4) with high attack complexity and required user interaction. No public exploit identified at time of analysis.
Arbitrary shortcode execution in the Kirki - Freeform Page Builder, Website Builder & Customizer plugin for WordPress (all versions up to and including 6.3.1) lets any authenticated user with Subscriber-level access or above inject shortcodes by writing them into their own `display_name` profile field, which the plugin splices unfiltered into composed page markup and then passes through `do_shortcode()`. The flaw is exploitable as a remote, network-reachable issue requiring only a low-privileged account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, 5.4), rated moderate by the independent assessment; the key precondition is that a published page must exist containing a Kirki element whose dynamic content is explicitly bound to the `display_name` user field - typically a team or member-directory / users-collection page - and on sites without such a page the vulnerable code path is never reached. Where that binding does exist, the injected shortcode executes in the request of every visitor, including unauthenticated ones, so per-victim interaction is not required; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated subscriber-level bypass in the VideoWhisper MicroPayments WordPress plugin (versions up to and including 3.2.9) lets a low-privilege account tamper with payment and entitlement state that should require higher privileges. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L, base score 5.4) describes a network-reachable flaw that still requires the attacker to hold a subscriber account, which is the primary limiting factor: the target site must either allow subscriber self-registration or the attacker must already possess such an account. Impact is bounded to partial integrity and availability loss with no confidentiality exposure, and no public exploit code was identified at time of analysis.
Authorization bypass in the Hello Plus plugin for WordPress (all versions up to and including 1.7.7) allows authenticated users holding Contributor-level privileges or higher to publish their own Hello+ header/footer templates and to draft active templates belonging to higher-privileged users. The plugin's template-parts actions do not verify that the caller is authorized to publish or modify those documents, so the flaw is an integrity and availability problem rather than a data-disclosure one. Exploitation requires a valid low-privileged WordPress account, making multi-author sites and sites that allow Contributor-level self-registration the primary exposure; no public exploit code has been identified at time of analysis and there is no indication of active exploitation.
Stored cross-site scripting in the CleanTalk Anti-Spam WordPress plugin (versions up to and including 6.88) allows unauthenticated attackers to inject malicious scripts into comment fields, which then execute for any visitor viewing the affected page. Exploitation requires the attacker to first get one comment approved from their email address; default WordPress auto-approval then allows subsequent comments to store the payload without moderation. No public exploit code or active exploitation is identified at time of analysis, and the issue is rated CVSS 5.4 Medium (CWE-79).
Moderate-severity cross-site scripting (XSS) in Progress Kendo UI for Vue's chart component (@progress/kendo-vue-charts) versions 2.5.0 through 16.1.x allows an authenticated attacker with low privileges to inject malicious HTML into chart tooltip values, which executes JavaScript when a victim hovers over a data point. The default chart tooltip renders formatted point values as raw HTML without encoding, leading to potential compromise of data confidentiality and integrity. No public exploit identified at time of analysis. Exploitation requires the attacker to influence a string value bound to the chart and the victim to interact with the tooltip (UI:R).
Progress KendoReact's default chart tooltip fails to HTML-encode formatted point values, enabling a low-privileged attacker who can influence chart-bound string data to inject JavaScript that executes when a victim hovers over the affected data point. This stored/influenced XSS affects @progress/kendo-react-charts versions 1.1.0 through 16.1.x and requires user interaction, with a moderate CVSS score of 5.4. No public exploit code or active exploitation is known at this time, and upgrading to 16.2.0 or later eliminates the flaw.
WordPress sites running the W3 Total Cache plugin before 2.10.6 let an authenticated user with the Author role or higher plant media-import content that, once an administrator executes the plugin's import action, copies an arbitrary server-readable file - such as wp-config.php or a backup/credential file - into a publicly served directory where it can be fetched without authentication. The defect is a path-traversal / missing file-type restriction issue (CWE-22) rated 5.4 (medium) under CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N, yielding read-only information disclosure with no integrity or availability impact. A vendor patch is available in 2.10.6, no public exploit code has been identified at time of analysis, and because the attack cannot be completed alone - a privileged administrator must trigger the import, and the target file must be readable by the web-server process - practical priority is moderate rather than urgent.
Fluent Forms for WordPress (all versions up to and including 6.2.5) fails to verify that a user is authorized before performing several form-management actions, allowing an authenticated attacker holding Custom-level access or above to read private form submissions, change submission statuses, permanently delete submissions, and modify global plugin settings. The flaw is a missing-authorization issue (CWE-862) reachable over the network with low complexity and no user interaction once a qualifying account exists, and the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, score 5.4) reflects limited confidentiality and integrity impact with no availability impact. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); the practical exposure is concentrated in multi-user sites that provision low-privilege or custom roles.
Authenticated privilege escalation in the Academy LMS WordPress plugin through version 4.0.3 lets a user with the academy_guardian role or higher assign the academy_student role to any existing WordPress account, including their own, via the guardian add_child REST API. The flaw stems from add_role('academy_student') executing before Store::link() validates the guardian-ward relationship and not rolling back on WP_Error, so even self-links rejected by Store::link() leave the role grant in place. This yields Contributor-equivalent edit_posts unconditionally and Author-equivalent upload_files only when the student file-upload setting is enabled; CVSS is 5.4 and no public exploit has been identified at time of analysis.
Unauthenticated attackers can download exported WooCommerce order CSV files containing customer PII from sites using the WebToffee Order Export & Order Import plugin versions up to 2.7.8, but only when the wp-content/webtoffee_export/ directory lacks its .htaccess and index.php guard files-a state that can arise after uninstall/reinstall, migration, backup restore, or staging sync. The vulnerability (CWE-552) is rated moderate (assessed CVSS 3.1: AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) because exploitation additionally requires knowledge or brute-forcing of second-precision timestamp filenames; no public exploit code has been identified at time of analysis. The vendor has released version 2.7.9, which the referenced code changes suggest addresses the issue.