dbcve.org
XwikiApplication

CVE-2022-41928

HIGH · 8.8 CVSS v3.1 Published 2022-11-23
Fix available
A fix is available. Upgrade to 13.10.7 / 14.4.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
XWiki Platform vulnerable to Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') in AttachmentSelector.xml. The issue can also be reproduced by inserting the dangerous payload in the `height` or `alt` macro properties. This has been patched in versions 13.10.7, 14.4.2, and 14.5. 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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XwikiApplication
Affected:> 5.0, < 13.10.7>= 14.0.0, < 14.4.2= 5.0= 14.4.3= 14.4.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 13.10.7 / 14.4.2 or later
Fixed in 13.10.714.4.2
Vendor patch github.com →
Recommended fix High confidence

13.10.7 (13.x branch) or 14.4.2/14.5 (14.x branch)

  1. 1. Backup your XWiki database and configuration files before proceeding with any upgrade.
  2. 2. For production environments, test the upgrade in a non-production environment first to identify any potential issues.
  3. 3. If you are on the 13.x branch (versions > 5.0 to < 13.10.7), upgrade to version 13.10.7 or later.
  4. 4. If you are on the 14.x branch (versions 14.0.0 to 14.4.1 or 14.4.3), upgrade to version 14.4.2 or later.
  5. 5. Alternatively, if you cannot upgrade the entire platform, you can update the XWiki.AttachmentSelector object on a running wiki using the patched code from the commits: for 14.5+ use commit eb15147adf94bddb92626f862c1710d45bcd64a7, for 14.4.2+ use commit c02f8eb1f3c953d124f2c097021536f8bc00fa8d, for 13.10.7+ use commit efd0df0468d46149ba68b66660b93f31b6318515.
  6. 6. After applying the fix, verify that the AttachmentSelector macro no longer accepts dangerous payloads in the `height` or `alt` properties.
Caveat XWiki platform minor version upgrades typically include compatibility but test thoroughly in non-production first as UI/configuration changes may occur

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41928 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41928 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data