CVE-2022-41928

Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') in AttachmentSelector.xml

Workarounds

No known workaround.

References

• https://jira.xwiki.org/browse/XWIKI-19800

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

Any user with the right to edit his personal page can follow one of the scenario below:

Scenario 1:

• Log in as a simple user with just edit rights on the user profile
• Go to the user's profile
• Upload an attachment in the attachment tab at the bottom of the page (any image is fine)
• Click on "rename" in the attachment list and enter {{async async="true" cached="false" context="doc.reference"}}{{groovy}}println("Hello from groovy!"){{/groovy}}{{/async}}.png as new attachment name and submit the rename
• Go back to the user profile
• Click on the edit icon on the user avatar
• Hello from groovy! is displayed as the title of the attachment

Scenario 2:

• Log in as a simple user with just edit rights on a page
• Create a Page MyPage.WebHome
• Create an XClass field of type String named avatar
• Add an XObject of type MyPage.WebHome on the page
• Insert an attachmentSelector macro in the document with the following values:
  • classname: MyPage.WebHome
  • property: avatar
  • savemode: direct
  • displayImage: true
  • width: ]] {{async async="true" cached="false" context="doc.reference"}}{{groovy}}println("Hello from groovy!"){{/groovy}}{{/async}}. You'll find below a snippet of an attachmentSelector macro declaration.
• Display the page
• Use the attachment picker to select an image
• Hello from groovy is displayed aside the image

Example of an attachmentSelector macro declaration:

`{{attachmentSelector classname="MyPage.WebHome" property="avatar" savemode="direct" displayImage="true" width="]] {{async async=~"true~" cached=~"false~" context=~"doc.reference~"~}~}{{groovy~}~}println(~"Hello from groovy!~"){{/groovy~}~}{{/async~}~}"/}}`

Note: The issue can also be reproduced by inserting the dangerous payload in the height or alt macro properties.

CVE-2022-41928 has a CVSS score of 9.9 (Critical). 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 (13.10.7, 14.4.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The issue can be fixed on a running wiki by updating XWiki.AttachmentSelector with the versions below:

• 14.5-rc-1+: https://github.com/xwiki/xwiki-platform/commit/eb15147adf94bddb92626f862c1710d45bcd64a7#diff-e1513599ab698991f6cbba55d38f3f464432ced8d137a668b1f7618c7e747e23
• 14.4.2+: https://github.com/xwiki/xwiki-platform/commit/c02f8eb1f3c953d124f2c097021536f8bc00fa8d#diff-e1513599ab698991f6cbba55d38f3f464432ced8d137a668b1f7618c7e747e23
• 13.10.7+: https://github.com/xwiki/xwiki-platform/commit/efd0df0468d46149ba68b66660b93f31b6318515#diff-e1513599ab698991f6cbba55d38f3f464432ced8d137a668b1f7618c7e747e23

1. What is CVE-2022-41928? CVE-2022-41928 is a critical-severity security vulnerability in org.xwiki.platform:xwiki-platform-attachment-ui (maven), affecting versions >= 5.0-milestone-1, < 13.10.7. It is fixed in 13.10.7, 14.4.2.
2. How severe is CVE-2022-41928? CVE-2022-41928 has a CVSS score of 9.9 (Critical). 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-attachment-ui are affected by CVE-2022-41928? org.xwiki.platform:xwiki-platform-attachment-ui (maven) versions >= 5.0-milestone-1, < 13.10.7 is affected.
4. Is there a fix for CVE-2022-41928? Yes. CVE-2022-41928 is fixed in 13.10.7, 14.4.2. Upgrade to this version or later.
5. Is CVE-2022-41928 exploitable, and should I be worried? Whether CVE-2022-41928 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-41928 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-41928?
   • Upgrade org.xwiki.platform:xwiki-platform-attachment-ui to 13.10.7 or later
   • Upgrade org.xwiki.platform:xwiki-platform-attachment-ui to 14.4.2 or later

Other vulnerabilities in org.xwiki.platform:xwiki-platform-attachment-ui