# XWiki Platform vulnerable to privilege escalation via async macro and IconThemeSheet from the user profile Advisory record · `GHSA-vwr6-qp4q-2wj7` - **Identifiers:** `GHSA-vwr6-qp4q-2wj7` · `CVE-2023-26472` - **State:** Confirmed - **Severity:** CVSS 10.0 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-116](https://cwe.mitre.org/data/definitions/116.html) - **Tags:** [CWE-116](https://agentprime.io/advisories/tag/cwe-116.md) - **Published:** 3 Mar 2023 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 3 Mar 2023, 22:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 10.0: 9.0 or more. How we decide what’s critical: ## Affected packages - `org.xwiki.platform:xwiki-platform-icon-ui` (Maven): affected `>=6.2-milestone-1, <13.10.10 || >=14.0, <14.4.6 || >=14.5, <14.9`; fixed in `13.10.10`, `14.4.6`, `14.9` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > XWiki Platform's xwiki-platform-icon-ui Maven package is vulnerable in versions from 6.2-milestone-1 up to 13.10.10, from 14.0 up to 14.4.6, and from 14.5 up to 14.9. A user who can create an icon theme, including users without edit rights through their own profile, can run wiki content with the rights of the IconThemeSheet author, which enables privilege escalation. Upgrade to 13.10.10, 14.4.6, or 14.9. The source's workaround is to apply a code change to the IconThemeSheet page, which is not practical for most readers, so upgrading is the recommended fix. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 10.0 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.011, the 66th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:18 UTC: First seen by agentprime - 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vwr6-qp4q-2wj7) ## Sources - [GitHub Advisory Database: GHSA-vwr6-qp4q-2wj7](https://github.com/advisories/GHSA-vwr6-qp4q-2wj7) - [OSV: GHSA-vwr6-qp4q-2wj7](https://osv.dev/vulnerability/GHSA-vwr6-qp4q-2wj7) - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .