Is CVE-2023-48241 automatically exploitable on my domain?

Not necessarily. ThreatPort treats CVE-2023-48241 as a risk signal that must be connected to observed external assets, detected technologies, and reachable services.

What does ThreatPort check for CVE-2023-48241?

ThreatPort looks for public asset evidence, service fingerprints, CVE-linked technology signals, exposed endpoints, weak DNS/TLS posture, and remediation context.

Should this replace vendor advisories?

No. Use vendor advisories and official patches for final remediation decisions; use ThreatPort to find externally visible exposure and prove cleanup.

CVE-2023-48241 Xwiki exposure check

From CVE Record to External Exposure

XWiki Platform is a generic wiki platform. Starting in version 6.3-milestone-2 and prior to versions 14.10.15, 15.5.1, and 15.6RC1, the Solr-based search suggestion provider that also duplicates as generic JavaScript API for search results in XWiki exposes the content of all documents of all wikis to anybody who has access to it, by default it is public. This exposes all information stored in the wiki (but not some protected information like password hashes). While there is a right check normally, the right check can be circumvented by explicitly requesting fields from Solr that don't include the data for the right check. This has been fixed in XWiki 15.6RC1, 15.5.1 and 14.10.15 by not listing documents whose rights cannot be checked. No known workarounds are available.

Xwiki vulnerability should be triaged by matching the affected vendor and product to live, internet-facing assets rather than treating the CVE as an abstract feed item. ThreatPort focuses on the first question that budget-constrained IT leaders and CISOs ask: what can an outside observer find today, how severe is it, and what should be fixed first?

Known Exploitation Record

Known ransomware campaign use: Not recorded
EPSS exploitation probability: 72.82% (99p)
CVSS base score: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)
Disclosed: 2023-11-20
Weakness type: CWE-285

Source: CISA Known Exploited Vulnerabilities catalog and FIRST.org EPSS.

What ThreatPort Checks

Identify externally reachable services that appear related to Xwiki Xwiki.

Map detected technologies to CVE-2023-48241, severity context, and practical remediation priority.

Check TLS, DNS, headers, exposed panels, stale endpoints, and service fingerprints from a public attacker perspective.

Produce a concise scorecard first, then unlock deeper AI pentest evidence and PDF reporting when remediation planning begins.

The output is intentionally practical: ownership clues, risk context, remediation hints, and repeatable evidence that can be shared with technical teams or leadership. It is not positioned as magic compliance automation or a replacement for human security judgment.

Lean security teams rarely need another broad vulnerability list. They need to know whether an exposed endpoint, an expired certificate, a weak DNS setting, or a CVE-linked service is likely to affect the systems they actually run. ThreatPort scans from the outside in, ranks what it finds by real reachability rather than raw CVSS, and hands back evidence a team can act on the same day.

Route-Specific Evidence Profile

CVE-2023-48241 affects Xwiki, a CWE-285 weakness. Disclosed 2023-11-20. This page exists to answer one question: is anything you own externally reachable and running it.

Assets This Page Should Care About

Public domains Subdomains Externally reachable web apps TLS endpoints DNS records

Signals Worth Prioritizing

Forgotten subdomains

Weak DNS or email controls

Outdated services

Risky headers

What Should Be Reviewed First in This Context?

For teams running Xwiki, the first step is to validate internet-facing assets with business relevance instead of producing a generic vulnerability list.