Remote denial of service in Osmocom osmo-bsc 1.0.1 through 1.14.1: a heap-based buffer overflow in ipaccess_proxy_read_msg() is triggered when a crafted IPA frame carries an attacker-controlled length value that is used without adequate validation against the actual buffer size. The issue is remotely reachable and requires no authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N) from any host able to talk to an osmo-bsc instance with the ipaccess proxy component deployed, and the assessed impact is availability-only (C:N/I:N/A:H), meaning a successful trigger corrupts heap memory and crashes the process. There is no public exploit identified at time of analysis and EPSS is a low 0.14% (4th percentile), consistent with the deployment reality that BSC signaling paths such as the IPA/A-bis proxy are normally confined to segmented, non-public operator networks.
Denial of service in libheif 1.23.1 and earlier: decoding a crafted HEIF/AVIF file whose derived-image reference graph (grid, iovl, or iden items) points many branches at a common base image causes the decoder to re-decode that base image repeatedly, exhausting CPU and, depending on tile handling, memory. The flaw is unauthenticated and remotely triggerable (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) against any service that automatically decodes attacker-supplied files - upload pipelines, thumbnailers, and transcoders are the highest-value targets - while desktop viewers require the user to open the file, effectively adding user interaction. Impact is availability-only (no code execution, disclosure, or modification), and no public exploit code was identified at time of analysis, though the weaponized input is a small, trivially constructed file. Vendor-released patch: 1.23.2.
Denial of service in libheif 1.19.0 through 1.23.1 allows unauthenticated remote attackers to exhaust process memory and terminate the application by supplying a crafted HEIF or AVIF file whose compressed mime metadata or unci image data is decompressed without an effective output bound. According to the CVSS vector (AV:N/AC:L/PR:N/UI:N) no privileges or interaction are required, so automated server-side image ingestion pipelines that parse untrusted HEIF/AVIF content are the most exposed; interactive desktop viewers still require a user to open the malicious file. Impact is availability-only (crash/OOM, no code execution or data disclosure), no public exploit code has been identified at time of analysis, and the issue is fixed in libheif 1.23.2.
Heap corruption in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated remote user with a valid MQ session to crash the queue manager via a crafted MQINQ inquire request, and the same integer-overflow defect in request validation creates the potential for privilege escalation under specific memory-layout conditions. The issue is rated 7.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning credentials are required and the overflow is non-trivial to trigger reliably; there is no public exploit code and no public exploit identified at time of analysis, and IBM has published a vendor fix. Risk is further bounded because exploitation is confined to the specialized HPE NonStop platform running the affected 8.1.0.x maintenance levels, so deployments that have applied the patched level are not exposed.
Remote unauthenticated denial of service in µD3TN v0.15.0: an integer overflow (CWE-190) in the TCPCLv3 handshake processing path leads to a heap overflow that, per the reported analysis, reliably crashes the daemon. Any host able to reach a µD3TN node's TCPCLv3 listener can trigger it without credentials or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), but the impact is confined to availability - no confidentiality or integrity loss and no code execution is indicated. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV); exploitation also requires the deployment to actually run TCPCLv3 rather than another convergence layer.
Unauthenticated SQL injection in the Location Manager plugin for WordPress allows remote attackers to read arbitrary data from the underlying database. Every installation running version 2.3.38 or earlier is exposed, because the publicly reachable REST routes geodir/v2/locations/cities, /regions, /countries and /neighbourhoods pass the 'latitude' and 'longitude' parameters into SQL through the get_locations() and get_neighbourhoods() functions without escaping or query preparation whenever orderby=lat_lon is supplied. No authentication, user interaction, or non-default configuration is needed, giving the issue a CVSS 3.1 base score of 7.5 with high confidentiality impact; no public exploit code has been identified at time of analysis and there is no evidence of active exploitation.
Unauthenticated directory traversal in the Printcart Web to Print Product Designer for WooCommerce WordPress plugin (all versions up to and including 2.8.5) allows remote attackers to read arbitrary files on the underlying server by manipulating the 'mockups' parameter, exposing configuration files, wp-config.php-style secrets, and other sensitive data. The traversal is gated only by a 'nbdesigner-get-data' nonce, but that nonce is freely minted to anonymous visitors by the plugin's own nbd_check_use_logged_in nopriv AJAX endpoint, and the check disappears entirely if the NBDESIGNER_ENABLE_NONCE constant is disabled, so authentication requirements are effectively nil (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Impact is limited to confidentiality - integrity and availability are unaffected, and the depth of file access is bounded by the web server user's filesystem permissions. No CISA KEV listing and no public exploit code identified at time of analysis, though the low attack complexity and the absence of a confirmed patched release make exposed storefronts a high-priority remediation target.
An authentication bypass in ManageEngine DataSecurity Plus deployments running builds earlier than 6310 allows unenrolled agents to send requests to the server's agent communication interface without completing enrollment or authentication, potentially exposing or altering the data that interface handles. The vulnerability is remotely reachable and requires no user interaction and no prior authentication (CVSS vector PR:N/UI:N), though the vendor's AC:H rating and our own lower independent assessment (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) indicate the practical impact is modest and gated by preconditions such as knowledge of the proprietary agent request format. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so active exploitation is unconfirmed; the risk is hard to pin down because the vendor advisory is the only source and the description is terse.
OS command injection in IBM Guardium Data Protection 12.2 allows a privileged authenticated attacker to execute arbitrary commands with root-level privileges through the Universal Connector plugin upload feature. The flaw carries a CVSS 3.1 base score of 7.2 (HIGH) under the vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, reflecting network reachability and full confidentiality, integrity and availability impact, though exploitation is gated behind a high-privilege account. No public exploit code is identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
Command injection in IBM Guardium Data Protection 12.2 lets an authenticated, highly privileged administrator execute arbitrary shell commands with root privileges by supplying a crafted filename to the 'import remotelog_config file' CLI command. Successful exploitation compromises the confidentiality, integrity, and availability of the appliance, and no public exploit has been identified at time of analysis. IBM has released a fix via its support advisory, so exposure is limited to unpatched 12.2 deployments whose administrative CLI access is reachable by an attacker.
Heap-based out-of-bounds write in libheif prior to 1.23.2 lets an attacker who can supply an independently constructed tile image to the uncompressed-codec tiled encoding path corrupt memory past the heap output buffer. The flaw is only reachable when the library is built with WITH_UNCOMPRESSED_CODEC enabled and the host application uses the tiled writing API (heif_context_add_image_tile), which makes the encoder encode rather than decode attacker-influenced data; because that path is an encoder-side, build-optional feature requiring a specific application design, the vendor's AC:H rating is appropriate. CVSS is 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H) with high integrity and availability impact but no confidentiality impact, and no public exploit code or active exploitation has been identified at time of analysis; a vendor fix is available in 1.23.2.
Cross-origin data exposure in RESTEasy's CorsFilter (CVSS 7.4) occurs when a deployment is configured with allowedOrigins set to the wildcard '*' together with allowCredentials=true, causing the filter to reflect the caller's Origin header back in Access-Control-Allow-Origin alongside Access-Control-Allow-Credentials: true. Because that configuration defeats the browser's built-in guard against combining wildcard origins with credentials, an attacker who lures an already-authenticated user (UI:R) to an attacker-controlled page can issue credentialed cross-origin requests and read that user's authenticated API responses - a confidentiality-only impact (C:H/I:N/A:N), with no integrity or availability effect. The prerequisite wildcard-plus-credentials CORS configuration is a non-default operator choice, and analysis identifies no public exploit identified at time of analysis.
Command injection in the 'create csr wildcard' CLI command of IBM Guardium Data Protection 12.2 allows an authenticated privileged CLI user to embed shell metacharacters in the 'alias' input, breaking out of the restricted CLI and executing arbitrary commands with root privileges on the appliance. The CVSS v3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2 High) confirms this is not an unauthenticated remote compromise: the attacker must already hold privileged CLI credentials and CLI access, typically over SSH, making this fundamentally a restricted-shell-to-root privilege escalation rather than an external initial-access vector. Impact is total for confidentiality, integrity, and availability of the appliance given the root-level execution context; no public exploit code was identified at time of analysis, and CISA KEV does not list this CVE as actively exploited.
Improper authorization in IBM Guardium Data Protection 12.2 lets a remote attacker who already holds a valid low-privilege account reach functions or data that the platform's access controls are supposed to withhold, effectively bypassing security restrictions. The defect maps to CWE-285 (Improper Authorization); IBM rates it 7.4 while our independent assessment scores it 7.4-class only with scope unchanged, yielding a moderate 6.3-level risk because confidentiality, integrity, and availability impacts are all low. Authentication is required (CVSS vector PR:L), no user interaction is needed, and no public exploit code has been identified at time of analysis. A vendor patch is available via IBM support node 7288035, so remediation is straightforward for organizations that can schedule an upgrade.
TLS server identity verification bypass in PJSIP 2.17 and earlier can let an on-path attacker impersonate a SIP server and capture REGISTER credentials. The OpenSSL and GnuTLS backends in pjlib/src/pj/ssl_sock_ossl.c and pjlib/src/pj/ssl_sock_gtls.c copy DNS SubjectAltName values using string functions that recompute length and therefore truncate at an embedded NUL byte, so when server verification is enabled through --tls-verify-server, a certificate whose DNS SAN is the target hostname prefix followed by an embedded NUL and an attacker-controlled suffix is accepted for the prefix hostname. No public exploit code or confirmed active exploitation (no CISA KEV listing) was identified at time of analysis, and exploitation remains gated on the attacker holding such a certificate from a trusted issuer - compliant public CAs reject embedded-NUL SANs - plus an on-path interception position, which is what drives the high attack complexity even though the vector is network-reachable and unauthenticated.
Arbitrary code execution is possible on IBM Guardium Data Protection 12.2 when a remote attacker who already holds high-privilege credentials abuses a file-handling feature that fails to constrain a user-supplied pathname to its intended restricted directory (CWE-22). The requirement for HIGH privileges (PR:H) on the management interface is the primary limiting factor, restricting realistic exploitation to trusted administrative accounts on an appliance that is normally deployed on internal or segmented networks, though no user interaction is required (UI:N). The vendor has published a fix advisory, and no public exploit identified at time of analysis (no CISA KEV listing and no published proof-of-concept in the supplied intelligence).
Local privilege escalation in uutils coreutils before 0.10.0: the `install` utility applies a requested setuid/setgid mode (for example -m 4755 or -m 2755) to the destination before performing the requested ownership change, so if the underlying chown(2) call fails the file is left behind as a setuid/setgid executable owned by the privileged invoker who ran the command. Affected are uutils coreutils releases from 0.0.18 up to but not including 0.10.0 (CPE cpe:2.3:a:uutils:coreutils:*:*:*:*:*:*:*:*) on capability-restricted hosts where chown can actually fail, such as environments with euid != 0 or a dropped CAP_CHOWN; a local, authenticated low-privileged operator who can invoke `install` can then execute the leftover binary with elevated privileges. There is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was provided; the honest risk picture is a genuine but modest-priority local flaw (CVSS:4.0 7.3 AV:L/AC:H/AT:P/PR:L, our independent CVSS:3.1 assessment AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), not a mass-exploitable remote issue, because on unrestricted systems where chown succeeds the setuid bits are correctly cleared and re-applied.
Missing object-level authorization in the OpenStack Blazar V2 lease API allows any authenticated user to modify or delete leases belonging to other users and projects if they know the target lease UUID. The defect affects Blazar releases before 17.0.1 and arises because the oslo.policy authorize() wrapper resolves the wrong request parameter, so the ownership check silently degrades into comparing the requester against their own project_id and user_id and therefore always passes. No public exploit code has been identified at time of analysis, and exploitation requires a valid cloud credential plus a deployment that actually runs the optional reservation service, but the integrity and availability impact on lease objects is high because reservations underpin the scheduled resource allocations of other tenants.
SQL injection in SiYuan versions before 3.8.3 allows unauthenticated remote readers, in deployments running publish/sharing mode, to execute arbitrary SQL against the read-write database through the getGraph endpoint and exfiltrate private data across notebooks. The CWE-89 flaw arises in graph.go's query2Stmt function, where tag values are concatenated raw into SQL string literals without escaping single quotes, and it can be reached via inline HTML span tags. The vendor released a fix in 3.8.3, and no public exploit code or CISA KEV confirmed active exploitation was identified at time of analysis; the CVSS 4.0 base score is 7.2 (High) with high confidentiality impact.
Stored cross-site scripting in the Popup Maker WordPress plugin (all versions up to and including 1.24.0) allows unauthenticated visitors to inject arbitrary web scripts through the values[Name] field of an optin, newsletter, or subscriber form, with the payload stored server-side and later rendered in the WordPress admin. Execution is not automatic: it is gated on a logged-in administrator opening the Popup Maker Subscribers list table and clicking a contextual help-tab anchor, which routes the attacker-controlled value into the jQuery(link.attr('href')) DOM sink in wp-admin/js/common.js. The vendor/Wordfence CVSS 3.1 score is 7.2 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N), though the required privileged admin interaction is better reflected as UI:R; no public exploit code has been identified and the CVE is not listed in CISA KEV at time of analysis.
Stored cross-site scripting in the Jeg Elementor Kit WordPress plugin (all versions up to and including 3.2.16) allows unauthenticated attackers to inject arbitrary JavaScript into comment content, which then executes in the browser of any user who later views the affected page. The attack is conditional rather than universal: the targeted post must also render a legitimate Jeg Kit Countdown widget, which causes the plugin's countdown frontend script to be enqueued and to initialize on any matching DOM element - including forged Countdown widget markup smuggled into a published comment - and comments must be enabled and the malicious comment published (sites that hold first-time comments for administrator moderation break the unauthenticated path). The vendor rates this CVSS 3.1 7.2 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N), while our independent assessment scores it AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N given the widget dependency, moderation gate, and victim-visit requirement; impact is confined to client-side script execution with no availability impact, and no public exploit code has been identified at time of analysis.
Stored cross-site scripting in the Complianz GDPR/CCPA Cookie Consent Banner WordPress plugin, affecting all versions up to and including 7.5.4, allows unauthenticated attackers to embed arbitrary JavaScript in comment content that later executes in the browser of anyone viewing the approved comment page. Realistic exploitation is gated by three conditions that must all hold: a site administrator must approve the attacker's submitted comment, the Elementor page-builder plugin must be installed and active, and Complianz must be configured with the Twitter or Facebook cookie/script blocker enabled so comment content is routed through the vulnerable cookie-blocker regex path; independent assessment rates the vector as AC:H/UI:R despite PR:N, since exploitation depends on a moderator action and a specific third-party configuration. No public exploit code was identified at time of analysis, and there is no confirmed active exploitation (no CISA KEV listing); a vendor patch is available in version 7.5.5.
Privilege escalation in the Booking Calendar plugin for WordPress (wpdevelop, cpe:2.3:a:wpdevelop:booking_calendar) in all versions up to and including 11.8.2 lets an authenticated user holding Editor-level capabilities or higher promote themselves to Administrator and seize control of the site. The wpbc_ajax_option_save AJAX action writes an attacker-supplied option name straight into update_option() because the handler's per-option safeguards only cover names explicitly registered via register_option_policy(), so unregistered options - including core WordPress settings - receive an empty policy and skip every can_save, force_mode, and allowed_keys check; an attacker can therefore set default_role=administrator and users_can_register=1 and then register a new administrative account. The embedded nonce check offers no real barrier since both the nonce value and nonce action are attacker-controlled POST parameters and a valid nonce can be fetched from admin-ajax.php?action=rest-nonce; exploitation requires an authenticated Editor+ account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H per our assessment), no public exploit code has been identified at time of analysis.
An incomplete deny-list in ArcadeDB's polyglot script sandbox allows an authenticated user who holds the UPDATE_SCHEMA privilege (enough to create or alter a JavaScript trigger, but explicitly not server-admin rights) to reach the inherited static ResourceBundle.getBundle(String) method and read .properties resources from the application classpath, disclosing packaged configuration such as database credentials and API keys. Affects ArcadeDB (Maven com.arcadedb:arcadedb-engine) through 26.8.1 and is graded 7.1 (CVSS 4.0 PR:L, confidentiality-only; independently assessed as CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N). No public exploit code was identified at time of analysis, and the vendor advisory explicitly limits impact to classpath resource disclosure - not arbitrary host filesystem read and not remote code execution - with the fix released in 26.9.1.
Authenticated users of ClipBucket v5 through 5.5.3 can extract arbitrary data - including credential hashes - from the underlying database by abusing a time-based blind SQL injection in the back-office bulk photo-deletion handler. The root cause is a parameter-type bypass: submitting the check_photo parameter as an array causes its elements to slip past the clean_requests() sanitization in ClipBucket.class.php and reach photo_exists() in photos.class.php, where non-numeric values are concatenated directly into a SQL query. Exploitation requires a valid ClipBucket account able to reach manage_photos.php (CVSS vector shows PR:L, unauthenticated access is not sufficient), the injection is blind and time-based so extraction is slow and iterative, and no public exploit code has been identified at time of analysis; EPSS scoring was not provided in the source data. This is a moderate-risk, authentication-gated data-disclosure flaw rather than a critical exposure.
Authenticated users of LubeLogger versions prior to 1.6.8 can copy other users' vehicle maintenance records into a vehicle they control, because the DuplicateRecordsToOtherVehicles endpoint authorizes the destination vehicle but never checks edit permission on the source vehicle. This exposes the contents of service, collision, upgrade, fuel, tax, supply, note, odometer, reminder, plan, inspection and equipment records, including attachment paths, and creates persistent attacker-held copies. The flaw is rated CVSS 3.1 7.1 High (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N) and only matters on multi-user or household-shared instances; there is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis. The vendor-released patch: 1.6.8.
Azkaban through 4.0.0 fails to enforce project-level permission checks in the ScheduleServlet fetchSchedule action, letting any authenticated user read the scheduling configuration of projects they do not own or have rights to. A logged-in attacker who supplies arbitrary project and flow identifiers can retrieve execution times, cron expressions, flow parameters, and notification email lists belonging to other teams. This is a read-only confidentiality exposure (CWE-862 missing authorization) with no code execution or data modification, exploitation requires a valid account (CVSS 3.1 PR:L), and no public exploit code or CISA KEV active-exploitation listing was identified at time of analysis.
An authorization bypass in ArcadeDB before 26.9.1 lets authenticated users read data they are explicitly denied at the per-type and per-bucket level by steering the AI chat assistant's query_database tool, which executes queries without binding the authenticated principal to DatabaseContext so ACL checks silently pass. Exploitation requires a valid ArcadeDB account, network reach to the instance, and the AI chat endpoints exposing the tool to be enabled or reachable; impact is limited to unauthorized read of otherwise-restricted types and buckets, with no write or availability effect. The flaw is rated 7.1 (CVSS 4.0 AV:N/AC:L/PR:L, independent assessment agrees at CVSS 3.1 C:H/I:N/A:N), a vendor fix is available in 26.9.1, and no public exploit code or confirmed active exploitation was identified at time of analysis.
django-page-cms through 2.0.13 fails to enforce page-permission checks in its admin helper views, allowing low-privilege authenticated staff accounts to read arbitrary page content, unpublished drafts, listings, and stored media file paths. No write access or code execution is possible, and exploitation requires a valid Django admin staff login, confining the issue to insiders or compromised/over-provisioned staff accounts. No public exploit code or active exploitation has been identified at time of analysis, and the flaw is a bounded broken-access-control issue rather than a top-tier emergency.
Authenticated SQL injection in ClipBucket v5 (through release 5.5.3) lets any logged-in user read arbitrary database contents - including all user credential hashes and email addresses - by submitting the msg_id parameter as an array to the private-message deletion handler. The array form evades the clean_requests() sanitizer in ClipBucket.class.php, so unsanitized elements reach cb_pm::delete_msg(), which interpolates the message ID directly into a SQL query string and supports time-based blind extraction. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) confirms a low-privilege authenticated remote attacker with high confidentiality impact only; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing).
Authenticated workspace members in DataEase SQLBot through 1.10.1 can rename and rewrite other users' private dashboards because the update_resource and update_canvas endpoints never verify that the requesting user owns the target dashboard, letting any member of the same workspace supply an arbitrary dashboard ID and overwrite component data, canvas styles, and view information. Exploitation requires only a valid low-privileged workspace account over the network (PR:L, no user interaction, no admin rights), and the impact is confined to integrity - confidentiality and availability are unaffected per the assessed vector. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, but a vendor patch is available, so unpatched multi-tenant deployments should be upgraded promptly.
An authenticated user with access to the OpenStack Blazar V2 REST API can enumerate leases belonging to other projects in Blazar versions before 17.0.1, because the GET /v2/leases endpoint enforces neither project scoping nor an administrator-only policy. This broken access control (CWE-862) exposes lease IDs, reservation IDs, resource IDs, and reservation metadata; the leaked lease IDs can then be leveraged with a separate object-level authorization bypass to modify or delete those leases. The flaw requires valid Blazar credentials and a deployment running the optional Blazar reservation service, and no public exploit identified at time of analysis.
Silent, warning-free failure of encryption-configuration generation in the Mongoid object-document mapper causes fields that an application explicitly declared for client-side field-level encryption (CSFLE) to be written to MongoDB as cleartext, allowing any party with ordinary read access to the database - a DBA, a read replica, a backup, or a lower-privilege account with query rights - to read values that were intended to be protected from them. Only applications built on Mongoid that use MongoDB CSFLE and declare fields for encryption are affected; the CVSS vectors (the supplied 4.0 vector with PR:L and the independently assessed 3.1 vector with PR:L) indicate the attacker requires some existing privilege, consistent with the assessed precondition of ordinary database read access rather than an unauthenticated remote path. No public exploit code has been identified at time of analysis, and this is assessed as a genuine but conditional data-protection failure rather than an actively exploited priority.
Mongoid can silently persist values in readable form that applications intended to encrypt, because its client-side field-level encryption (CSFLE) schema generation omits encryption rules for fields declared on embedded models - the MongoDB driver then writes those values unencrypted with no error or warning. The exposure is limited to applications that both enable CSFLE and declare encrypted fields on embedded documents (top-level fields are not implicated), and to parties who already hold read access to the database, a backup, or the underlying on-disk data files; there is no write, integrity, or availability impact and no remote code execution. Data-level risk is real but bounded: no public exploit code identified at time of analysis, no confirmed active exploitation, and the reported CVSS 4.0 base score of 7.1 is consistent with the independent CVSS 3.1 assessment of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
Authorization bypass in IBM MQ Console allows an authenticated but non-administrative user to create and start queue managers through the web interface, violating intended role separation. This is network-reachable and low-complexity but requires a valid non-admin account (CVSS 3.1 PR:L, base 7.1), with impact limited to low integrity and high availability effects rather than data confidentiality. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has published a patch advisory.
ArcadeDB deployments through 26.8.1 allow any authenticated principal - including a low-privileged user explicitly denied readRecord and deleteRecord on a given type - to bypass per-type/per-record access-control rules and read indexed key values, record IDs, MIN/MAX values, record counts and TimeSeries samples, and to delete index entries via ordinary SQL statements such as SELECT key, rid FROM INDEX:Type[field] and DELETE FROM INDEX:Type[field]. The flaw exists because ACL checks are enforced only in LocalBucket (keyed on file id) and are never invoked by query paths that reach record data through LSM index files or the TimeSeries engine, while schema discovery via SELECT FROM schema:indexes is unfiltered and exposes the index and type names needed to build an exploit. It affects both embedded and server deployments across all transports (HTTP, Bolt, Postgres, Gremlin), is exploitable with a single ordinary SQL statement and no user interaction, carries a CVSS 4.0 base score of 7.1, and has no public exploit identified at time of analysis; upgrading to 26.9.1 removes the flaw.
Man-in-the-middle attackers positioned on the network path between a Synology DiskStation and its configured mail server can exploit improper TLS certificate validation in the DSM Email API to read or write arbitrary files and trigger denial-of-service conditions. The flaw affects DSM builds before 7.2.1-69057-10, 7.2.2-72806-7 and 7.3.2-86009-2, and is rated CVSS 7.1 with an adjacent-network, high-complexity, unauthenticated vector requiring some user interaction. Exploitation demands that the appliance actually send email and that an email-sending action be triggered, so this is a genuine but hard-to-exploit MITM issue rather than a mass-exploitable one; no public exploit identified at time of analysis, and CISA KEV status is not indicated.
Remote unauthenticated denial of service affects NanoMQ MQTT brokers running versions earlier than 0.24.14, where a crafted MQTT v5 SUBSCRIBE packet triggers a heap out-of-bounds read in the broker receive path and can crash the broker process. The assessed impact is availability-only (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H): no confidentiality or integrity effect was confirmed, and the assessed vector carries PR:N, so exploitation is possible without credentials wherever anonymous MQTT access is enabled, though any authentication or ACL gate that requires a valid client before SUBSCRIBE is processed limits reachability. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the practical limiting factor on a successful crash (versus a benign over-read) is heap layout, which is why AC is rated High.
Unauthenticated information disclosure in CordysCRM (1Panel-dev) versions prior to 1.7.2 lets any network-reachable caller retrieve CRM form metadata via GET /mcp/form/config/{formKey}, exposing field names, types, required flags, default values, options, validation rules, and binding sources. The flaw exists because ShiroFilter marks the /mcp/** path as anonymous and McpController.getMcpField carries no permission annotation, so the endpoint is reachable without credentials (CVSS 4.0 base 6.9; independent assessment CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). Impact is limited to schema/metadata disclosure rather than direct access to customer records, and no public exploit code has been identified at time of analysis; exploitation does require knowledge or brute-forcing of valid formKey identifiers.
Missing authentication in the FastAPI backend of Forget-C Jellyfish AI Short Drama Studio (versions 0.1.0-alpha, 0.2.0, 0.3.0, 0.3.1 and 0.3.2) lets unauthenticated remote attackers reach API endpoints that should require credentials, because the dependency logic in backend/app/dependencies.py does not enforce an authentication check. The CVSS 4.0 base score is 6.9, and the vector (AV:N/AC:L/AT:N/PR:N/UI:N, LOW confidentiality/integrity/availability) indicates no credentials, no user interaction and no special conditions are needed; no public exploit code is identified at time of analysis and there is no confirmed actively exploited (CISA KEV) status. Real-world priority remains low because the software is an obscure self-hosted hobby project, so exposure depends on someone operating a publicly reachable instance, and a successful bypass yields only LOW impact across all three security objectives.
Unauthenticated remote attackers can query the SNMP v2c service on Grandstream GWN7660ELR access points running firmware before 1.0.27.6 when the service is left with the factory-default community string 'public', harvesting system metadata such as OS and kernel versions, process names and command-line arguments, interface configuration, routing and ARP tables, active TCP connections, and filesystem paths. The CVSS 4.0 base score is 6.9 (vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N) and our independent assessment maps it to CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - a read-only reconnaissance issue requiring only UDP/161 reachability, with no write, code execution, or lateral-movement primitive on its own. No public exploit code has been identified at time of analysis and the CVE is not in CISA KEV, so this is a genuine but modest-priority information-disclosure weakness whose real-world exposure depends on whether SNMP is enabled, still using the default community string, and reachable from untrusted networks; it is fixed in firmware 1.0.27.6.
Heap memory corruption in snappy-java 1.1.10.8 and earlier allows remote attackers to write attacker-influenced bytes past the bounds of the output array when an application decompresses untrusted compressed data through the typed Snappy.uncompress*Array APIs (such as uncompressIntArray, uncompressFloatArray, or uncompressDoubleArray), which size their result array using the uncompressed length divided by element size while forwarding the undivided length to the native JNI layer. Per the assessed vector (CVSS 3.1 AV:N/AC:L/PR:N/UI:N, C:N/I:L/A:L) no authentication or user interaction is needed, but exploitation is conditional: the consuming application must expose the typed decompression path to attacker-controlled input, and applications that only use the generic byte[] uncompress path are not exposed. Impact is currently rated Low integrity and Low availability (heap corruption and crash) with no confirmed confidentiality loss or demonstrated code execution, and no public exploit was identified at time of analysis; this is a genuine memory-corruption flaw but a moderate, not top-tier, priority, and no vendor-released fixed version is identified in the available data.
Sustained brute-force attacks against the HCL BigFix Service Management v27 login interface are possible because the product fails to adequately lock out or throttle repeated failed authentication attempts, letting remote unauthenticated attackers (CVSS PR:N/UI:N) make unlimited credential guesses that, if successful, grant full access as scored (C:H/I:H/A:H). The vendor scores this 9.8, but our independent assessment uses AC:H because the missing lockout does not itself grant access - the attacker must still obtain or guess valid credentials, so real-world impact hinges on password strength, MFA, and whether the login page is internet-exposed. Competing signals frame this as a high-severity design weakness with low current urgency: EPSS is 0.25% (17th percentile), SSVC records Exploitation: none with partial technical impact, no CISA KEV listing exists, and no public exploit code has been identified at time of analysis.
Improper UTF-8 percent-decoding in uri-js through 4.4.1 lets remote, unauthenticated attackers feed crafted percent-encoded URIs that the library converts into ASCII metacharacters such as '/', '\', '.' and CRLF, enabling downstream path traversal or CRLF injection wherever the decoded output is consumed without re-validation. The flaw is remotely triggerable with no authentication or user interaction (CVSS:4.0 base 6.9; independent assessment CVSS:3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N), but real-world harm is constrained by the consuming application: no code execution, no availability impact, and no effect at all if the downstream code re-validates the decoded string. There is no CISA KEV listing and no public exploit identified at time of analysis, so this is currently a latent input-neutralization weakness for applications that treat uri-js output as already-sanitized rather than a live exploitation campaign.
Unrestricted file upload in HCL BigFix Service Management lets an attacker submit a crafted file through the product's upload functionality and, if the payload is subsequently triggered, achieve code execution and full server compromise. The public description characterizes the actor as unauthenticated, while the vendor-supplied CVSS vector (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N) requires a low-privileged authenticated account plus user interaction at high attack complexity; our own independent assessment scores it AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity, and availability impact, so the two views differ by both privilege requirement and severity and must be reconciled before prioritization. Exploitation is limited to deployments that expose the vulnerable upload feature and whose validation controls can be bypassed, and there is no public exploit identified at time of analysis.
Heap-based out-of-bounds write in the PJSIP pjmedia AVI player (pjproject 2.17 and earlier) lets a crafted AVI file overwrite memory beyond a frame buffer when an application plays the file or pulls its frames. The buffer capacity is derived from the video dimensions declared in the file, while the copy length is taken from the file's own chunk header, so a malicious header produces an attacker-controlled write; the protection that would normally catch this is a pj_assert() that is compiled out of production release builds. The issue is local and file-driven, requiring the victim to open the media (CVSS v3.1 AV:L/UI:R, PR:N per the assessed vector), with crash-level impact for ordinary local playback and full memory corruption for applications that ingest untrusted AVI from relays, transcoders or user uploads; no public exploit code has been identified at time of analysis, no CISA KEV listing applies, and no fixed release version is available as of this review.
Missing rate-limit enforcement in Saleor's authentication throttling allows attackers to defeat brute-force protection by spoofing the client IP used as the throttle key, and publicly available exploit code exists. Saleor versions up to and including 3.20.118, 3.21.54, 3.22.47, and 3.23.14 are affected: get_client_ip() in saleor/account/throttling.py trusts a client-supplied X-Forwarded-For value when the deployment does not sanitize or pin that header, so an attacker who rotates spoofed IPs across repeated login attempts is never throttled. The vendor disputes the report as working-as-intended, the proposed fix (right-to-left RFC 7239 hop selection) remains unmerged, and the project's own issue #19203 concedes 'IP can be spoofed in most deployments'; impact is limited to weakening authentication throttling (C:L) with no integrity or availability effect, so this is a low real-world priority despite the public POC.
Bransys ELD ships with hardcoded MQTT credentials that allow unauthenticated remote attackers to subscribe to the real-time telematics feed for every active device belonging to the subset of carriers that were connected to the affected MQTT broker. The assessed CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) confirms the weakness is remotely reachable, low complexity, and requires no authentication or user interaction, but confines impact to low confidentiality - read-only exposure of real-time data with no integrity or availability effect, consistent with the vendor-side CVSS 4.0 score of 6.9 (VC:L, VI:N, VA:N). No public exploit code has been identified at time of analysis, though the hardcoded-credential nature of the flaw means anyone who extracts the static string from firmware or a decompiled mobile/app binary can reuse it without further tooling; practical exposure is bounded by whether the broker stays network-reachable and still accepts the unchanged credentials.
Sandbox escape in vm2 through 3.12.0 lets untrusted guest code cross the NodeVM isolation boundary and change process-wide state by calling crypto.setFips(), which toggles the FIPS mode of the entire host Node.js process (observed as crypto.getFips() flipping from 0 to 1 in the reporter's test). The vulnerability is only reachable when the embedding application runs vm2 as a NodeVM with the non-default, opt-in configuration require.builtin: ['crypto']; authentication and user interaction are not required in that scenario, and the practical impact is limited to low-integrity and low-availability effects rather than arbitrary host code execution or data disclosure. No public exploit identified at time of analysis; the issue is fixed in vm2 3.12.1, available from the vendor (GHSA-x3v6-43hc-82mc).
An out-of-bounds read in GPAC's RTP depacketizer lets unauthenticated remote attackers crash or partially disclose memory by delivering a crafted 3GPP timed-text (TTXT) RTP payload with an oversized advertised length. The flaw lives in gf_rtp_parse_ttxt() in src/ietf/rtp_depacketizer.c and affects GPAC 26.08-DEV and earlier builds prior to abi-16.26; exploitation requires the target to be acting as an RTP receiver/depacketizer rather than simply parsing a local file. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV), so this is a genuine but moderate-severity memory-safety defect whose practical reach depends on GPAC being deployed in an RTP-consuming configuration.