Is this vulnerability remotely exploitable beyond the local network?

The vulnerability is reachable wherever the `/designer/loadReport` endpoint is exposed. Because it requires authentication, exploitation normally depends on attackers obtaining or abusing valid credentials, but it can be exploited remotely if the application is internet-facing and an attacker can log in.

What level of access does an attacker need to exploit this?

An attacker must be an authenticated user with access to the XML-based report loading functionality. They need the ability to submit or influence the XML payload processed by `/designer/loadReport`.

What is the safest general fix pattern for this issue?

The most robust fix is to harden all XML parsing by disabling DTDs and external entities across the application and, where feasible, constrain XML to a validated schema or a safer data representation. Ensuring that the XML parser used for `/designer/loadReport` cannot resolve external entities eliminates the XXE attack vector.

Severity:

HIGH RISK

(8.8)

XML External Entity Processing (CWE-611) in SpringBlade /designer/loadReport Endpoint

CVE-2026-36765

Published:

Apr 30, 2026

Status:

Deferred

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

XML External Entity (XXE)

CWE:

CWE-611

Impact:

Remote Code Execution via XML External Entity Processing

Severity:

HIGH RISK

(8.8)

CVSS Version:

3.1

Vulnerability Type

Category:

XML External Entity (XXE)

CWE:

CWE-611

Impact:

Remote Code Execution via XML External Entity Processing

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.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

XML External Entity Processing (CWE-611) in SpringBlade /designer/loadReport Endpoint

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal