Skip to content

← Public intelligence

Maven package

com.xwiki.confluencepro:application-confluence-migrator-pro-ui

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5MavenPublished

    com.xwiki.confluencepro:application-confluence-migrator-pro-ui's application homepage is public

    CVE-2025-27604 · GHSA-3w9f-2pph-j5vc

    Affected
    • Maven com.xwiki.confluencepro:application-confluence-migrator-pro-ui <= 1.11.6
    Fixed in
    1.11.7· Vendor fix available
    Issue
    Impact The homepage of the application is public which enables a guest to download the package which might contain sensitive information. Patches 1.11.7 Workarounds The access to the page can be manually restricted to a specific set of users or groups.

    Recommended action: Upgrade to 1.11.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Critical, CVSS 9.1MavenPublished

    com.xwiki.confluencepro:application-confluence-migrator-pro-ui Remote Code Execution via unescaped translations

    CVE-2025-27603 · GHSA-6qvp-39mm-95v8

    Affected
    • Maven com.xwiki.confluencepro:application-confluence-migrator-pro-ui >= 1.0, < 1.2.0
    Fixed in
    1.2.0· Vendor fix available
    Issue
    Impact A user that doesn't have programming rights can execute arbitrary code when creating a page using the Migration Page template. A possible attack vector is the following: Create a page and add the following content: Use the object editor to add an object of type XWiki.TranslationDocumentClass with scope USER. Access an unexisting page using the MigrationTemplate It is expected that {{/html}} {{async async="true" cached="false" context="doc.reference"}}{{groovy}}println("hello from groovy!"){{/groovy}}{{/async}} will be present on the page, however, hello from groovy will be printed. Patches The issue will be fixed as part of v1.2. The fix was added with commit 35cef22 Workarounds There are no known workarounds besides upgrading. References No references.

    Recommended action: Upgrade to 1.2.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →