CVE-2025-27603 — application-confluence-mi…
CRITICALFix: xwikisas/application-confluence-migrator-pro@36cef22CVE-2025-27603 is a critical-severity (CVSS 9.1) CWE-95 vulnerability in com.xwiki.confluencepro:application-confluence-migrator-pro-ui. A fix is available for com.xwiki.confluencepro:application-confluence-migrator-pro-ui — see the affected versions and patch details below.
XWiki Confluence Migrator Pro allows Remote Code Execution via unescaped translations
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-27603.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-27603 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
com.xwiki.confluencepro:application-confluence-migrator-pro-uiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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:
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.TranslationDocumentClasswith scopeUSER. - 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.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.xwiki.confluencepro:application-confluence-migrator-pro-ui | ≥ 1.0&&< 1.2.0 | 1.2.0com.xwiki.confluencepro:application-confluence-migrator-pro-ui:1.2.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.xwiki.confluencepro:application-confluence-migrator-pro-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.xwiki.confluencepro:application-confluence-migrator-pro-ui to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27603 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-27603 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-27603. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-27603 in your dependencies?
O3 Security finds CVE-2025-27603 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.