CVE-2025-65089

A user with no view rights on a page may see the content of an office attachment displayed with the view file macro.

Details

If on a public page is displayed an office attachment from a restricted page, a user with no view rights on the restricted page can view the attachment content, no matter the display type used.

PoC

1. Install and activate the Pro Macros application
2. Create a page and limit the view rights for a test user
3. Add an attachment to the restricted page
4. Create a new public page
5. Add the view file macro and select the attachment from the restricted page using any display type
6. Login as the test user with restricted view rights
7. The user will see the content despite having no view rights

Workarounds

None

Private data can be leaked if a user knows the reference to an attachment and has edit rights on a page.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2025-65089 has a CVSS score of 6.8 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.27.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-65089? CVE-2025-65089 is a medium-severity missing authorization vulnerability in com.xwiki.pro:xwiki-pro-macros-ui (maven), affecting versions <= 1.26.20. It is fixed in 1.27.0. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2025-65089? CVE-2025-65089 has a CVSS score of 6.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of com.xwiki.pro:xwiki-pro-macros-ui are affected by CVE-2025-65089? com.xwiki.pro:xwiki-pro-macros-ui (maven) versions <= 1.26.20 is affected.
4. Is there a fix for CVE-2025-65089? Yes. CVE-2025-65089 is fixed in 1.27.0. Upgrade to this version or later.
5. Is CVE-2025-65089 exploitable, and should I be worried? Whether CVE-2025-65089 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-65089 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-65089? Upgrade com.xwiki.pro:xwiki-pro-macros-ui to 1.27.0 or later.