/

CVE-2026-75814

Severity:

HIGH RISK

(8.8)

CSRF (CWE-352) in Ebyte Device Web Management Interface

CVE-2026-75814

Deferred

Vulnerability type

Category:

Cross-Site Request Forgery (CSRF)

CWE:

CWE-352

Impact:

Unauthorized Configuration Changes and Denial of Service

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 the Ebyte device web management interface allows a malicious website to submit unauthorized requests through an authenticated administrator's browser.

If an administrator visits a crafted page while logged in, an unauthenticated remote attacker may change device settings or disrupt device availability.

Affected context

The issue occurs in Ebyte devices that expose a web management interface and rely on the administrator's existing browser session to authorize state-changing requests. Risk is higher when the interface accepts cross-origin requests without sufficiently verifying request origin, authenticity, or user intent.

Exploit preconditions

  • Attack surface: Web management interface accessible through a browser
  • Required access: No direct authentication to the device; the attacker needs an authenticated administrator to visit a malicious or compromised webpage
  • Trigger point: A state-changing management request issued from the administrator's browser
  • Why exploitation is possible: The interface does not adequately validate request origin or authenticity before applying authenticated actions

Why this happens

The vulnerability results from insufficient protection of state-changing web requests against cross-site request forgery. When a management interface accepts browser-submitted requests based primarily on ambient session credentials, another site may cause an authenticated administrator's browser to send actions without clear user intent. This behavior maps to CWE-352: Cross-Site Request Forgery (CSRF).

Potential impact

  • Unauthorized changes to device configuration may occur
  • Device availability could be disrupted
  • Administrative settings may be altered without the administrator's intentional approval
  • Network behavior or operational reliability may be affected

General mitigation guidance

Mitigation generally focuses on ensuring that state-changing management actions require demonstrable user intent and validated request provenance.

Common defensive patterns include:

  • Applying strong, unpredictable anti-CSRF tokens to state-changing requests
  • Validating trusted origin or referrer signals where appropriate
  • Using restrictive cookie policies, such as suitable SameSite settings
  • Requiring explicit confirmation for high-impact administrative actions
  • Separating read-only requests from state-changing operations
  • Limiting management-interface exposure and applying least-privilege administrative roles
  • Avoiding reliance on browser cookies alone as proof of request legitimacy

How teams detect issues like this

Organizations can look for CSRF exposure through:

  • Static analysis of state-changing handlers that lack token or origin validation
  • Code review checks for administrative endpoints accepting browser requests without explicit intent verification
  • Dynamic testing that evaluates cross-origin submission behavior for configuration actions
  • Policy enforcement requiring CSRF protections on all cookie-authenticated state-changing endpoints
  • Automated security review tools that identify missing anti-CSRF controls and permissive cookie settings

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-237-06.json
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-237-06

Frequently asked

questions

Yes, an attacker may not need to authenticate directly to the device, but exploitation generally depends on an authenticated administrator visiting a crafted page while an active management session is available.

Not necessarily. The key requirement is that the administrator's browser can reach the management interface and submit the resulting request.

Require robust anti-CSRF tokens and request-origin validation for every state-changing management action, with explicit confirmation for especially sensitive operations.

Use secure cookie policies, enforce CSRF protections in web frameworks and API design, limit management-interface exposure, and test administrative workflows for cross-origin request acceptance.

Find out what's already
exploitable in your codebase.