ISO 27001 Certificate
SOC 1 Type I Certificate
SOC 2 Type II Certificate
PCI DSS
HIPAA
RGPD
Internal validation & live display
Multiple badges & continuous verification
Faster underwriting decisions
ISOSOC2 Type 1SOC2 Type 2PCI DSSHIPAAGDPR

Founded in 2004, XWiki is the leading provider of professional open-source solutions and consultancy for knowledge management and collaborative platforms. Planning to move to XWiki? Check our alternatives page: https://xwiki.com/en/Alternatives. Trusted by @Amazon, @Lenovo, @CNFPT, @Naval-group, and many more.

XWiki A.I CyberSecurity Scoring

XWiki

Company Details

Linkedin ID:

xwiki

Employees number:

53

Number of followers:

4,153

NAICS:

5112

Industry Type:

Software Development

Homepage:

xwiki.com

IP Addresses:

0

Company ID:

XWI_1785291

Scan Status:

In-progress

AI scoreXWiki Risk Score (AI oriented)

Between 700 and 749

https://images.rankiteo.com/companyimages/xwiki.jpeg
XWiki Software Development
Updated:
  • Powered by our proprietary A.I cyber incident model
  • Insurance preferes TPRM score to calculate premium
globalscoreXWiki Global Score (TPRM)

XXXX

https://images.rankiteo.com/companyimages/xwiki.jpeg
XWiki Software Development
  • Instant access to detailed risk factors
  • Benchmark vs. industry & size peers
  • Vulnerabilities
  • Findings

XWiki Company CyberSecurity News & History

Past Incidents
2
Attack Types
1
EntityTypeSeverityImpactSeenBlog DetailsIncident DetailsView
XWiki Platform (Open-Source Organizations)Vulnerability100510/2025
Rankiteo Explanation :
Attack threatening the organization’s existence

Description: The **CVE-2025-24893** vulnerability in **XWiki Platform’s SolrSearch component** allows unauthenticated guest users to execute arbitrary remote code via **eval injection (CWE-95)**, bypassing all security controls. Exploiting this flaw grants attackers full command execution privileges equivalent to the web server process, enabling **data exfiltration, malware deployment, lateral movement, and persistent network compromise**. Organizations using XWiki for collaboration or public-facing wikis are at acute risk, as the flaw weaponizes the platform’s trust model. CISA has issued an urgent directive with a **November 20, 2025, remediation deadline**, mandating immediate patching or complete discontinuation of XWiki if patching is infeasible. The **CVSS 9.8 (Critical)** severity reflects the vulnerability’s low attack complexity and network-based exploitation potential. While no active ransomware campaigns are confirmed, the flaw’s accessibility and severity make it a prime target for rapid weaponization by advanced threat actors. Failure to remediate risks **system takeover, sensitive data exposure, and operational disruption**, with cloud deployments subject to additional compliance mandates under **BOD 22-01**.

XWikiVulnerability10056/2023
Rankiteo Explanation :
Attack threatening the organization’s existence

Description: Cybersecurity researchers identified a critical **Remote Code Execution (RCE) vulnerability (CVE-2025-24893)** in **XWiki**, actively exploited by multiple threat actors, including botnets (e.g., **RondoDox**), cryptocurrency miners, and advanced attackers deploying reverse shells. The vulnerability, first exploited on **October 28, 2025**, escalated rapidly, with **CISA adding it to the KEV catalog** just two days later. Attackers leveraged the flaw to compromise servers globally, deploying **malware, coin miners (e.g., payload hash *03a77a556f074184b254d90e13cdd3a31efaa5a77640405e5f78aa462736acf7*), reverse shells (via AWS IPs like *18.228.3.32*), and persistence mechanisms**. Scanning operations (e.g., via **Nuclei templates**) targeted vulnerable installations, attempting to exfiltrate sensitive data (e.g., */etc/passwd*). The attack chain involved **compromised infrastructure (e.g., QNAP/DrayTek devices via CVE-2023-47218)**, indicating layered exploitation. The **speed of weaponization**—from isolated exploits to **widespread botnet integration (RondoDox by November 3)**—left defenders with minimal time to patch, risking **large-scale server takeovers, data breaches, and operational disruption** for organizations relying on XWiki for collaboration or documentation.

XWiki Platform (Open-Source Organizations)
Vulnerability
Severity: 100
Impact: 5
Seen: 10/2025
Blog:
Rankiteo Explanation
Attack threatening the organization’s existence

Description: The **CVE-2025-24893** vulnerability in **XWiki Platform’s SolrSearch component** allows unauthenticated guest users to execute arbitrary remote code via **eval injection (CWE-95)**, bypassing all security controls. Exploiting this flaw grants attackers full command execution privileges equivalent to the web server process, enabling **data exfiltration, malware deployment, lateral movement, and persistent network compromise**. Organizations using XWiki for collaboration or public-facing wikis are at acute risk, as the flaw weaponizes the platform’s trust model. CISA has issued an urgent directive with a **November 20, 2025, remediation deadline**, mandating immediate patching or complete discontinuation of XWiki if patching is infeasible. The **CVSS 9.8 (Critical)** severity reflects the vulnerability’s low attack complexity and network-based exploitation potential. While no active ransomware campaigns are confirmed, the flaw’s accessibility and severity make it a prime target for rapid weaponization by advanced threat actors. Failure to remediate risks **system takeover, sensitive data exposure, and operational disruption**, with cloud deployments subject to additional compliance mandates under **BOD 22-01**.

XWiki
Vulnerability
Severity: 100
Impact: 5
Seen: 6/2023
Blog:
Rankiteo Explanation
Attack threatening the organization’s existence

Description: Cybersecurity researchers identified a critical **Remote Code Execution (RCE) vulnerability (CVE-2025-24893)** in **XWiki**, actively exploited by multiple threat actors, including botnets (e.g., **RondoDox**), cryptocurrency miners, and advanced attackers deploying reverse shells. The vulnerability, first exploited on **October 28, 2025**, escalated rapidly, with **CISA adding it to the KEV catalog** just two days later. Attackers leveraged the flaw to compromise servers globally, deploying **malware, coin miners (e.g., payload hash *03a77a556f074184b254d90e13cdd3a31efaa5a77640405e5f78aa462736acf7*), reverse shells (via AWS IPs like *18.228.3.32*), and persistence mechanisms**. Scanning operations (e.g., via **Nuclei templates**) targeted vulnerable installations, attempting to exfiltrate sensitive data (e.g., */etc/passwd*). The attack chain involved **compromised infrastructure (e.g., QNAP/DrayTek devices via CVE-2023-47218)**, indicating layered exploitation. The **speed of weaponization**—from isolated exploits to **widespread botnet integration (RondoDox by November 3)**—left defenders with minimal time to patch, risking **large-scale server takeovers, data breaches, and operational disruption** for organizations relying on XWiki for collaboration or documentation.

Ailogo

XWiki Company Scoring based on AI Models

Cyber Incidents Likelihood 3 - 6 - 9 months

🔒
Incident Predictions locked
Access Monitoring Plan

A.I Risk Score Likelihood 3 - 6 - 9 months

🔒
A.I. Risk Score Predictions locked
Access Monitoring Plan
statics

Underwriter Stats for XWiki

Incidents vs Software Development Industry Average (This Year)

XWiki has 132.56% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs All-Companies Average (This Year)

XWiki has 56.25% more incidents than the average of all companies with at least one recorded incident.

Incident Types XWiki vs Software Development Industry Avg (This Year)

XWiki reported 1 incidents this year: 0 cyber attacks, 0 ransomware, 1 vulnerabilities, 0 data breaches, compared to industry peers with at least 1 incident.

Incident History — XWiki (X = Date, Y = Severity)

XWiki cyber incidents detection timeline including parent company and subsidiaries

XWiki Company Subsidiaries

SubsidiaryImage

Founded in 2004, XWiki is the leading provider of professional open-source solutions and consultancy for knowledge management and collaborative platforms. Planning to move to XWiki? Check our alternatives page: https://xwiki.com/en/Alternatives. Trusted by @Amazon, @Lenovo, @CNFPT, @Naval-group, and many more.

Loading...
similarCompanies

XWiki Similar Companies

At Sage, we knock down barriers with information, insights, and tools to help your business flow. We provide businesses with software and services that are simple and easy to use, as we work with you to give you that feeling of confidence. Customers trust our Payroll, HR, and Finance software to m

Upwork

Upwork is the world’s work marketplace that connects businesses with independent talent from across the globe. We serve everyone from one-person startups to large, Fortune 100 enterprises with a powerful, trust-driven platform that enables companies and talent to work together in new ways that unloc

Meta's mission is to build the future of human connection and the technology that makes it possible. Our technologies help people connect, find communities, and grow businesses. When Facebook launched in 2004, it changed the way people connect. Apps like Messenger, Instagram and WhatsApp further e

Amdocs

We help those who build the future to make it amazing. In an era where new technologies are born every minute, and the demand for meaningful digital experiences has never been so intense, we unlock our customers’ innovative potential, empowering them to transform their boldest ideas into reality, an

Cox Automotive Inc.

Cox Automotive is the world’s largest automotive services and technology provider. Fueled by the largest breadth of first-party data fed by 2.3 billion online interactions a year, Cox Automotive tailors leading solutions for car shoppers, auto manufacturers, dealers, lenders and fleets. The company

VMware by Broadcom delivers software that unifies and streamlines hybrid cloud environments for the world’s most complex organizations. By combining public-cloud scale and agility with private-cloud security and performance, we empower our customers to modernize, optimize and protect their apps an

Join us in our mission to help the world get well, help the world stay well, and help future generations be healthier. We hire smart and motivated people from all academic majors to code, test, and implement healthcare software that hundreds of millions of patients and doctors rely on to improve ca

Dassault Systèmes

Dassault Systèmes is a catalyst for human progress. Since 1981, the company has pioneered virtual worlds to improve real life for consumers, patients and citizens. With Dassault Systèmes’ 3DEXPERIENCE platform, 370,000 customers of all sizes, in all industries, can collaborate, imagine and create

Intuit

Intuit is a global technology platform that helps our customers and communities overcome their most important financial challenges. Serving millions of customers worldwide with TurboTax, QuickBooks, Credit Karma and Mailchimp, we believe that everyone should have the opportunity to prosper and we wo

newsone

XWiki CyberSecurity News

November 23, 2025 01:55 PM
Cybersecurity News Weekly Newsletter – Fortinet, Chrome 0-Day Flaws, Cloudflare Outage and Salesforce...

Welcome to this week's edition of the Cybersecurity News Weekly Newsletter, where we analyze the critical incidents defining the current...

November 17, 2025 08:54 PM
XWiki bug actively exploited by multiple threat actors

Exploitation of an XWiki bug has intensified as VulnCheck reported that a diverse set of threat actors are actively targeting the flaw.

November 17, 2025 11:06 AM
Widespread Exploitation of XWiki Vulnerability Observed

Threat actors started exploiting a critical XWiki vulnerability en masse within two weeks of the bug being reported as exploited in the...

November 17, 2025 09:35 AM
Hackers Exploiting XWiki Vulnerability in the Wild to Hire the Servers for Botnet

A sharp increase in attacks targeting a critical vulnerability in XWiki servers. Multiple threat actors are actively exploiting...

November 17, 2025 08:17 AM
RondoDox expands botnet by exploiting XWiki RCE bug left unpatched since February 2025

RondoDox botnet exploits unpatched XWiki flaw CVE-2025-24893 to gain RCE and infect more servers, despite fixes released in February 2025.

November 17, 2025 08:00 AM
RondoDox botnet malware now hacks servers using XWiki flaw

The RondoDox botnet malware is now exploiting a critical remote code execution (RCE) flaw in XWiki Platform tracked as CVE-2025-24893.

November 15, 2025 08:00 AM
RondoDox Exploits Unpatched XWiki Servers to Pull More Devices Into Its Botnet

The botnet malware known as RondoDox has been observed targeting unpatched XWiki instances against a critical security flaw that could allow...

November 05, 2025 08:00 AM
U.S. CISA adds Gladinet CentreStack, and CWP Control Web Panel flaws to its Known Exploited Vulnerabilities...

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added XWiki Platform, and Gladinet CentreStack, and CWP Control Web Panel...

November 04, 2025 08:00 AM
Xwiki and VMWare vulnerabilities exploited in the wild

A pair of newly exploited vulnerabilities has been added to CISA's Known Exploited Vulnerabilities Catalog.

faq

Frequently Asked Questions

Explore insights on cybersecurity incidents, risk posture, and Rankiteo's assessments.

XWiki CyberSecurity History Information

Official Website of XWiki

The official website of XWiki is http://www.xwiki.com.

XWiki’s AI-Generated Cybersecurity Score

According to Rankiteo, XWiki’s AI-generated cybersecurity score is 747, reflecting their Moderate security posture.

How many security badges does XWiki’ have ?

According to Rankiteo, XWiki currently holds 0 security badges, indicating that no recognized compliance certifications are currently verified for the organization.

Does XWiki have SOC 2 Type 1 certification ?

According to Rankiteo, XWiki is not certified under SOC 2 Type 1.

Does XWiki have SOC 2 Type 2 certification ?

According to Rankiteo, XWiki does not hold a SOC 2 Type 2 certification.

Does XWiki comply with GDPR ?

According to Rankiteo, XWiki is not listed as GDPR compliant.

Does XWiki have PCI DSS certification ?

According to Rankiteo, XWiki does not currently maintain PCI DSS compliance.

Does XWiki comply with HIPAA ?

According to Rankiteo, XWiki is not compliant with HIPAA regulations.

Does XWiki have ISO 27001 certification ?

According to Rankiteo,XWiki is not certified under ISO 27001, indicating the absence of a formally recognized information security management framework.

Industry Classification of XWiki

XWiki operates primarily in the Software Development industry.

Number of Employees at XWiki

XWiki employs approximately 53 people worldwide.

Subsidiaries Owned by XWiki

XWiki presently has no subsidiaries across any sectors.

XWiki’s LinkedIn Followers

XWiki’s official LinkedIn profile has approximately 4,153 followers.

NAICS Classification of XWiki

XWiki is classified under the NAICS code 5112, which corresponds to Software Publishers.

XWiki’s Presence on Crunchbase

No, XWiki does not have a profile on Crunchbase.

XWiki’s Presence on LinkedIn

Yes, XWiki maintains an official LinkedIn profile, which is actively utilized for branding and talent engagement, which can be accessed here: https://www.linkedin.com/company/xwiki.

Cybersecurity Incidents Involving XWiki

As of December 04, 2025, Rankiteo reports that XWiki has experienced 2 cybersecurity incidents.

Number of Peer and Competitor Companies

XWiki has an estimated 27,191 peer or competitor companies worldwide.

What types of cybersecurity incidents have occurred at XWiki ?

Incident Types: The types of cybersecurity incidents that have occurred include Vulnerability.

How does XWiki detect and respond to cybersecurity incidents ?

Detection and Response: The company detects and responds to cybersecurity incidents through an third party assistance with xwiki support for patch availability information, and containment measures with discontinue xwiki platform usage if patching is not feasible, containment measures with network segmentation to restrict lateral movement, and remediation measures with immediate implementation of vendor-supplied security patches, remediation measures with inventory all xwiki platform deployments (development, testing, production), remediation measures with establish patch testing procedures before enterprise-wide rollout, and network segmentation with recommended to restrict lateral movement, and third party assistance with vulncheck (early detection via canary intelligence), and containment measures with cisa kev catalog addition (2025-10-30), containment measures with public advisories, and remediation measures with urgent patching of xwiki instances, and communication strategy with security researcher reports, communication strategy with cisa kev listing, and enhanced monitoring with recommended for xwiki servers (e.g., detecting /etc/passwd access attempts)..

Incident Details

Can you provide details on each incident ?

Incident : Vulnerability Exploitation

Title: Critical Eval Injection Vulnerability in XWiki Platform (CVE-2025-24893)

Description: The Cybersecurity and Infrastructure Security Agency (CISA) has formally added CVE-2025-24893 to its Known Exploited Vulnerabilities catalog, drawing urgent attention to a critical eval injection flaw affecting XWiki Platform. This vulnerability permits any guest user to execute arbitrary remote code without requiring authentication, posing an acute security risk to organizations deploying this widely used open-source wiki platform across their infrastructure. The vulnerability stems from improper handling of eval functions within the XWiki Platform’s SolrSearch component, classified under CWE-95 for the improper neutralization of directives in dynamically evaluated code. Unauthenticated attackers can craft specially engineered requests to inject malicious code, bypassing established security controls and gaining complete command execution capabilities on affected systems. Once code execution is achieved, threat actors inherit the same privileges as the web server process, enabling them to exfiltrate sensitive organizational data, deploy malware payloads, or establish persistent network footholds for lateral movement attacks. CISA has established November 20, 2025, as the critical remediation deadline for organizations operating affected XWiki Platform instances.

Type: Vulnerability Exploitation

Attack Vector: Network

Vulnerability Exploited: Cve Id: CVE-2025-24893, Affected Product: XWiki Platform, Vulnerability Type: Eval Injection (CWE-95), Cvss Score: 9.8, Cvss Severity: Critical, Affected Component: SolrSearch, Authentication Required: None, Attack Complexity: Low.

Incident : Vulnerability Exploitation

Title: Widespread Exploitation of Critical XWiki Vulnerability (CVE-2025-24893)

Description: Cybersecurity researchers have detected a dramatic surge in exploitation attempts targeting a critical XWiki vulnerability (CVE-2025-24893), with multiple threat actors actively deploying botnets (e.g., RondoDox), cryptocurrency miners, reverse shells, and custom malware to compromise vulnerable servers worldwide. The vulnerability evolved from isolated attacks to widespread exploitation within days, leaving defenders with minimal time to patch systems. Exploitation includes botnet integration, coin mining campaigns, reverse shell establishment, and automated scanning operations.

Date Detected: 2025-10-28

Date Publicly Disclosed: 2025-10-28

Type: Vulnerability Exploitation

Attack Vector: Remote Code Execution (RCE)Exploitation of CVE-2025-24893 in XWiki

Vulnerability Exploited: CVE-2025-24893 (Critical RCE in XWiki)

Threat Actor: Name: RondoDox Botnet, Type: Botnet Operator, Indicators: {'user_agent': 'rondo.<value>.sh', 'ip_addresses': ['74.194.191.52'], 'first_observed': '2025-11-03'}, Name: Unknown Cryptocurrency Mining Group 1, Type: Cryptojacking Operator, Indicators: {'ip_addresses': ['172.245.241.123', '47.236.194.231'], 'domains': ['ospwrf10ny.anondns[.]net'], 'payload_hash': '03a77a556f074184b254d90e13cdd3a31efaa5a77640405e5f78aa462736acf7'}, Name: Unknown Cryptocurrency Mining Group 2, Type: Cryptojacking Operator, Indicators: {'ip_addresses': ['156.146.56.131']}, Name: Unknown Reverse Shell Actor 1, Type: Sophisticated Threat Actor, Indicators: {'ip_addresses': ['18.228.3.224'], 'tactics': ['AWS-hosted reverse shell via BusyBox netcat']}, Name: Unknown Reverse Shell Actor 2, Type: Opportunistic Threat Actor, Indicators: {'ip_addresses': ['118.99.141.178'], 'compromised_infrastructure': ['QNAP', 'DrayTek (vulnerable to CVE-2023-47218)']}, Name: Automated Scanning Operators, Type: Reconnaissance, Indicators: {'services': ['Nuclei scanner', 'oast.fun OAST probes'], 'ip_addresses': ['18.228.3.224'], 'commands': ['cat /etc/passwd', 'id', 'whoami']}, Name: Unknown Payload Hosting Group, Type: Infrastructure Operator, Indicators: {'ip_addresses': ['185.142.33.151', '90.156.218.31', '172.206.196.45']}.

Motivation: Financial Gain (Cryptojacking)Botnet ExpansionPersistence/Access BrokerageReconnaissancePotential Data Theft

What are the most common types of attacks the company has faced ?

Common Attack Types: The most common types of attacks the company has faced is Vulnerability.

How does the company identify the attack vectors used in incidents ?

Identification of Attack Vectors: The company identifies the attack vectors used in incidents through XWiki Platform SolrSearch component via eval injection and CVE-2025-24893 (XWiki RCE).

Impact of the Incidents

What was the impact of each incident ?

Incident : Vulnerability Exploitation XWI2092520103125

Systems Affected: XWiki Platform deployments (development, testing, production environments)

Operational Impact: Potential exfiltration of sensitive organizational dataDeployment of malware payloadsPersistent network footholds for lateral movementComplete compromise of system integrity and data confidentiality

Brand Reputation Impact: High risk due to potential data breaches and system compromise

Incident : Vulnerability Exploitation XWI0133201111725

Systems Affected: Global XWiki servers (exact count unknown)

Operational Impact: Potential server compromisesUnauthorized resource usage (CPU/memory for mining)Backdoor persistence

Brand Reputation Impact: Potential reputational damage for XWiki and affected organizations

Which entities were affected by each incident ?

Incident : Vulnerability Exploitation XWI2092520103125

Entity Type: Organizations using XWiki Platform

Incident : Vulnerability Exploitation XWI0133201111725

Entity Name: XWiki Project

Entity Type: Open-Source Software

Industry: Collaboration Platforms

Location: Global

Customers Affected: Unknown (all unpatched XWiki instances)

Incident : Vulnerability Exploitation XWI0133201111725

Entity Name: Organizations using XWiki

Entity Type: Corporations, Government Agencies, Educational Institutions

Industry: Multiple

Location: Global

Response to the Incidents

What measures were taken in response to each incident ?

Incident : Vulnerability Exploitation XWI2092520103125

Third Party Assistance: Xwiki Support For Patch Availability Information.

Containment Measures: Discontinue XWiki Platform usage if patching is not feasibleNetwork segmentation to restrict lateral movement

Remediation Measures: Immediate implementation of vendor-supplied security patchesInventory all XWiki Platform deployments (development, testing, production)Establish patch testing procedures before enterprise-wide rollout

Network Segmentation: Recommended to restrict lateral movement

Incident : Vulnerability Exploitation XWI0133201111725

Third Party Assistance: Vulncheck (Early Detection Via Canary Intelligence).

Containment Measures: CISA KEV catalog addition (2025-10-30)Public advisories

Remediation Measures: Urgent patching of XWiki instances

Communication Strategy: Security researcher reportsCISA KEV listing

Enhanced Monitoring: Recommended for XWiki servers (e.g., detecting /etc/passwd access attempts)

How does the company involve third-party assistance in incident response ?

Third-Party Assistance: The company involves third-party assistance in incident response through XWiki support for patch availability information, , VulnCheck (early detection via Canary Intelligence), .

Data Breach Information

What type of data was compromised in each breach ?

Incident : Vulnerability Exploitation XWI2092520103125

Data Exfiltration: Potential risk if exploited

Incident : Vulnerability Exploitation XWI0133201111725

File Types Exposed: /etc/passwd (attempted access)

What measures does the company take to prevent data exfiltration ?

Prevention of Data Exfiltration: The company takes the following measures to prevent data exfiltration: Immediate implementation of vendor-supplied security patches, Inventory all XWiki Platform deployments (development, testing, production), Establish patch testing procedures before enterprise-wide rollout, , Urgent patching of XWiki instances, .

How does the company handle incidents involving personally identifiable information (PII) ?

Handling of PII Incidents: The company handles incidents involving personally identifiable information (PII) through by discontinue xwiki platform usage if patching is not feasible, network segmentation to restrict lateral movement, , cisa kev catalog addition (2025-10-30), public advisories and .

Regulatory Compliance

Were there any regulatory violations and fines imposed for each incident ?

Incident : Vulnerability Exploitation XWI2092520103125

Regulatory Notifications: CISA Binding Operational Directive (BOD) 22-01 for vulnerability management in cloud services

Incident : Vulnerability Exploitation XWI0133201111725

Regulatory Notifications: CISA KEV catalog inclusion (2025-10-30)

Lessons Learned and Recommendations

What lessons were learned from each incident ?

Incident : Vulnerability Exploitation XWI2092520103125

Lessons Learned: Critical vulnerabilities in open-source platforms with guest access can be weaponized by threat actors with low complexity., Immediate patching or discontinuation of vulnerable software is essential when exploitation risk is high., Network segmentation and inventory management are critical defensive measures during vulnerability windows.

Incident : Vulnerability Exploitation XWI0133201111725

Lessons Learned: Rapid weaponization of vulnerabilities (days between disclosure and widespread exploitation), Importance of early detection systems (e.g., VulnCheck Canary Intelligence), Need for accelerated patching timelines for critical vulnerabilities, Threat actors leverage compromised infrastructure (e.g., QNAP/DrayTek devices) for follow-on attacks, Diverse motivations (botnets, cryptojacking, reconnaissance) require multi-layered defenses

What recommendations were made to prevent future incidents ?

Incident : Vulnerability Exploitation XWI2092520103125

Recommendations: Inventory all XWiki Platform deployments across development, testing, and production environments., Immediately apply vendor-supplied security patches or discontinue use if patching is not feasible., Implement network segmentation to limit lateral movement in case of exploitation., Monitor CISA advisories for newly disclosed vulnerabilities to proactively mitigate risks., Establish patch testing procedures before enterprise-wide rollout to avoid operational disruptions., Contact XWiki support for patch availability and guidance.Inventory all XWiki Platform deployments across development, testing, and production environments., Immediately apply vendor-supplied security patches or discontinue use if patching is not feasible., Implement network segmentation to limit lateral movement in case of exploitation., Monitor CISA advisories for newly disclosed vulnerabilities to proactively mitigate risks., Establish patch testing procedures before enterprise-wide rollout to avoid operational disruptions., Contact XWiki support for patch availability and guidance.Inventory all XWiki Platform deployments across development, testing, and production environments., Immediately apply vendor-supplied security patches or discontinue use if patching is not feasible., Implement network segmentation to limit lateral movement in case of exploitation., Monitor CISA advisories for newly disclosed vulnerabilities to proactively mitigate risks., Establish patch testing procedures before enterprise-wide rollout to avoid operational disruptions., Contact XWiki support for patch availability and guidance.Inventory all XWiki Platform deployments across development, testing, and production environments., Immediately apply vendor-supplied security patches or discontinue use if patching is not feasible., Implement network segmentation to limit lateral movement in case of exploitation., Monitor CISA advisories for newly disclosed vulnerabilities to proactively mitigate risks., Establish patch testing procedures before enterprise-wide rollout to avoid operational disruptions., Contact XWiki support for patch availability and guidance.Inventory all XWiki Platform deployments across development, testing, and production environments., Immediately apply vendor-supplied security patches or discontinue use if patching is not feasible., Implement network segmentation to limit lateral movement in case of exploitation., Monitor CISA advisories for newly disclosed vulnerabilities to proactively mitigate risks., Establish patch testing procedures before enterprise-wide rollout to avoid operational disruptions., Contact XWiki support for patch availability and guidance.Inventory all XWiki Platform deployments across development, testing, and production environments., Immediately apply vendor-supplied security patches or discontinue use if patching is not feasible., Implement network segmentation to limit lateral movement in case of exploitation., Monitor CISA advisories for newly disclosed vulnerabilities to proactively mitigate risks., Establish patch testing procedures before enterprise-wide rollout to avoid operational disruptions., Contact XWiki support for patch availability and guidance.

Incident : Vulnerability Exploitation XWI0133201111725

Recommendations: Immediate patching of XWiki instances to CVE-2025-24893, Monitor for indicators of compromise (IOCs) such as RondoDox User-Agent patterns and known malicious IPs, Deploy network segmentation to limit lateral movement, Enhance logging for XWiki servers to detect exploitation attempts (e.g., /etc/passwd access), Block known malicious IPs at perimeter firewalls, Conduct threat hunting for reverse shells and cryptominers, Review AWS and other cloud environments for unauthorized netcat/BusyBox usage, Educate teams on the rapid evolution of exploitation (from single actors to botnets within a week)Immediate patching of XWiki instances to CVE-2025-24893, Monitor for indicators of compromise (IOCs) such as RondoDox User-Agent patterns and known malicious IPs, Deploy network segmentation to limit lateral movement, Enhance logging for XWiki servers to detect exploitation attempts (e.g., /etc/passwd access), Block known malicious IPs at perimeter firewalls, Conduct threat hunting for reverse shells and cryptominers, Review AWS and other cloud environments for unauthorized netcat/BusyBox usage, Educate teams on the rapid evolution of exploitation (from single actors to botnets within a week)Immediate patching of XWiki instances to CVE-2025-24893, Monitor for indicators of compromise (IOCs) such as RondoDox User-Agent patterns and known malicious IPs, Deploy network segmentation to limit lateral movement, Enhance logging for XWiki servers to detect exploitation attempts (e.g., /etc/passwd access), Block known malicious IPs at perimeter firewalls, Conduct threat hunting for reverse shells and cryptominers, Review AWS and other cloud environments for unauthorized netcat/BusyBox usage, Educate teams on the rapid evolution of exploitation (from single actors to botnets within a week)Immediate patching of XWiki instances to CVE-2025-24893, Monitor for indicators of compromise (IOCs) such as RondoDox User-Agent patterns and known malicious IPs, Deploy network segmentation to limit lateral movement, Enhance logging for XWiki servers to detect exploitation attempts (e.g., /etc/passwd access), Block known malicious IPs at perimeter firewalls, Conduct threat hunting for reverse shells and cryptominers, Review AWS and other cloud environments for unauthorized netcat/BusyBox usage, Educate teams on the rapid evolution of exploitation (from single actors to botnets within a week)Immediate patching of XWiki instances to CVE-2025-24893, Monitor for indicators of compromise (IOCs) such as RondoDox User-Agent patterns and known malicious IPs, Deploy network segmentation to limit lateral movement, Enhance logging for XWiki servers to detect exploitation attempts (e.g., /etc/passwd access), Block known malicious IPs at perimeter firewalls, Conduct threat hunting for reverse shells and cryptominers, Review AWS and other cloud environments for unauthorized netcat/BusyBox usage, Educate teams on the rapid evolution of exploitation (from single actors to botnets within a week)Immediate patching of XWiki instances to CVE-2025-24893, Monitor for indicators of compromise (IOCs) such as RondoDox User-Agent patterns and known malicious IPs, Deploy network segmentation to limit lateral movement, Enhance logging for XWiki servers to detect exploitation attempts (e.g., /etc/passwd access), Block known malicious IPs at perimeter firewalls, Conduct threat hunting for reverse shells and cryptominers, Review AWS and other cloud environments for unauthorized netcat/BusyBox usage, Educate teams on the rapid evolution of exploitation (from single actors to botnets within a week)Immediate patching of XWiki instances to CVE-2025-24893, Monitor for indicators of compromise (IOCs) such as RondoDox User-Agent patterns and known malicious IPs, Deploy network segmentation to limit lateral movement, Enhance logging for XWiki servers to detect exploitation attempts (e.g., /etc/passwd access), Block known malicious IPs at perimeter firewalls, Conduct threat hunting for reverse shells and cryptominers, Review AWS and other cloud environments for unauthorized netcat/BusyBox usage, Educate teams on the rapid evolution of exploitation (from single actors to botnets within a week)Immediate patching of XWiki instances to CVE-2025-24893, Monitor for indicators of compromise (IOCs) such as RondoDox User-Agent patterns and known malicious IPs, Deploy network segmentation to limit lateral movement, Enhance logging for XWiki servers to detect exploitation attempts (e.g., /etc/passwd access), Block known malicious IPs at perimeter firewalls, Conduct threat hunting for reverse shells and cryptominers, Review AWS and other cloud environments for unauthorized netcat/BusyBox usage, Educate teams on the rapid evolution of exploitation (from single actors to botnets within a week)

What are the key lessons learned from past incidents ?

Key Lessons Learned: The key lessons learned from past incidents are Critical vulnerabilities in open-source platforms with guest access can be weaponized by threat actors with low complexity.,Immediate patching or discontinuation of vulnerable software is essential when exploitation risk is high.,Network segmentation and inventory management are critical defensive measures during vulnerability windows.Rapid weaponization of vulnerabilities (days between disclosure and widespread exploitation),Importance of early detection systems (e.g., VulnCheck Canary Intelligence),Need for accelerated patching timelines for critical vulnerabilities,Threat actors leverage compromised infrastructure (e.g., QNAP/DrayTek devices) for follow-on attacks,Diverse motivations (botnets, cryptojacking, reconnaissance) require multi-layered defenses.

References

Where can I find more information about each incident ?

Incident : Vulnerability Exploitation XWI2092520103125

Source: CISA Known Exploited Vulnerabilities Catalog

Incident : Vulnerability Exploitation XWI2092520103125

Source: CISA Binding Operational Directive (BOD) 22-01

Incident : Vulnerability Exploitation XWI0133201111725

Source: VulnCheck Research Report

Incident : Vulnerability Exploitation XWI0133201111725

Source: CISA Known Exploited Vulnerabilities Catalog

URL: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

Incident : Vulnerability Exploitation XWI0133201111725

Source: Security Telemetry Data (RondoDox, Cryptomining, Reverse Shells)

Where can stakeholders find additional resources on cybersecurity best practices ?

Additional Resources: Stakeholders can find additional resources on cybersecurity best practices at and Source: CISA Known Exploited Vulnerabilities Catalog, and Source: CISA Binding Operational Directive (BOD) 22-01, and Source: VulnCheck Research Report, and Source: CISA Known Exploited Vulnerabilities CatalogUrl: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, and Source: Security Telemetry Data (RondoDox, Cryptomining, Reverse Shells).

Investigation Status

What is the current status of the investigation for each incident ?

Incident : Vulnerability Exploitation XWI2092520103125

Investigation Status: Ongoing (CISA advisory issued, no active exploitation documented yet)

Incident : Vulnerability Exploitation XWI0133201111725

Investigation Status: Ongoing (active exploitation as of November 2025)

How does the company communicate the status of incident investigations to stakeholders ?

Communication of Investigation Status: The company communicates the status of incident investigations to stakeholders through Security Researcher Reports and Cisa Kev Listing.

Stakeholder and Customer Advisories

Were there any advisories issued to stakeholders or customers for each incident ?

Incident : Vulnerability Exploitation XWI2092520103125

Stakeholder Advisories: Cisa Mandates Remediation By November 20, 2025.

Customer Advisories: Organizations using XWiki Platform urged to patch immediately or discontinue use

Incident : Vulnerability Exploitation XWI0133201111725

Stakeholder Advisories: Cisa Kev Advisory, Security Researcher Warnings.

Customer Advisories: XWiki project patch notifications

What advisories does the company provide to stakeholders and customers following an incident ?

Advisories Provided: The company provides the following advisories to stakeholders and customers following an incident: were Cisa Mandates Remediation By November 20, 2025, Organizations Using Xwiki Platform Urged To Patch Immediately Or Discontinue Use, , Cisa Kev Advisory, Security Researcher Warnings, Xwiki Project Patch Notifications and .

Initial Access Broker

How did the initial access broker gain entry for each incident ?

Incident : Vulnerability Exploitation XWI2092520103125

Entry Point: Xwiki Platform Solrsearch Component Via Eval Injection,

Backdoors Established: ['Potential if exploited']

High Value Targets: Organizational Data, Web Server Process Privileges,

Data Sold on Dark Web: Organizational Data, Web Server Process Privileges,

Incident : Vulnerability Exploitation XWI0133201111725

Entry Point: CVE-2025-24893 (XWiki RCE)

Reconnaissance Period: October 28, 2025 – November 2025 (ongoing)

Backdoors Established: ['Reverse shells (e.g., via BusyBox netcat)', 'Persistence mechanisms from cryptomining payloads']

High Value Targets: Xwiki Servers With Internet Exposure, Systems With Weak Credential Hygiene,

Data Sold on Dark Web: Xwiki Servers With Internet Exposure, Systems With Weak Credential Hygiene,

Post-Incident Analysis

What were the root causes and corrective actions taken for each incident ?

Incident : Vulnerability Exploitation XWI2092520103125

Root Causes: Improper Neutralization Of Directives In Dynamically Evaluated Code (Cwe-95), Improper Handling Of Eval Functions In Solrsearch Component, Guest User Access Model Creating Exploitable Trust,

Corrective Actions: Apply Security Patches, Discontinue Use If Patching Is Not Feasible, Implement Network Segmentation, Enhance Monitoring For Suspicious Activity,

Incident : Vulnerability Exploitation XWI0133201111725

Root Causes: Delayed Patching Of Critical Vulnerability, Lack Of Early Detection For Exploitation Attempts, Exposed Management Interfaces (E.G., Qnap/Draytek) Used As Launchpads, Automated Scanning Tools (E.G., Nuclei) Lowering The Barrier For Attackers,

Corrective Actions: Accelerate Vulnerability Disclosure-To-Patch Timelines, Improve Threat Intelligence Sharing For Emerging Exploits, Enhance Detection Capabilities For Post-Exploitation Activity (E.G., Reverse Shells), Hardening Of Internet-Exposed Systems To Prevent Lateral Movement,

What is the company's process for conducting post-incident analysis ?

Post-Incident Analysis Process: The company's process for conducting post-incident analysis is described as Xwiki Support For Patch Availability Information, , Vulncheck (Early Detection Via Canary Intelligence), , Recommended For Xwiki Servers (E.G., Detecting /Etc/Passwd Access Attempts), .

What corrective actions has the company taken based on post-incident analysis ?

Corrective Actions Taken: The company has taken the following corrective actions based on post-incident analysis: Apply Security Patches, Discontinue Use If Patching Is Not Feasible, Implement Network Segmentation, Enhance Monitoring For Suspicious Activity, , Accelerate Vulnerability Disclosure-To-Patch Timelines, Improve Threat Intelligence Sharing For Emerging Exploits, Enhance Detection Capabilities For Post-Exploitation Activity (E.G., Reverse Shells), Hardening Of Internet-Exposed Systems To Prevent Lateral Movement, .

Additional Questions

General Information

Who was the attacking group in the last incident ?

Last Attacking Group: The attacking group in the last incident were an Name: RondoDox BotnetType: Botnet OperatorIndicators: {'user_agent': 'rondo.<value>.sh', 'ip_addresses': ['74.194.191.52'], 'first_observed': '2025-11-03'}Name: Unknown Cryptocurrency Mining Group 1Type: Cryptojacking OperatorIndicators: {'ip_addresses': ['172.245.241.123', '47.236.194.231'], 'domains': ['ospwrf10ny.anondns[.]net'], 'payload_hash': '03a77a556f074184b254d90e13cdd3a31efaa5a77640405e5f78aa462736acf7'}Name: Unknown Cryptocurrency Mining Group 2Type: Cryptojacking OperatorIndicators: {'ip_addresses': ['156.146.56.131']}Name: Unknown Reverse Shell Actor 1Type: Sophisticated Threat ActorIndicators: {'ip_addresses': ['18.228.3.224'], 'tactics': ['AWS-hosted reverse shell via BusyBox netcat']}Name: Unknown Reverse Shell Actor 2Type: Opportunistic Threat ActorIndicators: {'ip_addresses': ['118.99.141.178'], 'compromised_infrastructure': ['QNAP', 'DrayTek (vulnerable to CVE-2023-47218)']}Name: Automated Scanning OperatorsType: ReconnaissanceIndicators: {'services': ['Nuclei scanner', 'oast.fun OAST probes'], 'ip_addresses': ['18.228.3.224'], 'commands': ['cat /etc/passwd', 'id', 'whoami']}Name: Unknown Payload Hosting GroupType: Infrastructure OperatorIndicators: {'ip_addresses': ['185.142.33.151', '90.156.218.31' and '172.206.196.45']}.

Incident Details

What was the most recent incident detected ?

Most Recent Incident Detected: The most recent incident detected was on 2025-10-28.

What was the most recent incident publicly disclosed ?

Most Recent Incident Publicly Disclosed: The most recent incident publicly disclosed was on 2025-10-28.

Impact of the Incidents

What was the most significant system affected in an incident ?

Most Significant System Affected: The most significant system affected in an incident were XWiki Platform deployments (development, testing, production environments) and .

Response to the Incidents

What third-party assistance was involved in the most recent incident ?

Third-Party Assistance in Most Recent Incident: The third-party assistance involved in the most recent incident was xwiki support for patch availability information, , vulncheck (early detection via canary intelligence), .

What containment measures were taken in the most recent incident ?

Containment Measures in Most Recent Incident: The containment measures taken in the most recent incident were Discontinue XWiki Platform usage if patching is not feasibleNetwork segmentation to restrict lateral movement and CISA KEV catalog addition (2025-10-30)Public advisories.

Lessons Learned and Recommendations

What was the most significant lesson learned from past incidents ?

Most Significant Lesson Learned: The most significant lesson learned from past incidents was Diverse motivations (botnets, cryptojacking, reconnaissance) require multi-layered defenses.

What was the most significant recommendation implemented to improve cybersecurity ?

Most Significant Recommendation Implemented: The most significant recommendation implemented to improve cybersecurity was Immediately apply vendor-supplied security patches or discontinue use if patching is not feasible., Contact XWiki support for patch availability and guidance., Deploy network segmentation to limit lateral movement, Monitor for indicators of compromise (IOCs) such as RondoDox User-Agent patterns and known malicious IPs, Implement network segmentation to limit lateral movement in case of exploitation., Inventory all XWiki Platform deployments across development, testing, and production environments., Enhance logging for XWiki servers to detect exploitation attempts (e.g., /etc/passwd access), Monitor CISA advisories for newly disclosed vulnerabilities to proactively mitigate risks., Establish patch testing procedures before enterprise-wide rollout to avoid operational disruptions., Immediate patching of XWiki instances to CVE-2025-24893, Conduct threat hunting for reverse shells and cryptominers, Review AWS and other cloud environments for unauthorized netcat/BusyBox usage, Block known malicious IPs at perimeter firewalls and Educate teams on the rapid evolution of exploitation (from single actors to botnets within a week).

References

What is the most recent source of information about an incident ?

Most Recent Source: The most recent source of information about an incident are VulnCheck Research Report, CISA Binding Operational Directive (BOD) 22-01, CISA Known Exploited Vulnerabilities Catalog, Security Telemetry Data (RondoDox, Cryptomining and Reverse Shells).

What is the most recent URL for additional resources on cybersecurity best practices ?

Most Recent URL for Additional Resources: The most recent URL for additional resources on cybersecurity best practices is https://www.cisa.gov/known-exploited-vulnerabilities-catalog .

Investigation Status

What is the current status of the most recent investigation ?

Current Status of Most Recent Investigation: The current status of the most recent investigation is Ongoing (CISA advisory issued, no active exploitation documented yet).

Stakeholder and Customer Advisories

What was the most recent stakeholder advisory issued ?

Most Recent Stakeholder Advisory: The most recent stakeholder advisory issued was CISA mandates remediation by November 20, 2025, CISA KEV advisory, Security researcher warnings, .

What was the most recent customer advisory issued ?

Most Recent Customer Advisory: The most recent customer advisory issued were an Organizations using XWiki Platform urged to patch immediately or discontinue use and XWiki project patch notifications.

Initial Access Broker

What was the most recent entry point used by an initial access broker ?

Most Recent Entry Point: The most recent entry point used by an initial access broker was an CVE-2025-24893 (XWiki RCE).

What was the most recent reconnaissance period for an incident ?

Most Recent Reconnaissance Period: The most recent reconnaissance period for an incident was October 28, 2025 – November 2025 (ongoing).

Post-Incident Analysis

What was the most significant root cause identified in post-incident analysis ?

Most Significant Root Cause: The most significant root cause identified in post-incident analysis was Improper neutralization of directives in dynamically evaluated code (CWE-95)Improper handling of eval functions in SolrSearch componentGuest user access model creating exploitable trust, Delayed patching of critical vulnerabilityLack of early detection for exploitation attemptsExposed management interfaces (e.g., QNAP/DrayTek) used as launchpadsAutomated scanning tools (e.g., Nuclei) lowering the barrier for attackers.

What was the most significant corrective action taken based on post-incident analysis ?

Most Significant Corrective Action: The most significant corrective action taken based on post-incident analysis was Apply security patchesDiscontinue use if patching is not feasibleImplement network segmentationEnhance monitoring for suspicious activity, Accelerate vulnerability disclosure-to-patch timelinesImprove threat intelligence sharing for emerging exploitsEnhance detection capabilities for post-exploitation activity (e.g., reverse shells)Hardening of internet-exposed systems to prevent lateral movement.

cve

Latest Global CVEs (Not Company-Specific)

Description

MCP Server Kubernetes is an MCP Server that can connect to a Kubernetes cluster and manage it. Prior to 2.9.8, there is a security issue exists in the exec_in_pod tool of the mcp-server-kubernetes MCP Server. The tool accepts user-provided commands in both array and string formats. When a string format is provided, it is passed directly to shell interpretation (sh -c) without input validation, allowing shell metacharacters to be interpreted. This vulnerability can be exploited through direct command injection or indirect prompt injection attacks, where AI agents may execute commands without explicit user intent. This vulnerability is fixed in 2.9.8.

Risk Information
cvss3
Base: 6.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H
Description

XML external entity (XXE) injection in eyoucms v1.7.1 allows remote attackers to cause a denial of service via crafted body of a POST request.

Description

An issue was discovered in Fanvil x210 V2 2.12.20 allowing unauthenticated attackers on the local network to access administrative functions of the device (e.g. file upload, firmware update, reboot...) via a crafted authentication bypass.

Description

Cal.com is open-source scheduling software. Prior to 5.9.8, A flaw in the login credentials provider allows an attacker to bypass password verification when a TOTP code is provided, potentially gaining unauthorized access to user accounts. This issue exists due to problematic conditional logic in the authentication flow. This vulnerability is fixed in 5.9.8.

Risk Information
cvss4
Base: 9.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Rhino is an open-source implementation of JavaScript written entirely in Java. Prior to 1.8.1, 1.7.15.1, and 1.7.14.1, when an application passed an attacker controlled float poing number into the toFixed() function, it might lead to high CPU consumption and a potential Denial of Service. Small numbers go through this call stack: NativeNumber.numTo > DToA.JS_dtostr > DToA.JS_dtoa > DToA.pow5mult where pow5mult attempts to raise 5 to a ridiculous power. This vulnerability is fixed in 1.8.1, 1.7.15.1, and 1.7.14.1.

Risk Information
cvss4
Base: 5.5
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Access Data Using Our API

SubsidiaryImage

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?linkedin_id=xwiki' -H 'apikey: YOUR_API_KEY_HERE'

What Do We Measure ?

revertimgrevertimgrevertimgrevertimg
Incident
revertimgrevertimgrevertimgrevertimg
Finding
revertimgrevertimgrevertimgrevertimg
Grade
revertimgrevertimgrevertimgrevertimg
Digital Assets

Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.

These are some of the factors we use to calculate the overall score:

Network Security

Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.

SBOM (Software Bill of Materials)

Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.

CMDB (Configuration Management Database)

Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.

Threat Intelligence

Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.

Top LeftTop RightBottom LeftBottom Right
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.
Users Love Us Badge