a2ui 0.10.0 through 0.10.6 leaks stack traces and internal file-system paths through expression-error messages: the web_core renderer's DataContext.dispatchExpressionError copied the raw V8 'e.stack' into the 'details' field of the dispatched error instead of returning only a sanitized message. An attacker who can make expression evaluation throw (for example a dynamic value calling formatNumber with an out-of-range 'decimals' argument that raises a RangeError) can read the returned stack detail remotely; the CVSS 4.0 score is 2.1 (assessed CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), so confidentiality of internal error detail is the only impact, with low-privileged authenticated access required. A public PoC reference exists in issue #2385 but is not verified as working exploit code, no CISA KEV entry indicates active exploitation, and the vendor patch is available in commit 8f149a1c7b0ce1fa8e93ac3adfa5fda960faeb01.
Server-side request forgery in the Request Forwarder of MusicFreeDesktop 0.0.6, 0.0.7 and 0.0.8 allows a crafted proxy request to be relayed to an attacker-chosen destination, giving low confidentiality, integrity and availability impact (CVSS 4.0 base 5.3; independently assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:R with low C/I/A). The CVSS vector indicates the attack path is unauthenticated (PR:N) but requires user interaction (UI:P/UI:R), for example a user loading or playing attacker-influenced content that causes the app to emit a proxy request; the exact trigger is not described in the available sources. A public PoC reference exists in the form of GitHub issue #443, but it is not verified as working exploit code, there is no CISA KEV listing, and the vendor fix is upstream commit b0d3876247a0a64fa0e430e4b21870e41f503182.
Unbounded resource consumption in the a2ui web_core renderer (versions 0.10.0 through 0.10.6) lets an attacker who can influence a data-bound dynamic ChildList force the client to materialize an arbitrarily large number of child nodes. The flaw sits in the GenericBinder path of renderers/web_core/src/v0_9/rendering/generic-binder.ts, which pre-patch applied no size cap when expanding a {componentId, path} children binding into one node per array element; a 12,000-element array produced 12,000 nodes in the reference test. Exploitation requires write access to the bound data model (authenticated, PR:L per the assessed vector), causes only low availability degradation of the browser-side renderer with no confidentiality or integrity impact, and a public PoC reference exists on the upstream issue tracker although it is not verified as working exploit code. Priority signals are uniformly low (vuln.today decision: monitor), so this is a hardening item rather than an urgent patch.
Unbounded array-index handling in a2ui's web_core v0.9 state module (DataModel.set, renderers/web_core/src/v0_9/state/data-model.ts) in versions up to and including 0.10.6 allows a low-privileged caller who can submit a data-model path to force array auto-vivification or an array clone at an enormous index - for example '/items/999999999' or '/newArray/10000000/field' - exhausting renderer memory or hanging the thread. The assessed impact is availability-only against the client-side renderer (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/C:N/I:N/A:L; vendor scoring 2.1), with no confidentiality or integrity effect and no server-side compromise. A public PoC reference exists (issue #2386); it is not verified as working exploit code, no KEV-listed active exploitation is reported, and priority is monitor. An upstream fix is available as PR #2430 / commit 82789191ce551f4d7a095d273773fb24bd764c9d, which caps array indices at 10000.
Resource exhaustion in a2ui Web Core versions 0.10.0 through 0.10.6 lets low-privileged remote callers degrade availability by passing excessive or unknown function-call arguments to the data-context Resolver. The resolver in renderers/web_core/src/v0_9/rendering/data-context.ts did not validate argument names or enforce a maximum argument count before PR #2417, which adds MAX_FUNCTION_CALL_ARGS and rejects unknown keys. A public PoC reference exists; it is not verified as working exploit code. No active exploitation is confirmed in the supplied intelligence, and the assigned priority is monitor.
Resource exhaustion in the a2ui web renderer's expression parser affects versions 0.10.0 through 0.10.6: a crafted template string handed to the formatString basic function is parsed without any bound on length or part count, so an attacker who can supply that input can force excessive parsing work in a victim's renderer. The CVSS 4.0 vector requires low privileges (PR:L) and passive user interaction (UI:P) - a victim must load or render the malicious expression - and the resulting impact is limited to availability (VA:L) with no confidentiality or integrity effect. A public PoC reference exists (GitHub issue #2389); it is not verified as working exploit code, there is no CISA KEV listing, and the priority decision is 'this_month' rather than an emergency.
Authenticated users with only contributor-level access on WordPress sites running the Royal MCP plugin before 1.5.10 can duplicate arbitrary pages by identifier, reading the full content of private and draft pages and republishing them without holding the publish capability. The flaw is a broken object-level authorization issue (CWE-639): the duplication routine relies on a generic capability instead of verifying the caller's rights on the specific page object, so a low-privilege session is enough to cross a trust boundary. Real-world signals are subdued - EPSS is 0.15% (4th percentile), there is no CISA KEV listing, and no public exploit has been identified at time of analysis - and impact is confined to disclosure and unauthorized publication of page content, with no availability or code-execution effect.
Broken access control in the Welcart e-Commerce WordPress plugin before 2.12.6 lets any authenticated user holding the Author role or higher read, modify, create, delete and re-order SKU data - prices, confidential cost prices and stock levels - for products belonging to other users, because the plugin's capability check is not tied to the specific product being edited. Successful abuse requires only a low-privileged network-reachable account and no user interaction, so the confidentiality and integrity impact on store pricing and inventory data is real, but it is bounded: no administrative access is gained and no code execution or outage results. No public exploit has been identified at time of analysis, there is no CISA KEV listing, and EPSS is 0.15% (4th percentile), which aligns with the monitor-level priority assigned to this issue.
Contact-form submissions in Royal Addons for Elementor before 1.7.1070 can be silently redirected to an attacker-controlled email address by any authenticated user holding the WordPress Author role or higher. The plugin stores form email-delivery settings in a site-global namespace keyed only by an author-chosen identifier exposed in public page source, so an Author+ user can read the key from a victim page, overwrite the configuration, and receive that form's submissions. A vendor fix is available in 1.7.1070; EPSS is 0.15% and no public exploit was identified at time of analysis.
Query-parameter injection in i18next-http-backend before 4.0.4 lets attacker-controlled language or namespace values add or override parameters on outgoing translation requests whenever a loadPath or addPath template places {{lng}} or {{ns}} in the query string, such as the multiload shape /locales/resources.json?lng={{lng}}&ns={{ns}}. Server-side deployments using i18next-http-middleware's LanguageDetector are the most exposed case: an unauthenticated visitor supplying ?lng=de%26ns%3Dprivate%26admin%3Dtrue can make the application issue a request to its own translations API as ...?lng=de&ns=private&admin=true&ns=common, leveraging the server's network position and credentials; on the browser side the same crafted link affects the victim's same-origin request. Severity is bounded (CVSS 3.1 3.7, AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) because exploitation requires both a query-shaped template and attacker control of the language or namespace value, and real impact depends on how the translations API branches on the injected parameters; the default /locales/{{lng}}/{{ns}}.json template and supportedLngs-restricted applications are unaffected, the advisory publishes a proof-of-concept script, and no confirmed active exploitation is reported in the available sources (priority label: monitor).
Improper initialization in Juniper Networks Session Smart Router can allow unauthenticated network attackers to cause a limited denial of service, and the description also claims traffic decryption even though the scored confidentiality impact is low. The issue is reached through the router's security policy assignment, and the CVSS AC:H rating indicates conditions beyond the attacker's control; the exact trigger is not described in the available sources. No public exploit was identified at time of analysis, and the vuln.today priority is monitor (CVSS 3.7), making this a low-severity issue rather than an urgent one.
HCL BigFix AEX V13.0 contains a flaw in its bundled aws-sdk package that can cause AWS API requests to be directed to unintended or non-AWS endpoints, with limited confidentiality impact. The issue is rated CVSS 3.7 with high attack complexity and no authentication or user interaction required; the specific exploitation preconditions are not described in the available sources. No public exploit code or active exploitation is identified at time of analysis.
Acronis Cyber Protect 17 on Linux builds before 42587 ship executables that lack complete binary hardening protections (CWE-693), which can make a separate local memory-corruption or exploitation primitive easier to carry out but is not directly exploitable on its own. Abuse requires local access and existing low privileges with high attack complexity, and the resulting impact is limited to low confidentiality and integrity effects with no availability impact. No public exploit identified at time of analysis, and the vendor-released patch is build 42587.
PostgreSQL Anonymizer before 3.3.0 leaves table optimizer statistics fully readable to any role holding SELECT, so a masked role can recover a limited statistical sample of the very values the mask is supposed to hide. Exploitation requires an authenticated principal that has been assigned a masked database role with SELECT on the target table, and yields only histogram bounds and most-common-value entries rather than full rows, which keeps this at low severity (CVSS 3.5, assessed 3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N). No public exploit has been identified at time of analysis and the issue is not in CISA KEV; the fix ships in PostgreSQL Anonymizer 3.3.0.
Masked-role read-only enforcement in PostgreSQL Anonymizer can be bypassed with data-modifying common table expressions (CTEs), allowing an authenticated database user holding a masked role to make unauthorized data changes that the extension is intended to prevent. Affected releases are PostgreSQL Anonymizer versions before 3.3.0; impact is integrity-only, with no confidentiality or availability loss, and deployments that do not use masked roles for read-only enforcement are outside the assessed conditions. The independent assessment rates this as a low-severity, low-priority access-control bypass, no public exploit has been identified at time of analysis, and the complete fix is upgrading to 3.3.0 or later.
An out-of-bounds read in the Bluetooth RFCOMM control-channel handler prh_rfcomm_cc_process_test (inside libanwbtstack.so) on Alpine iLX-F511 in-dash units running firmware 7.0.000 lets a network-adjacent attacker leak limited process memory. The attacker must first pair a malicious Bluetooth device with the head unit - a user-interaction prerequisite (UI:R) - after which a crafted message reaches the vulnerable handler without further authentication (PR:N). Impact of the primitive alone is confined to low-confidentiality disclosure (C:L) for an assessed CVSS of 3.5; the ZDI advisory and CVE description note that chaining with other flaws would be needed to reach arbitrary code execution as root. No public exploit code has been identified at time of analysis, the issue is not in CISA KEV, and the vuln.today decision label is 'monitor'.
Denial of service and limited integrity impact in Dell PowerProtect Data Domain can result from a high-privileged local attacker exploiting a path traversal flaw, with no confidentiality impact (CVSS 3.4). The flaw affects Feature Release 7.7.1.0 through 8.8 and the LTS2024, LTS2025 and LTS2026 ranges listed in the Dell advisory, and requires local access plus high privileges rather than remote or anonymous access. No public exploit was identified at time of analysis, and the issue is low severity with a monitor priority.
Cached OAuth2 introspection responses in WSO2 API Manager, WSO2 Identity Server and related WSO2 identity/gateway products can cause a revoked access token to be returned to the client again until the cache entry is cleared, but only when the allowed_scopes configuration is enabled. An authenticated OAuth2 client able to call both the introspection and revocation endpoints must also hit a narrow ordering window - introspecting a token immediately before revoking it - which is why the issue is rated low (CVSS 3.1, AV:N/AC:H/PR:L, C:N/I:N/A:L). The re-issued token is not accepted for API authorization, so there is no confidentiality or integrity loss; the practical effect is a limited availability/authentication-flow disruption, since affected users may be unable to obtain a new valid token until the cache is flushed. No public exploit code and no active exploitation have been identified at time of analysis, and the priority decision is monitor.
Acronis Cyber Protect 17 builds before 42587 contain an improper authorization flaw (CWE-639) that lets an authenticated low-privilege account read sensitive information outside its permitted scope on Linux and Windows installations. The vendor rates the issue Low severity (CVSS 3.1) with High attack complexity and confined confidentiality impact, and no public exploit was identified at time of analysis; priority is monitor.
The GeoDirectory WordPress plugin before 2.8.195 renders listing data through its field shortcodes without verifying the status or ownership of the referenced listing, so an authenticated user holding the Contributor role or higher can read the content and custom fields of other users' draft, pending, private and trashed listings by supplying the corresponding id attribute. The exposure is read-only - no modification or deletion is possible - and is gated by the requirement for a Contributor-level account on the target site. A vendor patch is available in 2.8.195, EPSS is low at 0.16% (5th percentile) and there is no public exploit or KEV entry identified at time of analysis.
SiteOrigin Page Builder before 2.38.0 exposes unpublished WordPress content to users with contributor-level access or higher through its Post Loop widget. The widget accepts user-supplied query arguments and does not limit results to posts the user is permitted to read, allowing retrieval of other users' draft, pending, scheduled and private posts and pages. This is a low-severity, read-only information disclosure (CVSS 2.7, EPSS 0.16%, priority: monitor); no public exploit was identified at time of analysis and there is no KEV entry.
SQL injection in Dell PowerProtect Data Domain Management Center allows a high-privileged, remotely connected attacker to read information the account would not normally expose; there is no indication of data modification or denial of service. Affected releases span Feature Release 7.7.1.0 through 8.8, LTS2024 7.13.1.0 through 7.13.1.80, LTS2025 8.3.1.0 through 8.3.1.40, and LTS2026 8.6.1.0 through 8.6.1.20. The CVSS 3.1 score is 2.7 (PR:H, C:L), Dell has published a fixed-release advisory, and no public exploit has been identified at time of analysis; the dominant risk factor is the requirement for an existing administrative account.
SQL injection in Dell PowerProtect Data Domain Management Center (DDMC) lets an attacker who already holds high-privilege administrative access read limited data from the management appliance, with no integrity or availability impact. Affected builds span Feature Release 7.7.1.0 through 8.8, LTS2024 7.13.1.0 through 7.13.1.80, LTS2025 8.3.1.0 through 8.3.1.40, and LTS2026 8.6.1.0 through 8.6.1.20; the vector is network-reachable with no user interaction, but the PR:H prerequisite restricts realistic exploitation to insiders or someone who has already compromised an admin credential. At CVSS 2.7 this is a low-severity, low-priority item, no public exploit has been identified at the time of analysis, and the vendor has released fixed builds for each branch.
SQL injection in Dell PowerProtect Data Domain Management Center (DDMC) lets a high-privileged remote administrator disclose limited information from the product's database; the CVSS 2.7 score reflects the requirement for an existing administrative account and only a low confidentiality impact. Affected builds span Feature Release 7.7.1.0 through 8.8 and the listed LTS2024, LTS2025, and LTS2026 ranges; no public exploit or active exploitation is identified at time of analysis, so the issue is rated for monitoring.
SQL injection in Dell PowerProtect Data Domain Management Center (DDMC) allows an attacker who already holds administrative-level remote access to read information they should not be able to reach, with no integrity or availability impact. Affected builds are Feature Release 7.7.1.0 through 8.8, LTS2024 7.13.1.0 through 7.13.1.80, LTS2025 8.3.1.0 through 8.3.1.40, and LTS2026 8.6.1.0 through 8.6.1.20. Scoring is low at CVSS 2.7 (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N) because the PR:H prerequisite sharply limits the attacker pool; there is no CISA KEV listing and no public exploit identified at time of analysis, and the vulnerability is tracked at monitor priority.
The data-shredding workflow in pretix fails to bind generated files to the identity that authenticated the request, because every token-based API user is issued the same session token, so the per-user protection added in 2026.7.1 does not actually take effect. Only authenticated holders of a valid pretix API token can reach the affected code path (CVSS 4.0 PR:L, AC:H, AT:P), and exposure is sharply constrained: shredded files are addressable only through randomly generated UUIDs and are retained for roughly one day before deletion. The vendor rates real-world risk as virtually nil, the issue scores 2.3, no public exploit code has been identified at time of analysis, and the flaw is best characterized as a defense-in-depth regression rather than a directly exploitable data-exposure path. A vendor-released patch (2026.8.1) is available.
Authorization bypass in GROWI v4.5.5 through v8.0.6 lets an authenticated, non-read-only user copy the body of a page revision they cannot read into a page they can edit, via the tags.update API and, under specific editor conflict-check conditions, PUT /_api/v3/page. The attacker must know or guess the target revision's MongoDB ObjectId, which is not secret by design but is not trivially enumerable, making this a low-severity, monitor-level issue. No public exploit was identified at time of analysis, and the vendor fixed the flaw in v8.0.7.
Authenticated read-permission bypass in GROWI versions 3.2.10 through 8.0.6 lets any logged-in user, including read-only accounts without edit permission, read the body or comments of a revision belonging to a page they cannot view by pairing that revision ID with the ID of a page they can view. The flaw is a CWE-639 authorization bypass in the page view, GET /_api/v3/page, and GET /_api/comments.get paths; share-link access is unaffected. It is low severity (CVSS 4.0: 2.3), fixed in v8.0.7, and no public exploit was identified at time of analysis.
MusicFreeDesktop versions 0.0.6 through 0.0.8 expose information through the Request Forwarder component, allowing an attacker on the same local network segment to read limited data without authentication or user interaction. The vendor has not responded to the issue report (GitHub issue #444), and no vendor-released patch or fixed version is identified at time of analysis, while the CVE description states that exploit code has been released publicly. Independent assessment rates real-world risk as low, with confidentiality-only impact and no confirmed active exploitation or KEV listing.
Cross-site scripting in the Vue I18n internationalization plugin (npm vue-i18n, plus @intlify/core and @intlify/core-base) from 9.0.0-beta.5 up to 11.4.13 and in the 12.0.0-alpha line up to alpha.4 allows attacker-supplied markup to reach HTML-rendered translations when escapeParameter (escapeParameterHtml in the Legacy API) is enabled and one translate call supplies both a list and named values. The vendor advisory includes a PoC reference; it is not verified as working exploit code, and no public exploit or active exploitation is recorded at time of analysis (CISA KEV: no; vuln.today decision label: monitor, CVSS 4.0 base 2.1). Impact is limited: three prerequisites must all hold (escapeParameter enabled, translations rendered as HTML such as via v-html, and untrusted named values passed alongside a list), user interaction is required, and the retained sanitizeTranslatedHtml() normally strips event handlers and javascript: URLs, so script execution only follows on builds without the sanitizer or by chaining the iframe srcdoc bypass GHSA-83rm-6c8r-g728; realistic outcomes without that chain are injected phishing links, forms and layout changes.
Hop-by-hop header leakage in Caddy's reverse proxy during WebSocket upgrades allows an upstream that emits headers such as Set-Cookie, Alt-Svc, Keep-Alive or Proxy-Authenticate to have them relayed unmodified to clients instead of being stripped as RFC 7230 §6.1 requires. Caddy v2 releases up to and including 2.11.4 are affected when configured with reverse_proxy and handling HTTP 101 Switching Protocols; the assessed vector (AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:H/A:N) reflects that the attacker must control or compromise the upstream response and that a victim must actually open the WebSocket, with high integrity impact and limited confidentiality impact. A public proof-of-concept reproduction script is included in the GHSA advisory, no KEV entry or EPSS score was provided, and the vuln.today decision label is 'monitor'.
Authentication bypass in Apache Kafka Connect's isolated admin REST API allows unauthenticated network attackers to read and write logger settings, including cluster-wide changes via scope=cluster, when admin.listeners is explicitly configured as a separate listener and REST security extensions such as BasicAuthSecurityRestExtension are used. The issue affects Apache Kafka 2.4.0 through versions before 4.2.2 and 4.3.0 through versions before 4.3.2, with fixes released in 4.2.2, 4.3.2, and 4.4.0; deployments that leave admin.listeners unset are not affected. No public exploit was identified at time of analysis, and the assessed severity is moderate with limited confidentiality, integrity, and availability impact confined to the /admin/loggers endpoint.
Kafka Streams can be stalled indefinitely by a single record whose timestamp is at or near Long.MAX_VALUE, causing an integer overflow that moves the next stream-time punctuation to a negative time and makes PunctuationQueue re-queue it in a lock-holding loop until the StreamThread stops. EUVD lists Apache Kafka 1.1.0 through 4.1.2, 4.2.0 through 4.2.1, and 4.3.0 through 4.3.1 as affected; only the Streams application is impacted, not the brokers or cluster, and the hang returns on restart while the record stays in the topic. Exploitation requires producer write access to a source topic feeding a stream-time-punctuation topology and a broker that stores the extreme timestamp-brokers from 4.0.0 reject timestamps more than one hour in the future by default-so reachability is limited to older brokers or relaxed bounds; the assessed vector is CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H, no EPSS score is present, no KEV entry is listed, and no public exploit identified at time of analysis, with priority monitor.
Denial of service in Apache Kafka's KRaft controller affects releases 2.8.0 through 4.2.1 and 4.3.0 through 4.3.1, where a remote authenticated principal holding CLUSTER_ACTION authorization can terminate the controller process by sending a crafted FetchSnapshotRequest whose topics array is empty or whose single topic carries no partitions. The impact is availability-only: the controller dies, taking cluster metadata management down with it, but no data is exposed or altered (assessed CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). CLUSTER_ACTION is a cluster-level permission normally held by broker/controller identities rather than ordinary producers or consumers, so the realistic attacker is a compromised or malicious broker or a holder of inter-broker credentials. No public exploit has been identified at time of analysis, no CISA KEV entry exists, and the vuln.today decision label is 'monitor'.