Threats / XWiki / CVE-2025-24893
CVE-2025-24893
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
XWiki Platform vulnerability
XWiki Platform contains an eval injection vulnerability in SolrSearch that allows unauthenticated remote code execution.
Verdict
Today item — known-exploited.
An eval injection flaw in XWiki Platform's SolrSearch component permits guest users to execute arbitrary code remotely without authentication. Active exploitation in the wild elevates risk significantly.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
508 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-10-30).
Probability (EPSS)
EPSS 0.99898 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: XWiki, Platform. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-95 Eval Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request to the SolrSearch endpoint containing code injection payloads.
Business
Attackers gain immediate code execution capability on the server without requiring valid credentials.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute system commands to establish persistence, exfiltrate data, or pivot to internal systems.
Business
Confidential data, intellectual property, and system integrity are compromised; operational continuity is threatened.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy malware, webshells, or lateral movement tools across the infrastructure.
Business
Incident response costs, forensic investigation, and potential regulatory fines accumulate; brand reputation suffers.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05