# CVE-2023-26055: XWiki Commons may allow privilege escalation to programming rights via user's first name > Attackers can inject code via user profile fields to execute arbitrary code with programming rights, requiring a patch in XWiki Commons. - **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Mar 2023 - **Updated:** 5 Mar 2025 - **Also known as:** GHSA-8cw6-4r32-6r3h ## What is CVE-2023-26055? CVE-2023-26055 is a critical code injection vulnerability in xwiki-commons, published on 2 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description XWiki Commons are technical libraries common to several other top level XWiki projects. Starting in version 3.1-milestone-1, any user can edit their own profile and inject code, which is going to be executed with programming right. The same vulnerability can also be exploited in all other places where short text properties are displayed, e.g., in apps created using Apps Within Minutes that use a short text field. The problem has been patched on versions 13.10.9, 14.4.4, 14.7RC1. Weakness: CWE-150 (Improper Neutralization of Escape, Meta, or Control Sequences) ## Which versions are affected by CVE-2023-26055? 6 open source packages ship an affected version, including org.xwiki.commons:xwiki-commons-xml. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.xwiki.commons:xwiki-commons-xml` | Maven | From 14.0-rc-1 | 14.4.4 | | `org.xwiki.commons:xwiki-commons-xml` | Maven | From 14.0-rc-1 | 14.4.4 | | `org.xwiki.commons:xwiki-commons-xml` | Maven | From 14.5 | 14.7-rc-1 | | `org.xwiki.commons:xwiki-commons-xml` | Maven | From 14.5 | 14.7-rc-1 | | `org.xwiki.commons:xwiki-commons-xml` | Maven | From 3.1-milestone-1 | 13.10.9 | | `org.xwiki.commons:xwiki-commons-xml` | Maven | From 3.1-milestone-1 | 13.10.9 | Products: Xwiki Commons. ## How do I fix CVE-2023-26055? Upgrade org.xwiki.commons:xwiki-commons-xml to a fixed version for your release line: 14.4.4, 14.7-rc-1 or 13.10.9. ## Is CVE-2023-26055 being exploited? There is no known exploitation of CVE-2023-26055 in the wild and no public exploit code. ## Other vulnerabilities in xwiki-commons - [CVE-2023-36471](https://insights.sbomify.com/CVE-2023-36471/): HTML sanitizer allows form elements in restricted in org.xwiki.commons:xwiki-commons-xml (critical 9.1) - [CVE-2023-29528](https://insights.sbomify.com/CVE-2023-29528/): Cross-site Scripting in org.xwiki.commons:xwiki-commons-xml (critical 9.1) - [CVE-2022-24898](https://insights.sbomify.com/CVE-2022-24898/): Arbitrary file access through XML parsing in org.xwiki.commons:xwiki-commons-xml (medium 4.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-26055 and fix it if it is affected. What it is: CVE-2023-26055 is a critical code injection vulnerability in xwiki-commons, published on 2 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-26055 in the wild and no public exploit code. Affected packages and fixed versions: - org.xwiki.commons:xwiki-commons-xml (Maven): affected from 14.0-rc-1; fixed in 14.4.4 - org.xwiki.commons:xwiki-commons-xml (Maven): affected from 14.0-rc-1; fixed in 14.4.4 - org.xwiki.commons:xwiki-commons-xml (Maven): affected from 14.5; fixed in 14.7-rc-1 - org.xwiki.commons:xwiki-commons-xml (Maven): affected from 14.5; fixed in 14.7-rc-1 - org.xwiki.commons:xwiki-commons-xml (Maven): affected from 3.1-milestone-1; fixed in 13.10.9 - org.xwiki.commons:xwiki-commons-xml (Maven): affected from 3.1-milestone-1; fixed in 13.10.9 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-2023-26055/ (Markdown: https://insights.sbomify.com/CVE-2023-26055/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-26055 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-26055 - OSV: https://osv.dev/vulnerability/CVE-2023-26055 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-26055/ Summaries are generated and may contain mistakes; the official description above is the record.