LiveActive security incident?Get immediate response
CVE Record

CVE-2025-24893: Remote code execution as guest via SolrSearchMacros request in xwiki

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.

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-24893 lets an unauthenticated visitor run arbitrary code on vulnerable XWiki installations through SolrSearch RSS handling. Because it can compromise confidentiality, integrity, and availability and is listed in CISA KEV, exposed XWiki systems should be treated as urgent remediation candidates.

Executive priority

Prioritize immediate remediation for any reachable XWiki instance. This is unauthenticated critical RCE with confirmed KEV status, so the business risk includes full wiki compromise, data exposure, service disruption, and attacker persistence.

Technical view

The issue is CWE-95 code evaluation in XWiki Platform SolrSearchMacros. A guest-accessible SolrSearch request can cause arbitrary remote code execution. Affected ranges are >=5.3-milestone-2 and <15.10.11, and >=16.0.0-rc-1 and <16.4.1. Fixed releases are 15.10.11, 16.4.1, and 16.5.0RC1.

Likely exposure

Highest exposure is guest-accessible or internet-facing XWiki Platform instances running the affected version ranges. Authentication is not required, so public search endpoints materially increase risk. Internal-only deployments still matter because compromise can affect the whole XWiki installation.

Exploitation context

CISA KEV inclusion supports active exploitation. The vendor advisory describes unauthenticated RCE and a validation indicator, but this assessment does not include exploit steps. Treat vulnerable reachable instances as already at elevated risk until upgraded or mitigated.

Researcher notes

Evidence is strong for affected versions, CVSS 9.8 severity, unauthenticated attack surface, fixed releases, and workaround direction. The bundle does not provide environment-specific indicators of compromise or details on observed attacker campaigns beyond CISA KEV status.

Mitigation direction

  • Upgrade XWiki to 15.10.11, 16.4.1, 16.5.0RC1, or later fixed releases.
  • If upgrade is blocked, apply the vendor-documented SolrSearchMacros rawResponse workaround.
  • Restrict unauthenticated access to XWiki while remediation is pending, where operationally feasible.
  • Review exposed XWiki instances for unexpected changes, new users, and suspicious administrative activity.
  • Monitor vendor advisory and CISA KEV guidance for updated response requirements.

Validation and detection

  • Inventory all XWiki Platform instances and record exact versions.
  • Compare versions against the two affected ranges in the advisory.
  • Confirm SolrSearch is not guest-reachable on vulnerable deployments unless mitigated.
  • Review logs for suspicious unauthenticated SolrSearch RSS requests and macro-like input.
  • Verify patched systems contain the fixed SolrSearchMacros handling referenced by the vendor.
Prepared
Reviewed
Confidence
high
Sources
7

Michael Williams reviewed this cited source version on .

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-95: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-24893 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-24893Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
xwikixwiki-platform>= 5.3-milestone-2, < 15.10.11, >= 16.0.0-rc-1, < 16.4.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-95 · source CWE mapping

Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')

Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.