CVE-2025-65036
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. Prior to 1.27.1, the macro executes Velocity from the details pages without checking for permissions, which can lead to remote code execution. This vulnerability is fixed in 1.27.1.
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 component has a missing authorization vulnerability where macros execute Velocity code from details pages without permission checks, allowing unauthenticated or low-privileged users to execute arbitrary Velocity scripts and achieve remote code execution.
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.27.1CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
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 Remote Macros extension is installedIn XWiki, navigate to the Extension Manager and search for 'Remote Macros' or check the installed extensions list for the Remote Macros extension.Affected if The Remote Macros extension appears in the installed extensions list.
-
Check installed version of Remote MacrosIn the Extension Manager details for Remote Macros, note the version number displayed. Compare it against the affected version range of versions prior to 1.27.1.Affected if The installed version is lower than 1.27.1 (for example, 1.27.0, 1.26.x, or earlier).
-
Confirm macro execution from details pages is accessibleAccess the macro details page for any remote macro (typically found at /bin/view/Macros/ or similar path depending on your XWiki setup) and verify if macros execute Velocity code from this page.Affected if The details page renders and executes Velocity content without elevated permission checks.
-
Verify user access permissions to macro detailsTest accessing the Remote Macros details page while logged in as a low-privilege or standard authenticated user. Check if the macro execution occurs without requiring admin rights.Affected if Standard authenticated users can trigger macro execution from details pages.
You are affected if the Remote Macros extension is installed with a version prior to 1.27.1 and macros can execute Velocity code from details pages accessible to authenticated users.
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.27.1
Upgrade XWiki Remote Macros to version 1.27.1 or later to apply the permission checks. If immediate upgrade is not possible, disable the Remote Macros functionality until the patch can be applied.
1.27.1
- Identify the current installed version of the Pro Macros extension in your XWiki instance
- Access the XWiki administration interface or check the extension manager
- Locate the Pro Macros (or Remote Macros) extension
- Upgrade the extension to version 1.27.1 or later
- Verify the upgrade completed successfully
- Test that the macro execution now properly checks permissions before allowing Velocity execution
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-65036 — 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-65036 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