CVE-2024-31988

Xwiki remote code execution

9.6 CRITICALEPSS 0.70%

Published10 Apr 2024

Description

XWiki Platform is a generic wiki platform. Starting in version 13.9-rc-1 and prior to versions 4.10.19, 15.5.4, and 15.10-rc-1, when the realtime editor is installed in XWiki, it allows arbitrary remote code execution with the interaction of an admin user with programming right. More precisely, by getting an admin user to either visit a crafted URL or to view an image with this URL that could be in a comment, the attacker can get the admin to execute arbitrary XWiki syntax including scripting macros with Groovy or Python code. This compromises the confidentiality, integrity and availability of the whole XWiki installation. This vulnerability has been patched in XWiki 14.10.19, 15.5.4 and 15.9. As a workaround, one may update `RTFrontend.ConvertHTML` manually with the patch. This will, however, break some synchronization processes in the realtime editor, so upgrading should be the preferred way on installations where this editor is used.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionRequired

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

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

Affected products

Xwiki≥ 13.9 < 14.10.19 · ≥ 15.0 < 15.5.4 · ≥ 15.6 < 15.9

Remediation

Fixed in

Xwiki≥ 14.10.19

Frequently asked

Is CVE-2024-31988 being actively exploited?

CVE-2024-31988 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.70%.

How severe is CVE-2024-31988?

CVE-2024-31988 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.70% probability of exploitation.

Which products are affected by CVE-2024-31988?

Affected products include Xwiki.

How do I fix CVE-2024-31988?

Upgrade affected software to a fixed version, for example Xwiki 14.10.19 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-31988 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.