CVE-2022-31167

XWiki Platform Security Parent POM vulnerable to overwriting of security rules of a page with a final page having the same reference

Workarounds

No workaround other than patching.

References

https://jira.xwiki.org/browse/XWIKI-14075
https://jira.xwiki.org/browse/XWIKI-18983

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

A bug in the security cache is storing rules associated to document Page1.Page2 and space Page1.Page2 in the same cache entry.

That means that it's possible to overwrite the rights of a space or a document by creating the page of the space with the same name and checking the right of the new one first so that they end up in the security cache and are used for the other too.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2022-31167 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.10.11, 13.4.6, 13.10.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem has been patched in XWiki 12.10.11, 13.10.1, 13.4.6.

1. What is CVE-2022-31167? CVE-2022-31167 is a high-severity missing authorization vulnerability in org.xwiki.platform:xwiki-platform-security (maven), affecting versions >= 5.0, < 12.10.11. It is fixed in 12.10.11, 13.4.6, 13.10.1. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2022-31167? CVE-2022-31167 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.xwiki.platform:xwiki-platform-security are affected by CVE-2022-31167? org.xwiki.platform:xwiki-platform-security (maven) versions >= 5.0, < 12.10.11 is affected.
4. Is there a fix for CVE-2022-31167? Yes. CVE-2022-31167 is fixed in 12.10.11, 13.4.6, 13.10.1. Upgrade to this version or later.
5. Is CVE-2022-31167 exploitable, and should I be worried? Whether CVE-2022-31167 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31167 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31167?
   • Upgrade org.xwiki.platform:xwiki-platform-security to 12.10.11 or later
   • Upgrade org.xwiki.platform:xwiki-platform-security to 13.4.6 or later
   • Upgrade org.xwiki.platform:xwiki-platform-security to 13.10.1 or later