Summary
CVE-2026-71878 is a missing-authentication vulnerability in the GBIF Integrated Publishing Toolkit (IPT) that leaves the application’s initial setup functionality exposed even after setup has been completed. Remote attackers can use this exposed functionality to reconfigure the application, create a new administrative account, and log in with full administrative control. The flaw carries a CVSS score of 9.2 (Critical).
Technical details
- Root cause: Setup wizard steps (implemented in the
SetupActioncomponent) are meant to run only once, but most steps validate the wrong condition — checking whether a later step has completed rather than their own — allowing setup actions to be re-executed after the instance is already configured. - Trigger conditions: An IPT instance that has already completed initial setup remains reachable via the same setup endpoints, with no authentication check preventing re-invocation.
- Attack vector: Network-based; no prior authentication or specialized tooling is required, only knowledge of the exposed setup endpoints.
- Impact: An attacker can reconfigure the application’s data directory, create a new administrative user, authenticate as that user, and obtain full administrative control of the IPT instance — resulting in high confidentiality and integrity impact.
Affected software
- GBIF Integrated Publishing Toolkit (IPT) — all versions prior to 3.3.4 (including 3.3.2)
Severity
- CVSS Score: 9.2 (Critical)
- Vector (CVSS v4.0):
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N - Weakness: CWE-306 – Missing Authentication for Critical Function
Mitigation and recommended actions
- Immediate: Upgrade GBIF IPT to version 3.3.4 or later, which fixes the setup-step state validation logic so each step correctly checks its own completion state.
- If immediate patching is not possible: Restrict network access to the IPT setup/admin interface (e.g., via firewall rules or reverse-proxy access controls) so it is not reachable from untrusted networks, and audit existing installations for unauthorized administrative accounts or unexpected data-directory configuration changes.
How IONIX identifies potentially affected assets
IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Meta tag
generator: content beginning withIPTfollowed by a version number (e.g.IPT 3.3.2)

