CVE-2026-36765
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn XML external entity (XXE) vulnerability in the /designer/loadReport endpoint of SpringBlade v4.8.0 allows authenticated attackers to execute arbitrary code via injecting a crafted payload.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSpringBlade v4.8.0 contains an XML External Entity (XXE) injection vulnerability in the /designer/loadReport endpoint. An authenticated attacker can inject malicious XML payloads containing external entity references, allowing the parser to read local files or potentially execute arbitrary code by leveraging the XXE to trigger further attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SpringBlade versionLocate the SpringBlade application JAR/WAR files or check the build configuration (pom.xml, build.gradle) for the version declaration. Typically found in the project root or WEB-INF/lib directory.Affected if The installed version matches v4.8.0 or falls within the affected range without a security patch applied.
-
Verify /designer/loadReport endpoint existsCheck if the endpoint is accessible by reviewing the application's routing configuration (controller annotations, application.yml routing definitions) or by attempting a HEAD/GET request to /designer/loadReport if the application is running.Affected if The endpoint is present and exposed in the application routing.
-
Inspect XML parser configuration for the loadReport endpointLocate the Java controller handling /designer/loadReport (typically a designer-related controller class). Examine the XML parsing code to determine if DocumentBuilderFactory or similar XML parsers have explicitly disabled external entities via features such as 'DISABLE_DOCTYPE_DECL', 'external-general-entities', and 'external-parameter-entities'.Affected if The XML parser configuration does not explicitly set these features to false, meaning external entity processing is enabled.
-
Review access logs for XXE exploitation attemptsSearch application access logs (typically in logs/ or /var/log/ directories) for requests to /designer/loadReport containing patterns like 'DOCTYPE', 'ENTITY', 'SYSTEM', or 'file://' URIs.Affected if Suspicious XXE payload patterns are found in recent requests to the endpoint.
You are affected if SpringBlade v4.8.0 is running with the /designer/loadReport endpoint exposed and the XML parser has not disabled external entity processing.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable external entity processing and DTD processing in the XML parser configuration used by the /designer/loadReport endpoint. Apply vendor-provided patches when available and validate that XML input parsing follows secure defaults.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36765 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36765 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data