How severe is CVE-2025-49585?

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

How do I fix CVE-2025-49585?

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

How do I mitigate CVE-2025-49585 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.

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

No public exploit code has been indexed for CVE-2025-49585 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-49585?

CVE-2025-49585 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-49585?

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

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

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

☕ Maven

Not in CISA KEV

CVE-2025-49585 — xwiki-platform-security-r…

Fix: xwiki/xwiki-platform@385bde9

CVE-2025-49585 is a CWE-357 vulnerability in org.xwiki.platform:xwiki-platform-security-requiredrights-default. A fix is available for org.xwiki.platform:xwiki-platform-security-requiredrights-default — see the affected versions and patch details below.

XWiki does not require right warnings for XClass definitions

Also known asGHSA-59w6-r9hm-439h

Published

Jun 13, 2025

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

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

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

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-security-requiredrights-default☕org.xwiki.platform:xwiki-platform-security-requiredrights-default☕org.xwiki.platform:xwiki-platform-security-requiredrights-default

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

Impact

When an attacker without script or programming right creates an XClass definition in XWiki (requires edit right), and that same document is later edited by a user with script, admin, or programming right, malicious code could be executed with the rights of the editing user without prior warning. In particular, this concerns custom display code, the script of computed properties and queries in database list properties. Note that warnings before editing documents with dangerous properties have only been introduced in XWiki 15.9, before that version, this was a known issue and the advice was simply to be careful.

Patches

This has been patched in XWiki 16.10.2, 16.4.7 and 15.10.16 by adding an analysis for the respective XClass properties.

Workarounds

We're not aware of any real workarounds apart from just being careful with editing documents previously edited by untrusted users as a user with script, admin or programming right.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-security-requiredrights-default`	all versions	15.10.16`org.xwiki.platform:xwiki-platform-security-requiredrights-default:15.10.16`
☕Maven	`org.xwiki.platform:xwiki-platform-security-requiredrights-default`	≥ 16.0.0-rc-1&&< 16.4.7	16.4.7`org.xwiki.platform:xwiki-platform-security-requiredrights-default:16.4.7`
☕Maven	`org.xwiki.platform:xwiki-platform-security-requiredrights-default`	≥ 16.5.0-rc-1&&< 16.10.2	16.10.2`org.xwiki.platform:xwiki-platform-security-requiredrights-default:16.10.2`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 16.5.0 && < 16.10.2

range

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-security-requiredrights-default, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-security-requiredrights-default to 15.10.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-49585 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.

Frequently Asked Questions

### Impact When an attacker without script or programming right creates an XClass definition in XWiki (requires edit right), and that same document is later edited by a user with script, admin, or programming right, malicious code could be executed with the rights of the editing user without prior warning. In particular, this concerns custom display code, the script of computed properties and queries in database list properties. Note that warnings before editing documents with dangerous properties have only been introduced in XWiki 15.9, before that version, this was a known issue and the advi