`.\nWhen the admin user then saves the document, a conflict popup appears."}},{"@type":"Question","name":"How severe is CVE-2024-41947?","acceptedAnswer":{"@type":"Answer","text":"CVE-2024-41947 has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended."}},{"@type":"Question","name":"Which packages are affected by CVE-2024-41947?","acceptedAnswer":{"@type":"Answer","text":"CVE-2024-41947 affects the following packages: org.xwiki.platform:xwiki-platform-web-templates (Maven), org.xwiki.platform:xwiki-platform-web-templates (Maven). Ecosystems affected: Maven."}},{"@type":"Question","name":"How do I fix CVE-2024-41947?","acceptedAnswer":{"@type":"Answer","text":"Update org.xwiki.platform:xwiki-platform-web-templates to 15.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-41947 is resolved across your whole dependency graph."}},{"@type":"Question","name":"How do I detect CVE-2024-41947 in my Maven dependencies?","acceptedAnswer":{"@type":"Answer","text":"Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-web-templates, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version."}},{"@type":"Question","name":"How do I mitigate CVE-2024-41947 if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page."}},{"@type":"Question","name":"Is CVE-2024-41947 actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"Yes. There are 1 known exploit references for CVE-2024-41947, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization."}},{"@type":"Question","name":"What is the EPSS score for CVE-2024-41947?","acceptedAnswer":{"@type":"Answer","text":"CVE-2024-41947 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th 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."}},{"@type":"Question","name":"What type of vulnerability is CVE-2024-41947?","acceptedAnswer":{"@type":"Answer","text":"CVE-2024-41947 is classified as CWE-80 (CWE-80), Cross-site Scripting (XSS) (CWE-79). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure."}},{"@type":"Question","name":"When was CVE-2024-41947 published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"CVE-2024-41947 was published on July 31, 2024 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."}}]}
NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

CVE-2024-41947 — xwiki-platform-web-templa…

CRITICALFix: xwiki/xwiki-platform@821d43e

CVE-2024-41947 is a critical-severity (CVSS 9) CWE-80 vulnerability in org.xwiki.platform:xwiki-platform-web-templates. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-web-templates — see the affected versions and patch details below.

XWiki Platform XSS through conflict resolution

Also known asGHSA-692v-783f-mg8x
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-41947.

EPSS Exploitation Probability

via FIRST.org ↗
1.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk
0.00%5.48%11.0%16.4%13.0%1.7%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.xwiki.platform:xwiki-platform-web-templates☕org.xwiki.platform:xwiki-platform-web-templates

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

By creating a conflict when another user with more rights is currently editing a page, it is possible to execute JavaScript snippets on the side of the other user, which compromises the confidentiality, integrity and availability of the whole XWiki installation.

To reproduce on a XWiki instance, a user with admin rights needs to edit a document without saving right away. Then, as another user without any other right than edit on the specific document, change the whole content to <script>alert('XSS')</script>. When the admin user then saves the document, a conflict popup appears. If they select "Fix each conflict individually" and see an alert displaying "XSS", then the instance is vulnerable.

Patches

This has been patched in XWiki 15.10.8 and 16.3.0RC1.

Workarounds

We're not aware of any workaround except upgrading.

References

For more information

If you have any questions or comments about this advisory:

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.xwiki.platform:xwiki-platform-web-templates≥ 11.8-rc-1&&< 15.10.815.10.8org.xwiki.platform:xwiki-platform-web-templates:15.10.8
☕Mavenorg.xwiki.platform:xwiki-platform-web-templates≥ 16.0.0-rc-1&&< 16.3.0-rc-116.3.0-rc-1org.xwiki.platform:xwiki-platform-web-templates:16.3.0-rc-1

Affected Products

1 product · 2 configurations
Application
xwikixwiki
≥ 16.0 && < 16.3.0
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52209webappsphp

OpenCMS 17.0 - Stored Cross Site Scripting (XSS)

by Siddhartha Naik · Apr 15, 2025

Exploit-DB Source

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-web-templates, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.xwiki.platform:xwiki-platform-web-templates to 15.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-41947 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact By creating a conflict when another user with more rights is currently editing a page, it is possible to execute JavaScript snippets on the side of the other user, which compromises the confidentiality, integrity and availability of the whole XWiki installation. To reproduce on a XWiki instance, a user with admin rights needs to edit a document without saving right away. Then, as another user without any other right than edit on the specific document, change the whole content to `<script>alert('XSS')</script>`. When the admin user then saves the document, a conflict popup appears.
O3 Security · Impact-Aware SCA

Is CVE-2024-41947 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-41947: xwiki-platform-web — Fixed in 15.10.8