dbcve.org
CommonsApplication · Xwiki

CVE-2023-26055

CRITICAL · 9.9 CVSS v3.1 Published 2023-03-02
Fix available
A fix is available. Upgrade to 13.10.9 / 14.4.4 or later.
See remediation →
100/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 Commons are technical libraries common to several other top level XWiki projects. Starting in version 3.1-milestone-1, any user can edit their own profile and inject code, which is going to be executed with programming right. The same vulnerability can also be exploited in all other places where short text properties are displayed, e.g., in apps created using Apps Within Minutes that use a short text field. The problem has been patched on versions 13.10.9, 14.4.4, 14.7RC1.

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
CommonsApplication
Affected:>= 3.2, < 13.10.9>= 14.4, < 14.4.4>= 14.5, < 14.7= 3.1= 3.1.1= 14.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.9 / 14.4.4 / 14.7 or later
Fixed in 13.10.914.4.414.7
Vendor patch jira.xwiki.org →
Recommended fix High confidence

Upgrade to XWiki Commons 13.10.9, 14.4.4, or 14.7+ depending on your current branch

  1. 1. Identify the currently installed XWiki Commons version by checking your project dependencies or libraries
  2. 2. Determine which release branch you are on (13.x, 14.4.x, or 14.5+) to select the appropriate upgrade target
  3. 3. Backup your XWiki data and configuration before proceeding with the upgrade
  4. 4. Update the XWiki Commons dependency in your project to version 13.10.9 (for 13.x branch), 14.4.4 (for 14.4.x branch), or 14.7 or later (for 14.5+ branch)
  5. 5. Rebuild and redeploy the application
  6. 6. Verify that the short text property rendering no longer allows arbitrary code execution
Caveat Review release notes for the target version as minor/major version jumps may include breaking changes in API or configuration

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 $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26055 — 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-2023-26055 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