Apioo Fusio - Server-Side Request Forgery

Answer in brief

CVE-2026-72598 records a Medium severity (CVSS 6.5) vulnerability in Apioo Fusio - Server-Side Request Forgery. The current sources do not mark it as known exploited. The current feed maps Apioo/Fusio (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 11, 2026Updated Sep 3, 2026Source checked Sep 25, 2026First seen by HOL Aug 11, 2026Material review Sep 3, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Apioo/Fusio (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Apioo/Fusiogeneric	0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Apioo/Fusio.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 3, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 11, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source description

A server-side request forgery vulnerability in Apioo Fusio 8.8.3 allows authenticated consumer-role users to make the server issue HTTP requests to internal network addresses by registering a webhook URL pointing to an internal host. The webhook registration endpoint validates URL syntax via FILTER_VALIDATE_URL but applies no IP or host denylist. When the registered event fires, the server issues an HTTP POST to the attacker-supplied internal URL.

Quoted source text, attributed separately from HOL analysis.