Summary iPlain-English security verdict for XWiki, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
XWiki currently scores 0/100 — critical. No tracked vulnerabilities are currently known to be exploited in the wild. Upgrade promptly to address the open critical vulnerabilities.
Disclosure trend iNew CVEs published for XWiki each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2023-29525 CRITICAL Injection EPSS 78% → fixed in 14.10.3 CVE-2023-32070 CRITICAL CWE-83 EPSS 1% → see advisory CVE-2026-33229 CRITICAL Missing authorization EPSS 1% → fixed in 17.10.1Get alerted about XWiki
Be emailed the moment XWiki gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for XWiki — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is XWiki safe and patched?
XWiki currently scores 0/100 — critical. No tracked vulnerabilities are currently known to be exploited in the wild. Upgrade promptly to address the open critical vulnerabilities.
What should I do about XWiki now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against XWiki's official advisory.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against XWiki's official advisory before you patch or upgrade — XWiki official site ↗