CVE-2025-24893
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 · uneditedXWiki 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.
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 confidenceUnauthenticated remote code execution vulnerability in XWiki Platform's SolrSearch endpoint. Attackers can inject Groovy scripts via URL parameters (text=) in the RSS feed request, leading to arbitrary command execution on the server without any authentication.
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>= 5.4, < 15.10.11>= 16.0.0, < 16.4.1= 5.3CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed XWiki versionCheck the version file in your XWiki installation directory, typically in WEB-INF/version.properties or through the XWiki administration interface under 'About'.Affected if The installed version is >= 5.4 and < 15.10.11, OR >= 16.0.0 and < 16.4.1, OR equals 5.3.
-
Verify SolrSearch component is activeConfirm that the SolrSearch feature is installed and enabled in your XWiki instance. This can be verified by checking if the SolrSearch extension is listed in the installed extensions through the XWiki administration panel.Affected if SolrSearch is installed and active in the environment.
-
Confirm guest user access to SolrSearchCheck the rights configuration for the SolrSearch page (typically at Main.SolrSearch or Main.SolrSearchMacros) and verify whether guest users (XWikiAllGroup) have view or execute permissions. This can be checked in the XWiki administration under 'Rights' or by inspecting the document rights in the database.Affected if Guest users (unauthenticated users) have view or execute rights to SolrSearch pages.
-
Inspect rawResponse macro configuration in SolrSearchMacrosLocate and examine the Main.SolrSearchMacros document in your XWiki installation. Specifically inspect line 955 (or nearby) where the rawResponse macro is defined. Check whether the content type is set to 'application/xml' or if it allows dynamic content type based on the media parameter.Affected if The rawResponse macro content type is NOT set to 'application/xml' (i.e., it uses a dynamic or default content type that can be influenced by the media parameter).
You are affected if your XWiki version falls within the affected ranges AND guest users have access to SolrSearch AND the rawResponse macro is not locked to application/xml content type.
Generated from the published advisory. Verify against your own configuration.
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 · scoped15.10.1116.4.1
Upgrade to XWiki 15.10.11, 16.4.1, or 16.5.0RC1 or later. Alternatively, edit Main.SolrSearchMacros in SolrSearchMacros.xml at line 955 to set the rawResponse macro content type to application/xml instead of plain output.
XWiki 15.10.11 (or 16.4.1 or later)
- Backup your XWiki database and configuration files before upgrading
- Download XWiki 15.10.11 (for 15.x installations) or XWiki 16.4.1 (for 16.x installations) or later from the official XWiki download page
- Stop the XWiki application server
- Install the new XWiki version following the standard upgrade documentation at https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/
- Start the XWiki application server
- Verify the vulnerability is patched by accessing the test URL: <host>/xwiki/bin/get/Main/SolrSearch?media=rss&text=%7D%7D%7D%7B%7Basync%20async%3Dfalse%7D%7D%7B%7Bgroovy%7D%7Dprintln%28%22Hello%20from%22%20%2B%20%22%20search%20text%3A%22%20%2B%20%2823%20%2B%2019%29%29%7B%7B%2Fgroovy%7D%7D%7B%7B%2Fasync%7D%7D - the RSS feed title should NOT contain 'Hello from search text:42'
- If still vulnerable, the workaround is to edit Main.SolrSearchMacros in SolrSearchMacros.xml at line 955 to set content type to 'application/xml' similar to rawResponse macro in macros.vm#L2824
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24893 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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