CVE-2025-24893
XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. 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. This vulnerability has been patched in XWiki 15.10.11, 16.4.1 and 16.5.0RC1. Users are advised to upgrade. Users unable to upgrade may edit `Main.SolrSearchMacros` in `SolrSearchMacros.xml` on line 955 to match the `rawResponse` macro in `macros.vm#L2824` with a content type of `application/xml`, instead of simply outputting the content of the feed.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Cloudflare publishes WAF rules written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.
Cloudflare · 2 rules (Block) · since 5 May 2025
- XWiki - Remote Code Execution - CVE:CVE-2025-24893 · Cloudflare Managed Ruleset
- XWiki - Remote Code Execution - CVE:CVE-2025-24893 2 · Cloudflare Managed Ruleset
Also consider: patch · enable the vendor rule in block mode · remove eval sinks · RASP
Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-24893 being exploited?
Yes. CVE-2025-24893 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-24893?
CVE-2025-24893 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-24893?
Yes. A fix has been recorded for CVE-2025-24893. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-24893 affect?
CVE-2025-24893 affects xwiki:xwiki. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 5.3-milestone-2 and < 15.10.11
- affected>= 16.0.0-rc-1 and < 16.4.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Public exploit code: 2 on Exploit-DB · 1 Metasploit module · 45 GitHub proofs of concept · 1 Nuclei template
- XWiki Platform 15.10.10 - Metasploit Module for Remote Code Execution (RCE) · webapps · 16 Sept 2025
- XWiki Platform 15.10.10 - Remote Code Execution · webapps · 7 Apr 2025
- exploit/multi/http/xwiki_unauth_rce_cve_2025_24893 · exploit · excellent
- XWiki Platform - Remote Code Execution · detection template · critical
- gunzf0x/CVE-2025-24893 · 23 ★
- dollarboysushil/CVE-2025-24893-XWiki-Unauthenticated-RCE-Exploit-POC · 17 ★
- b0ySie7e/CVE-2025-24893 · 11 ★
- iSee857/CVE-2025-24893-PoC · 10 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 30 Oct 2025 (SSVC 2.0.3).
timeline
- 20 Feb 2025Published
- 25 Feb 2025First public exploit or proof of concept · 4 days later
- 30 Oct 2025Added to CISA KEV (exploited in the wild) · 247 days (about 8 months) later
- 30 Oct 2025CISA SSVC assessment: exploitation active · same day later
- 20 Nov 2025CISA remediation due date (US federal agencies) · 21 days later
- 26 Feb 2026CVE record last updated · 99 days (about 3 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
also known as
- Linkgithub.com /xwiki/xwiki-platform/security/advisories/GHSA-rr6p-3pfg-562j
- Linkgithub.com /xwiki/xwiki-platform/commit/67021db9b8ed26c2236a653269302a86bf01ef40
- Linkgithub.com /xwiki/xwiki-platform/blob/568447cad5172d97d6bbcfda9f6183689c2cf086/xwiki-platfo
- Linkgithub.com /xwiki/xwiki-platform/blob/67021db9b8ed26c2236a653269302a86bf01ef40/xwiki-platfo
- Linkjira.xwiki.org /browse/XWIKI-22149
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24893
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- Metasploit Framework: exploit and scanner modules
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.