/

CVE-2026-85236

Severity:

HIGH RISK

(8.8)

CSRF (CWE-352) in MISP cullEmptyEvents Deletion Endpoint

CVE-2026-85236

Analyzed

Vulnerability type

Category:

Cross-Site Request Forgery

CWE:

CWE-352

Impact:

Unauthorized and potentially irreversible deletion of MISP event records

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A cross-site request forgery vulnerability in MISP's cullEmptyEvents action allowed an authenticated, sufficiently privileged user to be tricked into deleting published empty events. Because the state-changing endpoint accepted HTTP GET requests, a browser could issue the request without explicit user interaction, potentially causing irreversible event deletion.

Affected context

The vulnerability occurs in MISP deployments where the cullEmptyEvents action is reachable by authenticated users with sufficient privileges and accepts HTTP GET requests for a destructive operation. Bodyless GET requests may bypass CakePHP's normal CSRF validation, allowing a request initiated by an external webpage or automatically loaded browser resource to reach the state-changing endpoint. The use of skipBlocklist increases the significance of deletion because removed events may not leave blocklist entries that would prevent or identify later synchronization.

Exploit preconditions

  • Attack surface: The MISP cullEmptyEvents HTTP endpoint
  • Required access: A victim must be authenticated and have sufficient privileges to invoke the action
  • Trigger point: A browser request to the state-changing endpoint
  • Why exploitation is possible: The action accepts HTTP GET requests, while bodyless GET requests are not subject to the expected CakePHP CSRF validation
  • User condition: The victim may only need to visit or load content from an attacker-controlled or compromised location

Why this happens

The underlying flaw is a state-changing, irreversible operation exposed through an HTTP GET endpoint without effective CSRF protection. GET requests are conventionally treated as safe and may be generated by browsers as a side effect of loading external resources, but this action performed deletion instead. This behavior maps to CWE-352: Cross-Site Request Forgery, where an application accepts an authenticated request that an external party can cause a user's browser to send. The absence of a method restriction allowed the operation to bypass the framework's normal CSRF validation path.

Potential impact

  • An attacker could cause deletion of published empty MISP events
  • Event records may be removed without deliberate user interaction
  • Deleted events may not produce blocklist entries because of skipBlocklist
  • Subsequent synchronization behavior could become difficult to prevent or track
  • Security monitoring and incident-response records could be affected by untracked deletion

General mitigation guidance

Mitigation generally focuses on ensuring that destructive actions cannot be triggered through cross-originable, side-effect-free request methods.

Common defensive patterns include:

  • Restricting state-changing and irreversible operations to HTTP POST or another appropriate non-GET method
  • Applying framework-provided CSRF validation to every state-changing request
  • Treating all externally supplied request parameters and browser-originated requests as untrusted
  • Requiring explicit authorization checks and least-privilege roles for destructive actions
  • Adding confirmation and audit controls for irreversible administrative operations
  • Avoiding deletion behaviors that bypass retention, blocklisting, or traceability controls unless explicitly required

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules that flag state-changing behavior implemented in GET handlers
  • Code review checks for deletion, modification, or administrative actions exposed through idempotent methods
  • Verification that CSRF middleware covers every state-changing route and controller action
  • Integration tests that attempt cross-origin requests against authenticated sessions
  • Policy enforcement requiring POST, PUT, PATCH, or DELETE semantics for corresponding state changes
  • Audit-log monitoring for unexpected event deletions, especially those lacking associated user intent or blocklist records

Automated security review tools may help identify unsafe HTTP method usage and missing CSRF protections, but application-specific testing remains important.

Sources

SourceLink
github.comgithub.com/MISP/MISP/commit/2b6b3ac90
github.comgithub.com/MISP/MISP/commit/50106c9a0
github.comgithub.com/MISP/MISP/commit/66ecb5acb
github.comgithub.com/MISP/MISP/commit/9c1346ce1
github.comgithub.com/MISP/MISP/commit/cfc8b8a6d

Frequently asked

questions

Yes, in the browser-based sense. An attacker may be able to cause a victim's authenticated browser to send the request from an external webpage or resource, provided the victim has the required MISP privileges.

Not necessarily. The key requirement is that the victim is authenticated and authorized to invoke cullEmptyEvents; the attacker primarily needs a way to cause the victim's browser to issue the request.

Expose destructive operations only through appropriate state-changing methods, such as POST, and ensure framework CSRF validation is enforced before the operation runs.

Review every endpoint for correct HTTP method semantics, apply CSRF protection consistently, enforce least privilege, and test destructive workflows against cross-origin browser requests.

Find out what's already
exploitable in your codebase.