PULSE
FEED
ransomsilentransomgroup reclama a Jackson Walker · US · Professional Servicesransomsilentransomgroup reclama a T... K...ransomhyflock reclama a An independent asset management firm in Casablanca · MA · Financial Servicesransomcurious worm reclama a eo***r******y.com · Technologyransomlockbit5 reclama a primecareofmi.com · US · Healthcareransomlockbit5 reclama a softlinefurniture.com · US · Retail & E-Commerceransomlockbit5 reclama a laguarda.com.ec · EC · Otherransomlockbit5 reclama a umraocashmere.com · IN · Retail & E-Commerceransomlockbit5 reclama a cih.com.vn · VN · Otherransomkrybit reclama a STL International Pte Ltd · SG · Otherransomakira reclama a Bench Equity · Financial Servicesransomakira reclama a Audiotec · Technologyransomrhysida reclama a WILLIAMS, BRODERSEN, PRITCHETT & RUIZ LLP · Professional Servicesransomakira reclama a Flagship Cruises & Events · US · Hospitalityransomsilentransomgroup reclama a Jackson Walker · US · Professional Servicesransomsilentransomgroup reclama a T... K...ransomhyflock reclama a An independent asset management firm in Casablanca · MA · Financial Servicesransomcurious worm reclama a eo***r******y.com · Technologyransomlockbit5 reclama a primecareofmi.com · US · Healthcareransomlockbit5 reclama a softlinefurniture.com · US · Retail & E-Commerceransomlockbit5 reclama a laguarda.com.ec · EC · Otherransomlockbit5 reclama a umraocashmere.com · IN · Retail & E-Commerceransomlockbit5 reclama a cih.com.vn · VN · Otherransomkrybit reclama a STL International Pte Ltd · SG · Otherransomakira reclama a Bench Equity · Financial Servicesransomakira reclama a Audiotec · Technologyransomrhysida reclama a WILLIAMS, BRODERSEN, PRITCHETT & RUIZ LLP · Professional Servicesransomakira reclama a Flagship Cruises & Events · US · Hospitality
CVE Watch417,234 en archivo total

Vulnerabilidades explotables hoy

417,234en la vista actual

Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.

En catálogo KEV1,782
Nuevos KEV · 24H0
Exploit Today ≥ 701,710

Distribución · última ventana

  • Crítico
    4,728
  • Alto
    18,200
  • Medio
    17,813
  • Bajo
    1,948
Filtros
Filtros

Ventana

Severidad

Filtros

Vulnerabilidades417,121–417,160 · 417,234
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-130091—
—
———A caller with write permission in a namespace can terminate temporal-proxy through memory exhaustion by storing highly compressed payloads in Workflow history, and the stored history causes the same failure on every later read. temporal-proxy 1.2.0 decompresses every payload marked as compressed in the responses it forwards, whether or not compression is configured. Each payload is limited to 4 MiB after decompression, but the total for a response is not, and the decoded payloads are held in memory together. The caller can store many small, highly compressed payloads through the proxy or directly at the upstream Temporal service. When that history is read through the proxy, for example by a Worker processing a task, the proxy can run out of memory and be terminated. The codec server's /decode endpoint is affected in the same way when it is enabled. Only temporal-proxy 1.2.0 is affected; earlier versions do not decompress payloads. The issue is fixed in 1.2.1. Upgrade to 1.2.1 or later.3h
CVE-2026-130092—
—
———A caller who can reach the temporal-proxy gRPC listener, with or without a valid credential, can grow the proxy's memory until the process is terminated by sending requests with many distinct gRPC method names. temporal-proxy labels its request metrics with the method name exactly as the caller sent it, and records every request, including those that authentication or routing reject. Each distinct method name adds metric series that are never removed. The series grow whether or not the metrics endpoint is scraped, and metric labels configured from request metadata multiply the growth. temporal-proxy versions 0.1.0-alpha.20260716 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.3h
CVE-2026-1322816.3 MED
—
———A vulnerability was found in elunez eladmin up to 2.7. This affects the function SqlUtils.batchExecute of the file /api/database/upload of the component Database Maintenance Module. The manipulation results in sql injection. It is possible to launch the attack remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.32m
CVE-2026-1321376.3 MED
—
———A vulnerability was identified in Relaticle up to 3.10.0. This affects the function mapToField of the file packages/ImportWizard/src/Livewire/Steps/MappingStep.php of the component Import Wizard. Such manipulation of the argument Target leads to authorization bypass. The attack can be executed remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure.4h
CVE-2026-1321399.9 CRÍ
—
———A weakness has been identified in DrayTek Vigor2960 up to 1.5.1.6. Affected is the function setSWMProfile of the file /cgi-bin/mainfunction.cgi. Executing a manipulation of the argument filename can lead to stack-based buffer overflow. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. Upgrading to version 1.5.1.7 is able to address this issue. It is recommended to upgrade the affected component. The vendor recommends: "1.5.1.6 isn't the latest version of 2960, the latest version fixes many security issues. And we have another one in our release plan which should solve the issues reported."4h
CVE-2026-1321407.5 ALT
—
———A security vulnerability has been detected in DrayTek Vigor2960 up to 1.5.1.6. Affected by this vulnerability is an unknown functionality of the file mainfunction.cgi of the component Apmcfg Upload. The manipulation leads to null pointer dereference. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 1.5.1.7 addresses this issue. Upgrading the affected component is advised. The vendor recommends: "1.5.1.6 isn't the latest version of 2960, the latest version fixes many security issues. And we have another one in our release plan which should solve the issues reported."4h
CVE-2023-544199.8 CRÍ
—
———nginxWebUI 3.0.0 before 3.5.8 contains an authentication bypass vulnerability that allows unauthenticated attackers to reach the /AdminPage/conf/runCmd endpoint by using a case-variant path that evades the case-sensitive /adminPage/ login filter. Attackers can pass OS commands through the cmd parameter, which are executed via /bin/sh with insufficient filtering of & and $() characters, achieving remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.8h
CVE-2023-544207.5 ALT
—
———LiveBOS builds through 2023-08-16 contain a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files via the imgName parameter in /feed/ShowImage.do using a ';.js.jsp' suffix bypass. Attackers can send crafted GET requests with directory traversal sequences in imgName to read system files such as /etc/passwd. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-30.9h
CVE-2026-132144—
—
———MISP contains an authorization flaw in the user login-email change logic. When an external authentication backend is configured (LDAP, Shibboleth, ApacheSecureAuth, or CustomAuth), the login email address serves as the key by which the directory service resolves a user's identity, organization, and role on each login. The __canChangeLogin() method in UsersController only checked the MISP.disable_user_login_change setting and site-admin status; it did not account for whether an external authentication backend was active. As a result, any authenticated non-admin user (including org admins) could change their own login email to an address that matches a higher-privilege account in the external directory. On the user's next login, the external backend would resolve that email to the target directory identity, granting the attacker the organization and role associated with that identity. This constitutes an account-identity capture and privilege escalation: the attacker effectively assumes the identity of any directory account whose email they can guess or discover. The vulnerability requires an authenticated session with a valid API key or session token and a MISP instance configured with at least one external authentication backend. The impact is limited to the scope of the captured directory identity's privileges within MISP.4h
CVE-2023-544216.1 MED
—
———phpLDAPadmin 1.1.0 before 1.2.5 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the dn parameter of cmd.php?cmd=template_engine. Attackers can supply an unparseable dn value that pretty_print_dn returns unescaped in the 'No such entry' error, executing JavaScript in victims' browsers. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23.9h
CVE-2026-132559—
—
———When payload encryption is enabled, failure messages and stack traces that temporal-proxy is configured to keep from the upstream Temporal service can reach it in plaintext, where anyone who can read the Workflow's history at the upstream can read them. When the proxy returns a failure to a Worker, it decrypts the failure's encoded attributes and copies the message and stack trace back onto the failure, keeping the attributes. A Worker that sends that failure back through the proxy, as SDKs do when an Activity failure becomes the cause of a Workflow failure, sends the restored text with it, and the proxy forwards the text unchanged because the failure already has encoded attributes. The upstream then stores the text in plaintext beside its encrypted copy. This affects deployments that enable failure encryption in the proxy, and deployments that leave it off while the SDK encodes failure attributes itself. Payloads are not affected. temporal-proxy versions 0.9.0 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.3h
CVE-2026-132636—
—
———MISP contains an authorization bypass in its event search and filter functionality. When a user performed searches through events/restSearch (value, value prefix, searchall, type, uuid, attribute tags, object filters), objects/restSearch, or the event index tag, galaxy, and quick filters, the underlying SQL subqueries matched against attributes and objects without enforcing the per-attribute distribution, sharing-group, or soft-deleted visibility rules that apply when fetching individual elements. A user who could view an event (for example, a community-distributed event) could therefore use search to determine whether organisation-only, sharing-group-restricted, or soft-deleted attributes and objects existed within that event. Because the value filter supports prefix matching (LIKE), an attacker could enumerate the full value of a hidden attribute one character at a time. Tags attached exclusively to hidden attributes also leaked through the tag, galaxy, and quick-filter paths on the event index. The vulnerability affects the EventsController quick-filter and index-filter logic, the Event model wildcard/value/uuid/tag filter methods, the MispAttribute tag filter, the MispObject buildFilterConditions and restSearch methods, and the ReportFromEvent object filter. Site administrators and users belonging to the event's own organisation retain full visibility, and sync users continue to match soft-deleted elements as intended. The issue was reported by ENISA.4h
CVE-2026-132637—
—
———MISP contains an authorization bypass in the correlations/eventCorrelations endpoint and the underlying correlation engines (Default and OnDemand). The CorrelationsController::eventCorrelations action did not verify that the requesting user was permitted to view the event specified by the event ID parameter. Any authenticated user could supply the ID of an event belonging to another organisation (distribution level 0, organisation-only) and receive its full correlation results, including attribute identifiers and values. Additionally, for events the user could partially view, the correlation engines filtered only the related (target) side of each correlation row and did not vet the queried event's own source attributes. As a result, correlations keyed by attributes hidden from the user (organisation-only attributes, attributes in sharing groups the user is not a member of, or attributes inside organisation-only objects) were returned with their IDs and values. The Default engine's related-event listing (used in events/view) also included events related solely through such hidden attributes. The vulnerability was reported by ENISA. Successful exploitation requires a valid authenticated session with any role and knowledge or enumeration of a target event ID. The security impact is disclosure of threat-intelligence attribute values (IP addresses, domain names, etc.) and attribute identifiers that the user is not authorised to see, as well as confirmation of the existence of otherwise invisible events.3h
CVE-2026-132641—
—
———MISP's EventDelegationsController delegateEvent method accepted a user-supplied sharing_group_id parameter without verifying that the requesting user was a member of the referenced sharing group. When a delegation request was submitted with distribution set to 4 (sharing-group distribution), the raw sharing_group_id value was stored directly into the EventDelegation record. The delegation view subsequently rendered the stored sharing group's name back to the requester. Because no authorization check was performed, any authenticated user with delegation permission could enumerate sharing group identifiers (by guessing sequential IDs or other values) and read the names of sharing groups to which their organisation did not belong, including hidden or restricted groups. Hidden, missing, and malformed identifiers were not distinguished in the response, but the successful case still leaked the group name. The vulnerability required an authenticated session with the perm_delegate capability and knowledge of a valid event ID to delegate. The security impact is limited to disclosure of sharing group names (a low-impact confidentiality breach) and does not grant access to the group's contents or modify any data.4h
CVE-2023-544229.8 CRÍ
—
———iDocView before 13.10.1_20231115 contains an unrestricted file upload vulnerability in the /html/2word endpoint that allows unauthenticated attackers to write arbitrary files by supplying a malicious url parameter. Attackers can send a crafted GET request with the url parameter to download linked resources with an unsanitized path and unblocked .jsp extension, achieving remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-11-22.7h
CVE-2024-584016.1 MED
—
———Bagisto 2.1.0 before 2.2.1 contains a client-side template injection vulnerability in the search page where the 'query' parameter is rendered unescaped inside a Vue app root. Unauthenticated attackers can send crafted VueJS template expressions to the /bagisto-common/search endpoint via the 'query' parameter to execute arbitrary JavaScript in victims' browsers. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-07-30.8h
CVE-2026-132642—
—
———MISP contains an access control flaw in its tag management endpoints: events/addTag (single and bulk), events/removeTag, and attributes/removeTag. These endpoints loaded their target event or attribute using an unscoped database query (recursive = -1) that did not apply the calling user's ACL visibility rules. As a result, two distinct security issues existed: (1) Information disclosure: the removeTag endpoint returned different responses depending on whether a given tag was present on a hidden event, allowing an authenticated user to enumerate which tags were applied to events they had no visibility into. (2) Unauthorized modification: users belonging to the host organisation, who are permitted to set local tags on records they can see, could add or remove local tags on events and attributes they could not see, because the canModifyTag ACL check operated on the unscoped object without first verifying the caller's visibility. The fix replaces the unscoped find() calls with ACL-aware fetch methods (fetchSimpleEvent and fetchAttributeSimple) that apply the user's visibility before the object is returned, and adds an explicit empty-object check in removeTag so that a hidden event responds identically to a non-existent one. Affected components include the EventsController (addTag, removeTag), the AttributesController (removeTag), and the ACLComponent (canModifyTag). The vulnerability requires an authenticated user with at least the tagger role (perm_tagger) or host-organisation membership.3h
CVE-2026-132643—
—
———MISP contains an information disclosure vulnerability in the Sighting model when the Sightings_anonymise setting is enabled. The listSightings and sightings/restSearch endpoints accepted a caller-supplied org_id filter parameter and applied it directly to the SQL query without verifying whether the requesting user was authorized to filter by that organisation. Because the anonymization mechanism masks the reporter's organisation in the returned records, a non-site-admin user could bypass the anonymization by specifying another organisation's ID in the filter. The query would then return only that organisation's sightings, effectively naming the reporter and defeating the purpose of the anonymization feature. A negated filter (NOT IN) similarly revealed which sightings belonged to the target organisation by exclusion. The vulnerability requires an authenticated user with sighting read permissions (perm_sighting) who is not a site administrator, and the Sightings_anonymise plugin setting must be enabled. The security impact is the disclosure of which organisation reported a given sighting, undermining the privacy guarantees that the anonymization feature is designed to provide. This issue was reported by ENISA.3h
CVE-2026-55169—
—
———Open OnDemand is an open-source high-performance computing portal. Prior to 4.1.6 and 4.2.3, the Open OnDemand dashboard includes noVNC passwords in query parameters generated by apps/dashboard/app/helpers/batch_connect/sessions_helper.rb and apps/dashboard/app/views/batch_connect/sessions/connections/_novnc.html.erb. The server records those query strings in per-user PUN access logs, and insufficiently protected log directories can allow another local user to recover and replay a launch URL. Replaying the credential grants access to the running remote desktop and can result in horizontal or vertical privilege escalation according to the privileges of the desktop owner. This issue is fixed in versions 4.1.6 and 4.2.3.4h
CVE-2026-55171—
—
———Open OnDemand is an open-source high-performance computing portal. Prior to Open OnDemand 4.1.6 and 4.2.3, and prior to ood-ansible 4.2.1, the portal generator defaults OIDCCryptoPassphrase to SHA1(servername), and the templates/ood_portal.yml.j2 role checks a different variable from the documented passphrase setting. Administrators who set ood_oidc_crypto_passphrase can therefore believe a strong secret is configured while the deployment continues to use an attacker-derivable value. In OIDCSessionType client-cookie deployments, an unauthenticated remote attacker can derive the encryption key and forge a mod_auth_openidc_session cookie for another user, while server-cache deployments permit lower-impact tampering with protected OIDC state and nonce cookies. This issue is fixed in Open OnDemand versions 4.1.6 and 4.2.3 and ood-ansible version 4.2.1.4h
CVE-2024-584028.2 ALT
—
———Azon Dominator releases through 2024-06-03 contain an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries through the cid parameter in /fetch_products.php. Attackers can send crafted POST requests with boolean-based or time-based blind payloads to extract sensitive database information. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-07-30.9h
CVE-2026-55172—
—
———Open OnDemand is an open-source high-performance computing portal. Prior to 4.1.6 and 4.2.3, apps/dashboard/config/initializers/session_store.rb stores dashboard sessions by default in a predictable /var/tmp/<username> directory, or in another location configured by an administrator, but omits PUN user directory ownership and mode 0700 validation. A local attacker can pre-create another user's directory, read the victim's session identifier and CSRF token after login, or stage a predetermined session identifier. ActiveSupport file-store deserialization of attacker-controlled cache data may also occur in the victim's context, enabling file modification or code execution with the victim's privileges. This issue is fixed in versions 4.1.6 and 4.2.3.4h
CVE-2026-555054.9 MED
—
———Wavelog is web-based amateur radio logging software. Prior to 3.2.4, the application/controllers/Lotw.php import() workflow passes the lotw_download_url configuration value to curl without scheme validation, accepts file:// content, and writes the response to a predictable path under ./uploads/ that can be retrieved through an unauthenticated HTTP request. A standard user can trigger the LotW import, although changing lotw_download_url normally requires installer administrator access, and related vulnerabilities can remove that prerequisite. The same missing status-validation pattern affects the LotW lotw_users fetch helper and per-user download helper. This exposes files readable by the www-data user, including environment data, mounted secrets, and application configuration. This issue is fixed in version 3.2.4.4h
CVE-2026-555069.6 CRÍ
—
———Wavelog is web-based amateur radio logging software. Prior to 2.5, the filename parameter accepted by POST /qsl/addQsoToQsl in application/controllers/Qsl.php addQsoToQsl() is stored without rejecting directory separators or relative path components, and POST /qsl/delete reaches application/models/Qsl_model.php deleteQsl(), which passes the planted qsl_images filename to unlink(). A standard authenticated user can associate the malicious filename with the user's own QSO, satisfy the ownership check, escape the per-user QSL image directory, and delete files writable by the PHP worker. Deleting configuration or operational files can cause denial of service, while deleting installer gate files can reopen the unauthenticated installer and enable application identity takeover through attacker-controlled database configuration. This issue is fixed in version 2.5.4h
CVE-2026-555076.0 MED
—
———Wavelog is web-based amateur radio logging software. In 3.2.5 and earlier, the Hams of Note feature stores the administrator-supplied hon_url configuration value through application/controllers/Options.php hon_save() and application/models/Update_model.php update_hams_of_note() fetches that URL without restricting the scheme, host, loopback, link-local, or private network destinations. An administrator can cause the Wavelog server to request arbitrary HTTP or HTTPS destinations from its network position and have parsed response content rendered in the administrator interface, providing a read primitive against otherwise unreachable internal HTTP services. The HTTP status requirement prevents file scheme responses from succeeding, so this issue does not provide local file disclosure. No fixed version is available as of this review.4h
CVE-2026-555089.4 CRÍ
—
———Wavelog is web-based amateur radio logging software. Prior to 2.5, the callsign parameter accepted by POST /oqrs/search_log in application/controllers/Oqrs.php search_log() reaches application/models/Oqrs_model.php search_log(), where it is concatenated directly into a raw SQL WHERE clause without parameter binding. An unauthenticated remote attacker can use UNION-based SQL injection to read arbitrary application database records, including account data, password hashes, API keys, station credentials, reset tokens, QSO data, and station metadata. Disclosure of password reset tokens can be combined with the forgot_password workflow to take over accounts, including administrator accounts. This issue is fixed in version 2.5.4h
CVE-2026-1322826.3 MED
—
———A vulnerability was determined in elunez eladmin up to 2.7. This vulnerability affects the function FileUtil.upload of the file /api/localStorage of the component File Upload Handler. This manipulation causes path traversal. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.32m
CVE-2026-599645.9 MED
—
———uftpd is a UNIX FTP and TFTP server. Prior to 2.16, uftpd's compose_path function in src/common.c can overflow the fixed dir[PATH_MAX] stack buffer when the server runs without chroot and prepends the configured home directory to a near-PATH_MAX attacker-supplied path using memmove. A logged-in FTP client, including an anonymous or guest client where enabled, can trigger the out-of-bounds write through commands such as CWD, RETR, STOR, or LIST, causing memory corruption and a reliable service crash. Remote code execution has not been demonstrated. This issue is fixed in version 2.16.4h
CVE-2024-584037.5 ALT
—
———AnyShare builds through 2024-11 contain a missing authentication vulnerability in the /api/ShareMgnt/Usrm_GetAllUsers endpoint that exposes user records including password fields. Attackers can send unauthenticated POST requests with a [start,limit] body to retrieve usernames, passwords, and department information for all users. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-12-25.9h
CVE-2026-1134258.1 ALT
—
———When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-free in an nginx worker process. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: A remote unauthenticated attacker may crash an nginx worker process or corrupt its memory, disrupting service. Remote code execution is a potential impact. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.8h
CVE-2026-1164439.8 CRÍ
—
———Dell PowerStore SDNAS contains a stack-based buffer overflow in the NAS TFTP service that could allow an unauthenticated remote attacker to cause a denial of service or potential code execution.6h
CVE-2026-1164499.8 CRÍ
—
———Dell PowerStore SDNAS contains an OS Command Injection vulnerability that could allow an attacker with internal network access to execute arbitrary commands as root on the NAS node.8h
CVE-2026-599757.5 ALT
—
———SharpIppNext is a .NET Standard library for building Internet Printing Protocol clients and servers. Prior to 4.1.0, server-side SharpIppNext implementations using SharpIppServer.ReceiveRequestAsync or SharpIppServer.ReceiveRawRequestAsync pass incoming data to IppProtocol.ReadIppRequestAsync in SharpIpp/Protocol/IppProtocol.cs, where ReadDocumentStream is enabled by default and the remaining document body is copied with CopyToAsync into a MemoryStream without a size limit. An unauthenticated remote client can send an arbitrarily large IPP document body, exhausting process memory and causing an out-of-memory failure or service termination. Client-only implementations using SharpIppClient are not affected. This issue is fixed in version 4.1.0.4h
CVE-2026-1169539.8 CRÍ
—
———Description: When an iRule that processes client traffic using the GENERICMESSAGE::route command is configured on a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate and may lead to remote code execution (RCE).  Impact: Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system and may allow the attacker to perform RCE. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.8h
CVE-2026-691314.3 MED
—
———django-filer is a file and image management application for Django. Prior to 3.5.0, the delete_files_or_folders action in filer/admin/folderadmin.py checks global Django model-level deletion permission but omits check_folder_edit_permissions and check_files_edit_permissions when FILER_ENABLE_PERMISSIONS is enabled. An authenticated staff user who has a global delete_file, delete_folder, or delete_image permission but is limited to read-only access by FolderPermission can therefore delete files, folders, and descendants from the restricted folder. Deployments using the default disabled per-folder permission system are not affected, and the issue does not create a read-confidentiality impact. This issue is fixed in version 3.5.0.4h
CVE-2026-1188997.5 ALT
—
———When using the listen directive with the ssl parameter in the http block with TLSv1.3 enabled, an attacker can use a specially crafted TLS connection to cause an infinite loop in the NGINX worker process while reading the HTTP request body. As a result, the worker process stops accepting new connections and processing existing connections. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. Impact: This vulnerability allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) of NGINX. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.8h
CVE-2026-691386.5 MED
—
———djangocms-versioning is a general-purpose versioning package for django CMS 4 and later. Prior to 2.6.1, the check_discard and check_edit_redirect Conditions on djangocms_versioning.models.Version omit user_can_change, while VersionAdmin.discard_view and VersionAdmin.edit_redirect_view obtain a version by its primary key and rely on those conditions for object-level authorization. With CMS_PERMISSION set to True, the affected views are gated only by is_staff, allowing any staff user to select content without object-level change permission. With the default CMS_PERMISSION value of False, a staff user must also hold the global Django change_ permission, but that model-level permission does not enforce the intended per-object authorization, so the user can delete a draft version and its content object through discard or create an editable draft from a published version through edit_redirect even when the user cannot change that specific content object. This issue is fixed in version 2.6.1.4h
CVE-2026-714275.3 MED
—
———WPGraphQL Content Blocks is a WordPress plugin that extends WPGraphQL to support querying Gutenberg blocks as data. Prior to 4.8.6, the editorBlocks renderedHtml field in includes/Data/ContentBlocksResolver.php uses resolve_content_blocks() to read a post with get_post() without applying post_password_required(). An unauthenticated caller who knows a supported post identifier can therefore retrieve the complete body of a password-protected published post without a post password, nonce, or valid cookie, exposing paid, member-only, preview, or internal content. This issue is fixed in version 4.8.6.4h
CVE-2026-1200495.4 MED
—
———The Link Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'linkfile[name]' parameter in all versions up to, and including, 7.10.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an administrator to have enabled the "Link File" option within the plugin's settings, which activates the vulnerable file upload field on the public add-link form.5h
CVE-2026-739678.7 ALT
—
———AnsibleForms is a self-hosted web application that turns automation into self-service forms. Prior to 6.2.1, AnsibleForms stores attacker-influenceable job output that server/src/lib/common.js processes through formatOutput without HTML escaping and client/src/components/AppAnsibleOutput.vue renders through v-html. An authenticated user can submit job input that is echoed into persistent output, causing script execution when another user views the job. Additional designer-controlled HTML and expression values reach v-html in client/src/components/AppForm.vue and client/src/components/BsInputForForm.vue without sanitization. Because Content Security Policy is disabled and the JWT is stored in localStorage, script execution can steal a victim's token and take over the account, including an administrator account. This issue is fixed in version 6.2.1.4h