How severe is CVE-2025-66472?

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

Which packages are affected by CVE-2025-66472?

CVE-2025-66472 affects the following packages: org.xwiki.platform:xwiki-platform-flamingo-skin-resources (Maven), org.xwiki.platform:xwiki-platform-flamingo-skin-resources (Maven), org.xwiki.platform:xwiki-platform-web-templates (Maven), org.xwiki.platform:xwiki-platform-web-templates (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-66472?

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

How do I detect CVE-2025-66472 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-flamingo-skin-resources, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-66472 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-66472?

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

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

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

CVE-2025-66472 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th 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-66472?

CVE-2025-66472 is classified as Cross-site Scripting (XSS) (CWE-79), CWE-80 (CWE-80). 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.

Is there exploit tooling available for CVE-2025-66472?

A Nuclei detection template exists for CVE-2025-66472, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

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

CVE-2025-66472 was published on December 10, 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.

☕ Maven

Not in CISA KEV

CVE-2025-66472 — xwiki-platform-flamingo-s…

Fix: xwiki/xwiki-platform@cb578b1

CVE-2025-66472 is a Cross-site Scripting (XSS) vulnerability in org.xwiki.platform:xwiki-platform-flamingo-skin-resources. A fix is available for org.xwiki.platform:xwiki-platform-flamingo-skin-resources — see the affected versions and patch details below.

XWiki vulnerable to a reflected XSS via xredirect parameter in DeleteApplication

Also known asGHSA-7vpr-jm38-wr7w

Published

Dec 10, 2025

Updated

Aug 12, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-66472.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% 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

4 pkgs affected

☕org.xwiki.platform:xwiki-platform-flamingo-skin-resources☕org.xwiki.platform:xwiki-platform-flamingo-skin-resources☕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

A reflected XSS vulnerability in XWiki allows an attacker to send a victim to a URL with a deletion confirmation message on which the attacker-supplied script is executed when the victim clicks the "No" button. When the victim has admin or programming right, this allows the attacker to execute basically arbitrary actions on the XWiki installation including remote code execution.

Patches

This vulnerability has been patched in XWiki 16.10.10, 17.4.2 and 17.5.0 by using the affected URL parameter only in the intended context.

Workarounds

The patch can be manually applied to the templates that are present in the WAR. A restart of XWiki is needed for the changes to be applied.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-flamingo-skin-resources`	≥ 6.2-milestone-1&&< 16.10.10	16.10.10`org.xwiki.platform:xwiki-platform-flamingo-skin-resources:16.10.10`
☕Maven	`org.xwiki.platform:xwiki-platform-flamingo-skin-resources`	≥ 17.0.0-rc-1&&< 17.4.2	17.4.2`org.xwiki.platform:xwiki-platform-flamingo-skin-resources:17.4.2`
☕Maven	`org.xwiki.platform:xwiki-platform-web-templates`	≥ 6.2-milestone-1&&< 16.10.10	16.10.10`org.xwiki.platform:xwiki-platform-web-templates:16.10.10`
☕Maven	`org.xwiki.platform:xwiki-platform-web-templates`	≥ 17.0.0-rc-1&&< 17.4.2	17.4.2`org.xwiki.platform:xwiki-platform-web-templates:17.4.2`

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-flamingo-skin-resources, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-flamingo-skin-resources to 16.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-66472 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-66472 can be triaged on real exposure rather than presence alone.

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

How to detect CVE-2025-66472

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2025-66472 -u https://target

Template: XWiki DeleteApplication - Cross-Site Scripting
Severity: medium
Impact: An attacker can execute arbitrary JavaScript in the victim's browser, leading to potential session hijacking, data theft, or further attacks.
Remediation: Upgrade to XWiki 14.10.14, 15.5.1, 15.8-rc-1 or above. Do not interact with suspiciously crafted links.

Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact A reflected XSS vulnerability in XWiki allows an attacker to send a victim to a URL with a deletion confirmation message on which the attacker-supplied script is executed when the victim clicks the "No" button. When the victim has admin or programming right, this allows the attacker to execute basically arbitrary actions on the XWiki installation including remote code execution. ### Patches This vulnerability has been patched in XWiki 16.10.10, 17.4.2 and 17.5.0 by using the affected URL parameter only in the intended context. ### Workarounds The [patch](https://github.com/xwiki/x

O3 Security · Impact-Aware SCA

Is CVE-2025-66472 in your dependencies?

O3 Security finds CVE-2025-66472 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-66472 — xwiki-platform-flamingo-s…

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

How to detect CVE-2025-66472

Frequently Asked Questions

Is CVE-2025-66472 in your dependencies?