How severe is CVE-2022-23621?

CVE-2022-23621 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-23621?

CVE-2022-23621 affects the following packages: org.xwiki.platform:xwiki-platform-oldcore (Maven), org.xwiki.platform:xwiki-platform-oldcore (Maven), org.xwiki.platform:xwiki-platform-oldcore (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-23621?

Update org.xwiki.platform:xwiki-platform-oldcore to 13.7-rc-1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23621 is resolved across your whole dependency graph.

How do I detect CVE-2022-23621 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-oldcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2022-23621 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-23621 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-23621?

CVE-2022-23621 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th 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-2022-23621?

CVE-2022-23621 is classified as CWE-862 (CWE-862), CWE-552 (CWE-552). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-23621 published, and has it been updated?

CVE-2022-23621 was published on February 9, 2022 and was last updated on August 12, 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

MEDIUM severity

CVE-2022-23621 — xwiki-platform-oldcore

MEDIUMFix: xwiki/xwiki-platform@df8bd49

CVE-2022-23621 is a medium-severity (CVSS 5.5) CWE-862 vulnerability in org.xwiki.platform:xwiki-platform-oldcore. A fix is available for org.xwiki.platform:xwiki-platform-oldcore — see the affected versions and patch details below.

Missing authorization in xwiki-platform

Also known asGHSA-2jhm-qp48-hv5j

Published

Feb 9, 2022

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2022-23621 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcore

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 SCRIPT right (EDIT right before XWiki 7.4) can read any file located in the XWiki WAR (for example xwiki.cfg and xwiki.properties) through XWiki#invokeServletAndReturnAsString:

$xwiki.invokeServletAndReturnAsString("/WEB-INF/xwiki.cfg")

Patches

It has been patched in XWiki versions 12.10.9, 13.4.3 and 13.7-rc-1.

Workarounds

The only workaround is to give SCRIPT right only to trusted users.

References

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

For more information

If you have any questions or comments about this advisory:

Open an issue in Jira XWiki
Email us at our security mailing list

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-oldcore`	≥ 13.6-rc-1&&< 13.7-rc-1	13.7-rc-1`org.xwiki.platform:xwiki-platform-oldcore:13.7-rc-1`
☕Maven	`org.xwiki.platform:xwiki-platform-oldcore`	≥ 13.0.0&&< 13.4.3	13.4.3`org.xwiki.platform:xwiki-platform-oldcore:13.4.3`
☕Maven	`org.xwiki.platform:xwiki-platform-oldcore`	all versions	12.10.9`org.xwiki.platform:xwiki-platform-oldcore:12.10.9`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 13.4.4 && ≤ 13.7

range

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-oldcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-oldcore to 13.7-rc-1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23621 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact Any user with SCRIPT right (EDIT right before XWiki 7.4) can read any file located in the XWiki WAR (for example xwiki.cfg and xwiki.properties) through XWiki#invokeServletAndReturnAsString: ``` $xwiki.invokeServletAndReturnAsString("/WEB-INF/xwiki.cfg") ``` ### Patches It has been patched in XWiki versions 12.10.9, 13.4.3 and 13.7-rc-1. ### Workarounds The only workaround is to give SCRIPT right only to trusted users. ### References https://jira.xwiki.org/browse/XWIKI-18870 ### For more information If you have any questions or comments about this advisory: * Open an issue