Authenticated users of IBM ContextForge MCP Gateway through v1.0.4 can bypass the gateway's payload protection mechanisms because its recursive content inspection does not fully traverse deeply nested or embedded payload structures. Successful abuse yields limited but real integrity and confidentiality impact (CVSS 5.4, AV:N/AC:L/PR:L/UI:N) by allowing disallowed content or instructions to pass through the filter that is meant to stop them, undermining the gateway's role as a security boundary between MCP clients and downstream tool servers. There is no public exploit code or CISA KEV entry at time of analysis, and IBM has published a fix via its support portal, so exposure is limited to unpatched deployments reachable by an authenticated account.
IBM Business Automation Workflow (both containerized and traditional deployments) fails to enforce authorization checks on certain import operations, letting an authenticated user invoke restricted import actions they should not be permitted to perform. Successful abuse yields limited confidentiality and integrity impact (CVSS 5.4, AV:N/AC:L/PR:L/UI:N) rather than full system compromise. No public exploit code has been identified and the flaw is not listed in CISA KEV, but IBM has published a vendor patch, so unpatched deployments remain exposed to any user holding a valid low-privileged account.
IBM Cloud Pak for Business Automation is affected by HTML injection (CWE-80) in one or more web UI components, allowing an attacker who already holds low-privileged authenticated access to inject markup that executes in a victim's browser within the hosting site's security context. The CVSS 3.1 base score is 5.4 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), reflecting a network-reachable, low-complexity flaw that still requires authentication and victim interaction, with scope change because the injected script runs against the site's origin. No EPSS score, CISA KEV entry, or public exploit code was provided in the intelligence feed, so active exploitation is unconfirmed; IBM has published a fix advisory.
MISP 2.5.45 and earlier can write corrupted access-log records for any HTTP request that ends in an unhandled exception, because CakePHP's CakeErrorController extends AppController and re-runs the application startup path, causing AccessLog::logRequest() to register a second deferred writer that overwrites the row written by the first pass. The overwritten fields include request duration, SQL query count, memory usage and potentially the query log, silently degrading the fidelity of MISP's own audit trail. Exploitation requires an authenticated session (CVSS 4.0 PR:L, VI:L only); no public exploit code or CISA KEV listing was identified at time of analysis, and an upstream fix commit (0dae5c072) is available.
Unauthenticated information disclosure in the 3D FlipBook - PDF Embedder, PDF Flipbook Viewer, Flipbook Image Gallery WordPress plugin (all versions ≤1.16.20) allows any remote attacker to retrieve the full metadata payload of password-protected flipbooks - including title, outline, props, and the serialized data blob containing the underlying PDF file's direct URL - bypassing WordPress post-password confidentiality entirely. The plugin's AJAX handler in inc/ajax-get.php processes the 'id' parameter without verifying that the requestor has authenticated against the post password, and a companion unauthenticated AJAX action (fb3d_send_posts) enables systematic enumeration of all flipbook post IDs with no prior knowledge of the target site's content structure. No public exploit code and no CISA KEV listing exist at time of analysis.
Cross-site scripting in Governikus AusweisApp through version 2.5.4 lets a remote attacker plant script through the ResultMessage argument handled by the StartPAOSResponse component, so that attacker-influenced content is rendered instead of plain result text. The flaw is network-reachable with no privileges required, but the user must be engaged in an eID flow before the malicious response is processed. No public exploit code or CISA KEV entry is associated with this CVE at time of analysis, and the vendor has released version 2.5.5 as the fix.
Authenticated users of MISP 2.5.45 and earlier can list dashboard templates that are supposed to be restricted to other permission flags, such as perm_site_admin, because a MySQL type-juggling flaw makes the 'unrestricted' branch of the template query match every permission-restricted template. The bug is an incorrect-authorization error (CWE-863) in DashboardsController::listTemplates(), patched upstream in MISP 2.5.46; no public exploit code or CISA KEV entry was identified at time of analysis, and the CVSS 4.0 base score of 5.3 reflects only low confidentiality impact with no integrity or availability effect.
Let me synthesize the analysis. Key facts: - CVE-2026-91857, CSRF (CWE-352) in MISP ≤2.5.45, fixed in 2.5.46. - State-changing controller actions accept GET: EventReportsController::purgeUnusedPictures(), NoticelistsController::enableNoticelist() (actually toggleEnable?), ServersController::removeOrphanedCorrelations(), WorkflowsController::rebuildRedis(). - Patch adds allowMethod(['post']). - CVSS 4.0 vector given: AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N → 5.3 - EPSS: not provided. KEV: not provided. POC: not provided. - Patch available from vendor; commit hash b4a5486b5. - Reporter: CIRCL (MISP's developer). - Tags: CSRF, Misp - CPE: cpe:2.3:a:misp:misp:*:*:*:*:*:*:*:* - Prevalence: MISP is a widely used threat intelligence sharing platform — high (widely-deployed enterprise software, but niche in that it's a specific security tool). I'd say "medium" or "high". MISP is deployed in many SOCs, CERTs, ISACs. I'd say high — it's a well-known platform in security community. Hmm. Given anchors: high = widely-deployed enterprise software. MISP is pretty common in threat intel sharing. I'll say "high". Actually could argue medium (common but not everywhere). MISP is used by most CERTs/ISACs and many enterprises. I'll go with "high". UI:P in the CVSS 4.0 vector — user must be tricked into visiting a page / clicking a link. Actually the description says GET can be induced cross-origin through links, images, redirects, or navigation. CVSS 4.0 UI:P (Passive) means the user doesn't have to actively interact beyond normal — e.g., just visiting a malicious page. So UI:P. PR:N in the CVSS 4.0 vector — no privileges required, but requires the victim's authenticated session. That's typical CSRF: PR:N in the CVSS sense (attacker doesn't need credentials), but exploitation requires the victim to be authenticated. My assessed CVSS 3.1 vector: CSRF requiring victim interaction. AV:N, AC:L, PR:N, UI:R (in 3.1, UI:R because victim must be tricked — in 3.1 there's no pa
Let me synthesize this into the required JSON. Key facts: - CVE-2026-91773, Soft Serve (charmbracelet/soft-serve), Git LFS lock metadata disclosure. - CWE-639 Authorization Bypass Through User-Controlled Key (IDOR) - CVSS 4.0 vector: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N → 5.3 - Affected: 0.7.1 through 0.11.6 (fixed in 0.12.0) - Patch: vendor available; commit e34914699128c937afad167d43ccb5310e48b319 adds repo_id scoping. - No KEV, no POC noted explicitly. But commit includes tests. No EPSS given. - Tags: Authentication Bypass, Soft Serve. Product name: "Soft Serve" (charmbracelet soft-serve) — 2 words. Good. Prevalence: Soft Serve is a self-hosted Git server — niche. "low" or "rare". It's a fairly well-known project in the Charm ecosystem but not widely deployed enterprise. I'll say "low" with basis "self-hosted Git server, niche deployment footprint". Assessed CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N = 4.3. Wait: CVSS 3.1 with PR:L, C:L → base score. Let me compute: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. Exploitability = 8.22 * AV(0.85) * AC(0.77) * PR(0.62) * UI(0.85) = 8.22*0.85=6.987; *0.77=5.38; *0.62=3.335; *0.85=2.835. Impact sub-score for C:L only: ISS = 1 - [(1-0.22)*(1-0)*(1-0)] = 0.22. Impact = 6.42*0.22 = 1.412. Base = roundup(min(1.412+2.835, 10)) = roundup(4.247) = 4.3. Fine. CVSS 4.0: matches provided: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. Attack chain: Authenticate to Soft Serve → Access any repo with write permission (own repo) → Enumerate LFS lock IDs via lock list endpoint → Retrieve lock metadata from private repos → Recover file paths, usernames, timestamps. 5 steps. Exploitation conditions: requires authenticated account with write access to at least one repository; the LFS lock list endpoint accepts `id` query param; target must be using Soft Serve Git LFS locks feature with locks present in private repos. Limits: read-only (confidentiality only), no ability to modify/delete others' locks? Actually
An out-of-bounds read in the ARP filter import handler (filter_arp_put_file.cgi) of Netcore NR255-V firmware 1.5.130703 lets an attacker who can reach the router's web management interface and supply a malformed, non-null-terminated string cause the string-handling API to read past the end of an allocated buffer, exposing adjacent process memory in the response. The flaw is rated CVSS 5.3 (CVSS:4.0/AV:N/AC:L/PR:L/UI:N/VC:L/VI:N/VA:L), indicating a network-reachable, low-privilege issue with limited confidentiality and availability impact only — there is no confirmed integrity impact, no CISA KEV listing, and no confirmed public exploit code; the only public material is a VulnCheck advisory plus a third-party GitHub technical reference whose exploit content is unverified.
Unauthenticated attackers with adjacent network access to the mySCADA myPRO Manager notification gateway can send arbitrary SMS messages through its connected GSM modem by submitting a phone number and message text to an exposed HTTP endpoint that performs no authorization checks. The flaw is a missing-authorization weakness (CWE-862) affecting myPRO versions 0 through 2.1, rated CVSS 4.0 base 5.3. Impact is limited to SMS abuse and messaging-service integrity — no code execution, data disclosure, or process disruption — and no public exploit code or CISA KEV entry was identified at time of analysis.
An incorrect authorization flaw in the Netcore NR255-V router (firmware 1.5.130703) lets any authenticated user with a broad or low-privileged role pull live QoS/bandwidth telemetry from the mod_qos_bandwidth plan.json read routes, exposing network activity data they are not entitled to see. The bug is rooted in missing role checks within filter_conns_dump_cgi.c and IGD_CgiCall.c, so the endpoints return connection and bandwidth statistics regardless of the caller's privilege level. Impact is confidentiality-only and rated moderate (CVSS 4.0 base 5.3, AV:N/PR:L/UI:N/VC:L); no CISA KEV listing or confirmed public exploit code exists, though a public technical write-up of the QoS telemetry disclosure is referenced from the NVD entry.
VRRPv2 IP Authentication Header (IP-AH) authentication can be bypassed in affected versions of Arista EOS, allowing an unauthenticated attacker on the same Layer 2 segment as the VRRP group to impersonate the virtual router master. Successful takeover lets the attacker intercept, modify, or discard traffic that hosts send to the virtual gateway IP, effectively hijacking the default gateway for that VLAN. The issue is vendor-reported through Arista PSIRT (advisory 0157) and tracked as EUVD-2026-80009; no public exploit code or CISA KEV entry was present at time of analysis, and the CVSS 4.0 base score of 5.3 reflects adjacent-network access with no privileges or user interaction.
Let me construct the JSON. CVE-2026-91744: Chrome on Mac, race condition in PlatformIntegration, renderer compromise + social engineering, info disclosure, CVSS 5.3, CWE-367. Let me write fields carefully. Product name: "Google Chrome" — 1-3 words. Or "Google Chrome (macOS)". Keep "Google Chrome". Summary: must not start with "A vulnerability". Start with impact verb + product. Info disclosure in Google Chrome for macOS prior to 153.0.8010.47... Race condition in PlatformIntegration component. Requires attacker to already have compromised renderer process and use social engineering (UI:R). CVSS 5.3. No KEV, no POC identified. Technical context: PlatformIntegration is macOS-specific integration layer (native macOS APIs, app bindings, drag-and-drop, services, etc.). CWE-367 TOCTOU race condition — check and use of resource with different timing, enabling a race window where a resource's state changes between check and use, allowing access to data not intended for the renderer. Chrome's multi-process architecture & site isolation — renderer compromise is assumed by Chrome's threat model. The flaw crosses the sandbox boundary in the sense that the renderer-obtained access to macOS integration surfaces yields sensitive info. Risk assessment: CVSS 5.3 moderate, AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N. AC:H reflects the race condition timing win. UI:R because social engineering. PR:N per the vector — unauthenticated. Requires a compromised renderer, which raises the practical bar considerably: a separate renderer exploit is needed first. EPSS not provided — state missing. KEV not listed. No POC identified. Include "radom" once, naturally, in one sentence as illustrative hypothetical mid-sized operator. Affected products: Google Chrome on macOS prior to 153.0.8010.47. EUVD lists Chrome 153.0.8010.47 <153.0.8010.47 (odd formatting). References: chromereleases blog, chromium issue 520019273. CPE not provided — state that. Remediation: upgrade to 153.0.8010.47 or later (Ch
Information disclosure in Google Chrome desktop builds prior to 153.0.8010.47 allows a remote attacker to leak sensitive data by measuring observable CSS rendering discrepancies induced by a crafted HTML page. Exploitation is unauthenticated (PR:N) but requires the victim to open the attacker-controlled page (UI:R), and the leak depends on high-attack-complexity side-channel measurement rather than a deterministic parsing bug, so the impact is limited to confidentiality with no integrity or availability effect. The issue is rated Medium by Chromium; no public exploit code has been identified at time of analysis, and Google has released a fixed build.
Information disclosure in Google Chrome builds prior to 153.0.8010.47 allows a remote, unauthenticated attacker to leak sensitive data from the victim's browser by measuring font-related observable discrepancies on a crafted HTML page, a technique that requires the victim to be socially engineered into loading that page (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N, base 5.3). Impact is confidentiality-only, with no integrity or availability effect, and the high attack complexity reflects the probabilistic nature of the CWE-203 side channel, so reliable exfiltration demands specific conditions rather than a single deterministic request. No public exploit code was identified at time of analysis and the flaw is not listed in CISA KEV; Google has shipped a vendor-released patch in Chrome 153.0.8010.47, and auto-updating installations at or above that version are not affected.
A crafted remote-desktop (RDP) interaction with Oracle VM VirtualBox 7.2.16 can hang or repeatedly crash the hypervisor's Core component, producing a complete denial of service against the affected VM sessions. Exploitation is rated difficult (AC:H) and requires a low-privileged account with network reachability to the virtual machine's remote display service, so it is not a drive-by or unauthenticated attack. Only availability is impacted — there is no confidentiality or integrity loss. No EPSS score, CISA KEV listing, or public exploit code was present in the supplied intelligence, so the vulnerability should be treated as a medium-priority patching item rather than an active emergency.
Unauthenticated attackers with network access to HTTP endpoints can cause a partial denial of service in Oracle Helidon versions 4.0.0 through 4.5.4 by abusing the WebSocket component. The flaw carries a CVSS 3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N, availability-only partial impact) and requires no credentials or user interaction, making it trivially automatable against any reachable WebSocket-enabled service. No public exploit code, EPSS score, or CISA KEV listing was provided in the available intelligence, so active exploitation is not confirmed.
Unauthenticated HTTP requests can drive Oracle Helidon 3.0.0 through 3.2.20 into a partial denial-of-service condition through the helidon-media-multipart component, which handles multipart/form-data parsing. The flaw is network-reachable with no privileges or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, base 5.3) and impacts availability only — confidentiality and integrity are unaffected. Oracle rates it easily exploitable in its CPU advisory, but no KEV listing or public exploit code was present in the supplied intelligence feeds, so no public exploit identified at time of analysis.
Unauthenticated attackers with network access to an HTTP endpoint on Oracle Helidon 4.0.0 through 4.5.4 can trigger a partial denial of service in the framework's JSON component, degrading availability of the hosted application. The flaw is rated CVSS 3.1 base 5.3 (AV:N/AC:L/PR:N/UI:N, availability-only impact) and is described by Oracle as easily exploitable, though no public proof-of-concept, EPSS score, or CISA KEV entry was supplied in the input data, so active exploitation is unconfirmed.
Unauthenticated attackers with HTTP access to Oracle Forms Services can read a limited subset of data the application exposes, per Oracle's Fusion Middleware security advisory affecting versions 12.2.1.19.0 and 14.1.2.0.0. The flaw is rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/C:L/I:N/A:N), meaning low-complexity, no-credential, no-user-interaction exploitation whose only impact is partial confidentiality loss - there is no integrity or availability impact and no scope change. No public exploit code, EPSS score, or CISA KEV listing is present in the supplied intelligence, so this should be treated as a patch-now confidentiality leak rather than an actively exploited emergency.
Unauthenticated remote attackers can query an API endpoint in HPE Networking EdgeConnect SD-WAN Orchestrator and read security-relevant configuration details and security feature status. The flaw is a CWE-200 information exposure rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N, with only a low confidentiality impact and no integrity or availability impact), so it does not by itself compromise the platform but hands an adversary reconnaissance material that directly enables follow-on attacks against the managed SD-WAN fabric. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV.
Boolean-based SQL injection in Netmaker's SQLite database backend (versions prior to 1.5.0) lets an authenticated attacker manipulate the SQL executed by the `sqliteDeleteRecord` function through the `{domain}` path parameter of the `DELETE /api/dns/{network}/{domain}` endpoint. By crafting injected conditions that evaluate true or false, the attacker can infer the existence and contents of arbitrary database tables, columns, and values, resulting in limited confidentiality exposure. The flaw is rated CVSS 5.3 and requires a valid authenticated session and a SQLite-backed deployment; PostgreSQL-backed installations use parameterized queries and are not affected. Netmaker 1.5.0 patches the issue by replacing string concatenation with parameterized SQL. No exploitation in the wild or public exploit code has been identified at time of analysis.
Parameter smuggling into the PayPal notify redirect of the J2Store extension for Joomla (versions 1.0.0-3.3.2, 4.0.0-4.0.22, and 4.1.0-4.1.7) lets an attacker-chosen query string ride along with the redirect that the notify endpoint issues to com_j2store's checkout controller, instead of the intended fixed parameter set. A victim must load the crafted link (UI:P in the CVSS 4.0 vector), after which the follow-up request to the checkout controller is processed with the injected view/task/paction parameters, giving a limited integrity impact (VI:L) with no confidentiality or availability loss. The vendor's own description concedes this does not grant an unauthenticated attacker anything they could not obtain by calling the same com_j2store URL directly; no public exploit code and no CISA KEV listing were identified in the supplied intelligence.
Control-character injection in gitoxide's gix-transport crate before version 0.59.2 lets crafted git-daemon URLs smuggle NUL, CR and LF bytes into connect requests, enabling spoofing of virtual hosts and injection of forged newlines into daemon requests and logs. The flaw affects any Rust application or tool that uses gix-transport to open a git:// connection to a URL whose host or path components are attacker-influenced, and requires the victim to initiate that connection (UI:P). Impact is limited to low confidentiality and integrity effects (5.3 Medium), no public exploit code or CISA KEV entry is present in the supplied intelligence, and a vendor advisory with a fixed release is available.
Broken object-level authorization in Vikunja before 2.6.0 lets any authenticated user write task-position records into project views belonging to other tenants by supplying a project_view_id that is never checked against the target task's project. Because only integrity of view ordering is affected (no read, no availability impact), the practical damage is cross-tenant data corruption and ordering manipulation rather than data theft. A vendor patch (2.6.0) and a GitHub security advisory are available; the issue is not listed in CISA KEV and no public exploit code was identified at time of analysis.
An API token scope bypass in Vikunja before 2.6.0 allows a holder of a deliberately limited-scope API token to read task data outside that token's permissions — specifically comments, reactions, and time entries — by adding the 'expand' query string parameter to task read requests, because the authorization layer never inspects query parameters. Exploitation requires an already-valid low-privilege token (CVSS 4.0 PR:L) and only results in limited confidentiality loss, giving a modest base score of 5.3; there is no public exploit and no evidence of active exploitation at time of analysis. The vendor has released a fix in Vikunja 2.6.0.
Vikunja releases before 2.6.0 return the raw TOTP shared secret from the GET /api/v1/user/settings/totp and /api/v1/user/settings/totp/qrcode endpoints without demanding re-authentication, so anyone holding a valid access token can clone the victim's second factor. Because the exposed seed lets an attacker generate valid codes indefinitely, a hijacked session token can be converted into durable account takeover that survives password changes but not TOTP secret rotation. The vendor has shipped a fix in 2.6.0; no public exploit code or CISA KEV entry was identified at time of analysis.
Missing authorization checks in Vikunja's v2 API allow anyone holding a read-only project link-share token to enumerate users through the project users endpoint and to confirm arbitrary usernames exist via the global search endpoint. All Vikunja deployments before 2.6.0 are affected; the flaw is a limited-confidentiality information disclosure (CVSS 4.3, PR:L because a share token is required) and is fixed in 2.6.0. No public exploit code or CISA KEV entry was present at time of analysis.
Vikunja versions before 2.6.0 omit team-level access validation when a team is attached to a project, letting any authenticated user enumerate teams they do not belong to through the project teams endpoint. An attacker with a low-privileged account can supply arbitrary team IDs and receive complete rosters - member names and administrative flags - for unauthorized teams. Impact is confidential-only (CVSS 4.3, CWE-200) and no public exploit code or KEV listing was provided with the source data.
AVideo through 29.0 is affected by a blind server-side request forgery (SSRF) in the getHeaderContentTypeFromURL function, which performs get_headers() calls on URL values that are only checked for format rather than destination. An authenticated user holding the canUpload permission can persist an attacker-chosen URL as a video link; the vulnerable lookup then fires on every render of that video's watch page, letting the attacker probe internal hosts and infer results through content-type differences and response timing. No public exploit code or CISA KEV entry is associated with this CVE at time of analysis, and no EPSS score was supplied in the input, so real-world exploitation activity remains unconfirmed.
Integer overflow in the FreeRDP client's Apple/CoreAudio audio-input (audin) backend, present in all versions before 3.31.0, allows a malicious or compromised RDP server to corrupt memory on the connecting client. The server sends an MSG_SNDIN_OPEN message carrying a crafted FramesPerPacket value that wraps the size arithmetic used by AudioQueueAllocateBuffer, producing an undersized allocation that is then written past its bounds during audio capture. Impact is bounded to the client (CVSS 5.3, all impacts Low, UI:P — the victim must initiate a connection to the hostile server); patch status is 'available from vendor' with a fix in 3.31.0, and no public exploit or CISA KEV entry was identified at time of analysis.
Reflected cross-site scripting in Steedos Platform (all versions through 3.0.15-beta.47) lets an attacker inject JavaScript into the anonymous /api/page/render endpoint by abusing the schemaApi or data query parameters, which are written unescaped into inline script elements. Because the endpoint requires no authentication, a crafted link is enough: when a logged-in Steedos user opens it, the attacker's script runs in the victim's browser context and can read and exfiltrate the X-Auth-Token session credential, enabling full account takeover of that session. No public exploit code or active exploitation has been observed at time of analysis, though the vulnerable source files and route are publicly linked in the advisory references.
The self-registration flow in WSO2 Identity Server and related WSO2 identity/API management products returns a distinct error when a submitted username already exists, letting unauthenticated users enumerate valid accounts. Any remote party who can reach the self-registration endpoint can harvest a list of confirmed usernames, which then feeds credential-stuffing, brute-force, and targeted phishing campaigns. Rated CVSS 5.3 (medium) with confidentiality-only impact; no public exploit code or active exploitation is identified in the supplied data at time of analysis.
Yao (YaoApp) through v1.0.0-rc22 allows any authenticated user to read complete team records via the GET /user/teams/:id endpoint, which authenticates the caller but never verifies team membership. Attackers who hold a low-privilege account and know or guess a team identifier can retrieve team name, description, owner information and settings. The flaw is remotely reachable with low complexity but yields only low confidentiality impact (CVSS 5.3), and no public exploit code or CISA KEV entry was identified at time of analysis.
Let me produce the JSON. Product: Halo (halo-dev) — a Java CMS/blog platform. Product name: "Halo". Summary: Open redirect in anonymous thumbnail endpoint, uri param unvalidated. Halo through 2.26.1. CVSS 4.0: AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N — base likely 5.3. Note: no patch info explicitly. References include issue #10247 — likely the fix issue. No exact fix version. So "Upstream fix available (PR/commit); released patched version not independently confirmed"? Hmm — the issue link is an untagged cveorg reference. I'd say "No vendor-released patch identified at time of analysis" — but there's an issue link. Let me phrase carefully: no patch version confirmed in the provided data; the issue reference may track remediation. Prevalence: Halo is a Chinese open-source blogging/CMS platform — medium? It's a popular Java-based CMS/blog framework in China with GitHub ~36k stars. Deployment footprint: medium seems fair. Actually blogging platforms — I'd say medium. Assessed CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N → 6.1? Wait, CVSS 4.0 gave 5.3 with UI:P (passive). In 3.1, UI:R. Scope: open redirect — does it cross trust boundary? Typically scope unchanged. C:L/I:L? The 4.0 vector has SC:L/SI:L which implies the subsequent system (the redirect target) has low confidentiality/integrity impact. In 3.1 that would suggest S:C. So AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N → 6.1. Hmm. Alternatively S:U → 4.3? Let's compute: AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N = 5.4? Let's check: base with C:L/I:L — impact sub score = 1 - (1-0.22)(1-0.22)(1-0) = 1-0.6084 = 0.3916. ISS = 6.42*0.3916 = 2.514. Exploitability = 8.22*1*1*1*0.62 = 5.096. Base = roundup(min(2.514+5.096, 10)) = roundup(7.61) = 7.6? Hmm, that seems too high. Wait: with S:U, Impact = 6.42*ISS = 6.42*0.3916=2.514. Base score = roundup(min(Impact+Exploitability,10)) = roundup(7.61)=7.6. Hmm, that's for C:L/I:L. Hmm but that requires multiplying 1.08? No, only for S:C: Impact = 7.52*(ISS-0.029) - 3.2
Stored XSS in bizwell xClick groupware allows authenticated low-privileged users to inject malicious scripts that execute in the browsers of other users who view the affected content. The flaw stems from improper input validation (CWE-20) across xClick releases R2, R3, and R3.1. No public exploit code or active exploitation has been identified at time of analysis, and real-world impact is limited by the product's regional deployment footprint.
Netcore NR255-V firmware 1.5.130703 stores attacker-supplied script in L7 content management fields - specifically the call board text and policy group handling components - and later renders that content through eval() sinks, so the payload executes in the browser of any user who views the affected page. Exploitation requires an authenticated management session (CVSS PR:L) plus a victim who opens the poisoned page (UI:P), which keeps the practical severity moderate (CVSS 5.1, low confidentiality and integrity impact). There is no public exploit identified at time of analysis and no CISA KEV listing; the issue is documented through a VulnCheck advisory and a GitHub proof-of-concept-style technical write-up rather than a vendor security bulletin.
Stored cross-site scripting in Netcore NR255-V firmware 1.5.130703 allows an attacker positioned on the same LAN to inject script through DHCP client hostname fields and ARP bind entries; the router persists the payload and network_config.js and network_security.js render it unescaped in the web management interface. When an administrator opens the DHCP dynamic IP list or ARP bind list page, the injected script runs in their authenticated session, potentially exposing session tokens or enabling management actions as the admin. The issue is rated CVSS 5.1 (AV:A, PR:N, UI:P) and no public exploit was identified at time of analysis.
Stored cross-site scripting in the Netcore NR255-V router (firmware 1.5.130703) lets a user with access to the web management interface persist malicious JavaScript into DHCP static IP reservations and IP ACL entries via the dhcp_add_staticip_cgi, dhcp_staticip_show_cgi, ip_acl_set_cgi and ip_acl_show_cgi handlers. The injected script is stored on the device and executes in the browser of any other user — typically a higher-privileged administrator — who opens the affected DHCP or ACL pages, enabling session theft or unauthorised configuration changes performed as that victim. The issue carries only a moderate CVSS 4.0 base score of 5.1 (AV:N/AC:L/AT:N/PR:L/UI:P), no CISA KEV listing and no confirmed public exploit code, so it is a real but comparatively narrow risk concentrated on this specific legacy SOHO router model.
Stored cross-site scripting in the web management interface of the Netcore NR255-V router (firmware 1.5.130703) allows an attacker who already holds a valid management session to plant persistent JavaScript on routing and NAT configuration pages; the payload then executes in the browser of any user who later opens those pages, including higher-privileged administrators. The flaw sits in four CGI handlers (routing_tab_add_cgi, routing_table_list_show_cgi, route_policy_add_cgi, route_policy_parame_show_cgi) that fail to sanitise or encode route/NAT parameters before rendering them. CVSS 4.0 is a moderate 5.1 (AV:N/AC:L/AT:N/PR:L/UI:P), reflecting the need for an authenticated foothold plus a victim viewing the page; at time of analysis there is no CISA KEV listing and no public exploit code identified.
Reflected cross-site scripting in QloApps up to and including 1.7.0 lets an attacker inject JavaScript into the back-office Hotel Reservation System feature-management page by supplying a crafted child_features parameter that is echoed back unescaped inside a validation error message. Only authenticated back-office users are targeted, and they must follow an attacker-supplied link before the payload fires in their administrative session, which is why the CVSS 4.0 base score is a moderate 5.1 rather than critical. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but an upstream fix exists in commit 54a3b30 / PR #1796.
Information disclosure in Google Chrome for Android before 153.0.8010.47 allows a locally installed app on the same device to retrieve sensitive browser data because an authorization check is missing on an Android-exposed Chrome component. The flaw is local-only and rated AC:H, giving a modest CVSS 3.1 base of 5.1 (AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) even though the confidentiality impact is complete; Google's Chromium team nevertheless classifies it as High severity. Google has shipped a fix in 153.0.8010.47, there is no CISA KEV listing, and no public exploit code has been identified at time of analysis.
Arbitrary image-file read in Newell Brands DYMO Connect Desktop allows a crafted file-path parameter sent to the local LoadImageAsPngBase64 web-service endpoint to pull image files from anywhere on the host filesystem rather than from the intended directory. Versions before 1.6.2 are affected; the shipped fix only whitelists file extensions and does not enforce a directory boundary, so out-of-scope reads of files with allowed image extensions remain possible by accepted design. No public exploit code has been identified at time of analysis, and impact is limited to confidentiality (CVSS 4.0 base 5.1, Medium, AV:L/PR:N/UI:N/VC:L).
Stored HTML injection in the 'Firma Circolare' (circular signing) feature of the Design Scuole Italia WordPress theme, affecting versions 1.0 through 2.17.3, allows an authenticated user who can edit the 'sign' parameter to persist arbitrary HTML that forces visiting users to an attacker-controlled URL. Exploitation requires a valid low-privileged account with access to the signing feature (PR:L) plus a victim subsequently viewing the affected page (UI:P/UI:R), and the impact is confined to integrity of the rendered page with no confidentiality or availability effect. No public exploit identified at time of analysis and CISA's SSVC assessment records Exploitation: none with Technical Impact: partial, so this is a low-to-moderate priority issue rather than an urgent one.
A reflected cross-site scripting (XSS) flaw in the Italian government school WordPress theme "Design Scuole Italia" lets an unauthenticated attacker run arbitrary JavaScript in a victim's browser by luring them to a crafted URL whose archive parameter is echoed unsanitized by filters-scheda-didattica.php. All versions from 1.0 through 2.18.2 are reported affected by ENISA/EUVD. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but any site running the theme is exposed to session theft, credential phishing and drive-by redirects against visitors and logged-in administrators alike.
A DOM-based cross-site scripting flaw in the Crawl4AI Playground UI (versions before 0.9.3) lets attacker-controlled crawled content — for example a malicious page title — be re-parsed as HTML inside the forceHighlightElement() routine, which writes textContent back into innerHTML. Because the Playground stores the operator's API token in sessionStorage, a successful payload can read that token and hand an attacker full control of the underlying Crawl4AI server. Exploitation requires the operator to load attacker-controlled page content in the Playground and trigger the highlight action; no public exploit code or CISA KEV entry is confirmed in the supplied intelligence, and the vendor has released a fix in 0.9.3.
Let me synthesize. CVE-2026-91942: crawl4ai before 0.9.3, DOM-based XSS in Docker Playground UI, innerHTML assignment of untrusted crawl results. Malicious PDFs with event-handler markup execute JS in Playground origin, steal API tokens from sessionStorage. CVSS 4.0 vector given: AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N — score 5.1. UI:A means user interaction active (user must open the PDF in the playground). Subsequent system impacts limited (SC:L/SI:L). PR:N unauthenticated. Wait — description says "steal API tokens from sessionStorage for authenticated API abuse" — the attacker themselves may be unauthenticated but the victim is an authenticated user. PR:N with UI:A. Let me construct fields. product_name: "Crawl4AI" (2 words? one token). Fine. prevalence: crawl4ai is a popular open-source LLM-friendly web crawler — medium? It's fairly widely used in AI/RAG pipelines. It's a Python library with ~40k GitHub stars. Deployment footprint: medium. Docker Playground UI is a specific deployment mode though — that reduces. I'd say "medium" with basis "popular open-source LLM crawler; Playground UI subset narrower". Hmm, but the specific vulnerable component (Docker Playground UI) is niche. But prevalence is about the product. crawl4ai is popular open-source library. Medium seems fair. assessed_cvss_vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N — scope changed because it impacts the Playground origin / API tokens (sessionStorage tokens, the script executes in the Playground origin). Actually the CVSS 4.0 vector shows SC:L/SI:L which implies subsequent system impacts → in 3.1 that maps to S:C with C:L/I:L. Hmm, but is scope change right? The vulnerable component is the Playground UI; the impacted component is... the API tokens / authenticated API. The XSS executes in the Playground origin — same origin. Stealing sessionStorage tokens then abusing the API — the API is arguably a different security authority. Given the CVSS 4.0 has subsequent-sys
Failed authentication attempts against MISP 2.5.45 and earlier stop being written to the audit log whenever the Redis instance used for log throttling is unreachable, and they remain unwritten for the entire duration of the outage. The flaw is in AppController::_shouldLog(), which treats 'Redis returned false' as 'nothing to log' rather than degrading to verbose logging, so brute-force or credential-stuffing activity against the login endpoint silently disappears from the record. No public exploit code and no CISA KEV entry exist for this issue, and the vendor shipped a fix in MISP 2.5.46 via commit a39b25d2f.
Stored cross-site scripting in the Netcore NR255-V router (firmware 1.5.130703) lets an authenticated administrator persist malicious JavaScript inside a QoS rule name, which the qos_xianz_add_cgi, qos_xianz_show_cgi, qos_filter_add_cgi and qos_filter_show_cgi handlers later pass to eval() without sanitisation. The injected script runs in the browser of any administrator who subsequently opens the affected QoS pages, allowing session theft, credential capture, or silent reconfiguration of the device through the victim's authenticated session. No public exploit code or active exploitation has been confirmed from the available intelligence.