CVE-2026-56422
CriticalCVSS 9.4Exploitation Probability (EPSS)
Low risk28th percentile - higher than 28% of all known CVEs
Summary
Multiple MISP core controllers and model capture paths accepted client-controlled request fields such as primary keys and foreign keys without proper server-side validation. This allows authenticated users to submit crafted data, potentially leading to object overwrites or unauthorized data access.
Risk Assessment
The organization may face serious security breaches, including unauthorized data sharing and object manipulation, which could result in data integrity loss and user trust issues.
Recommendation
It is recommended to implement fixes that strip client-supplied primary keys and validate identifiers before save operations. Additionally, ensure that ownership fields cannot be edited by users.
Related vulnerabilities
- CVE-2026-105215Critical
ZITADEL before 3.4.14 and 4.x before 4.16.2 contains an authentication bypass in the hosted Login V1 UI because the 'external account not found' registration endpoint trusts client-supplied external identity fields without a completed IdP callback. Unauthenticated attackers can submit forged IDPConfigID and ExternalUserID values to pre-create an account bound to a victim's external IdP identity, which the victim's later genuine external login then signs into.
- CVE-2026-105209Critical
ZITADEL 3.x before 3.4.15 and 4.x before 4.17.1 contains an improper authorization vulnerability: when issuing passkey or passwordless enrollment codes, it checks only the organization in the x-zitadel-orgid header, not the target user's organization. Attackers with user-write permission in one organization can obtain an enrollment code for a user in another organization on the same instance and register their own authenticator to take over that account.
- CVE-2026-105207Critical
ZITADEL 3.0.0 through 3.4.15 and 4.0.0 before 4.17.3 creates links between user accounts and external identity providers without verifying a primary factor or the caller's permission, including on identify-only Login V2 sessions and via the User Service V2 AddIDPLink endpoint. An unauthenticated attacker knowing a victim's login name can bind their own external IdP identity to the victim's account and then sign in as the victim.
- CVE-2026-103355Critical
The Unlimited Elements For Elementor plugin up to version 2.0.20 contains a blind SQL injection vulnerability. An attacker can exploit this flaw to manipulate database queries without knowing the database structure.
- CVE-2026-105135Critical
A code injection vulnerability was found in InternLM MindSearch 0.1.0 in the ExecutionAction.run function in mindsearch/agent/graph.py. The attack can be launched remotely, and exploit details have been publicly disclosed.
- CVE-2026-105134Critical
An OS command injection vulnerability was found in AhsayCBS up to version 10.3.2 in the file /rps/api/json/UpdateReceivers.do. The attack can be launched remotely, and the exploit has been published. Upgrading to version 10.3.4 resolves the issue.
- CVE-2026-105105Critical
Missing authentication for critical function in the ait-server telemetry and command broker in NASA-AMMOS AIT-Core through 3.1.1. An unauthenticated remote attacker with network access to the ZeroMQ message bus can inject spacecraft command data, exfiltrate command and telemetry traffic, inject forged telemetry, or disrupt the bus. The ZeroMQ broker binds XSUB and XPUB sockets to all interfaces by default without authentication.
- CVE-2026-71885Critical
In Bouncy Castle for Java before 1.86, the Messaging Layer Security (MLS, RFC 9420) implementation did not bind an X.509 credential to a LeafNode's signature_key. LeafNode.verify() checked a leaf's signature against the signature_key carried in the leaf itself, while the credential's X.509 certificate chain was stored but never parsed or validated, so the end-entity certificate's public key was never required to match signature_key as RFC 9420 sec. 5.3 requires. An attacker could present another party's certificate as its credential while signing the leaf, and the enclosing KeyPackage, with an unrelated key, and be accepted under that other party's identity through KeyPackage.verify() and the Group leaf-validation path.
- CVE-2026-92084Critical
The Beaver Builder Page Builder plugin for WordPress up to version 2.11.0.5 is vulnerable to arbitrary shortcode execution. This is due to insufficient validation before running do_shortcode, allowing unauthenticated attackers to execute arbitrary shortcodes. Exploitation requires a page with the Sidebar module containing a widget that displays attacker-controlled text, such as the Recent Comments widget with approved comments.
- CVE-2026-87115Critical
The VikAppointments Services Booking Calendar plugin for WordPress up to version 1.2.21 is vulnerable to arbitrary file deletion due to insufficient file path validation in the extract function. This allows unauthenticated attackers to delete arbitrary files on the server, potentially leading to remote code execution (e.g., by deleting wp-config.php). Exploitation requires at least one File-type custom field published on the confirmation page.
Original NVD description (English source)
Multiple MISP core controllers and model capture paths accepted client-controlled request fields such as primary keys (id) and ownership/scope foreign keys (event_id, org_id, user_id, sharing_group_id, galaxy_cluster_uuid, organisation_uuid, and related nested object identifiers) without consistently stripping, pinning, or revalidating them against the server-authorized object. In affected paths, an authenticated user with access to one authorized object could submit crafted REST or form payloads that caused MISP to save data against a different object than the one checked by the authorization logic. Depending on the endpoint, this could allow object overwrite, object re-parenting, ownership transfer, unauthorized sharing-group scoping, event/object injection, proposal retargeting, or stored attacker-controlled content appearing in another user’s context. The fixes harden affected create/edit/import flows by stripping client-supplied primary keys on create-only saves, re-pinning route- or database-authorized identifiers before save operations, validating effective sharing-group scope, and adding field whitelists where ownership fields must never be editable. The initial broad fix also added a central CRUDComponent::edit() primary-key re-pin so payload-supplied IDs cannot redirect saves away from the already-authorized row. GitHub’s patch for 7acf8220c describes this central issue as CRUDComponent::edit() copying supplied fields, including a payload primary key, onto the loaded record, allowing CakePHP save() to update an arbitrary row unless the loaded ID is re-pinned.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

