dbcve.org
Pro MacrosApplication · Xwiki

CVE-2025-55727

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 1.26.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 Remote Macros provides XWiki rendering macros that are useful when migrating content from Confluence. Starting in version 1.0 and prior to version 1.26.5, missing escaping of the width parameter in the column macro allows remote code execution for any user who can edit any page or who can access the CKEditor converter. The width parameter is used without escaping in XWiki syntax, thus allowing XWiki syntax injection which enables remote code execution when the macro has been installed by a user with programming right, or it at least allows executing Velocity code as the wiki admin. Version 1.26.5 contains a patch for the issue.

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 · high confidence

The XWiki Remote Macros extension (versions 1.0-1.26.4) contains an RCE vulnerability in the column macro where the width parameter is not properly escaped, allowing XWiki syntax injection. Attackers with page edit rights or CKEditor converter access can inject malicious Velocity code that executes with programming-rights-level privileges.

MitigationUpgrade XWiki Remote Macros to version 1.26.5 or later. Until patched, restrict page edit permissions and monitor for unauthorized macro usage.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Pro MacrosApplication
Affected:>= 1.0, < 1.26.5

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify XWiki Remote Macros extension is installed
    Navigate to XWiki Administration > Extensions (or use the Extension Manager) and search for 'Remote Macros' to confirm it is installed.
    Affected if The Remote Macros extension appears in the installed extensions list.
  2. Check the installed version of Remote Macros
    In the Extension Manager, view the details of the Remote Macros extension to see its version number.
    Affected if The version is 1.0 through 1.26.4 (any version in the 1.0-1.26.4 range).
  3. Identify users with page edit permissions
    Go to XWiki Administration > Users and Groups, or check the rights on specific wikis and pages to see which users or groups have Edit or Admin rights.
    Affected if Multiple users or groups beyond administrators have edit permissions on any wiki page.
  4. Detect usage of the column macro
    Search your wiki content (using XWiki's search or grep across the database) for instances of '{{column' or 'column macro' to see if it is being used.
    Affected if The column macro from the Remote Macros extension is present in any wiki page content.
  5. Check CKEditor converter accessibility
    Verify if the CKEditor-to-WikiSyntax converter endpoint is accessible to non-admin users (check URL patterns like /bin/convert/ or similar converter endpoints in your XWiki).
    Affected if The CKEditor converter is accessible to users with edit rights.

You are affected if the XWiki Remote Macros extension versions 1.0-1.26.4 is installed AND the column macro is being used OR CKEditor converter is accessible to users with edit permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 1.26.5 or later
Fixed in 1.26.5
Vendor patch github.com →
Interim mitigation

Upgrade XWiki Remote Macros to version 1.26.5 or later. Until patched, restrict page edit permissions and monitor for unauthorized macro usage.

Recommended fix High confidence

1.26.5

  1. Identify the current version of Pro Macros installed in your XWiki instance
  2. Download or update to version 1.26.5 or later from the official XWiki extensions repository
  3. Install the new version following standard XWiki extension installation procedures
  4. Verify the patch was applied by checking the column macro's width parameter handling
  5. If possible, test that the width parameter is now properly escaped before allowing untrusted users to edit pages

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

Fix this in Pro Macros Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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