# CVE-2025-49582: XWiki's required right warnings for macros are incomplete > Incomplete macro security checks allow attackers to hide malicious scripts, leading to remote code execution when privileged users edit pages. - **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 13 Jun 2025 - **Updated:** 13 Jun 2025 - **Also known as:** GHSA-c32m-27pj-4xcj ## What is CVE-2025-49582? CVE-2025-49582 is a high-severity vulnerability in Xwiki Xwiki, published on 13 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description XWiki is a generic wiki platform. When editing content that contains "dangerous" macros like malicious script macros that were authored by a user with fewer rights, XWiki warns about the execution of these macros since XWiki 15.9RC1. These required rights analyzers that trigger these warnings are incomplete, allowing an attacker to hide malicious content. For most macros, the existing analyzers don't consider non-lowercase parameters. Further, most macro parameters that can contain XWiki syntax like titles of information boxes weren't analyzed at all. Similarly, the "source" parameters of the content and context macro weren't anylzed even though they could contain arbitrary XWiki syntax. In the worst case, this could allow a malicious to add malicious script macros including Groovy or Python macros to a page that are then executed after another user with programming righs edits the page, thus allowing remote code execution. The required rights analyzers have been made more robust and extended to cover those cases in XWiki 16.4.7, 16.10.3 and 17.0.0. Weakness: CWE-357 (Insufficient UI Warning of Dangerous Operations) ## Which versions are affected by CVE-2025-49582? 24 open source packages ship an affected version, including org.xwiki.platform:xwiki-platform-rendering-macro-cache, org.xwiki.platform:xwiki-platform-rendering-macro-context and org.xwiki.platform:xwiki-platform-rendering-xwiki. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.xwiki.platform:xwiki-platform-rendering-macro-cache` | Maven | From 15.9-rc-1 | 16.4.7 | | `org.xwiki.platform:xwiki-platform-rendering-macro-cache` | Maven | From 15.9-rc-1 | 16.4.7 | | `org.xwiki.platform:xwiki-platform-rendering-macro-cache` | Maven | From 16.5.0-rc-1 | 16.10.3 | | `org.xwiki.platform:xwiki-platform-rendering-macro-cache` | Maven | From 16.5.0-rc-1 | 16.10.3 | | `org.xwiki.platform:xwiki-platform-rendering-macro-cache` | Maven | From 17.0.0-rc-1 | 17.0.0 | | `org.xwiki.platform:xwiki-platform-rendering-macro-cache` | Maven | From 17.0.0-rc-1 | 17.0.0 | | `org.xwiki.platform:xwiki-platform-rendering-macro-context` | Maven | From 15.9-rc-1 | 16.4.7 | | `org.xwiki.platform:xwiki-platform-rendering-macro-context` | Maven | From 15.9-rc-1 | 16.4.7 | | `org.xwiki.platform:xwiki-platform-rendering-macro-context` | Maven | From 16.5.0-rc-1 | 16.10.3 | | `org.xwiki.platform:xwiki-platform-rendering-macro-context` | Maven | From 16.5.0-rc-1 | 16.10.3 | | `org.xwiki.platform:xwiki-platform-rendering-macro-context` | Maven | From 17.0.0-rc-1 | 17.0.0 | | `org.xwiki.platform:xwiki-platform-rendering-macro-context` | Maven | From 17.0.0-rc-1 | 17.0.0 | | `org.xwiki.platform:xwiki-platform-rendering-xwiki` | Maven | From 15.9-rc-1 | 16.4.7 | | `org.xwiki.platform:xwiki-platform-rendering-xwiki` | Maven | From 15.9-rc-1 | 16.4.7 | | `org.xwiki.platform:xwiki-platform-rendering-xwiki` | Maven | From 16.5.0-rc-1 | 16.10.3 | | `org.xwiki.platform:xwiki-platform-rendering-xwiki` | Maven | From 16.5.0-rc-1 | 16.10.3 | | `org.xwiki.platform:xwiki-platform-rendering-xwiki` | Maven | From 17.0.0-rc-1 | 17.0.0 | | `org.xwiki.platform:xwiki-platform-rendering-xwiki` | Maven | From 17.0.0-rc-1 | 17.0.0 | | `org.xwiki.platform:xwiki-platform-security-requiredrights-default` | Maven | From 15.9-rc-1 | 16.4.7 | | `org.xwiki.platform:xwiki-platform-security-requiredrights-default` | Maven | From 15.9-rc-1 | 16.4.7 | | `org.xwiki.platform:xwiki-platform-security-requiredrights-default` | Maven | From 16.5.0-rc-1 | 16.10.3 | | `org.xwiki.platform:xwiki-platform-security-requiredrights-default` | Maven | From 16.5.0-rc-1 | 16.10.3 | | `org.xwiki.platform:xwiki-platform-security-requiredrights-default` | Maven | From 17.0.0-rc-1 | 17.0.0 | | `org.xwiki.platform:xwiki-platform-security-requiredrights-default` | Maven | From 17.0.0-rc-1 | 17.0.0 | Products: Xwiki Xwiki. ## How do I fix CVE-2025-49582? Upgrade org.xwiki.platform:xwiki-platform-rendering-macro-cache to a fixed version for your release line: 16.4.7, 16.10.3 or 17.0.0. ## Is CVE-2025-49582 being exploited? There is no known exploitation of CVE-2025-49582 in the wild and no public exploit code. ## Other vulnerabilities in Xwiki Xwiki - [CVE-2025-24893](https://insights.sbomify.com/CVE-2025-24893/): XWiki Platform Eval Injection (critical 9.8, exploited in the wild) - [CVE-2025-53836](https://insights.sbomify.com/CVE-2025-53836/): XWiki Rendering is vulnerable to RCE attacks when processing nested macros (critical 10.0) - [CVE-2024-55662](https://insights.sbomify.com/CVE-2024-55662/): XWiki allows remote code execution through the extension sheet (critical 10.0) - [CVE-2024-55877](https://insights.sbomify.com/CVE-2024-55877/): XWiki allows remote code execution from account through macro descriptions and XWiki.XWikiSyntaxMacrosList (critical 10.0) - [CVE-2024-37901](https://insights.sbomify.com/CVE-2024-37901/): XWiki Platform vulnerable to remote code execution from account via SearchSuggestConfigSheet (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-49582 and fix it if it is affected. What it is: CVE-2025-49582 is a high-severity vulnerability in Xwiki Xwiki, published on 13 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-49582 in the wild and no public exploit code. Affected packages and fixed versions: - org.xwiki.platform:xwiki-platform-rendering-macro-cache (Maven): affected from 15.9-rc-1; fixed in 16.4.7 - org.xwiki.platform:xwiki-platform-rendering-macro-cache (Maven): affected from 15.9-rc-1; fixed in 16.4.7 - org.xwiki.platform:xwiki-platform-rendering-macro-cache (Maven): affected from 16.5.0-rc-1; fixed in 16.10.3 - org.xwiki.platform:xwiki-platform-rendering-macro-cache (Maven): affected from 16.5.0-rc-1; fixed in 16.10.3 - org.xwiki.platform:xwiki-platform-rendering-macro-cache (Maven): affected from 17.0.0-rc-1; fixed in 17.0.0 - org.xwiki.platform:xwiki-platform-rendering-macro-cache (Maven): affected from 17.0.0-rc-1; fixed in 17.0.0 - org.xwiki.platform:xwiki-platform-rendering-macro-context (Maven): affected from 15.9-rc-1; fixed in 16.4.7 - org.xwiki.platform:xwiki-platform-rendering-macro-context (Maven): affected from 15.9-rc-1; fixed in 16.4.7 - org.xwiki.platform:xwiki-platform-rendering-macro-context (Maven): affected from 16.5.0-rc-1; fixed in 16.10.3 - org.xwiki.platform:xwiki-platform-rendering-macro-context (Maven): affected from 16.5.0-rc-1; fixed in 16.10.3 - org.xwiki.platform:xwiki-platform-rendering-macro-context (Maven): affected from 17.0.0-rc-1; fixed in 17.0.0 - org.xwiki.platform:xwiki-platform-rendering-macro-context (Maven): affected from 17.0.0-rc-1; fixed in 17.0.0 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-49582/ (Markdown: https://insights.sbomify.com/CVE-2025-49582/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-49582 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-49582 - OSV: https://osv.dev/vulnerability/CVE-2025-49582 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-49582/ Summaries are generated and may contain mistakes; the official description above is the record.