Sanitizer bypass in rhukster dom-sanitizer up to and including 1.0.15 lets attackers smuggle external references through SVG presentation attributes that the library is supposed to neutralize, because the raw regex check can be defeated by CSS comments or hex escapes while a browser's CSS tokenizer still decodes the value into a live URL. The flaw is remote and requires no authentication or user privileges (CVSS 4.0 base 6.9; assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L), and it only produces impact in deployments that sanitize attacker-supplied SVG (DOMSanitizer::SVG mode, or HTML mode containing inline SVG) and then render that output in a browser. Publicly available exploit code exists and the vendor has released 1.0.16 as the fix; there is no indication of confirmed active exploitation (CISA KEV) at time of analysis, and EPSS-style risk is driven mainly by the low attack complexity and the availability of a public proof of concept.
Unauthenticated remote attackers can delete arbitrary order records in ZongXR SuperMarket 1.0.0.0 because the OrderController.deleteOrder endpoint lacks authentication checks (CWE-306). Publicly available exploit code exists (GitHub issue #31), and the project maintainer has not responded to the report. With a CVSS 4.0 score of 6.9 (medium) and an independent assessment confirming only low integrity and availability impact, the vulnerability poses a low-to-moderate risk, primarily limited by the product's rare deployment in production environments.
Missing authentication in the ZongXR SuperMarket 1.0.0.0 order-save endpoint (OrderController.addOrder) allows unauthenticated remote attackers to submit order actions while passing an arbitrary userId argument, letting them act on behalf of other accounts without any credentials. The root cause is CWE-306: the handler performs no authentication check at all, so the caller-supplied userId is implicitly trusted. Publicly available exploit code exists (documented in the project's own GitHub issue #32), but real-world priority is low because SuperMarket is a niche, non-production Java project with no large-scale enterprise deployment footprint - the practical limit is whether an instance is network-reachable, and no privileges or user interaction are required (CVSS:4.0 PR:N/UI:N; our assessment scores it AV:N/AC:L/PR:N/UI:N with limited integrity impact, C:N/I:L/A:N).
Information disclosure in Johnson Controls Easy IO Neo versions before 3.3b63 allows an authenticated high-privileged attacker to read sensitive data from predictable common resource locations, but requires passive user interaction and yields low confidentiality impact per the independent assessment. This medium-severity flaw (CVSS 4.0 base 6.3, CWE-200) has no public exploit identified at time of analysis. Exploitation depends on the attacker already holding high-privilege access to the controller and on a victim performing passive user interaction, substantially limiting opportunistic exploitation.
Argument injection in the AWS EFS CSI Driver v3.1.0 through v3.4.2 allows an authenticated Kubernetes user or service account that already holds PersistentVolume creation permissions to smuggle extra mount options into an EFS mount by embedding comma-separated tokens in a PersistentVolume's mounttargetipmap volumeAttribute. Because the driver fails to neutralize the argument delimiter, injected tokens are parsed as additional mount flags, giving high confidentiality and integrity impact along the container storage path, while availability is not affected under the assessed vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N (6.5). No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has shipped v3.5.0 to remove the condition.
Filter bypass in the SendGrid, Freshservice, and ServiceNow nodes of n8n (versions before 2.39.6 and 2.40.0 before 2.40.1) lets unescaped parameter interpolation break out of query literals and widen single-record lookups into match-all queries, exposing bulk data such as contact lists, tickets, and directory entries on the connected third-party service. Exploitation is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N) but conditional: the workflow must actually use one of the three affected nodes and bind a vulnerable lookup/filter parameter to untrusted external input, which is reflected in the AT:P attack-requirement rating. No public exploit code was identified at time of analysis and the issue is not in CISA KEV; impact is bounded to bulk read exposure of third-party data, not compromise of the n8n host itself, and a vendor-released patch is available.
Wormhole.app deployments built before 2026-08-22 ship with a misconfigured coturn TURN server that fails to restrict TCP relay peers, allowing an unauthenticated remote attacker to pivot through the relay to reach internal resources such as cloud instance metadata or to source TCP connections from the relay's own IP address. Because the TURN endpoint is reachable over the network with no credentials or user interaction required (CVSS:4.0 base 6.9; independently assessed as CVSS:3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N), impact is bounded by what the relay host's network position can reach - meaningful information disclosure and limited integrity impact rather than full compromise. This is a moderate-priority issue: it is not in CISA KEV and no public exploit code was identified at time of analysis, and the vendor has made a fixed build available.
The Joyland.ai application fails to validate the hostname in TLS certificates presented by the server, allowing an attacker who already occupies a man-in-the-middle position on the network path to impersonate the Joyland.ai backend and read or manipulate chat traffic. All versions of the app appear affected (CPE cpe:2.3:a:joyland:joyland.ai:* and EUVD-2026-91028 both list the wildcard version range). Exploitation is gated by the attacker's need to interpose on the connection (rogue AP, shared Wi-Fi, ARP/DNS spoofing, or compromised segment), which is why the independent assessment rates it CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N rather than the higher CVSS 4.0 6.9 reported by CISA; no public exploit has been identified at time of analysis and the issue is not in CISA KEV.
Hard-coded GeTui push-service credentials embedded in the Joyland AI client app let anyone who extracts them from a copy of the binary call the GeTui REST API without authenticating to Joyland and push arbitrary notification content to individual users, chosen groups, or the app's entire user base. The flaw applies to all observed versions of Joyland.ai (CPE cpe:2.3:a:joyland:joyland.ai:*:*:*:*:*:*:*:*), and exploitation is unauthenticated from the network perspective (CVSS vector PR:N/AC:L/UI:N) - the only practical prerequisite is obtaining the app package and the credentials remaining valid. Impact is bounded to the push-notification channel: the attacker cannot read Joyland backend data or execute code, and no public exploit code or confirmed active exploitation was identified at time of analysis, so the primary risk is mass notification abuse, phishing lures, and brand/reputational damage rather than data compromise.
Arbitrary file creation, overwrite, and truncation outside the intended workspace is possible on hosts running AWS security-agent-mcp-server before version 0.2.0, because the diff scan operation injects an attacker-controlled 'reference' value as extra command arguments. The flaw is local (AV:L) and requires the operator or AI agent to run the diff scan against attacker-influenced input (UI:R), but no authentication is needed once that operation is invoked (PR:N) and the impact crosses a security boundary (S:C), yielding high integrity and availability impact with no confidentiality loss (CVSS 8.2, High). No public exploit code or confirmed active exploitation was identified at time of analysis; the vendor-released fix is version 0.2.0.
Improper TLS certificate validation in the Joyland AI app causes its invisible advertisement WebView to accept invalid or forged SSL certificates by default, letting an attacker who already sits on the victim's network path silently intercept and alter the content flowing through that ad channel. All versions of the app appear affected (CPE cpe:2.3:a:joyland:joyland.ai:* and EUVD lists the version range as '*'), and the CVSS 4.0 vector provided is AV:N/AC:L/AT:N/PR:N/UI:N, meaning no authentication or user interaction is required once a man-in-the-middle position is established. Exploitation is not confirmed in the wild (not listed in CISA KEV) and no public exploit code has been identified at time of analysis, but the real-world barrier is the requirement for an interception position such as a hostile Wi-Fi hotspot, ARP spoofing, or an upstream network foothold; our independent assessment rates this as CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, i.e. lower practical ease than the 6.9 base score suggested by the input vector, with impact bounded to the advertisement WebView rather than the full application.
Man-in-the-middle interception of traffic between the Joyland AI application and its backend is possible because the app accepts any TLS certificate from any server without validating it (CWE-295), exposing transported data to an on-path attacker who can silently decrypt or alter it. Every user of an affected Joyland.ai release is vulnerable by default - no special victim-side configuration is required - but the attacker must first obtain an on-path position (shared or rogue Wi-Fi, a compromised gateway, or ARP/DNS spoofing) and present a forged certificate; the flaw cannot be triggered purely over the internet. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; the vendor-reported CVSS 4.0 base score is 6.9, while our independent CVSS 3.1 reassessment treats the lost confidentiality and integrity of intercepted traffic as high impact with the on-path requirement as the primary limiting factor (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).
The setup endpoint in Ghost CMS returns the site owner's email address to any remote, unauthenticated visitor, exposing every release from 0.8.0 up to but not including 6.23.0. Exploitation requires no account, no user interaction, and no non-default configuration, but the yield is limited to a single email address - no credentials, content, or system access - so realistic impact is reconnaissance and phishing enablement rather than direct compromise. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and vendor patching is available in 6.23.0.
Unauthenticated attackers can read theme template and metadata files from internet-facing Ghost blogs running any version before 6.20.0 by supplying URL-encoded file paths that slip past the platform's file-extension validation, exposing theme source and configuration but not member data, user records, or site secrets. The flaw requires no special configuration and works against a default installation (CVSS 4.0 base 6.9; independent assessment scores it CVSS 3.1 AV:N/AC:L/PR:N/UI:N with only low confidentiality impact, no integrity or availability impact). No public exploit code has been identified at time of analysis, and the vendor-released fix is Ghost 6.20.0.
Unauthenticated visitors to Ghost instances running versions 5.3.0 through 6.57.x in private mode with comments enabled can read comments that private mode should restrict, bypassing the site's privacy settings. This is a low-impact confidentiality flaw limited to comment text disclosure-no write access, account takeover, or integrity impact-and it requires the configuration of private mode plus comments being enabled. Vendor-released patch: 6.58.0; no public exploit identified at time of analysis.
Authenticated Ghost site members on versions 5.3.0 through 6.61.x can retrieve the post excerpts (preview snippets) of gated, members-only or premium posts they are not entitled to read, because the excerpts endpoint fails to enforce the same access checks applied to full post content. The exposure is limited to excerpt text rather than complete article bodies, so the practical impact is partial content disclosure, and sites that publish no gated or paywalled content are unaffected. Any registered member account - including a free-tier member with no subscription - is sufficient to trigger the issue; no public exploit code has been identified at time of analysis, and no confirmed active exploitation (CISA KEV) has been reported.
Unbounded query-string parsing in Tornado before 6.5.9 lets unauthenticated remote attackers stall the event loop of affected servers by sending GET requests whose query strings carry thousands of short parameters. Because HTTPServerRequest.__init__ parses the query string synchronously inside Tornado's single-threaded IOLoop with no field-count cap, a burst of such requests degrades response times for every client sharing that loop rather than triggering a clean crash - impact is availability degradation rated Low (assessed CVSS:3.1 AV:N/AC:L/PR:N/UI:N/C:N/I:N/A:L; vendor CVSS 4.0 base 6.9 with VA:L), and sustained concurrent high-field requests are needed to meaningfully starve other connections. A vendor-released patch exists in Tornado 6.5.9 (upstream PR 3719 / commit 03945136ea9746eccf61caf88edae39642e59c93), and no public exploit code has been identified at time of analysis.
Stored DOM cross-site scripting in the n8n workflow automation platform affects all releases before 1.123.80 on the 1.x line, 2.0.0 up to but not including 2.39.6, and 2.40.0 up to but not including 2.40.1. An authenticated user with workflow-authoring privileges can store a malicious script URL inside a node's Resource Locator parameter dropdown; when another user opens that node's dropdown and clicks the external-link icon, the injected JavaScript executes in the n8n editor origin. Because the payload is embedded in the workflow definition, it survives workflow imports and shares, allowing one poisoned workflow to reach multiple victims over time - though the assessed CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N) makes clear that a second, distinct user must actively click the link, so passive viewing is insufficient and single-user instances face minimal exposure. No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied; the vendor has released patches, so this is a conditional mid-tier priority rather than an emergency.
Unauthenticated attackers can forge webhook requests to n8n instances that run the Webflow Trigger node, because the handler fails to validate the x-webflow-signature HMAC (CWE-347), letting workflows be triggered with attacker-controlled payloads. Affected releases are all versions before 1.123.80, the 2.x line from 2.0.0 up to but not including 2.39.6, and 2.40.0 up to but not including 2.40.1, with fixes released as 1.123.80, 2.39.6, and 2.40.1. Impact is integrity-only and bounded by whatever the triggered workflow does downstream; no public exploit code has been identified at time of analysis, the flaw is not confirmed actively exploited (not in CISA KEV), and exploitation requires an internet-reachable Webflow Trigger webhook endpoint.
Improper authorization in Immich's Shared Link Preview Handler (server/src/utils/access.ts, function checkSharedLinkAccess) affects Immich releases up to and including 2.7.5 and allows a remote, unauthenticated attacker who knows or obtains a shared link's URL/token to bypass that link's password protection and view media that should require a password. The assessed impact is confined to confidentiality (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N; CWE-285), with no integrity or availability effect, and instances that do not use password-protected shared links are unaffected. No public exploit code or confirmed active exploitation was identified at time of analysis (the CVE is not listed in CISA KEV), and the originating GitHub report (immich-app/immich issue 29599) was closed as a duplicate, so a vendor-confirmed fix version should be verified directly with the project.
Server-side request forgery in decolua 9Router (versions up to and including 0.5.55) lets a remote attacker steer the server's outbound HTTP requests by controlling the provider_options.baseUrl argument handled by the Search Endpoint and its fetch path in src/shared/utils/ssrfGuard.js, potentially reaching loopback services, internal networks, or cloud metadata endpoints such as 169.254.169.254. The vulnerable code is a pre-patch guard that can be defeated through several documented bypass classes (trailing-dot FQDNs like 'localhost.', IPv4-mapped IPv6 addresses in hex form such as '::ffff:7f00:1', wildcard-DNS hostnames that resolve to private addresses, and public URLs that 30x-redirect to internal targets). Per the vendor vector the flaw is unauthenticated (PR:N) and exploitable in default configurations; no public exploit code was identified at time of analysis and CISA KEV does not list this issue, while the upstream project has published a fixing pull request (PR #3723) referencing the reporter's bypass analysis in issue #3714.
Command injection in Red Hat Satellite's Hammer CLI (rubygem-hammer_cli) allows a local authenticated user to run arbitrary shell commands by controlling the $EDITOR environment variable, which the application interpolates into a single-string Ruby system() call that is then interpreted by /bin/sh. The flaw affects Red Hat Satellite 6 and Satellite 6.19 for RHEL 9, and exploitation requires an attacker to already hold a valid local account, be able to set $EDITOR, and trigger a CLI operation that launches an external editor (such as editing a resource), meaning remote or unauthenticated exploitation is not possible. Public exploit code and confirmed active exploitation are not indicated in the available intelligence, and Red Hat has published an erratum (RHSA-2026:74503) to address the issue.
Authenticated path traversal in the web management interface of Fujifilm Apeos multifunction devices and printers (including Apeos C4571 firmware 1.1.3 and earlier and Apeos C3567 1.1.3, plus other listed models) lets an attacker who already holds high privileges on the device's admin interface read arbitrary files from the appliance by submitting a crafted request with traversal sequences in an externally supplied parameter. The exposure is access-gated rather than internet-facing: the assessed vector (CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N) requires adjacent-network reachability to the management UI and administrative credentials, and the impact is confined to confidentiality (file/data disclosure) with no integrity or availability effect. There is no confirmed active exploitation (the CVE is not in CISA KEV) and no public exploit code identified at time of analysis, so the practical risk is moderate and concentrated on organizations whose printer web consoles are reachable from untrusted or flat internal networks.
Privilege escalation in JetBrains YouTrack before 2026.2.19422 allows an authenticated attacker with pre-existing elevated privileges (CVSS PR:H) to abuse user-group membership changes and gain higher privileges, though success requires a specific group-configuration state (AC:H). The flaw is network-reachable (AV:N) and needs no user interaction (UI:N), but the high privilege and configuration prerequisites sharply narrow realistic risk to insiders or holders of a compromised privileged account; no public exploit identified at time of analysis. Vendor CVSS 6.6 Medium and CWE-266 (Incorrect Privilege Assignment) match the assessed vector and the need to manipulate group membership under constrained conditions.
The Aruba Migration Tool plugin for WordPress, versions up to and including 1.0.4, is affected by a broken access control vulnerability (CWE-862) that enables an authenticated attacker with subscriber-level permissions to access sensitive data, resulting in a high confidentiality impact. With a CVSS score of 6.5, exploitation requires a valid low-privilege account and no user interaction; no public exploit has been identified at time of analysis. The risk is moderate but constrained by the authentication prerequisite and the plugin's niche deployment.
Authenticated WordPress users at subscriber level or above can exploit an insecure direct object reference in the Simply Schedule Appointments plugin (all versions up to and including 1.6.12.31) through the 'complete_group' parameter to harvest every co-booker's private per-appointment id_token (surfaced as public_token) along with their name and email address, then reuse each leaked token to read, overwrite arbitrary appointment metadata, or cancel the victim's booking via the same REST controller. Exploitation is access-gated rather than open to anonymous scans: the attacker must already hold a valid id_token for at least one appointment inside the targeted group booking, and the exposure is confined to co-bookers of that shared booking, so real-world risk scales with how heavily a site relies on group bookings. No public exploit code and no CISA KEV listing were identified at time of analysis, though an independent assessment rates integrity and availability impact higher than the vendor vector (CVSS 3.1 C:H/I:H/A:L versus the published C:H/I:N/A:N), reflecting the token-reuse tampering path.
Extracting a specially crafted Transport Neutral Encapsulation Format (TNEF, "winmail.dat") file that contains multiple message bodies can crash the tnef utility through a use-after-free and double-free in its memory handling. The flaw is remotely reachable without credentials (PR:N), but exploitation depends on the malicious file actually reaching a tnef parsing step, which requires user interaction such as opening an email attachment or an automated mail gateway decoding it (UI:R). Impact is confined to availability - our independent assessment rates this as a modest-severity denial of service (A:L) rather than the vendor's higher 6.5 score, and no public exploit code and no confirmed active exploitation were identified at time of analysis.
Heap-based buffer overflow in the tnef command-line TNEF (winmail.dat) extractor allows a crafted TNEF file with a large number of colliding attachment filenames to overflow the numeric-suffix counter used by find_free_number(), producing a crash and denial of service; arbitrary code execution is theoretically possible but unproven. The bug only triggers under a non-default configuration in which numbered backups are enabled while file overwriting is disabled, and it requires the victim to actually run tnef against the malicious file (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L, base 3.1), so no public exploit code has been identified at time of analysis and real-world risk is low despite the RCE and memory-corruption tags attached to this report. Impact is limited to availability; there is no confidentiality or integrity impact in the assessed vector.
An authenticated low-privileged user can inject SQL through the Katello Registry Proxy in Red Hat Satellite 6 by placing a crafted label in the request path, allowing them to read arbitrary data from the Satellite database. The vulnerable code paths (check_blob_push_org_label and get_matching_products_from_org) interpolate request-supplied labels straight into raw SQL, and the only prerequisite is an account holding the create_personal_access_tokens permission - even a heavily restricted account with no Organization or Location assigned, which makes the effective privilege bar unusually low. Impact is limited to confidentiality (CVSS 6.5, C:H/I:N/A:N); no public exploit code has been identified at time of analysis, and Red Hat has published erratum RHSA-2026:74503 to address the flaw. This is a genuine but moderate-priority issue, not a critical drop-everything vulnerability.
Improper access control in InfiniFlow RAGFlow 0.24.0 lets any authenticated user read documents they do not own by calling the /v1/document/get/<doc_id> REST endpoint, because the handler fails to verify that the requested document belongs to the caller. Exploitation requires a valid account on the target instance (CVSS PR:L - this is not an unauthenticated flaw) and network reachability to the API, so real-world impact concentrates on multi-tenant or shared deployments where documents belonging to other users are stored; single-user or isolated installs expose little. No public exploit identified at time of analysis, EPSS is low at 0.15% (4th percentile), and the issue is not listed in CISA KEV.
Improper access control in RAGFlow 0.25.3's resume functionality (api/apps/connector_app.py) allows an authenticated low-privilege user to perform unauthorized cross-session or privilege-crossing operations, compromising data integrity. The issue is network-reachable and low-complexity but requires a valid RAGFlow account (CVSS PR:L), and the realized impact depends on which connector entry is exposed and reachable. No public exploit identified at time of analysis, EPSS is 0.14% (3rd percentile), and the limiting authentication prerequisite makes this a moderate-severity, low-priority issue in practical terms.
Authenticated low-privilege users can alter metadata settings of knowledge bases they do not own in RAGFlow 0.24.0 and earlier due to missing authorization in the update_metadata_setting function (api/apps/kb_app.py). This remote integrity-only flaw requires network access and valid credentials (CVSS 6.5), with no confidentiality or availability impact, and publicly available exploit code exists per SSVC (Exploitation: poc) though it is not automatable. EPSS is 0.14% (3rd percentile), and no active exploitation (CISA KEV) is reported.
Incorrect access control in infiniflow RAGFlow 0.24.0 allows a caller reaching the run_mindmap code path to supply an object or tenant identifier they do not own and have the resulting data-access operation proceed, because that operation is not bound to any owner, tenant, workspace, or membership check. The result is cross-tenant information disclosure and limited data manipulation in multi-tenant or shared RAGFlow deployments where isolation between tenants is expected; NVD rates it 6.5 with an unauthenticated vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N), while our assessment treats it as requiring at least a valid session/tenant context (PR:L), which materially lowers exposure for single-tenant or network-isolated instances. EPSS is 0.14% (3rd percentile) and no public exploit code or confirmed active exploitation has been identified at time of analysis, so this is a moderate-priority access-control defect rather than an emergency.
Untrusted code execution in the NetBox devicetype-library CI pipeline lets any contributor who can open a pull request run arbitrary commands on the repository's GitHub Actions runner before a maintainer ever reviews the change. Because validation.yml triggers on the pull_request event and consumes three PR-editable files (requirements.txt for pip install, the pre-commit hook configs, and .gitmodules for submodule checkout), an unauthenticated remote attacker with no repository write access can inject code that executes automatically with no user interaction; impact is capped at low confidentiality and integrity loss because fork PRs run with a read-only token and no secrets. Only versions prior to commit f41fc1e are affected, and no public exploit code identified at time of analysis.
Information disclosure and denial of service in Keycloak's X.509 client certificate authenticator occur when CRL Distribution Point checking is enabled and an unauthenticated remote attacker submits a crafted client certificate. The server fails to properly validate file paths from the certificate, allowing limited local file reads and extreme memory consumption that can crash the system; exploitation requires the non-default combination of certificate-based client authentication and CRL checking, and no public exploit was identified at time of analysis.
Missing authorization checks in the WordPress plugin Review Schema 3.1.0 let unauthenticated, remote attackers invoke plugin functionality that should require elevated privileges, tampering with or disrupting the site's review and structured-data (schema) content. The issue is network-reachable, low-complexity, and requires no victim interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L, score 6.5), but impact is bounded: no confidential data exposure (C:N) and only low-level integrity and availability effects (I:L/A:L), so a full site takeover is not possible. There is no public exploit identified at time of analysis and the CVE is not in CISA KEV; independent assessment rates this as a moderate, not emergency, issue with the primary uncertainty being which specific endpoint or action lacks the check, since the Patchstack advisory does not name it.
Unauthenticated attackers can exploit an insecure direct object reference (IDOR) in WPFunnels 3.13.1 and earlier to read or alter funnel-related objects they do not own. The flaw has a CVSS base score of 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N), reflecting remote, unauthenticated exploitation with low confidentiality and integrity impact but no availability impact. No public exploit code has been identified at time of analysis, and CISA KEV does not list this CVE; the risk is assessed as moderate, pragmatic risk, with impact limited to the exposed funnel objects.
Unauthenticated remote attackers can tamper with or disrupt booking and reservation records on WordPress sites running the Bus Ticket Booking with Seat Reservation plugin in versions up to and including 5.9.3, by manipulating object identifiers passed to plugin endpoints (CWE-639 IDOR). The assessed CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L, base 6.5) confirms network-reachable, unauthenticated exploitation with no confidentiality loss - only partial integrity and availability impact on booking data - so this is a real-but-moderate issue rather than a site-takeover or data-exfiltration risk. No public exploit identified at time of analysis, and no CISA KEV listing; exploitation is limited in practice by the plugin's niche deployment footprint and the need to enumerate or guess valid object identifiers, and no vendor-released patch was identified in the available data.
Heap-based out-of-bounds write in the boks_ksllogsd logging daemon of Fortra BoKS Manager / BoKS Server allows an authenticated KSL client to corrupt memory by placing an oversized but OpenSSL-recognized digest name in the MD field of a KSL start message. The daemon validates that OpenSSL recognizes the supplied digest name but does not confirm that the name fits the fixed 16-byte checksum context field before copying, so an over-long value is written past the end of the heap allocation (CWE-787; CVSS 3.1 6.5, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). Because the attacker must already hold KSL client credentials and the written content is constrained to valid digest-name strings, the practical result is a crash or memory corruption of the logging service rather than reliable remote code execution; no public exploit code and no confirmed active exploitation were identified at time of analysis, so this is a moderate-priority availability risk pending a vendor fix.
Stored cross-site scripting in the Essential Addons for Elementor WordPress plugin (all versions through 6.8.4) allows an authenticated user holding at least contributor- or editor-level privileges to persist malicious JavaScript through plugin widget content, which then executes in the browser of any visitor or administrator who views the affected page (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, base 6.5, per Patchstack). Because the injected script runs in the context of the victim's session and the vulnerability scope changes (S:C), an attacker can potentially act with the victim's privileges against the site, though exploitation requires both a valid low-privilege account and a victim who subsequently loads the poisoned content. No public exploit code was identified at time of analysis and the flaw is not listed in CISA KEV, so this is a moderate-priority issue rather than an actively exploited one, and the plugin's very large install base makes it worth prioritizing despite the gating prerequisites.
Stored cross-site scripting in the Wpmet Metform WordPress plugin (versions through 4.3.0) lets a low-privilege authenticated user, such as a contributor, plant a malicious script inside form fields or plugin settings; the payload is then stored and executes in the browser of any higher-privileged user (typically an administrator or editor) who views the affected page. The base CVSS score is 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), and the practical risk is LOW-to-MEDIUM because exploitation is gated by two prerequisites: an authenticated account with at least contributor-level access and a victim who subsequently opens the page where the stored payload renders. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, so this is a latent persistence-and-privilege-abuse vector rather than an actively exploited campaign.
Stored cross-site scripting (XSS) in ElementsKit Lite (a WordPress plugin) versions up to 4.0.6 allows an authenticated attacker with contributor or author privileges to inject malicious JavaScript into a page via a vulnerable widget, which then executes in the browser of any user who views the compromised page. The vulnerability requires a separate user to trigger the payload (UI:R) and is limited to the Lite edition; it is rated moderate severity (CVSS 6.5) with no public exploit identified at time of analysis. No evidence of elevated real-world risk or active exploitation (CISA KEV) is present.
Stored cross-site scripting (XSS) in ElementsKit Lite (ElementsKit Elementor addons Lite) versions up to and including 4.0.6 allows an authenticated attacker with contributor-level privileges to inject malicious scripts into Elementor widget content, which then execute in the browser of any user viewing the affected page. The vendor (Patchstack) rates this as medium severity with a CVSS 3.1 score of 6.5, but our assessment confirms it requires user interaction and results in partial confidentiality and integrity loss without availability impact. No public exploit code or active exploitation has been identified at time of analysis.
Stored cross-site scripting (XSS) in the FluentForm WordPress plugin (versions through 6.2.14) allows authenticated attackers with low privileges to inject malicious scripts into form fields, which execute when other users view the affected page. Exploitation requires victim interaction and a low-privileged WordPress account, limiting the attack to authenticated scenarios. No public exploit code has been identified, and the risk is considered moderate due to these prerequisites.
Denial of service in JetBrains YouTrack instances running versions before 2026.2.19422 lets an authenticated user who can upload attachments hang or crash the server by submitting a crafted PSD file that drives the image-processing path into an infinite loop. The attack is network-reachable and needs no victim interaction, but it requires a valid low-privileged account (PR:L), so it is not exploitable by fully anonymous visitors unless the instance permits self-registration or guest attachment uploads; impact is confined to availability, with no confidentiality or integrity loss. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
Authorization bypass in JetBrains YouTrack before 2026.2.19422 allows an authenticated user with only low privileges to read the activity history of restricted issues they are not authorized to view. The root cause is an insecure direct object reference in the issue activities API, where the endpoint resolves a caller-supplied issue identifier without verifying that the caller holds read access to that issue. Exploitation requires valid low-privileged credentials but no user interaction or non-default configuration, and the impact is confidentiality-only (CVSS 3.1 base 6.5, C:H/I:N/A:N); no public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released a fix in 2026.2.19422.
Unauthenticated attackers can overwrite the CRM integration endpoint and stored credentials of any WordPress site running WP Fusion Lite versions from 3.37.14 up to but not including 3.48.0, redirecting the plugin's outbound data sync to a server they control. Because the vulnerable settings handler runs on the WordPress admin initialization hook without any capability or nonce check, a crafted request needing no login, no user interaction, and no special configuration is sufficient (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, rated 6.5). The practical payoff is ongoing exfiltration of synced user records to the attacker's host, so sites with substantial synced customer data face the greatest exposure; no confirmed active exploitation or public exploit code was identified at time of analysis, and a vendor patch is available.
HTML injection in HCL Digital Experience portals allows unauthenticated remote attackers to place attacker-controlled markup into portal pages, spoofing content that appears to be served from the trusted portal domain; exploitation requires the victim to load the crafted page or link (UI:R), and the assessed impact is integrity-only with no confidentiality or availability loss. No public exploit code or confirmed active exploitation was identified at the time of analysis, and signals are consistent in pointing to a moderate, non-urgent issue. A vendor fix is available in HCL Digital Experience 9.5 CF238 or later.
Stored cross-site scripting in the Essential Blocks - Page Builder for Gutenberg Blocks & Patterns WordPress plugin (versions up to and including 6.4.5) allows authenticated attackers with Contributor-level access or higher to inject arbitrary JavaScript that executes when a victim views the affected page. The flaw sits in the Google Map block's 'marker' attribute: marker title/content values are stored as JSON and later decoded and concatenated directly into raw HTML by the frontend InfoWindow builder, so it is insufficient input sanitization plus missing output escaping rather than a logic error. It is network-reachable at low complexity with a scope change (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, 6.4 Medium); the practical barrier is the Contributor authentication requirement, and no public exploit code was identified at time of analysis. Sites that allow open registration or grant Contributor roles to low-trust users should treat this as a priority upgrade.
Signature verification failure in the Apache APISIX saml-auth plugin (versions 3.17.0 through 3.18.0) allows an attacker to forge SAML assertions and impersonate arbitrary users on every route protected by that plugin, and the plugin's DEFAULT configuration is vulnerable, so no additional misconfiguration or attacker-controlled precondition is needed. The vendor's CVSS 4.0 vector scores the issue 6.4 with PR:L and no direct CIA impact on the vulnerable component (only SC:H/SI:H on subsequent systems), which understates the practical effect described by the vendor itself as 'any unauthenticated attacker could impersonate any user'; our independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N, and the PR:N versus PR:L discrepancy between the description and the vendor vector should be verified. No public exploit code and no confirmed active exploitation were identified at time of analysis; exposure is limited to the two-release version window and to deployments that actually enable saml-auth on at least one route.