dbcve.org
XwikiApplication

CVE-2025-49581

HIGH · 8.8 CVSS v3.1 Published 2025-06-13
Fix available
A fix is available. Upgrade to 12.0 / 12.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click 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 is a generic wiki platform. Any user with edit right on a page (could be the user's profile) can execute code (Groovy, Python, Velocity) with programming right by defining a wiki macro. This allows full access to the whole XWiki installation. The main problem is that if a wiki macro parameter allows wiki syntax, its default value is executed with the rights of the author of the document where it is used. This can be exploited by overriding a macro like the children macro that is used in a page that has programming right like the page XWiki.ChildrenMacro and thus allows arbitrary script macros. This vulnerability has been patched in XWiki 16.4.7, 16.10.3 and 17.0.0 by executing wiki parameters with the rights of the wiki macro's author when the parameter's value is the default value.

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-94

The application evaluates attacker-influenced input as code, handing them a way to run logic inside the process. Depending on the runtime this can escalate directly to remote code execution. Remediation means removing dynamic evaluation of untrusted input and replacing it with safe, data-driven alternatives.

General guidance for the code injection 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:>= 11.10.11, < 12.0>= 12.6.3, < 12.7>= 12.8, < 16.4.7>= 16.5.0, < 16.10.3= 17.0.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 12.0 / 12.7 / 16.4.7 or later
Fixed in 12.012.716.4.7
Vendor patch github.com →
Recommended fix High confidence

16.4.7, 16.10.3, or 17.0.0 (depending on current version branch)

  1. Identify the currently installed XWiki version using the administration dashboard or version lookup
  2. Review the upgrade path: versions 11.10.11 to <12.0 should upgrade to 12.0+ then to a fixed version; versions 12.6.3 to <12.7 should upgrade to 12.7+ then to a fixed version; versions 12.8 to <16.4.7 should upgrade to 16.4.7; versions 16.5.0 to <16.10.3 should upgrade to 16.10.3
  3. Plan the upgrade following XWiki's official upgrade documentation at https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/
  4. Before upgrading, perform a full backup of the XWiki database and configuration files
  5. Execute the upgrade to the target fixed version (16.4.7, 16.10.3, or the latest 17.x release)
  6. Verify the upgrade was successful by checking the version number in the administration interface
  7. Test that wiki macros with default parameter values execute with the macro author's rights (the fix behavior) rather than the document author's rights
  8. Confirm normal wiki functionality remains intact after the upgrade
Caveat Standard upgrade precautions apply - review release notes for breaking changes between versions, test in staging first

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 $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49581 — 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-2025-49581 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