CVE-2025-65089
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 version 1.27.0, a user with no view rights on a page may see the content of an office attachment displayed with the view file macro. This issue has been patched in version 1.27.0.
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 confidenceXWiki Remote Macros before version 1.27.0 contains an authorization bypass vulnerability where the view file macro displays office attachment content to users who lack view rights on the parent page. This is an Access Control List (ACL) bypass allowing unauthorized information disclosure of attached documents.
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.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 extension is installedIn XWiki admin interface, go to Extension Manager and search for 'Remote Macros' or check the installed extensions list for 'org.xwiki.rendering:xwiki-rendering-remote-macros'Affected if The extension is installed and version is below 1.27.0
-
Check the installed version numberIn Extension Manager, view the details of the Remote Macros extension to see the exact version number, or query via XWiki's REST API: GET /rest/extensions/org.xwiki.rendering:xwiki-rendering-remote-macrosAffected if Version is lower than 1.27.0
-
Identify office attachments in the wikiSearch for attachments with office document types (.doc, .docx, .xls, .xlsx, .ppt, .pptx, .odt, .ods, .odp) using the attachments API or browsing pages with attachment tablesAffected if Office attachments exist in the wiki and are accessible via the view file macro
-
Verify view file macro usage with office attachmentsLocate documents using the viewfile or view attachment macro to display office attachment content, particularly checking if these macros are placed on pages with restricted accessAffected if The view file macro is used to display office attachments on pages where users may not have view permissions on the parent document
-
Test ACL bypass conditionAs a user WITHOUT view rights on a document containing office attachments, attempt to access that document through the view file macro (e.g., using URL pattern /bin/viewfile/PageName/AttachmentName)Affected if The user can view the office attachment content despite lacking view permission on the parent page
User is affected if XWiki Remote Macros version is below 1.27.0 AND office attachments exist that can be accessed via the view file macro by users lacking view rights on the parent document.
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.0
Upgrade XWiki Remote Macros to version 1.27.0 or later to apply the patch that enforces proper view permission checks on office attachments.
1.27.0
- Upgrade Pro Macros to version 1.27.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65089 — 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-65089 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