Stored cross-site scripting in the WordPress plugin CP Multi View Events Calendar (CodePeople) in all versions up to and including 1.4.42 lets unauthenticated attackers inject arbitrary JavaScript through the CalendarTitle parameter, which is then rendered without escaping and executes in the browser of any user - including administrators - who later views the poisoned calendar page. Exploitation is conditional on a non-default configuration: a site administrator must have enabled the 'Allow edition in frontend?' option on at least one calendar view, which exposes the unauthenticated event-add endpoint together with a publicly accessible nonce that the attacker uses to submit the malicious title. No public exploit code was identified at the time of analysis and the issue is not listed in CISA KEV, but the 7.2 CVSS score with PR:N (unauthenticated) and scope change (S:C) makes the attack path low-complexity once that frontend-editing setting is active.
Stored cross-site scripting in the Salon Booking System WordPress plugin (Appointment Booking for Salons, Barbershops & Spas, all versions up to and including 10.31.9) lets unauthenticated attackers inject arbitrary JavaScript through the sln[<checkout-field-key>] checkout parameter, which is persisted and later executed when a user loads the affected page - in practice the admin customer view. Impact is conditional: the site must have at least one admin-configured custom checkout field of type Html or File, a documented but non-default plugin feature, so sites without such a field are not exploitable. No public exploit code has been identified at time of analysis, and the independent assessment rates the issue as a moderate, conditional risk rather than an emergency, downgrading the vendor's AC:L to AC:H because of the configuration dependency and the admin-context trigger.
Stored DOM-based cross-site scripting in the Opti-Behavior WordPress plugin (all versions up to and including 1.9.2.1) allows unauthenticated attackers to inject arbitrary JavaScript that executes when a victim later views recorded heatmap, session, or analytics data. The heatmap recording endpoint requires no authentication, and its only guard - a nonce - is freely obtainable by any anonymous visitor through the plugin's public opti_behavior_refresh_nonces AJAX action, so there is effectively no privilege barrier; the payload is stored rather than reflected, meaning it fires only when an administrator or other user loads the affected analytics page. The assessed CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N (7.2), there is no CISA KEV entry and no public exploit code identified at time of analysis, and it should be treated as a genuine but moderate-priority issue rather than an emergency.
Stored cross-site scripting in WPConsent (Cookie Banner & Cookie Consent for Privacy Compliance) through 1.1.9 allows unauthenticated attackers to inject arbitrary web scripts into comment content that execute when a user views an injected page. Exploitation is constrained: it requires the optional Script Blocking feature to be enabled, the ability to submit comments that are rendered, and two coordinated comments that place event-handler syntax in an allowed code element and the deterministic ___noise___ restoration key in an allowed abbr title attribute, with the key offset confirmable via an unauthenticated wpconsent_debug=1 request. No public exploit identified at time of analysis, and the assessed vector is AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N, so the non-default configuration and precise coordination limit realistic exploitation below the raw 7.2 score.
Stored cross-site scripting in the WordPress Profile Builder plugin (Cozmoslabs) affects all versions up to and including 4.0.3 and lets unauthenticated remote attackers plant arbitrary JavaScript through the First Name registration field, which executes in the browser of any user who later views the injected page - realistically an administrator processing pending registrations. The attack is explicitly gated on the plugin's Email Confirmation feature being enabled, so sites using default or other registration flows are not reachable through this path. Scoring is CVSS 7.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) with a scope change reflecting script execution in the victim's browser context, and no public exploit has been identified at time of analysis.
Stored cross-site scripting in the NotificationX WordPress plugin (all versions up to and including 3.3.3) lets remote unauthenticated attackers inject arbitrary JavaScript through the 'name' parameter, which then executes in the browser of any visitor loading an affected page. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2), no authentication or victim interaction is required to deliver the payload, but exploitation is conditional: a site administrator must first enable the WordPress.org Reviews campaign and place the notificationx-pro/notificationx dynamic block on a publicly reachable page, neither of which is a default configuration. No confirmed active exploitation (not in CISA KEV) and no public exploit code has been identified at time of analysis, and the independent assessment rates this as a real-but-conditional, lower-tier priority rather than an urgent threat; a fix is available in version 3.3.4.
Stored DOM-based cross-site scripting in SiteOrigin CSS 1.6.7 and earlier allows unauthenticated attackers to inject scripts through the WordPress comment 'Website' (comment_author_url) field, executing when a victim loads a page where the plugin renders the stored comment URL into a DOM sink. Exploitation requires the site to accept comments from unauthenticated visitors and to use an affected plugin version; the CVSS 3.1 score of 7.2 reflects network reachability, low complexity, no authentication, and a scope change, with limited confidentiality and integrity impact. No public exploit code was identified at time of analysis.
Stored DOM-based cross-site scripting in the SiteOrigin CSS WordPress plugin (all versions up to and including 1.6.7) lets an unauthenticated attacker smuggle script into a page via the 'href' parameter, which the plugin's Visual Inspector later writes into the DOM without sanitization. Exploitation is not self-firing: the attacker's comment must survive moderation and be approved, and an administrator must subsequently open the Visual Inspector and manually click the injected anchor link - a mandatory user-interaction step that the CVSS base vector understates (our assessment re-scores it AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N versus the published 7.2). There is no confirmed active exploitation or public exploit code identified at time of analysis, and the practical impact is bounded to script execution in an authenticated administrator's browser context.
Unauthenticated attackers can store arbitrary JavaScript in WordPress sites running the Simply Schedule Appointments plugin through version 1.6.12.35 by submitting an unsanitized 'status' parameter; the payload is written to the plugin's debug log unconditionally because debug logging is enabled by default. The script does not fire automatically for arbitrary visitors: execution is gated behind the plugin's debug-log viewer, which is reachable by anyone holding the site-wide Support PIN (an HMAC-MD5 of AUTH_SALT displayed in wp-admin), so the realistic victim is an administrator or support agent reviewing the log during routine troubleshooting, where the script executes in their session (assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N). There is no CISA KEV listing and no public exploit code identified at time of analysis, and the practical risk is lower on sites that rarely open the debug log or that rotate/restrict the Support PIN; signals are moderately concerning but do not indicate an urgent, widespread threat.
Stored cross-site scripting in the premium build of the User Registration PRO WordPress plugin (all versions up to and including 6.2.9) lets unauthenticated attackers inject arbitrary JavaScript through the HTTP Referer header into a vulnerable AJAX endpoint, with the payload persisting so it executes whenever a victim loads the injected page. The nonce that normally protects that endpoint is localized into the page source of every front-end page for anonymous visitors, so no account or credentials are required, although the attacker must target a site running the paid premium build - the free WordPress.org distribution is not affected - and the payload only fires once a user actually visits the compromised page. No public exploit code and no confirmed active exploitation were identified at time of analysis; the assessed severity of 7.2 reflects the scope change and the limited, though real, confidentiality and integrity impact of script execution in a victim's browser.
Stored cross-site scripting in the WP Ghost (Hide My WP Ghost) - Security & Firewall plugin for WordPress versions up to and including 7.0.12 lets unauthenticated attackers inject arbitrary web scripts through the plugin's replaceHeadersAndTags function, which performs insufficient input sanitization and output escaping; the injected payload persists and executes in a victim's browser when they click the crafted link, with impact limited to that victim's session (no availability impact). Exploitation requires the affected code path to be reachable on a site running 7.0.12 or earlier, but no authentication (CVSS PR:N) and no special non-default plugin configuration; although the published CVSS 3.1 vector scores UI:N, the practical trigger is a victim clicking the injected link, which is why our assessment adjusts user interaction to UI:R while keeping the same 7.2 base impact. The vendor has released a fix in version 7.0.13 (WordPress.org changeset from 7.0.12 to 7.0.13), no public exploit code has been identified and there is no CISA KEV entry indicating active exploitation at time of analysis. Reported by Wordfence, a credible source for WordPress plugin vulnerability intelligence.
Cross-tenant authorization bypass in Magistrala through 1.0.0 allows any authenticated member of a workspace to view, issue, and revoke device certificates belonging to other tenants by supplying foreign serial numbers or entity/device IDs to the certs service (RevokeBySerial, RevokeAll, ViewCert, ListCerts, IssueCert). A successful attacker can disconnect other tenants' devices, disclose their certificates, and mint CA-signed certificates for arbitrary device IDs, giving high integrity and availability impact with limited confidentiality exposure (assessed CVSS:3.1 base 7.2, AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H). Exploitation is not pre-authentication, and no public exploit was identified at time of analysis; the practical risk is greatest on multi-tenant deployments that actively use the certificate service.
Mailu, an open-source mail server distributed as a set of Docker images, contains an authorization flaw that lets an authenticated domain manager reset the password of, or mint an API token for, a higher-privileged account that merely owns a mailbox in a domain they manage - including a global admin or a manager of another domain. Because the vulnerable endpoints are the user edit, password reset, and token creation flows, a successful attack grants full control of the victim account and all of its privileges, escalating a limited domain-manager role into global administrative control; the CVSS 3.1 vector is 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation requires valid domain-manager credentials and the specific condition that a higher-privileged user owns a mailbox inside the attacker's managed domain, so single-tenant installs with no delegated domain managers are effectively not exposed; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Stored cross-site scripting in the WP Sessions Time Monitoring Full Automatic WordPress plugin affects all versions up to and including 1.1.5 and allows unauthenticated attackers to inject arbitrary JavaScript that persists in the site's stored data. Because the CVSS vector is PR:N, exploitation requires no prior authentication, but the injected payload only fires when a victim - typically an administrator reviewing the plugin's active-session and activity views - subsequently loads the affected page, so impact is deferred and depends on a privileged user visiting the poisoned view. The issue is assessed as moderate priority rather than a top-tier emergency, and no public exploit code or confirmed active exploitation was identified at time of analysis; the primary mitigations are updating or disabling the plugin and restricting exposure of its admin views.
Path traversal in WildFly's management take-snapshot operation lets an authenticated user holding only the Monitor RBAC role write a copy of the server configuration to an arbitrary filesystem location and then read it back, bypassing RBAC restrictions to disclose sensitive credentials. This is a credible, moderate-priority privilege-boundary bypass rather than a critical internet-facing threat, because exploitation requires an authenticated management session and a reachable management endpoint; no public exploit code has been identified at time of analysis and no vendor-released patch version is specified in the provided data.
Authenticated SQL injection in ZR.Admin.NET through 3.8.2 allows any account holding the system:user:list permission to inject subquery or CASE expressions into the ORDER BY clause of the shared ToPage paging helper by supplying a crafted PagerInfo.Sort query parameter to GET /system/user/list, enabling blind extraction of database contents such as stored credentials. The flaw is read-only (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N; vendor-published CVSS 4.0 base of 7.1) and requires a valid low-privileged session with that specific list permission, so it is not remotely exploitable without authentication. No public exploit code and no confirmed active exploitation were identified at time of analysis, though a public technical writeup describing the ORDER BY injection path exists; a vendor patch is available.
Authenticated SQL injection (CWE-89) in FilePress through version 3.0.1 lets any low-privilege logged-in user inject arbitrary SQL into the ORDER BY clause through the unvalidated 'asc' parameter, enabling blind boolean- or time-based extraction of database contents including administrator credential hashes. The affected endpoints are dzz/pichome/library/filelist.php and dzz/collection/filelist.php; exploitation requires a valid authenticated session (PR:L) rather than anonymous access, and the injected queries are read/inference-based so the assessed impact is confidentiality-only. No active exploitation is confirmed (not in CISA KEV) and no public exploit identified at time of analysis, though the CVE record references a public technical writeup describing the injection point; rated CVSS 7.1 (4.0) / 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, making this a moderate, contained priority.
Integer overflow in pupnp's HTTP Content-Length parser (raw_to_int in upnp/src/genlib/net/http/httpparser.c) allows a remote adjacent-network attacker to desynchronize the parser from the declared body length on LP64 builds, enabling either request smuggling in persistent or proxied contexts or a denial of service by forcing a worker to wait for an oversized body. Affected are all pupnp releases prior to 2.0.2 across the whole CPE range cpe:2.3:a:pupnp:pupnp:*:*:*:*:*:*:*:*; no authentication (PR:N) and no user interaction (UI:N) are required, though exploitation is limited to adjacent/link-local reachability (AV:A) and to 64-bit builds where long is 64 bits and int is 32 bits. No public exploit identified at time of analysis; vendor-released patch: 2.0.2.
Authenticated users of Rocboss paopao-ce through 0.6.0-alpha.3 can obtain signed download URLs for other users' private, friend-only, and following-only media by requesting arbitrary content IDs from the /v1/attachment endpoint. Because post_content IDs are sequential, an ordinary registered low-privileged account (no administrative role required) is enough to enumerate IDs and harvest images, videos, and attachments belonging to other users, giving a high confidentiality impact with no write or availability effect. This is a genuine but bounded data-confidentiality issue rather than a critical infrastructure threat; no public exploit code was identified at time of analysis, although a public technical write-up describing the cross-user IDOR is referenced.
Mall4cloud through 4.0 allows an authenticated merchant to read other shops' buyer shipping addresses by enumerating sequential orderAddrId values through GET /m/order/order_addr/{orderAddrId}, exposing consignee names, mobile numbers, addresses, and post codes. The flaw is an insecure direct object reference (CWE-639) in the multishop OrderController getOrderAddr handler, which serves records without an ownership or tenant check. Exploitation requires a valid merchant account and use of the multishop order module, so the realistic threat population is registered sellers rather than anonymous internet users; no public exploit identified at time of analysis, no CISA KEV active exploitation is noted, and the signals are moderately consistent but point to a targeted, not mass-exploitation, profile.
Insecure direct object reference in DataCap (the MetaForge data platform) through 2025.1.1 allows any authenticated, low-privileged user to read other users' datasources, snippets and dashboards by iterating numeric auto-increment ids on the source, snippet and dashboard getById endpoints, with serialized datasource responses exposing host, port, username and cleartext passwords. Exploitation needs only a valid ordinary account and network reachability to those endpoints - no administrator role and no non-default configuration - so the realistic threat model is a malicious or compromised low-privilege tenant on a multi-user deployment, with high confidentiality impact but no integrity or availability impact. The provided score is 7.1 (independent CVSS 3.1 assessment: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N); no public exploit identified at time of analysis and the CVE is not listed in CISA KEV, making this a credible mid-tier priority rather than a drop-everything emergency.
Nezha monitoring dashboards running versions 1.0.0 through 2.3.14 can be knocked offline by an authenticated user who holds file-manager scope, because the dashboard's file manager WebSocket handler (fmStream) never imposes a read limit on incoming frames. A single oversized binary message sent to /api/v1/ws/file/:id is buffered whole by gorilla/websocket, exhausting process memory until the kernel OOM-killer terminates the dashboard - which in turn severs monitoring visibility for every agent the dashboard managed. There is no public exploit identified at time of analysis, but a vendor patch (2.3.15) and the upstream fixing commit are already public, so any dashboard exposed to users with file-manager permissions should be treated as a moderate-priority availability risk rather than a critical one; the attacked service is the dashboard itself, not the monitored endpoints.
Resource exhaustion in Nezha 2.0.13 through 2.3.14 allows an authenticated user to open unbounded concurrent connections to the /api/v1/ws/transfer WebSocket endpoint and hold thousands of ServerTransferClass.Subscribe subscriptions without limit, exhausting file descriptors, memory, and goroutines and blocking agent gRPC reconnections. Exploitation requires a valid authenticated dashboard session (CVSS vector includes PR:L), with no user interaction and no non-default configuration beyond a login-capable account; the impact is limited to availability of the dashboard and agent connectivity, and no public exploit has been identified at time of analysis. A vendor patch is available in Nezha 2.3.15 and later.
Authenticated workspace members can exploit an insecure direct object reference in Shaiwz data-platform-open (through commit efeacd3) to read, modify, or delete datasources belonging to other workspaces by supplying sequential numeric IDs. The flaw exposes JDBC credentials and database schemas via endpoints /datasource/detail, /listSchemaTable, /tableDetail, /update, and /delete, with no per-workspace authorization check. No public exploit code identified; exploitation requires a valid workspace-member account (PR:L) and no user interaction, and the impact is assessed as a moderately serious authorization flaw rather than an emergency-tier vulnerability.
Cleartext third-party credentials are exposed to any authenticated principal holding DDNS read access in Nezha versions 2.2.5 through 2.3.14, because the GET /api/v1/ddns list handler returns DDNS webhook profiles without redacting the WebhookURL and WebhookRequestBody fields. An admin account or a Personal Access Token granted the nezha:ddns:read scope can retrieve tokens embedded directly in other users' webhook URLs (for example query strings such as ?token=...) or request bodies, which the vendor's fix specifically addresses for every user's profiles rather than only the requester's. Per the vendor-assigned CVSS 4.0 vector (7.1, PR:L, VC:H with no integrity or availability impact), the exposure is confidentiality-only and gated behind the authentication and scope prerequisite; no public exploit identified at time of analysis, and neither CISA KEV status nor public exploit code is reported for this issue.
Memory exhaustion in FreeRDP 2.0.0 through 3.31.x lets an authenticated RDP client degrade or crash a server that exposes FreeRDP's listener role: the attacker opens a static virtual channel message and then streams endless channel-data fragments while withholding the CHANNEL_FLAG_LAST terminator, so the server-side reassembly buffer grows without bound. The issue is scored 7.1 under CVSS 4.0 and independently assessed as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, meaning availability-only impact with no confidentiality or integrity loss. Exploitation is not confirmed in the wild (no CISA KEV listing) and no public exploit identified at time of analysis; the practical exposure is narrowed because the vulnerable code path is server-side and the attacker must already hold an authenticated RDP session.
Cross-origin data exposure in LoopX's local status server lets an attacker-controlled web page read control-plane state from an operator's machine. From version 0.0.1 up to but not including 0.4.5, `loopx serve-status` (`loopx/status_server.py`) emits `Access-Control-Allow-Origin: *` on unauthenticated responses bound to predictable loopback ports, so any website the operator visits while the server is running can script cross-origin requests to `GET /status.json`, `GET /review-material?goal_id=...&path=...`, `GET /`, and `POST /control-plane/configure-goal/dry-run`, harvesting goal and run metadata, absolute local paths, private Markdown files under registered goal roots, and dry-run configuration projections. The request vector is unauthenticated (CVSS PR:N) but exploitation requires the user-interaction step of visiting malicious web content (UI:P), and the affected routes are strictly read-only. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; it is a genuine but bounded-impact information disclosure best treated as medium priority, with the upstream fix released in 0.4.5.
Authenticated SQL injection in WebVella ERP through 1.8.8 allows any valid user account to read unauthorized entities, including user and role tables, by sending crafted single-quoted literals in WHERE clauses to the EQL query API at POST /api/v3/en_US/eql. The flaw is CWE-89 in EqlBuilder's unsanitized SQL string interpolation, and the CVSS vector confirms PR:L, so unauthenticated attackers cannot exploit it directly. No public exploit code was identified at time of analysis, and although CVSS 4.0 scores this 7.1, the independent assessment correctly frames it as a genuine but moderate-priority issue rather than an overstated high-CVSS finding.
An authenticated member of a shared Space in Tandoor Recipes prior to 2.6.10 can reach another member's private recipes - including reading private recipe files, sending those file bytes to the configured AI provider, and generating external or public share links - by supplying the victim's recipe identifier to the api/ai-import/, api/get_recipe_file/, api/get_external_file_link/, or api/share-link/ endpoints, because those flows retrieve Recipe objects without invoking the private-recipe owner/sharing check (CustomRecipePermission). The prerequisite is an account already inside the same shared Space (Space sharing must be enabled) plus knowledge or enumeration of the target recipe ID, so single-user or non-shared deployments are not exposed; scoring is CVSS 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N) with confidentiality as the dominant impact and no public exploit identified at time of analysis. The issue is fixed in 2.6.10.
Server-side request forgery in Wegow's ticket sales chart PDF export allows an authenticated promoter to inject malicious SVG content into the export request, causing the third-party Highcharts cloud service to fetch attacker-controlled external resources and embed the responses in the generated PDF. This provides a request proxying/laundering capability constrained to what the external SaaS can reach, and no public exploit has been identified at time of analysis. The CVSS 4.0 base score is 7.1 (High), driven almost entirely by high integrity impact (VI:H) while confidentiality and availability impacts are none, an unusual weighting for an SSRF which more typically carries a confidentiality impact.
Authenticated SAML users can join any team - including invite-only teams - on affected Mattermost servers because the application fails to verify the integrity of the SAML RelayState POST parameter, allowing the team_id or invite_id fields inside it to be forged. Exploitation requires the target instance to have SAML single sign-on configured and enabled, and the attacker must already hold valid SAML credentials for that instance (CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, 7.1); no victim interaction is needed. Impact is bounded to unauthorized team membership rather than administrative takeover. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so this is a moderate-priority, authentication-gated authorization flaw rather than a mass-exploitation emergency; no EPSS score was provided in the available intelligence.
Reflected cross-site scripting (XSS) in the Houzez WordPress theme (versions up to and including 4.4.0) allows remote attackers to execute arbitrary script in a victim's browser by tricking them into clicking a crafted URL while the theme is active. The flaw requires user interaction (UI:R) and is unauthenticated from the attacker's side (PR:N), but since it is reflected and not stored, each victim must be individually targeted via phishing or a malicious link. No public exploit code or confirmed active exploitation was identified in the available intelligence at the time of analysis; the assessed CVSS 3.1 base score is 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).
Algorithmic resource exhaustion in destructive_command_guard (dcg) versions prior to 0.6.6 lets a crafted shell command - a destructive command followed by nested or unclosed $( or $(( substitution sequences - trigger exponential-time rescans in the split_command_segments scanners (src/packs/mod.rs), hanging the process. Because dcg runs as a PreToolUse guard hook for AI coding agents and that hook fails open on timeout, the hang does not block the command but instead allows the destructive command to be executed - turning a denial-of-service bug (CWE-400) into a safety-control bypass with high integrity impact. The issue is rated 7.1 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H), indicating a local attack path with no privileges required but requiring user interaction (the command must actually be submitted), and the fix is the vendor-released version 0.6.6; no public exploit code was identified at time of analysis and the CVE is not in CISA KEV.
SQL injection in AipexBase through commit 690adb9 allows an authenticated low-privilege attacker to read other users' database rows and tables by injecting SQL through the order_by and group_by fields of the /api/data/invoke endpoint. The attacker can supply subqueries or MySQL error-based functions (EXTRACTVALUE/UPDATEXML) to bypass the SqlGuard denylist and row-level security, but impact is limited to confidentiality with no write or modification path described. No public exploit identified at time of analysis; CVSS 7.1 with PR:L indicates a moderate-severity issue requiring valid authentication and a MySQL-style backend.
HUIZHI ChargeOS cloud through version 3.0.9 fails to bind the caller-supplied userId parameter in the hcp-mp PayController.xcxRecharge endpoint to the identity of the authenticated member making the request, so any low-privilege member or mini-program account (PR:L per the CVSS vector) can arbitrarily credit or reduce any other member's wallet balance without any payment and consume charging services for free. The issue is a CWE-639 authorization bypass through a user-controlled key, scored 7.1 by the reporter and independently assessed as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, meaning network reachable, no user interaction, and pure integrity impact on wallet balances with no confidentiality or availability effect. No public exploit identified at time of analysis, although a public technical writeup of the IDOR and the affected Java source are both linked in the references, and no vendor-released patch has been identified, so any internet-exposed instance at or below 3.0.9 whose member API is reachable and where a member account can be obtained should be treated as at risk.
HUIZHI ChargeOS cloud deployments through version 3.0.9 expose other members' wallet balances, credit, profile and charging-order records to any authenticated member account, because the hcp-mp MeController and OrderController trust client-supplied userId, openId and orderNumber parameters instead of deriving identity from the session. The CVSS 4.0 base score is 7.1 (assessed as CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), reflecting a genuine but bounded confidentiality-only risk: a low-privileged authenticated user (any registered member, no admin role) can enumerate sequential member IDs against endpoints such as /me/getMemberBalanceByUserId and /order/orderDetail to read arbitrary members' data, with no modification or denial-of-service capability. There is no CISA KEV confirmation of active exploitation and no public exploit code identified at time of analysis, although a public technical writeup of the flaw and the vulnerable source files are referenced; exploitability is gated on first obtaining one valid member credential.
Stored datasource passwords in data-platform-open (through commit efeacd3) can be recovered in plaintext by any authenticated, low-privileged workspace user, because the service encrypts those passwords with a hardcoded AES key that is published in the project's own source repository. An attacker who reaches the datasource detail API - for example by abusing a cross-workspace IDOR to read datasources belonging to other tenants - can pull the ciphertext and decrypt it offline without any key-cracking effort, exposing the underlying database credentials. The issue is authentication-gated rather than remote-unauthenticated, is limited to confidentiality impact, and no public exploit code has been identified at time of analysis.
EFAK 5.0.0 through 5.1.0 exposes stored LLM provider API keys to any authenticated user holding the lowest-privilege ROLE_USER account, because the /api/model-config/page and /api/model-config/{id} REST endpoints are not covered by the admin authorization gate implemented in WebSecurityConfig. A successful query returns the provider keys unmasked, letting a low-privilege account reuse those credentials against external LLM providers, run up charges on the victim's account, or pivot into provider-side resources. Exploitation requires a valid non-anonymous account (PR:L per the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N vector) and a deployment that actually stores LLM provider keys, so multi-user or multi-tenant installations with self-provisioned accounts carry the highest risk while single-admin deployments without configured keys are effectively unexposed; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation.
Cube-studio instances through version 2026.09.01 let any authenticated, low-privileged user act on other tenants' notebooks and inference services by supplying another user's object id to lifecycle endpoints (stop, reset, clear, redeploy) in view_notebook.py, view_inferenceserving.py and view_serving.py, allowing pod deletion and taking production inference endpoints offline. The CVSS 4.0 score of 7.1 (PR:L, VI:L, VA:H, VC:N) and CWE-639 classification describe a bounded cross-tenant authorization flaw in the data-infra/cube-studio product rather than a confidentiality breach. No public exploit code or active exploitation has been confirmed (no public exploit identified at time of analysis), though a public technical writeup describing the IDOR exists.
Authenticated users in multi-tenant Risesoft Digital-Infrastructure deployments through 9.6.11 can export another tenant's personnel directory through the log module DownloadController endpoints exportLoginXLS and exportNotLoginXLS. The flaw is a missing-authorization/IDOR issue: a low-privilege account changes the tenantId parameter to a target tenant's value and receives XLSX files containing names, login names, organization paths, mobile numbers, and email addresses. This is a confidentiality-only cross-tenant data exposure rated CVSS 4.0 7.1 (HIGH); no public exploit was identified at time of analysis, and single-tenant deployments are not affected.
Authenticated merchant-portal users on Jeepay through 3.2.9 can overwrite another merchant's payment channel configuration - signing keys, certificates and fee rates - through an insecure direct object reference in the POST pay-config endpoint handled by MchPayInterfaceConfigController.saveOrUpdate, allowing the attacker to break or redirect the victim merchant's payment processing. Exploitation requires only a valid merchant account holding the default ENT_MCH_PAY_CONFIG_ADD permission (granted by default, no non-default configuration) plus knowledge or enumeration of the victim merchant application's infoId, with no user interaction. The issue is a bounded multi-tenant isolation / malicious-insider risk that is most impactful on shared Jeepay deployments serving multiple independent merchants and largely irrelevant on single-tenant installations; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV.
Missing authorization checks in the Advanced Post Manager WordPress plugin through version 4.5.6 let an authenticated user invoke functionality that should be reserved for higher-privileged roles, weakening the site's access-control boundary. Exploitation requires a valid low-privileged session (CVSS PR:L), so realistic exposure exists mainly on sites with open registration or attacker-controlled accounts, and no public exploit code has been identified at time of analysis. The demonstrated impact is limited to integrity and availability (C:N/I:L/A:L per our assessment), which is why this reads as a moderate-priority issue rather than a top-tier emergency.
Delta ISPSoft contains an out-of-bounds read (CWE-125) that can crash the application and potentially leak limited memory contents when a user opens a specially crafted project file. Exploitation is client-side and requires user interaction (opening the file on an engineering workstation), not remote access to a listening service, so the practical risk is moderate. No public exploit code has been identified at time of analysis.
Out-of-bounds read in Delta ISPSoft can disclose limited sensitive memory contents and cause a high availability impact when a user opens a specially crafted project or data file. The vulnerability affects installations of the Delta ISPSoft engineering software (CPE cpe:2.3:a:deltaww:ispsoft:*:*:*:*:*:*:*:* indicates no version limitation in the supplied data) and is a client-side file-parsing issue requiring user interaction, not an unattended network service flaw. No public exploit identified at time of analysis; the independent assessment rates it as a moderate-priority, client-side exposure rather than a mass-exploitable server vulnerability.
Heap buffer overflow in FreeRDP before 3.32.0 can let a local attacker corrupt heap memory and potentially execute code when the victim loads a crafted persistent bitmap cache v2 file, because persistent_cache_read_entry_v2 miscalculates bitmap sizes via integer wraparound and then performs fixed 16 KiB reads against mismatched entry-size accounting. Exploitation requires the local attacker to place a malicious cache file in the client's load path and relies on low-level local privileges plus user interaction (PR:L/UI:P), so there is no remote unauthenticated path; no public exploit identified at time of analysis. No CISA KEV entry was provided, making this a moderate-priority local risk rather than a mass-exploitation threat.
Heap buffer overflow in FreeRDP before 3.32.0 allows a local attacker with low privileges to corrupt memory and potentially execute code by supplying a crafted v3 persistent bitmap cache file. The vulnerability is triggered when the FreeRDP client processes a malicious cache file with crafted width and height values, causing an integer overflow in size calculation and a subsequent heap overflow via fread. Exploitation requires the victim to load the poisoned cache during a session (passive user interaction); no public exploit code has been identified at time of analysis.
Local privilege escalation in Dell Alienware Command Center (AWCC) versions prior to 6.14.54.0 allows a low-privileged local user to gain elevated privileges and, in some exploitation paths, to disrupt the service and cause denial of service. The victim must already have an authenticated local session on the affected machine (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base score 7.0); attack complexity is high, indicating a non-deterministic race or specific runtime state is required rather than a reliable one-shot trigger, and no user interaction is needed. No public exploit code has been identified at time of analysis, no CISA KEV listing is present, and no EPSS score was provided, so this should be treated as a moderate-priority local hardening issue rather than an urgent remote-exploitation emergency.
Unauthenticated remote attackers can enumerate sensitive user directory information-including phone numbers, roles, and department structure-from qKnow through version 2.4.3 by directly calling /flyflow workflow integration endpoints that are mistakenly permitted without authentication in the shipped SecurityConfig. The affected endpoints are /flyflow/userById (which accepts sequential userId values), roleAll, and deptListByParentDeptId; exploitation requires only network reachability of the qKnow instance, with no credentials or user interaction. The flaw is rated CVSS 6.9 (CVSS 4.0) and CWE-306, but the impact is limited to read-only information disclosure; no write, modification, or code execution is possible. No public exploit code or confirmed active exploitation has been identified at time of analysis.
Unauthenticated attackers can cancel any member's pending unpaid orders in waynboot-mall through 2.0.0 by calling the /callback/order/unpaid endpoint directly, because that callback handler performs no authentication and accepts the order identifier from attacker-controlled input. Order identifiers (orderSn) are generated from epoch seconds plus a sequential counter, so they are predictable enough to enumerate or guess, allowing an attacker to repeatedly cancel live orders and distort product stock levels. No vendor patch has been identified and no public exploit code was confirmed at time of analysis, although a public technical writeup describing the flaw exists; the impact is bounded to order-state and inventory manipulation rather than data disclosure or account takeover.
Unauthenticated access to the administrative /api/ui surface of Misaka Danmu Server through 2.8.9 allows any attacker who can reach the HTTP service to read audit logs containing login IP addresses, server logs and environment paths, and to delete episode rows, clear media-server mappings, and wipe audit history. The audit, diagnostics, data-check, scan-index and health route modules ship without the get_current_user dependency, so a default deployment applies no authentication to them whatsoever (CWE-306). The reported CVSS 4.0 score is 6.9, and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) concurs that this is a genuine but moderate-priority issue rather than an inflated critical one; the realistic limiting factor is exposure, since Misaka Danmu Server is self-hosted and normally confined to a LAN or fronted by a reverse proxy. There is no CISA KEV entry and no public exploit code identified at time of analysis, so exploitation is opportunistic and requires direct network reachability of the affected endpoints.