Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕ Maven

GHSA-vpx4-7rfp-h545

MEDIUM

Unprivileged XWiki Platform users can make arbitrary select queries using DatabaseListProperty and suggest.vm

Also known asCVE-2023-26473
Published
Mar 3, 2023
Updated
Nov 8, 2023
Affected
3 pkgs
Patched
3 / 3
Exploits
2 known

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk46th percentile+0.54%
0.00%0.38%0.76%1.14%0.2%0.6%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected
☕org.xwiki.platform:xwiki-platform-web☕org.xwiki.platform:xwiki-platform-web☕org.xwiki.platform:xwiki-platform-web

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

Any user with edit right can execute arbitrary database select and access data stored in the database.

To reproduce:

  • In admin, rights, remove scripting rights for {{XWikiAllGroup}}.
  • Create a new user without any special privileges.
  • Create a page "Private.WebHome" with {{TOKEN_42}} as content. Go to "page administration" and explicitly set all rights for "Admin" to remove them for all other users.
  • Logout and login as the unprivileged user. Ensure that the previously created page cannot be viewed.
  • Create a new page "ExploitClass.WebHome" and then open it in the class editor (first, make the user an advanced user).
  • Add a field named {{ContentList}} of type {{Database List}}
  • Enter in field "Hibernate Query" the following content: {noformat}select doc.content, doc.fullName from XWikiDocument as doc where doc.fullName = 'Private.WebHome'{noformat}
  • Save the class.
  • Open [http://localhost:8080/xwiki/bin/view/ExploitClass/?xpage=suggest&classname=ExploitClass.WebHome&fieldname=ContentList&firCol=doc.fullName&secCol=-]

Patches

The problem has been patched on XWiki 13.10.11, 14.4.7, and 14.10.

Workarounds

There is no workaround for this vulnerability other than upgrading.

References

https://jira.xwiki.org/browse/XWIKI-19523

For more information

If you have any questions or comments about this advisory:

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.xwiki.platform:xwiki-platform-web≥ 1.3-rc-1&&< 13.10.1113.10.11
☕Mavenorg.xwiki.platform:xwiki-platform-web≥ 14.0&&< 14.4.714.4.7
☕Mavenorg.xwiki.platform:xwiki-platform-web≥ 14.5&&< 14.1014.10
Exploits & PoCs
2

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. Starting in version 1.3-rc-1,…

jira.xwiki.orgNVDMar 2023

XWiki Platform is a generic wiki platform. Starting in version 1.3-rc-1,…

github.comNVDMar 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-web. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.xwiki.platform:xwiki-platform-web to 13.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vpx4-7rfp-h545 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-vpx4-7rfp-h545 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vpx4-7rfp-h545. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Any user with edit right can execute arbitrary database select and access data stored in the database. To reproduce: * In admin, rights, remove scripting rights for {{XWikiAllGroup}}. * Create a new user without any special privileges. * Create a page "Private.WebHome" with {{TOKEN_42}} as content. Go to "page administration" and explicitly set all rights for "Admin" to remove them for all other users. * Logout and login as the unprivileged user. Ensure that the previously created page cannot be viewed. * Create a new page "ExploitClass.WebHome" and then open it in the class
O3 Security · Impact-Aware SCA

Is GHSA-vpx4-7rfp-h545 in your dependencies?

O3 detects GHSA-vpx4-7rfp-h545 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works