Cross-site scripting in udecode Plate's core HTML deserialization APIs allows attacker-controlled script to execute in a consuming application's origin when untrusted or cross-user HTML is deserialized and then loaded by another user; affected builds are all versions prior to 53.3.11 plus the discontinued 54.0.0-beta.0 and 54.0.0-beta.1 prereleases. The pre-fix code parsed supplied HTML strings in the active document, so certain attributes triggered browser behavior before the markup was converted into editor nodes; the assessed vector (CVSS 6.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) reflects network-delivered input needing no authentication (PR:N) but requiring victim interaction (UI:R) and a scope change, and exploitation is only realistic where the consuming application itself wires attacker-influenced HTML into these APIs. There is no public exploit identified at time of analysis and no KEV listing, but the vendor has shipped a fix in 53.3.11.
SQL injection in the ID parameter of /module/employee/index.php in itsourcecode Leave Management System 1.0 allows an attacker holding a low-privilege authenticated session to read sensitive records and partially modify database contents, with no user interaction and no special configuration required. Publicly available exploit code exists, disclosed through a public GitHub issue and catalogued by VulDB, but there is no CISA KEV listing and therefore no confirmation of active exploitation. Our independent re-assessment (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N) treats the confidentiality impact as High and rates the issue more seriously than the CVSS 4.0 base score of 2.1 attached to the VulDB entry, although the practical risk is constrained by the product's extremely small real-world deployment footprint.
An authorization bypass in the Ash framework (Elixir) lets authenticated, lower-privileged actors recover values they are not permitted to see by using filtered calculations or aggregates as a yes/no oracle. Ash field policies are designed to protect against filter-based disclosure by rewriting references to forbidden attributes into an expression that evaluates to nil, but prior to 3.33.4 that rewriting only matched Ash.Resource.* structs and not Ash.Query.Calculation or Ash.Query.Aggregate structs, so filters on those ran against real values. Any application that uses Ash.Policy.Authorizer with field policies on calculations or aggregates and exposes filter arguments (commonly via AshGraphql or AshJsonApi) is affected; no public exploit identified at time of analysis, and the disclosure is gradual - one probe at a time - with no integrity or availability impact.
Authenticated attackers with admin-level access to Synaptik CMS (synaptik-cms) through version 1.3.4.4 can abuse the rename function in admin/file-manager.php to place executable files on the server, bypassing the intended file-type restrictions. Exploitation is remote and requires only administrative privileges (PR:H, UI:N), with limited confidentiality, integrity, and availability impact per the CVSS 4.0 vector scoring 5.1; publicly available exploit code has been published in a GitHub security-research repository, so weaponized use against unpatched instances is plausible. The vendor has released version 1.3.5, which remediates the issue, and no CISA KEV listing or EPSS score was supplied in the source data.
SQL injection in the gedelumbung HospitalManagement application (PHP/CodeIgniter-style MVC codebase) allows an attacker who can reach the patient-index search function to inject arbitrary SQL through the 'cari' argument passed to generate_index_pasien in application/models/app_global_admin_model.php. The flaw is CWE-89, reachable over the network (AV:N, AC:L), but the CVSS 4.0 vector assigns PR:H, indicating exploitation in the intended path requires high-level (administrative) privileges; impact is limited to low confidentiality, integrity and availability (VC:L/VI:L/VA:L). Publicly available exploit code exists, but there is no CISA KEV listing and no confirmed active exploitation; the project uses rolling releases, so no fixed version is identified and the maintainer has not responded to the issue report.
A crafted OSPFv2 packet delivered by an adjacent OSPF neighbor can force an unexpected restart of the OSPF process on Arista EOS devices that run both OSPFv2 and OSPFv2 segment routing, producing an availability-only denial of service (CVSS 6.5, AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Only deployments with segment routing enabled under OSPF are exposed, since this is not a default OSPF setting, and the attacker must already be positioned on the same routing segment or link (typically a compromised or rogue device inside the OSPF domain) rather than an arbitrary internet host. No authentication or user interaction is required once adjacency is achievable, repeated packets can sustain the outage, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
An authenticated user with gRPC/gNSI access on Arista EOS can retain permissions that a security policy rotation was supposed to revoke, because a race condition in the gNSI Authz service causes the policy rotation to fail silently when multiple gNSI transports are configured on the device. Only non-default deployments with more than one gNSI transport are affected, Bootz is explicitly out of scope, and the flaw does not grant new privileges - it merely preserves access the attacker already legitimately held, so the outcome is a stale authorization state rather than a privilege escalation. Exploitation requires the revocation and the race to coincide, making it opportunistic rather than attacker-triggerable on demand; Arista discovered the issue internally and reports no malicious exploitation, and no public exploit code has been identified at time of analysis. The vendor's CVSS 4.0 score of 6.0 is well-calibrated for a genuinely moderate, not critical, issue.
Arbitrary local file read and server-side request forgery are possible in the Nodemailer npm package through version 9.1.0 when an application that has deliberately enabled the disableFileAccess/disableUrlAccess sandbox resolves untrusted message content through the legacy three-argument API MailMessage.resolveContent(data, key, callback). Because the omitted options argument is normalized to an empty object inside shared.resolveContent(), the message-level sandbox flags copied into mail.data by the MailMessage constructor are discarded and resolveContentValue() skips both access-control guards, reaching fs.createReadStream() for local files or nmfetch() for outbound HTTP(S) requests driven by attacker-controlled html, text, or attachment path/href values. The flaw is strongly condition-gated: it is inert unless the sandbox was enabled AND the legacy signature is used on attacker-controlled content, which is reflected in the high attack complexity and present-attacker scoring; the internal transporter.sendMail() resolution paths are unaffected, no public exploit code has been identified at time of analysis, and the vendor shipped a fix in 9.1.1.
Stored cross-site scripting in ChangeWeDer CRM allows an authenticated low-privilege user to plant JavaScript in the customerName argument submitted through the customer record Save Endpoint (src/main/resources/public/js/customerServe/customer.serve.js), which then executes in the browser of a CRM operator who later opens the same customer record. The project follows a rolling-release model, so no affected or fixed version numbers are published, and the maintainers were notified through an upstream GitHub issue but have not responded. Publicly available exploit code exists; there is no CISA KEV listing, and EPSS data is not available. The assessed CVSS:3.1 vector is AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, matching a low-to-moderate severity finding rather than a top-priority emergency.
Cross-site scripting in PbootCMS versions 3.2.0 through 3.2.22 lets an authenticated backend user supply a malicious value in the content Title argument, which the decode_string function in apps/admin/controller/content/ContentController.php fails to neutralize before the Template Rendering component outputs it; the injected script then executes in the browser of any user who loads the rendered page. Publicly available exploit code exists, but exploitation is constrained by two prerequisites - a valid backend account and victim interaction with the tainted page - and the assessed impact is limited to manipulation of page content in the viewer's browser, with no confidentiality or availability impact. This is a low-priority issue despite being remotely reachable.
Malformed PIM Sparse Mode messages can crash the Pimsm agent on Arista EOS switches, causing a sustained denial of service when an unauthenticated, network-adjacent attacker repeatedly sends the triggering traffic. Exploitation is constrained to devices where both PIM Sparse Mode and MLAG are configured simultaneously - a non-default combination, and the attacker must be Layer-2 adjacent rather than Internet-reachable. Impact is availability-only: the Pimsm agent auto-restarts, so a single malformed message causes only a brief multicast-routing interruption, while continuous repetition is required to keep the agent in a restart loop. No public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited (no CISA KEV listing); risk is bounded rather than urgent.
CPU exhaustion denial of service in jwcrypto's JWK.import_key() allows a remote unauthenticated attacker to supply a crafted JWK with an arbitrarily large key_ops array and trigger O(n²) duplicate-detection work, consuming CPU proportional to the square of the array length. Any Python application that passes externally-supplied JWK material to this API - via ECDH-ES key agreement, OIDC dynamic client registration, DPoP proof parsing, or ACME account key registration - is vulnerable. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis; CVSS rates this at 5.9 (Medium) with AC:H reflecting the requirement that attacker-controlled key material must reach the vulnerable code path.
Unauthenticated HTTP/2 requests to Fastify routes that register response trailers crash the entire Node.js process, dropping all in-flight requests and repeating the outage on every restart. The flaw affects Fastify versions before 5.12.5 and requires two non-default, application-specific conditions: the server must have HTTP/2 enabled and at least one route must call reply.trailer(). No public exploit code or confirmed active exploitation is identified at time of analysis, and the 5.9 CVSS score reflects a bounded availability-only impact rather than a high-severity compromise. Fastify 5.12.5 contains the fix.
Denial of service in NLnet Labs Unbound 1.12.0 through 1.26.0 arises from a use-after-free in the DNS-over-HTTPS (DoH) code path, reachable only in builds compiled with --with-libnghttp2 when failure conditions such as an RPZ drop action or heavy-traffic stream jostling occur. A remote, unauthenticated attacker can trigger the flaw with a single DoH connection and appropriate traffic, causing memory corruption that, under a hardened allocator, results in controlled termination of the Unbound process. No public exploit code has been identified at time of analysis; the impact is confined to availability (CVSS 5.9, C:N/I:N/A:H) with no confidentiality or integrity effect.
Improper authorization in the n8n source control push endpoint (versions before 1.123.76, 2.37.7, and 2.38.2) allows an authenticated, project-scoped privileged user such as a project admin to reference files outside their own projects and push deletions of other projects' workflows and credentials, causing cross-project data destruction. Exploitation is gated: the Source Control (Environments) enterprise feature must be licensed, enabled, and connected to a remote repository, and the attacker must already hold a privileged in-app account (CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N; CVSS 4.0 base 5.9, integrity-only with PR:H). No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has released fixed versions 1.123.76, 2.37.7, and 2.38.2.
An out-of-bounds read in GPAC 26.08-DEV (the wait_for_header_and_parse routine in src/utils/downloader.c) can disclose memory contents or crash the process when the downloader parses a crafted or empty Content-Range value in an HTTP response header. The victim must actively initiate a download from a malicious or man-in-the-middle server for the malformed header to reach the parser; the vulnerable code path is in GPAC's generic HTTP/fetch machinery rather than a media-decoding path, and the consequence is limited to information disclosure or a crash - no write primitive or code execution is demonstrated. Publicly available exploit code exists (the issue is tracked publicly on the GPAC GitHub project) but the flaw is not confirmed actively exploited (CISA KEV), and the assessed impact is low on both the availability and confidentiality axes.
Opening a specially crafted BIFS or LASeR scene file in GPAC 26.08-DEV can trigger a use-after-free in the scene-graph command handler, crashing the application. Only local exploitation is possible: the victim must load attacker-supplied media in a vulnerable pre-abi-16.24 build, there is no network-reachable trigger, and impact is limited to availability (denial of service) with no confidentiality or integrity effect. Publicly available exploit code exists (referenced PoC archive on GitHub), and the underlying flaw is remediated by the upstream fix released in abi-16.24 (commit e34f4ba); despite the public PoC this is a low-priority, low-real-risk issue given the local, user-interaction-dependent attack path.
Denial of service in GPAC 26.08-DEV can result from a use-after-free when a local user opens a crafted BIFS/MPEG-4 scene file containing malicious proto-library links. Exploitation requires local processing of an attacker-supplied file and the realistic outcome is an application crash with availability impact only; there is no demonstrated confidentiality or integrity impact and no demonstrated code execution. Publicly available exploit code exists, but the issue is low severity (CVSS 1.9 in the supplied 4.0 vector) and the independent assessment notes the PR:L requirement is questionable, viewing the attack as local file parsing with user interaction. The vulnerability is fixed in GPAC abi-16.24 via commit e34f4ba349d55cd1849f0bcf4cf46552732e2db7.
Local use-after-free in GPAC's scenegraph command handling (gf_sg_command_apply / gf_node_deactivate_ex) lets an attacker crash MP4Box and other GPAC-based tools when a victim opens or converts a crafted LASeR/SVG scene, or an MP4 that embeds one. The vector is local and requires the victim to process the malicious media, and the assessed impact is availability only (process crash; C:N/I:N/A:L) with no confidentiality or integrity loss and no demonstrated code execution. Publicly available exploit code exists (a PoC archive was published alongside the VulDB report), the issue is fixed by the GPAC abi-16.24 release, and it is explicitly distinct from CVE-2026-90827.
Apache NiFi 1.5.0 through 2.11.0 expose REST API methods for replacing an entire Process Group's contents (flow replacement plus versioned-flow update and rebase) that enforce only read/write privileges on the target Process Group, while the parallel asynchronous update methods additionally authorize every component encapsulated in the flow plus referenced Controller Services, Parameter Contexts, and Parameter Providers. An authenticated user holding write access to one Process Group (CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:L) can therefore submit a crafted flow definition that modifies or deletes components in descendant Process Groups governed by more restrictive policies, or binds components to referenced services and contexts they are not authorized to use. Exploitation is limited to deployments that actually rely on component-level authorization policies and to stopped components, since existing verification checks prevent modification of running ones; no public exploit code or confirmed active exploitation was identified at time of analysis, and the flaw is fixed in Apache NiFi 2.12.0.
Cross-site scripting (XSS) in the Category Update function (/admin/update_category.php) of SourceCodester Online Food Ordering System 1.0 allows an authenticated administrator to inject script payloads that execute in the browser when the manipulated category page is rendered, requiring user interaction. Publicly available exploit code exists, but the high-privilege prerequisite (admin access) and limited integrity-only impact make this a low-severity admin self-XSS scenario; no active exploitation (CISA KEV) is indicated.
DNSSEC validation downgrade in ISC BIND 9 lets a remote, unauthenticated attacker who can inject or spoof responses on the resolution path present a validly signed NSEC3 record taken from an unrelated sibling zone as an insecurity proof, so a securely delegated name is treated as insecure and a forged unsigned answer is accepted. Only resolvers actively performing DNSSEC validation are exposed, and the affected ranges are 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, plus the subscription builds 9.11.3-S1 through 9.18.50-S1 and 9.20.9-S1 through 9.20.27-S1. The issue is integrity-only (no confidentiality or availability impact) and rated 5.9 because exploitation is difficult: the attacker must legitimately obtain a signed NSEC3 from another zone and win the response race, and no public exploit identified at time of analysis, though vendor patches are available.
DNSSEC-validating BIND 9 resolvers can be induced to accept an inapplicable NSEC record as proof that no wildcard exists at a given name, letting an attacker who controls a zone at the same or an upstream level of the victim's name mask the existence of the victim's wildcard record and thereby disrupt resolution of names it should answer. Affected releases span BIND 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and the corresponding 9.11.3-S1 through 9.18.50-S1 and 9.20.9-S1 through 9.20.27-S1 subscription branches. The flaw is rated CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N) and is an integrity-only issue confined to wildcard denial-of-existence proofs; no public exploit identified at time of analysis, and no confidentiality or availability impact is claimed by the assessed vector.
Denial of service in ISC BIND 9 recursive resolvers: an attacker who controls (or compromises) an authoritative server for a DNSSEC-signed zone can cause `named` to abort after it encounters a use-after-free when processing a specific crafted sequence of answers. The attacker must first induce the victim resolver to issue multiple queries for that attacker-hosted zone, and the malicious responses must then arrive in a particular order and timing to trip the race, which is why this is rated high complexity (AC:H) despite being remote and unauthenticated (PR:N, no user interaction). Impact is availability-only (C:N/I:N/A:H), and exploitation is limited to `named` running as a recursive resolver on the listed versions; only 9.20.29 and later are fixed, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Access-control bypass in Cisco Secure Firewall ASA and Threat Defense (FTD) software allows an unauthenticated, remote attacker to push traffic that should be blocked through the device and reach hosts in networks the firewall is meant to protect. The defect is a logic error in how group access control policies (ACPs) are populated when the Access Control List Object Group Search (OGS) feature is enabled, so it only manifests on devices that both enable OGS and rely on group objects in their ACLs. Cisco rates it 5.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N) with limited integrity impact and scope change, no public exploit code has been identified at time of analysis, and the configuration dependency keeps real-world exposure below the raw score for most deployments.
Denial of service in Cisco Secure Firewall Threat Defense (FTD) can be triggered remotely without authentication when the legacy Snort 2 Detection Engine parses a crafted SSL/TLS certificate during connection setup, causing the engine to restart unexpectedly. The flaw affects FTD releases running Snort 2 and processing SSL policy inspection; the provided assessment rates it CVSS 3.1 5.8 (AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L), so impact is limited to a transient availability loss rather than code execution or data compromise. No public exploit code has been identified at time of analysis, and CISA KEV does not list this CVE.
A malformed zone loaded into ISC BIND 9 authoritative servers can contain an NS or DNAME node above the zone origin, which named misinterprets as a zone cut, so queries for names inside the configured zone lose authoritative status and return out-of-zone delegations. Exploitation requires high privileges (PR:H) because the attacker must control the zone data delivered to the server, for example by controlling a primary from which the target secondary performs zone transfers; this is not a remotely unauthenticated attack. On servers that also provide recursion, BIND can follow the locally sourced cut and cache attacker-supplied data for names outside the configured zone, and the condition persists as long as the malformed zone remains in the zone database. No public exploit identified at time of analysis.
SQL injection in the login handler of SourceCodester Inventory and Monitoring System 1.0 lets remote unauthenticated attackers inject arbitrary SQL through the Username argument of /index.php, potentially reading and altering database contents. The flaw requires no credentials, no user interaction, and no non-default configuration, and publicly available exploit code exists; there is no indication of confirmed active exploitation (no CISA KEV listing). Note the scoring split: the CNA's CVSS 4.0 vector rates 5.5 with limited (VC:L/VI:L/VA:L) impact, while our independent assessment treats confidentiality and integrity as High (CVSS 3.1 9.8); real-world risk is in practice bounded less by any technical prerequisite than by the product's small deployment footprint.
Denial of service in Dell ObjectScale is possible in all versions prior to 4.4.0.0 when a high-privileged remote attacker abuses an incorrectly assigned permission on a critical OS-level resource, rated CVSS 5.5 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H). Exploitation requires the attacker to already hold administrative privileges on the platform (PR:H), so realistic exposure is confined to insiders or adversaries who have already compromised a privileged account; only availability is meaningfully impacted, with a minor integrity effect and no confidentiality loss. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV). Dell has released a vendor patch in ObjectScale 4.4.0.0.
Stored cross-site scripting in Adobe Experience Manager lets a low-privileged authenticated attacker (CVSS vector PR:L) persist malicious JavaScript into vulnerable form fields, which then executes in the browser of any user who later views the affected page (UI:R), driving the score to 5.4 with a changed scope (S:C) because the impact lands on the victim's session rather than the vulnerable component itself. The affected line-up is AEM as a Cloud Service, AEM 6.5 LTS, and AEM 6.5, and exploitation is not self-contained: the attacker needs an account able to write into the form field and must wait for a separate, ideally higher-privileged, victim to browse that page. No public exploit code and no confirmed active exploitation were identified at time of analysis, and this is assessed as a genuinely moderate, not high-priority, issue.
Credential isolation bypass in Jenkins GitLab Plugin 1.2149.vcfc32c82b_f7f and earlier allows an authenticated user who holds Item/Configure permission on a folder to reach 'alternative GitLab API token credentials' that are scoped to a different folder and that they are not entitled to use, because the plugin caches the GitLab API client under a cache key derived solely from the credentials ID and never incorporates the folder in which the credentials were resolved. Rated CVSS 3.1 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) under CWE-522 (insufficiently protected credentials), the issue is a moderate authorization/credential-isolation flaw rather than an unauthenticated remote compromise, and it only exists on multi-tenant Jenkins controllers that actually rely on folder-scoped credentials - single-tenant installations and controllers where all credentials are global/system-scoped see no practical impact. There is no public exploit identified at time of analysis, CISA SSVC records Exploitation: none and Automatable: no, and the CVE is not KEV-listed, so it warrants scheduled patching rather than emergency response.
Information disclosure in Jenkins Gradle Plugin 2.19.1252.v15196b_5a_6e10 and earlier lets an authenticated Jenkins user who can influence the build log of a Gradle job trick the plugin into fetching build scan data from an attacker-controlled URL in preference to the Develocity server URL set in the plugin's global configuration. Because the plugin attaches the globally configured Develocity access key to that outbound request, the attacker can capture the credential; instances with no Develocity access key configured have nothing to leak, so exposure is conditional rather than universal. No public exploit code has been identified at time of analysis, and this is a genuine but moderate-severity issue: exploitation requires authenticated job-run or job-configure privileges plus a configured access key, and the resulting impact is limited to confidentiality (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
Open redirect in the A2UI web rendering library (a2ui-project a2ui) through version 0.10.7 lets an attacker craft a URL that the Binder component's openUrl handler forwards to the
Mass assignment (CWE-915) in the a2ui message-processing component lets an authenticated remote attacker inject arbitrary, dynamically-determined object attributes by submitting crafted messages to the message processor, producing limited confidentiality, integrity and availability effects. All a2ui versions up to and including 0.10.6 are affected according to the CPE range, and the upstream maintainers have not responded to the reported issue (#2297), so no patched release exists. No public exploit code and no CISA KEV entry were identified at time of analysis; the EPSS probability was not supplied with the input data.
Algorithmic complexity attacks against DNSSEC validation in NLnet Labs Unbound 1.26.0 and earlier let remote unauthenticated attackers degrade resolver performance by steering queries to malicious zones that amplify validation work - TagTrap (floods of mismatched DNSKEY/RRSIG/DS records), DelegationTrap (deeply nested chain-of-trust validation), NsecTrap (excessive invalid NSEC records), and AdditionalTrap (Unbound's default DNSSEC validation of the ADDITIONAL section). Exploitation requires a DNSSEC-validating Unbound resolver and attacker control of the zone being resolved, and impact is limited to resource exhaustion (CVSS 5.3, availability Low) rather than compromise or a guaranteed crash. No public exploit identified at time of analysis, and the attacker must be able to drive query volume through the resolver for meaningful effect.
Sustained high-rate streams of distinct uncached names over TCP or DNS-over-TLS can monopolize a single NLnet Labs Unbound worker's event loop, degrading resolver availability for other clients in Unbound versions up to and including 1.26.0. The issue is remotely reachable and unauthenticated (assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L), but the attacker must hold a connection and keep write throughput ahead of the server's drain/processing so the unbounded consecutive-read loop never yields; impact is confined to the affected worker, is degradation rather than a crash, and ends once the traffic stops, while connection caps, query-rate limits, and upstream rate-limiting reduce feasibility. No public exploit identified at time of analysis, and no evidence of confirmed actively exploited (CISA KEV) status; the vendor's CVSS of 5.3 is consistent with this modest degradation-of-service profile.
The Ad Inserter – Ad Manager & AdSense Ads WordPress plugin (all versions up to and including 2.8.16) exposes administrator-configured header and footer code blocks to unauthenticated visitors through the `ai-debug-code` URL parameter, because the debug handler performs no capability check. An attacker who can reach a site running the vulnerable plugin can simply append that parameter to a request and read code fragments — ad scripts, analytics snippets, custom CSS/JS — that the site owner deliberately disabled from public display. The impact is confidentiality-only (CVSS 5.3, PR:N/UI:N), and there is no public exploit code or CISA KEV listing identified at time of analysis.
Server-side request forgery in the AWS Strands Python integration of ag-ui (ag_ui_strands) 0.3.0 allows a user who can submit a chat message to make the agent backend fetch an arbitrary URL through urllib.request.urlopen, reaching loopback, RFC1918, link-local and cloud metadata addresses from the server's network position. The flaw lives in the multimodal content path, where image, document or video attachments can be supplied as URLs rather than inline data, and the pre-patch code applied no scheme, host or redirect validation. Impact is bounded rather than devastating (CVSS 4.0 base 5.3, PR:L), and no public exploit code or CISA KEV entry was identified at time of analysis; the upstream fix commit bf0c34df34cbb4b1992bc37c9bfffe6dd54bb189 is public and referenced by issue #2432 and pull request #2491.
Authenticated Craft CMS control-panel users holding viewEntries and viewPeerEntries (but not savePeerEntries) can silently reorder Matrix blocks and Addresses belonging to other authors' entries in Craft CMS 5.0.0 through 5.10.12 by POSTing directly to the actions/nested-elements/reorder endpoint. The flaw is a missing-authorization condition: the read-only entry view hands the session a manageNestedElements::<ownerId>::field:<handle> flag, and the reorder action trusts that flag without re-verifying the caller's save permission on the owner element, unlike the corresponding delete endpoint. Impact is limited to integrity of sort order (no read, creation, or deletion of content) and requires valid CP credentials plus a multi-author deployment with shared peer content, so it rates 5.3 (CVSS 4.0) and the low end of the integrity-only range; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing). A vendor-released patch exists in 5.10.13.
Sandbox bypass in the n8n Git node lets an authenticated member-level user read git repository objects located outside the path enforced by N8N_RESTRICT_FILE_ACCESS_TO. n8n validates a relative remote URL against the configured repositoryPath, but git is then executed with that directory as its working directory and walks up to the enclosing repository's top level, where it resolves the identical URL string from outside the sandbox; a subsequent fetch or pull merges the external repository's objects into the attacker's own repository, from which the contents can be read back. Versions before 1.123.76, 2.37.7, and 2.38.2 are affected; no public exploit code has been identified at time of analysis, and the confidentiality-only impact (CVSS 4.0 base 5.3, assessed as CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N) is neutralized by upgrading or by disabling the Git node.
Missing authorization in AVideo through 29.0 lets any authenticated user post comments to password-protected or group-restricted videos by submitting crafted POST requests to the comment API with arbitrary video IDs. The flaw lives in the set_api_comment function (CVE-2026-92586, CWE-862), which validates that a video exists but not that the requesting user is permitted to interact with it; exploitation requires only a standard registered account (CVSS 4.0 PR:L, no user interaction) and knowledge or enumeration of the target video's ID. Impact is strictly integrity-limited - attackers can inject comment content onto restricted videos, but the password/group viewing gate itself is not bypassed and the protected media remains unreadable. No CISA KEV listing or public exploit code is associated with this issue in the supplied intelligence, and our independent assessment rates it a genuine-but-low-severity broken-authorization flaw rather than an emergency.
Vote-counter manipulation in AVideo through 29.0 allows any authenticated user to like or dislike password-protected and group-restricted videos they cannot view, because the set.json.php API endpoint does not enforce video access permissions. The flaw is an object-level missing authorization issue (CWE-862) affecting commit c3edcc274c389816d434acadac07ee78eaf330c1; impact is integrity-only, with no content disclosure, availability, or confidentiality effect. No public exploit identified at time of analysis, and the independent assessment rates real-world risk as low despite the medium CVSS score.
Stored cross-site scripting in AVideo through 29.0 (revision e01e41ecc) allows unauthenticated remote attackers to inject arbitrary HTML/JavaScript into the videos_statistics table via the view-counter endpoint, which is then executed in the session of a video owner or administrator who visits the statistics page. The vulnerability arises because unrecognized User-Agent strings are stored verbatim in the app column without invoking the sanitizing setter, and the DataTables 1.12.1 renderer on view/videoViewsInfo.php uses innerHTML. No vendor patch is available, no public exploit code was identified at time of analysis, and exploitation is limited by the need for a privileged user to view the stats page and a 45-character payload truncation.
Authenticated AVideo users can drive video like counts arbitrarily negative by submitting the 'like' request parameter as an array rather than a scalar, exploiting counter arithmetic in Like::__construct() that executes before input validation; the resulting corruption is stored in a denormalized counter and persists until an administrator manually repairs it. Impact is confined to integrity of the engagement metric (no confidentiality, availability, code execution, or user interaction required), and no public exploit code or confirmed active exploitation is associated with this issue at time of analysis. CVSS 4.0 base score is 5.3 for AVideo through version 29.0; our independent assessment (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) rates this a low-to-moderate integrity issue rather than a security priority.
Forced logout of authenticated AVideo users (versions through 29.0) is possible when the third-party LoginWordPress plugin is installed and enabled, because the core autoCSRFGuard() function exempts plugin files whose basenames collide with exempt core filenames. An unauthenticated remote attacker (CVSS vector PR:N) can induce an already-authenticated victim to submit a cross-site POST to the plugin's login.json.php endpoint, which inherits the CSRF exemption and terminates the victim's session before credential validation occurs; the attack does not read data, alter server-side records beyond ending the session, or bypass login, and impact is confined to session termination. No public exploit is identified at time of analysis, and the independent assessment rates this as a genuine but low-to-moderate priority issue rather than a high-severity compromise.
Guest-level users on kan through 0.6.0 can create boards they are not entitled to create by invoking the GitHub project import mutation, which never applies the board:create permission check that the normal board-creation path enforces. The impact is an authenticated, integrity-only authorization bypass (assessed CVSS 3.1 base 5.3, AV:N/AC:L/PR:L/UI:N/C:N/I:L/A:N) that requires the attacker to already hold a low-privilege account on the target instance; there is no disclosure of other users' data and no availability impact. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (CISA KEV), so this is a genuine but low-severity permission-model defect rather than an emergency.
Prototype pollution in the unflatten helper of Builder.io Gen2 SDKs (the @builder.io/sdk-react, sdk-vue, sdk-svelte and sdk-solid packages at or below 5.2.11, and sdk-angular, sdk-react-nextjs and sdk-qwik at or below 0.25.13) lets unauthenticated remote attackers poison Object.prototype in a victim's browser by luring the victim into opening a crafted preview link whose builder.userAttributes query parameters carry __proto__ or prototype segments. Exploitation is not automatable against a passive server - it hinges on user interaction (UI:P), because the SDK must actually be running in the victim's browser when the malicious URL is processed, and real harm (DOM XSS, client-side logic tampering, denial of service) only materializes if downstream application code reads the polluted inherited properties. No CISA KEV entry and no public exploit code were identified at time of analysis, and the independent assessment rates real-world risk as moderate-to-low.
Yahoo CMAK through 3.0.0.6 fails to enforce its scheduled leader election feature toggle on the PreferredReplicaElection HTML form routes, allowing an authenticated user (CVSS PR:L) with network access to the web UI to start or stop the recurring election scheduler and disrupt leadership across the Kafka clusters managed by that instance. This is a protection-mechanism failure (CWE-693) with no confidentiality impact (C:N) and limited integrity/availability impact (I:L/A:L); the assessed severity is low-to-moderate (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L), and no public exploit code has been identified at time of analysis. Environments are at risk only if they run CMAK 3.0.0.6 or earlier and actively manage live Kafka clusters.
Organization-scoped API tokens in OpenCVE before 3.1.0 can list and retrieve every organization belonging to the token creator because the organizations API endpoint ignores the token's organization scope. This is a low-severity confidentiality-only broken-access-control flaw (CWE-863); exploitation requires a valid organization-scoped token (authenticated, PR:L) whose creator belongs to multiple organizations, and it yields no extra data in single-organization deployments. No public exploit identified at time of analysis; vendor-released patch: 3.1.0.
Authenticated low-privilege users of PatrowlManager (versions 0 through 1.8.4) can enumerate the complete user list and read each account's privilege flags - including superuser and staff status - because the authorization decorator on the user-listing API endpoint in users/apis.py was commented out. The issue is rated low severity (CVSS 4.0 5.3, assessed as CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N): it requires valid credentials and yields read-only account metadata with no integrity or availability impact, so its practical value is reconnaissance for privilege-escalation planning rather than direct compromise. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV.