# CVE-2023-32068: URL Redirection to Untrusted Site in XWiki > Attackers can redirect users to untrusted sites via crafted URLs, potentially facilitating phishing attacks against XWiki users. - **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 15 May 2023 - **Updated:** 22 Jan 2025 - **Also known as:** GHSA-6gvj-8vc5-8v3j ## What is CVE-2023-32068? CVE-2023-32068 is a medium-severity vulnerability in Xwiki Xwiki, published on 15 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. In versions prior to 14.10.4 it's possible to exploit well known parameters in XWiki URLs to perform redirection to untrusted site. This vulnerability was partially fixed in the past for XWiki 12.10.7 and 13.3RC1 but there is still the possibility to force specific URLs to skip some checks, e.g. using URLs like `http:example.com` in the parameter would allow the redirect. The issue has now been patched against all patterns that are known for performing redirects. This issue has been patched in XWiki 14.10.4 and 15.0. Users are advised to upgrade. There are no known workarounds for this vulnerability. Weakness: CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2023-32068? 2 open source packages ship an affected version, including org.xwiki.platform:xwiki-platform-oldcore. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.xwiki.platform:xwiki-platform-oldcore` | Maven | All versions | 14.10.4 | | `org.xwiki.platform:xwiki-platform-oldcore` | Maven | All versions | 14.10.4 | Products: Xwiki Xwiki. ## How do I fix CVE-2023-32068? Upgrade org.xwiki.platform:xwiki-platform-oldcore to 14.10.4 or later. ## Is CVE-2023-32068 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32068 exists. Public exploit code: - XWiki - Open Redirect (nuclei): http/cves/2023/CVE-2023-32068.yaml ## 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-2023-32068 and fix it if it is affected. What it is: CVE-2023-32068 is a medium-severity vulnerability in Xwiki Xwiki, published on 15 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32068 exists. Affected packages and fixed versions: - org.xwiki.platform:xwiki-platform-oldcore (Maven): affected all versions; fixed in 14.10.4 - org.xwiki.platform:xwiki-platform-oldcore (Maven): affected all versions; fixed in 14.10.4 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-32068/ (Markdown: https://insights.sbomify.com/CVE-2023-32068/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-32068 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-32068 - OSV: https://osv.dev/vulnerability/CVE-2023-32068 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-32068/ Summaries are generated and may contain mistakes; the official description above is the record.