CVE-2022-41935 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in org.xwiki.platform:xwiki-platform-livetable-ui. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-livetable-ui — see the affected versions and patch details below.
Exposure of Sensitive Information to an Unauthorized Actor in org.xwiki.platform:xwiki-platform-livetable-ui
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-2022-41935.
EPSS Exploitation Probability
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
org.xwiki.platform:xwiki-platform-livetable-ui☕org.xwiki.platform:xwiki-platform-livetable-ui☕org.xwiki.platform:xwiki-platform-livetable-uiReal-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
User without the right to view documents can deduce their existence by repeated Livetable queries.
Reproduction steps
- Restrict "view" access to
Sandbox.TestPage3by setting an explicit view right for admins - As a user who is not an admin, open
<server>/bin/get/XWiki/LiveTableResults?outputSyntax=plain&classname=&collist=doc.title%2Cdoc.location%2Cdoc.content&doc.title=Sandbo&doc.location=Sandbox.TestPage3&doc.content=dummy&limit=0where<server>is the URL of your XWiki installation.
Expect Result:
No results are displayed as the user doesn't have view rights on Sandbox.TestPage3.
Actual Result:
The result
{
"reqNo": null,
"matchingtags": {},
"tags": [],
"totalrows": 1,
"returnedrows": 0,
"offset": 1,
"rows": [
{
"doc_viewable": false,
"doc_fullName": "obfuscated"
}
]
}
is displayed.
This reveals that a document Sandbox.TestPage3 exists (we explicitly searched for this name) which has a title containing "Sandbo" and a content containing "dummy". By starting with a single letter and then iteratively extending the match, the full content of the title/content or XObject properties can be discovered. Several tests can be combined in a single request to use binary search to narrow down the actual match from a list of possible characters/words. If the used alphabet is known and smaller than 128 distinct characters, it is possible to discover one character with 7 requests. Alternatively, frequencies of words and word pairs (2-gram frequencies) can be used to first guess whole words and only resort to guessing individual characters if none of the predicted words match, allowing a much faster recovery of the textual content. As it also depends on the content how easy the attack is and how much recovered content would be a "successful" attack, it is hard to quantify how many requests are necessary.
Patches
The issue has been patched in XWiki 14.6RC1, 13.10.8, and 14.4.3, the response is not properly cleaned up of obfuscated entries.
Workarounds
The patch for the document XWiki.LiveTableResultsMacros can be manually applied or a XAR archive of a patched version can be imported, on versions >= 12.10.11, >= 13.9-rc-1, and >= 13.4.4.
References
- https://github.com/xwiki/xwiki-platform/commit/1450b6e3c69ac7df25e5a2571186d1f43402facd#diff-5a739e5865b1f1ad9d79b724791be51b0095a0170cc078911c940478b13b949a
- https://jira.xwiki.org/browse/XWIKI-19999
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-livetable-ui | ≥ 12.10.11&&< 13.10.8 | 13.10.8org.xwiki.platform:xwiki-platform-livetable-ui:13.10.8 |
| ☕Maven | org.xwiki.platform:xwiki-platform-livetable-ui | ≥ 14.0.0&&< 14.4.3 | 14.4.3org.xwiki.platform:xwiki-platform-livetable-ui:14.4.3 |
| ☕Maven | org.xwiki.platform:xwiki-platform-livetable-ui | ≥ 14.5.0&&< 14.6-rc-1 | 14.6-rc-1org.xwiki.platform:xwiki-platform-livetable-ui:14.6-rc-1 |
Affected Products
xwikixwikiResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-livetable-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-livetable-ui to 13.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41935 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
Is CVE-2022-41935 in your dependencies?
Find it across Maven, including transitive dependencies.