CVE-2025-27603

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

Workarounds

There are no known workarounds besides upgrading.

References

No references.

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:

confluencepro.job.question.advanced.input={{/html}} {{async async="true" cached="false" context="doc.reference"}}{{groovy}}println("hello from groovy!"){{/groovy}}{{/async}}

• Use the object editor to add an object of type XWiki.TranslationDocumentClass with scope USER.
• Access an unexisting page using the MigrationTemplate

http://localhost:8080/xwiki/bin/edit/Page123?template=ConfluenceMigratorPro.Code.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.

CVE-2025-27603 has a CVSS score of 9.1 (Critical). The vector is network-reachable, high privileges required, and no user interaction. 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.2.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The issue will be fixed as part of v1.2. The fix was added with commit 35cef22

1. What is CVE-2025-27603? CVE-2025-27603 is a critical-severity security vulnerability in com.xwiki.confluencepro:application-confluence-migrator-pro-ui (maven), affecting versions >= 1.0, < 1.2.0. It is fixed in 1.2.0.
2. How severe is CVE-2025-27603? CVE-2025-27603 has a CVSS score of 9.1 (Critical). 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.confluencepro:application-confluence-migrator-pro-ui are affected by CVE-2025-27603? com.xwiki.confluencepro:application-confluence-migrator-pro-ui (maven) versions >= 1.0, < 1.2.0 is affected.
4. Is there a fix for CVE-2025-27603? Yes. CVE-2025-27603 is fixed in 1.2.0. Upgrade to this version or later.
5. Is CVE-2025-27603 exploitable, and should I be worried? Whether CVE-2025-27603 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-27603 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-27603? Upgrade com.xwiki.confluencepro:application-confluence-migrator-pro-ui to 1.2.0 or later.

Other vulnerabilities in com.xwiki.confluencepro:application-confluence-migrator-pro-ui