Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕ Maven

GHSA-rmm7-r7wr-xpfg

CRITICAL

XWiki Realtime WYSIWYG Editor extension allows privilege escalation (PR) through realtime WYSIWYG editing

Also known asCVE-2025-23025
Published
Jan 14, 2025
Updated
Jan 14, 2025
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk31th percentile-1.80%
0.00%2.15%4.30%6.45%5.1%0.4%Dec 25Apr 26Jun 26

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.

Blast Radius

3 pkgs affected
☕org.xwiki.platform:xwiki-platform-realtime-wysiwyg-ui☕org.xwiki.platform:xwiki-platform-realtime-wysiwyg-ui☕org.xwiki.platform:xwiki-platform-realtime-wysiwyg-ui

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

NOTE: The Realtime WYSIWYG Editor extension was experimental, and thus not recommended, in the versions affected by this vulnerability. It has become enabled by default, and thus recommended, starting with XWiki 16.9.0.

A user with only edit right can join a realtime editing session where others, that where already there or that may join later, have script or programming access rights. This user can then insert script rendering macros that are executed for those users in the realtime session that have script or programming rights. The inserted scripts can be used to gain more access rights.

Here's an example that works with XWiki 15.10.9+ and 16.2.0+:

  • the attacker starts editing a wiki page in realtime (for which they have edit right)
  • another user, with script or programming access right joins the editing session (e.g. by clicking on a link / URL provided by the attacker)
  • the attacker inserts a script rendering macro, say {{velocity}}I can run scripts{{/velocity}}, in the edited content, using the WYSIWYG editor UI
  • the edited content is reloaded for both the attacker and the other user, in order to render the inserted macro
    • the attacker gets a rendering error message
    • the other user sees "I can run scripts"

The attacker can obviously use more advanced scripts to gain access rights.

Before XWiki 15.10.9 and 16.2.0 the edited content was not re-rendered for all the users in the editing sesesion, but only for the user that inserted the macro. This means that in order to reproduce the problem the other user had to insert or update a macro or save and view the content.

Patches

This vulnerability has been patched in XWiki 15.10.12, 16.4.1 and 16.6.0-rc-1.

Workarounds

To avoid this vulnerability you can:

References

For more information

If you have any questions or comments about this advisory:

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.xwiki.platform:xwiki-platform-realtime-wysiwyg-ui≥ 13.9-rc-1&&< 15.10.1215.10.12
☕Mavenorg.xwiki.platform:xwiki-platform-realtime-wysiwyg-ui≥ 16.0.0-rc-1&&< 16.4.116.4.1
☕Mavenorg.xwiki.platform:xwiki-platform-realtime-wysiwyg-ui≥ 16.5.0-rc-1&&< 16.6.0-rc-116.6.0-rc-1

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-realtime-wysiwyg-ui. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.xwiki.platform:xwiki-platform-realtime-wysiwyg-ui to 15.10.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rmm7-r7wr-xpfg is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-rmm7-r7wr-xpfg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rmm7-r7wr-xpfg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact NOTE: The [Realtime WYSIWYG Editor](https://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime%20WYSIWYG%20Editor/) extension was **experimental**, and thus **not recommended**, in the versions affected by this vulnerability. It has become enabled by default, and thus recommended, starting with XWiki 16.9.0. A user with only **edit right** can join a realtime editing session where others, that where already there or that may join later, have **script** or **programming** access rights. This user can then insert **script rendering macros** that are executed for those users in t
O3 Security · Impact-Aware SCA

Is GHSA-rmm7-r7wr-xpfg in your dependencies?

O3 detects GHSA-rmm7-r7wr-xpfg across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works