dbcve.org
XwikiApplication

CVE-2023-29508

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-16
Fix available
A fix is available. Upgrade to 13.10.11 / 14.4.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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. A user without script rights can introduce a stored XSS by using the Live Data macro, if the last author of the content of the page has script rights. This has been patched in XWiki 14.10, 14.4.7, and 13.10.11.

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 · high confidence

Stored XSS vulnerability in XWiki's Live Data macro where an attacker without script rights can inject malicious JavaScript that executes in the context of a user who has script rights (the last author of the page content), allowing privilege escalation.

MitigationUpgrade XWiki to version 14.10, 14.4.7, or 13.10.11 (or later) to patch this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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:< 13.10.11>= 14.4.0, < 14.4.7= 14.10

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your XWiki version
    Locate the XWiki version information, typically found in the application admin panel, version.properties file, or about page. Compare your installed version against the affected ranges: < 13.10.11; >= 14.4.0 and < 14.4.7; = 14.10
    Affected if Your XWiki version falls into any of these ranges: < 13.10.11, >= 14.4.0 but < 14.4.7, or exactly 14.10
  2. Identify pages using the Live Data macro
    Search your XWiki installation for pages containing the 'liveData' macro (often written as {{liveData/}} or with parameters). Check the page source or use XWiki's search functionality to find all macro invocations.
    Affected if Any page in your wiki uses the Live Data macro and your version is vulnerable
  3. Inspect Live Data macro definitions for suspicious content
    Review the source of pages containing the Live Data macro. Examine any parameters that accept user input, particularly 'source', 'columns', 'filters', or 'sort' parameters for encoded or unusual characters.
    Affected if The Live Data macro contains unsanitized user-controlled input in its parameters, especially values that could be interpreted as JavaScript
  4. Verify permission configuration on affected pages
    Check which users have edit rights on pages using the Live Data macro. Specifically identify if users WITHOUT script programming rights can edit pages containing Live Data macro content.
    Affected if Users without script rights can edit pages where the last author has script rights, allowing the XSS attack vector

You are affected if your XWiki version is vulnerable AND pages using the Live Data macro contain unsanitized user input, with the additional condition that users without script rights can edit those pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.11 / 14.4.7 or later
Fixed in 13.10.1114.4.7
Interim mitigation

Upgrade XWiki to version 14.10, 14.4.7, or 13.10.11 (or later) to patch this vulnerability.

Recommended fix High confidence

13.10.11, 14.4.7, or 14.10

  1. Backup your XWiki instance and database before upgrading
  2. Upgrade to XWiki 13.10.11, 14.4.7, or 14.10 (choose the release appropriate for your current major version)
  3. Restart the XWiki application server
  4. Verify the upgrade was successful by logging in and checking the Live Data macro functionality

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

Fix this in Xwiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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