Skip to content

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

High severity GitHub Reviewed Published Apr 3, 2025 in xwiki-contrib/jira • Updated Apr 4, 2025

Package

maven org.xwiki.contrib.jira:jira-macro-default (Maven)

Affected versions

>= 4.2, < 8.5.6

Patched versions

8.5.6

Description

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:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE foo [ <!ENTITY xxe SYSTEM "file:///etc/passwd"> ]>
<rss version="0.92">
...
    <item>
      <title>&xxe;</title>
      <link>https://jira.xwiki.org/browse/XE-307</link>
      <project id="10222" key="XE">{RETIRED} XWiki Enterprise</project>
      <description>&xxe;</description>
      <environment/>
...

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

For more information

If you have any questions or comments about this advisory:

References

@vmassol vmassol published to xwiki-contrib/jira Apr 3, 2025
Published by the National Vulnerability Database Apr 3, 2025
Published to the GitHub Advisory Database Apr 4, 2025
Reviewed Apr 4, 2025
Last updated Apr 4, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(6th percentile)

Weaknesses

CVE ID

CVE-2025-31487

GHSA ID

GHSA-wc53-4255-gw3f

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.