CVE-2025-55728
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 · uneditedXWiki 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 classes parameter in the panel macro allows remote code execution for any user who can edit any page The classes parameter is used without escaping in XWiki syntax, thus allowing XWiki syntax injection which enables remote code execution. 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 confidenceThe XWiki Remote Macros plugin versions 1.0 through 1.26.4 fail to properly escape the 'classes' parameter in the panel macro. This parameter is used directly in XWiki syntax without sanitization, enabling an authenticated attacker with page edit permissions to inject malicious XWiki syntax and achieve remote code execution on the server.
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>= 1.0, < 1.26.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify XWiki Remote Macros plugin is installedCheck your XWiki installation for the presence of the Remote Macros plugin. This is typically done through the XWiki administration interface under installed extensions, or by searching for the plugin package in your installation directories.Affected if The Remote Macros plugin is found installed in the XWiki instance
-
Determine the installed version of XWiki Remote MacrosLocate the version information for the Remote Macros plugin through the XWiki extension manager, the plugin's JAR file metadata, or the extension descriptor. Compare this version against the affected range.Affected if The installed version is 1.0 through 1.26.4 inclusive
-
Identify use of the panel macro with the classes parameterSearch XWiki pages and content for usage of the panel macro that includes the 'classes' parameter. This can be done by searching wiki content for patterns like '((panel' or 'panel)' combined with 'classes='.Affected if The panel macro is used with the 'classes' parameter in any wiki page
-
Verify edit permissions on wiki pagesCheck the permission configuration for the wiki to determine which users or groups have page edit or macro execution rights, particularly for pages using the vulnerable panel macro with the classes parameter.Affected if Users other than trusted administrators have edit permissions on pages containing the vulnerable macro usage
The environment is affected if the XWiki Remote Macros plugin versions 1.0 through 1.26.4 are installed and the panel macro is used with the classes parameter on pages accessible to users with edit permissions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.26.5
Upgrade XWiki Remote Macros to version 1.26.5 or later which contains the patch for proper parameter escaping. If immediate upgrading is not possible, restrict page edit permissions to trusted users only.
1.26.5
- Identify all deployments using xwiki-pro-macros with version lower than 1.26.5
- Upgrade the xwiki-pro-macros extension to version 1.26.5 or later
- Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55728 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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