Cross-site scripting in Integrated Publishing Toolkit
- Exploited
- No known exploitation
- Fix
- Fixed in 3.3.5
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.3.5.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.8/10CVSS 4.8
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.3.5.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- GBIF Integrated Publishing Toolkit
fixed in 3.3.5
Evidence 2
- Patch
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-71881
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: cve.now feed data
Which versions are affected by CVE-2026-71881?
Integrated Publishing Toolkit: before 3.3.5.Source: cve.now feed data
How do I fix CVE-2026-71881?
Upgrade to a fixed version: 3.3.5.Source: cve.now feed data