dbcve.org
XwikiApplication

CVE-2026-24128

MEDIUM · 6.1 CVSS v3.1 Published 2026-01-24
Fix available
A fix is available. Upgrade to 16.10.12 / 17.4.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Versions 7.0-milestone-2 through 16.10.11, 17.0.0-rc-1 through 17.4.4, and 17.5.0-rc-1 through 17.7.0 contain a reflected Cross-site Scripting (XSS) vulnerability, which allows an attacker to craft a malicious URL and execute arbitrary actions with the same privileges as the victim. If the victim has administrative or programming rights, those rights can be exploited to gain full access to the XWiki installation. This issue has been patched in versions 17.8.0-rc-1, 17.4.5 and 16.10.12. To workaround, the patch can be applied manually, only a single line in templates/logging_macros.vm needs to be changed, no restart is required.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-79

Untrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.

General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XwikiApplication
Affected:>= 7.0.1, < 16.10.12>= 17.0.1, < 17.4.5>= 17.6.0, < 17.8.0= 7.0= 17.0.0
Xwiki RenderingApplication
Affected:= 17.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 16.10.12 / 17.4.5 / 17.8.0 or later
Fixed in 16.10.1217.4.517.8.0
Vendor patch github.com →
Recommended fix High confidence

Upgrade to XWiki 16.10.12 (for 7.x-16.x lines), 17.4.5 (for 17.0.x-17.4.x), or 17.8.0 (for 17.6.x-17.7.x) depending on current version

  1. 1. Identify the currently installed XWiki version by checking the application or system administration panel
  2. 2. For XWiki versions >= 7.0.1 and < 16.10.12, or version 7.0: Upgrade to version 16.10.12 or later
  3. 3. For XWiki versions >= 17.0.1 and < 17.4.5: Upgrade to version 17.4.5 or later
  4. 4. For XWiki versions >= 17.6.0 and < 17.8.0: Upgrade to version 17.8.0 or later
  5. 5. For XWiki Rendering version 17.5.0: Upgrade to version 17.8.0 or later
  6. 6. After upgrade, verify the logging_macros.vm template has been patched by reviewing the commit at the vendor patch URL
  7. 7. Test the application to ensure the XSS vulnerability is resolved and no regressions were introduced
Caveat Review XWiki upgrade notes for your specific version jump as some deprecated features may have been removed; major version jumps may require migration steps

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24128 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24128 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data