Obfuscated email addresses should not be sorted

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2023-38509: 0.82% estimated exploitation activity in the next 30 days; percentile 57.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The mail obfuscation configuration was not fully taken into account and is was still possible by obfuscated emails. See https://jira.xwiki.org/browse/XWIKI-20601 for the reproduction steps. Patches This has been patched in XWiki 14.10.9, and XWiki 15.3-rc-1. Workarounds The workaround is to modify the page XWiki.LiveTableResultsMacros following this patch. References - https://jira.xwiki.org/browse/XWIKI-20601 - https://github.com/xwiki/xwiki-platform/commit/1dfb6804d4d412794cbe0098d4972b8ac263df0c 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

Published by the source

27 Jul 2023, 19:28 UTC

Last modified by the source

18 Mar 2024, 19:55 UTC

Source last checked

26 Oct 2026, 16:29 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g9w4-prf3-m25g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-38509

Advisory: Obfuscated email addresses should not be sorted
IDs: CVE-2023-38509, GHSA-g9w4-prf3-m25g
Record: https://patchnext.com/advisories/cve-2023-38509 (revision 1, source checked 26 Oct 2026, 16:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.xwiki.platform:xwiki-platform-livetable-ui 15.3-rc-1, 14.10.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.xwiki.platform:xwiki-platform-livetable-ui: affected >= 3.5-milestone-1, < 14.10.9; >= 15.0, < 15.3-rc-1; fixed in 15.3-rc-1, 14.10.9

## Suggested inspection (read-only)
- Maven org.xwiki.platform:xwiki-platform-livetable-ui: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.xwiki.platform:xwiki-platform-livetable-ui.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g9w4-prf3-m25g (GitHub-reviewed advisory GHSA-g9w4-prf3-m25g lists affected ranges: Maven org.xwiki.platform:xwiki-platform-livetable-ui >=3.5-milestone-1 =15.0 <15.3-rc-1)

Commands are suggestions: review each one before running it.