XWiki is a generic wiki platform. In XWiki 16.10.0, required rights were introduced as a way to limit which rights a document can have. Part of the security model of required rights is that a user who doesn't have a right also cannot define that right as required right. That way, users who are editing documents on which required rights are enforced can be sure that they're not giving a right to a script or object that it didn't have before. A bug in the implementation of the enforcement of this rule means that in fact, it was possible for any user with edit right on a document to set programming right as required right. If then a user with programming right edited that document, the content of that document would gain programming right, allowing remote code execution. This thereby defeats most of the security benefits of required rights. As XWiki still performs the required rights analysis when a user edits a page even when required rights are enforced, the user with programming right would still be warned about the dangerous content unless the attacker managed to bypass this check. Note also that none of the affected versions include a UI for enabling the enforcing of required rights so it seems unlikely that anybody relied on them for security in the affected versions. As this vulnerability provides no additional attack surface unless all documents in the wiki enforce required rights, we consider the impact of this attack to be low even though gaining programming right could have a high impact. This vulnerability has been patched in XWiki 16.10.4 and 17.1.0RC1. No known workarounds are available except for upgrading.
CVE-2025-48063
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 1.0% (63rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2025-16054 (ENISA EUVD) · GHSA-rhfv-688c-p6hp (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 56EG Risk 56/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 1.0%
- EPSS %ILE
- 63rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
May 21, 2025
Last Modified
June 20, 2025
Advisory Details (3)
Auto-updated Aug 4, 2026Users with just edit right can enforce required rights with programming right · Advisory · xwiki/xwiki-platform · GitHub
https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-rhfv-688c-p6hpcommit 2557813aef3b (xwiki/xwiki-platform)
Patch available: xwiki/xwiki-platform xwiki-platform-17.10.3 (contains commit 2557813aef3b)
https://github.com/xwiki/xwiki-platform/commit/2557813aef3b863988d6cca58de996e207086898Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| maven | org.xwiki.platform:xwiki-platform-security-authorization-bridge @ 16.10.4 (fixes >= 16.10.0-rc-1, < 16.10.4) | — | ghsa |
| maven | org.xwiki.platform:xwiki-platform-security-authorization-bridge @ 17.1.0-rc-1 (fixes >= 17.0.0-rc-1, < 17.1.0-rc-1) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.xwiki.platform:xwiki-platform-security-authorization-bridge | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 39× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 95 of 203 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:43 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-11-01 08:05 UTCGHSA enrichmentGHSA-rhfv-688c-p6hp · GitHub severity MODERATE
- 2026-11-01 08:05 UTCEG score recompute
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-29 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-28 16:30 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-27 12:14 UTCEG score recompute
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-25 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-25 16:22 UTCEG score recompute
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-23 16:30 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-18 05:30 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
- 2026-10-16 16:38 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 1.0% · 60th percentile
Show 70 moreShow fewer
- 2026-10-13 16:32 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-12 17:01 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-11 20:35 UTCEG score recompute
- 2026-10-11 18:46 UTCEG score recompute
- 2026-10-11 15:22 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-08 17:10 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-10-02 13:11 UTCOSV refresh
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-27 13:45 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-26 00:25 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-21 21:06 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-20 20:15 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 1.0% · 60th percentile
- 2026-09-17 19:29 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-15 03:09 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-13 11:24 UTCOSV refresh
- 2026-09-12 15:00 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-11 09:36 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-08 21:59 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-07 16:00 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-05 15:28 UTCEPSS rescoreEPSS 1.0% · 58th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-02 14:11 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-09-01 04:38 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 1.0% · 58th percentile
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 1.0% · 58th percentile
- 2026-08-27 14:24 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 1.0% · 59th percentile
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 1.0% · 58th percentile
- 2026-08-25 12:32 UTCOSV refresh
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 1.0% · 58th percentile
- 2026-08-24 09:22 UTCEPSS rescoreEPSS 1.0% · 58th percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 1.0% · 58th percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.9% · 56th percentile
- 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
- 2026-08-09 04:57 UTCOSV refresh
- 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
- 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
- 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2025-48063?
When was the CVE record for CVE-2025-48063 published?
Is CVE-2025-48063 actively exploited?
What is the CVSS score of CVE-2025-48063?
How do I remediate CVE-2025-48063?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-48063
Is Your Infrastructure Affected by CVE-2025-48063?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.