How severe is CVE-2023-29517?

CVE-2023-29517 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-29517?

CVE-2023-29517 affects the following packages: org.xwiki.platform:xwiki-platform-office-viewer (Maven), org.xwiki.platform:xwiki-platform-office-viewer (Maven), org.xwiki.platform:xwiki-platform-office-viewer (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-29517?

Update org.xwiki.platform:xwiki-platform-office-viewer to 13.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-29517 is resolved across your whole dependency graph.

How do I detect CVE-2023-29517 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-office-viewer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-29517 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2023-29517 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2023-29517, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-29517?

CVE-2023-29517 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-29517?

CVE-2023-29517 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-29517 published, and has it been updated?

CVE-2023-29517 was published on April 18, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2023-29517 — xwiki-platform-office-vie…

HIGH

CVE-2023-29517 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.xwiki.platform:xwiki-platform-office-viewer. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-office-viewer — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in org.xwiki.platform:xwiki-platform-office-viewer

Also known asGHSA-m3c3-9qj7-7xmx

Published

Apr 18, 2023

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

4 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-29517.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-office-viewer☕org.xwiki.platform:xwiki-platform-office-viewer☕org.xwiki.platform:xwiki-platform-office-viewer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The office document viewer macro was allowing anyone to see any file content from the hosting server, provided that the office server was connected and depending on the permissions of the user running the servlet engine (e.g. tomcat) running XWiki. The same vulnerability also allowed to perform internal requests to resources from the hosting server.

Patches

The problem has been patched in XWiki 13.10.11, 14.10.1, 14.4.8, 15.0-rc-1.

Workarounds

It might be possible to workaround this vulnerability by running XWiki in a sandbox with a user with very low privileges on the machine, now to run a servlet engine the user will always need access to some files, so in any case this workaround won't protect all files to be accessed.

References

Original jira ticket: https://jira.xwiki.org/browse/XWIKI-20447
Jira ticket related to another exploit using same root cause: https://jira.xwiki.org/browse/XWIKI-20324
Jira ticket related to the possibility to exploit the same vulnerability to perform internal requests: https://jira.xwiki.org/browse/XWIKI-20449

For more information

If you have any questions or comments about this advisory:

Open an issue in Jira XWiki.org
Email us at Security Mailing List

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-office-viewer`	≥ 2.5-milestone-2&&< 13.10.11	13.10.11`org.xwiki.platform:xwiki-platform-office-viewer:13.10.11`
☕Maven	`org.xwiki.platform:xwiki-platform-office-viewer`	≥ 14.0-rc-1&&< 14.4.8	14.4.8`org.xwiki.platform:xwiki-platform-office-viewer:14.4.8`
☕Maven	`org.xwiki.platform:xwiki-platform-office-viewer`	≥ 14.5&&< 14.10.1	14.10.1`org.xwiki.platform:xwiki-platform-office-viewer:14.10.1`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 14.5 && < 14.10.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

XWiki Platform is a generic wiki platform offering runtime services for …

github.comNVDApr 2023

Report on jira.xwiki.org

jira.xwiki.orgNVDApr 2023

Report on jira.xwiki.org

jira.xwiki.orgNVDApr 2023

Report on jira.xwiki.org

jira.xwiki.orgNVDApr 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-office-viewer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-office-viewer to 13.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-29517 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact The office document viewer macro was allowing anyone to see any file content from the hosting server, provided that the office server was connected and depending on the permissions of the user running the servlet engine (e.g. tomcat) running XWiki. The same vulnerability also allowed to perform internal requests to resources from the hosting server. ### Patches The problem has been patched in XWiki 13.10.11, 14.10.1, 14.4.8, 15.0-rc-1. ### Workarounds It might be possible to workaround this vulnerability by running XWiki in a sandbox with a user with very low privileges on the

O3 Security · Impact-Aware SCA

Is CVE-2023-29517 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-200Information Exposure

Weaponization

No Nuclei template or Metasploit module yet. 4 public proof-of-concept references are listed on this page.

Timeline

Disclosed

Apr 18, 2023

First exploit

Apr 28, 2023

Last updated

Oct 28, 2026

Identifiers

CVE-2023-29517

GHSA-m3c3-9qj7-7xmx

References

Advisorygithub.com · CVE 2023 29517.json Advisorygithub.com · GHSA m3c3 9qj7 7xmx Advisorynvd.nist.gov · CVE 2023 29517 Webjira.xwiki.org · XWIKI 20324 Webjira.xwiki.org · XWIKI 20447 Webjira.xwiki.org · XWIKI 20449 Packagegithub.com · xwiki platform

Related vulnerabilities

This CVE is high severity; 2 of 8 other CVEs with CWE-200 are rated as high or higher (top: high).

CVE-2026-55098GHSA-m3qr-fvp4-78xjCVE-2026-119199CVE-2026-118759CVE-2026-62264GHSA-473q-m89c-ghf8CVE-2026-116575CVE-2026-118666Browse all CWE-200

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-29517 — xwiki-platform-office-vie…

Exploitation Status

Proof-of-concept exploit code exists

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Workarounds

References

For more information

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-29517 in your dependencies?