How severe is CVE-2025-49584?

No CVSS score has been assigned to CVE-2025-49584 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-49584?

CVE-2025-49584 affects the following packages: org.xwiki.platform:xwiki-platform-rest-server (Maven), org.xwiki.platform:xwiki-platform-rest-server (Maven), org.xwiki.platform:xwiki-platform-rest-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-49584?

Update org.xwiki.platform:xwiki-platform-rest-server to 16.4.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-49584 is resolved across your whole dependency graph.

How do I detect CVE-2025-49584 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-rest-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-49584 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-49584?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-49584 can be triaged on real exposure rather than presence alone.

Is CVE-2025-49584 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-49584 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-49584?

CVE-2025-49584 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-49584?

CVE-2025-49584 is classified as CWE-201 (CWE-201). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-49584 published, and has it been updated?

CVE-2025-49584 was published on June 13, 2025 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2025-49584: xwiki-platform-rest-server

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-49584.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-rest-server☕org.xwiki.platform:xwiki-platform-rest-server☕org.xwiki.platform:xwiki-platform-rest-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

XWiki is a generic wiki platform. In XWiki Platform versions 10.9 through 16.4.6, 16.5.0-rc-1 through 16.10.2, and 17.0.0-rc-1, the title of every single page whose reference is known can be accessed through the REST API as long as an XClass with a page property is accessible, this is the default for an XWiki installation. This allows an attacker to get titles of pages whose reference is known, one title per request. This doesn't affect fully private wikis as the REST endpoint checks access rights on the XClass definition. The impact on confidentiality depends on the strategy for page names. By default, page names match the title, so the impact should be low but if page names are intentionally obfuscated because the titles are sensitive, the impact could be high. This has been fixed in XWiki 16.4.7, 16.10.3 and 17.0.0 by adding access control checks before getting the title of any page.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-rest-server`	≥ 10.9&&< 16.4.7	16.4.7`org.xwiki.platform:xwiki-platform-rest-server:16.4.7`
☕Maven	`org.xwiki.platform:xwiki-platform-rest-server`	≥ 16.5.0-rc-1&&< 16.10.3	16.10.3`org.xwiki.platform:xwiki-platform-rest-server:16.10.3`
☕Maven	`org.xwiki.platform:xwiki-platform-rest-server`	≥ 17.0.0-rc-1&&< 17.0.0	17.0.0`org.xwiki.platform:xwiki-platform-rest-server:17.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-rest-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-rest-server to 16.4.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-49584 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-49584 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-49584. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

XWiki is a generic wiki platform. In XWiki Platform versions 10.9 through 16.4.6, 16.5.0-rc-1 through 16.10.2, and 17.0.0-rc-1, the title of every single page whose reference is known can be accessed through the REST API as long as an XClass with a page property is accessible, this is the default for an XWiki installation. This allows an attacker to get titles of pages whose reference is known, one title per request. This doesn't affect fully private wikis as the REST endpoint checks access rights on the XClass definition. The impact on confidentiality depends on the strategy for page names. B

O3 Security · Impact-Aware SCA

Is CVE-2025-49584 in your dependencies?

O3 Security finds CVE-2025-49584 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

CVE-2025-49584 — xwiki-platform-rest-server