{"answers":{"affected":"2 open source packages ship an affected version, including org.xwiki.contrib.jira:jira-macro-default.","exploited":"There is no known exploitation of CVE-2025-31487 in the wild and no public exploit code.","fix":"Upgrade org.xwiki.contrib.jira:jira-macro-default to 8.5.6 or later.","what":"CVE-2025-31487 is a high-severity vulnerability in xwiki-contrib jira, published on 3 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-31487 and fix it if it is affected.\n\nWhat it is: CVE-2025-31487 is a high-severity vulnerability in xwiki-contrib jira, published on 3 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-31487 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.xwiki.contrib.jira:jira-macro-default (Maven): affected from 4.2; fixed in 8.5.6\n- org.xwiki.contrib.jira:jira-macro-default (Maven): affected from 4.2; fixed in 8.5.6\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-31487/ (Markdown: https://insights.sbomify.com/CVE-2025-31487/index.md)","id":"CVE-2025-31487","markdown":"https://insights.sbomify.com/CVE-2025-31487/index.md","name":"CVE-2025-31487","record":{"aliases":["GHSA-wc53-4255-gw3f"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"XWiki JIRA extension","requires_auth":"low_privilege","summary":"Logged-in users can leak local server files by configuring the JIRA macro to point to a malicious XML server.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"The XWiki JIRA extension provides various integration points between XWiki and JIRA (macros, UI, CKEditor plugin). 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). The vulnerability has been patched in the JIRA Extension v8.6.5.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"The XWiki JIRA extension allows data leak through an XXE attack by using a fake JIRA server","id":"CVE-2025-31487","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xxe","year":"2025"},"n_packages":2,"n_references":4,"next":{"headline":"Other in PCL2","id":"CVE-2025-31488"},"packages":[{"ecosystem":"Maven","fixed":["8.5.6"],"introduced":["4.2"],"last_affected":[],"package":"org.xwiki.contrib.jira:jira-macro-default","purl":null,"source":"GHSA-wc53-4255-gw3f"},{"ecosystem":"Maven","fixed":["8.5.6"],"introduced":["4.2"],"last_affected":[],"package":"org.xwiki.contrib.jira:jira-macro-default","purl":"pkg:maven/org.xwiki.contrib.jira/jira-macro-default","source":"GHSA-wc53-4255-gw3f"}],"prev":{"headline":"Vite allows server.fs.deny to be bypassed with .svg or relative paths","id":"CVE-2025-31486"},"products":["jira"],"published":"2025-04-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-03","vendors":["xwiki-contrib"]},"summary":"Logged-in users can leak local server files by configuring the JIRA macro to point to a malicious XML server.","url":"https://insights.sbomify.com/CVE-2025-31487/"}