IRONSMITHINTEL
CRITICALCVSS9.8
|
Actively Exploited
|CISA KEV|CVE-2025-24893|Auth: none — unauthenticated|Reboot: required|Manual only

XWiki Platform Eval Injection Vulnerability

XWiki Platform contains an eval injection vulnerability that could allow any guest to perform arbitrary remote code execution through a request to SolrSearch.

Published Feb 20, 2025 · Updated May 16, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2025-11-20 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-95) (CWE-95) vulnerability in XWiki Platform. Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

IT Security
Running xwiki: 5.4 ≤ v < 15.10.11, 16.0.0 ≤ v < 16.4.1, 5.3
Real-world incidentsWhat we've seen

Active exploitation documented in the wild. Threat-research write-up: https://jira.xwiki.org/browse/XWIKI-22149

How to patch

Manual remediation steps

Apply the Vendor Patch

This vulnerability is in the CISA Known Exploited Vulnerabilities catalog — apply the vendor's security update as soon as possible.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

References

    1
    Vendor advisory: https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-rr6p-3pfg-562j
    1
    NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2025-24893
    1
    CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24893
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.