The XWiki JIRA extension allows data leak through an XXE attack by using a fake JIRA server

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2025-31487: 0.40% estimated exploitation activity in the next 30 days; percentile 34.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact If the JIRA macro is installed, any logged in XWiki user could edit his/her user profile wiki page and use that JIRA macro, specifying a fake JIRA URL that returns an XML specifying a DOCTYPE pointing to a local file on the XWiki server host and displaying that file's content in one of the returned JIRA fields (such as the summary or description for example). For example: Patches The vulnerability has been patched in the JIRA Extension v8.6.5. Workarounds No easy workaround except to upgrade (which is easy using the XWiki Extension Manager). References https://github.com/xwiki-contrib/jira/commit/98a74c2a516b42689c73b13ecd94e9c1998fa9cb and https://github.com/xwiki-contrib/jira/commit/5049e352d16f8356734de70daf1202301f170ee6 https://jira.xwiki.org/browse/JIRA-49 For more information If you have any questions or comments about this advisory: Open an issue in Jira XWiki.org Email us at Security Mailing List

Published by the source

4 Apr 2025, 14:20 UTC

Last modified by the source

4 Apr 2025, 14:20 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wc53-4255-gw3f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-31487

Advisory: The XWiki JIRA extension allows data leak through an XXE attack by using a fake JIRA server
IDs: CVE-2025-31487, GHSA-wc53-4255-gw3f
Record: https://patchnext.com/advisories/cve-2025-31487 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.xwiki.contrib.jira:jira-macro-default 8.5.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.xwiki.contrib.jira:jira-macro-default: affected >= 4.2, < 8.5.6; fixed in 8.5.6

## Suggested inspection (read-only)
- Maven org.xwiki.contrib.jira:jira-macro-default: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.xwiki.contrib.jira:jira-macro-default.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wc53-4255-gw3f (GitHub-reviewed advisory GHSA-wc53-4255-gw3f lists affected ranges: Maven org.xwiki.contrib.jira:jira-macro-default >=4.2 <8.5.6)

Commands are suggestions: review each one before running it.