How severe is CVE-2025-24893?

CVE-2025-24893 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-24893?

CVE-2025-24893 affects the following packages: org.xwiki.platform:xwiki-platform-search-solr-ui (Maven), org.xwiki.platform:xwiki-platform-search-solr-ui (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-24893?

Update org.xwiki.platform:xwiki-platform-search-solr-ui to 15.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-24893 is resolved across your whole dependency graph.

How do I detect CVE-2025-24893 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-search-solr-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-24893 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2025-24893 actively exploited in the wild?

Yes. There are 13 known exploit references for CVE-2025-24893, including 2 documented proof-of-concept exploits on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-24893?

CVE-2025-24893 has an EPSS (Exploit Prediction Scoring System) score of 99.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2025-24893 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-24893 (XWiki Platform Eval Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-10-30. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-11-20. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-24893?

CVE-2025-24893 is classified as CWE-95 (CWE-95), Code Injection (CWE-94). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2025-24893?

A Nuclei detection template exists for CVE-2025-24893, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2025-24893 published, and has it been updated?

CVE-2025-24893 was published on February 20, 2025 and was last updated on October 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2025-24893 — xwiki-platform-search-sol…

CRITICALFix: xwiki/xwiki-platform@67021db

CVE-2025-24893 is a critical-severity (CVSS 9.8) CWE-95 vulnerability in org.xwiki.platform:xwiki-platform-search-solr-ui. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-10-30) — treat it as actively exploited and patch now. A fix is available for org.xwiki.platform:xwiki-platform-search-solr-ui — see the affected versions and patch details below.

Remote code execution as guest via SolrSearchMacros request in xwiki

Also known asGHSA-rr6p-3pfg-562j

Published

Feb 20, 2025

Updated

Oct 22, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

13 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-10-30. Federal agencies were required to remediate by 2025-11-20.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-24893.

EPSS Exploitation Probability

via FIRST.org ↗

99.9%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2025-24893 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.xwiki.platform:xwiki-platform-search-solr-ui☕org.xwiki.platform:xwiki-platform-search-solr-ui

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Any guest can perform arbitrary remote code execution through a request to SolrSearch. This impacts the confidentiality, integrity and availability of the whole XWiki installation.

To reproduce on an instance, without being logged in, go to <host>/xwiki/bin/get/Main/SolrSearch?media=rss&text=%7D%7D%7D%7B%7Basync%20async%3Dfalse%7D%7D%7B%7Bgroovy%7D%7Dprintln%28"Hello%20from"%20%2B%20"%20search%20text%3A"%20%2B%20%2823%20%2B%2019%29%29%7B%7B%2Fgroovy%7D%7D%7B%7B%2Fasync%7D%7D%20. If there is an output, and the title of the RSS feed contains Hello from search text:42, then the instance is vulnerable.

Patches

This vulnerability has been patched in XWiki 15.10.11, 16.4.1 and 16.5.0RC1.

Workarounds

This line in Main.SolrSearchMacros can be edited to match the rawResponse macro defined here with a content type of application/xml, instead of simply outputting the content of the feed.

References

Attribution

This vulnerability has been reported by John Kwak for Trend Micro's Zero Day Initiative.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-search-solr-ui`	≥ 5.3-milestone-2&&< 15.10.11	15.10.11`org.xwiki.platform:xwiki-platform-search-solr-ui:15.10.11`
☕Maven	`org.xwiki.platform:xwiki-platform-search-solr-ui`	≥ 16.0.0-rc-1&&< 16.4.1	16.4.1`org.xwiki.platform:xwiki-platform-search-solr-ui:16.4.1`

Affected Products

1 product · 5 configurations

Application

xwikixwiki

≥ 16.0.0 && < 16.4.1

1 version

5.3

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52429webappsmultiple

XWiki Platform 15.10.10 - Metasploit Module for Remote Code Execution (RCE)

by Maksim Rogov · Sep 16, 2025

Exploit-DB Source

EDB-52136webappsmultiple

XWiki Platform 15.10.10 - Remote Code Execution

by Al Baradi Joy · Apr 7, 2025

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-search-solr-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-search-solr-ui to 15.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-24893 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2025-24893

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2025-24893 -u https://target

Template: XWiki Platform - Remote Code Execution
Severity: critical
Impact: An attacker can execute arbitrary code on the server, leading to a complete compromise of the XWiki instance.
Remediation: Upgrade to XWiki 15.10.11, 16.4.1, or 16.5.0RC1 to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (iamnoooob, rootxharsh, pdresearch), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact Any guest can perform arbitrary remote code execution through a request to `SolrSearch`. This impacts the confidentiality, integrity and availability of the whole XWiki installation. To reproduce on an instance, without being logged in, go to `<host>/xwiki/bin/get/Main/SolrSearch?media=rss&text=%7D%7D%7D%7B%7Basync%20async%3Dfalse%7D%7D%7B%7Bgroovy%7D%7Dprintln%28"Hello%20from"%20%2B%20"%20search%20text%3A"%20%2B%20%2823%20%2B%2019%29%29%7B%7B%2Fgroovy%7D%7D%7B%7B%2Fasync%7D%7D%20`. If there is an output, and the title of the RSS feed contains `Hello from search text:42`, then the