after\"/}}`. Therefore, this can a"}},{"@type":"Question","name":"How severe is GHSA-6vgh-9r3c-2cxp?","acceptedAnswer":{"@type":"Answer","text":"GHSA-6vgh-9r3c-2cxp has a CVSS score of 8.9/10, rated HIGH. Immediate patching is strongly recommended."}},{"@type":"Question","name":"Which packages are affected by GHSA-6vgh-9r3c-2cxp?","acceptedAnswer":{"@type":"Answer","text":"GHSA-6vgh-9r3c-2cxp affects the following packages: org.xwiki.platform:xwiki-platform-flamingo-skin-resources (Maven), org.xwiki.platform:xwiki-platform-flamingo-skin (Maven), org.xwiki.platform:xwiki-platform-flamingo (Maven), org.xwiki.platform:xwiki-platform-web-templates (Maven), org.xwiki.platform:xwiki-platform-web (Maven), org.xwiki.platform:xwiki-web-standard (Maven), org.xwiki.platform:xwiki-platform-flamingo-skin-resources (Maven), org.xwiki.platform:xwiki-platform-flamingo-skin (Maven), and 10 more. Ecosystems affected: Maven."}},{"@type":"Question","name":"How do I fix GHSA-6vgh-9r3c-2cxp?","acceptedAnswer":{"@type":"Answer","text":"Update org.xwiki.platform:xwiki-platform-flamingo-skin-resources to 13.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6vgh-9r3c-2cxp is resolved across your whole dependency graph."}},{"@type":"Question","name":"How do I detect GHSA-6vgh-9r3c-2cxp 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-flamingo-skin-resources, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version."}},{"@type":"Question","name":"How do I mitigate GHSA-6vgh-9r3c-2cxp if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"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."}},{"@type":"Question","name":"How does O3 Security protect against GHSA-6vgh-9r3c-2cxp?","acceptedAnswer":{"@type":"Answer","text":"O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6vgh-9r3c-2cxp can be triaged on real exposure rather than presence alone."}},{"@type":"Question","name":"Is GHSA-6vgh-9r3c-2cxp actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"Yes. There are 2 known exploit references for GHSA-6vgh-9r3c-2cxp, including 2 in-the-wild exploitations observed on GitHub and other sources. 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 GHSA-6vgh-9r3c-2cxp?","acceptedAnswer":{"@type":"Answer","text":"GHSA-6vgh-9r3c-2cxp has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 71th 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 GHSA-6vgh-9r3c-2cxp?","acceptedAnswer":{"@type":"Answer","text":"GHSA-6vgh-9r3c-2cxp is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type 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 GHSA-6vgh-9r3c-2cxp published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"GHSA-6vgh-9r3c-2cxp was published on April 12, 2023 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting."}}]}
Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

GHSA-6vgh-9r3c-2cxp — xwiki-platform-flamingo-s…

HIGHFix: xwiki/xwiki-platform@65ca06c

GHSA-6vgh-9r3c-2cxp is a high-severity (CVSS 8.9) Cross-site Scripting (XSS) vulnerability in org.xwiki.platform:xwiki-platform-flamingo-skin-resources. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-flamingo-skin-resources — see the affected versions and patch details below.

Improper Neutralization of Script-Related HTML Tags (XSS) in the LiveTable Macro

Also known asCVE-2023-29207
Published
Apr 12, 2023
Updated
Sep 10, 2026
Affected
18 pkgs
Patched
18 / 18
Exploits
2 known
Exploitation data as of Sep 22, 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 GHSA-6vgh-9r3c-2cxp.

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs71th percentile — riskier than 71% 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.

How urgent is this, really

GHSA-6vgh-9r3c-2cxp plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

18 pkgs affected
☕org.xwiki.platform:xwiki-platform-flamingo-skin-resources☕org.xwiki.platform:xwiki-platform-flamingo-skin☕org.xwiki.platform:xwiki-platform-flamingo☕org.xwiki.platform:xwiki-platform-web-templates☕org.xwiki.platform:xwiki-platform-web☕org.xwiki.platform:xwiki-web-standard☕org.xwiki.platform:xwiki-platform-flamingo-skin-resources☕org.xwiki.platform:xwiki-platform-flamingo-skin+10 more

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

The Livetable Macro wasn't properly sanitizing column names, thus allowing the insertion of raw HTML code including JavaScript. This vulnerability was also exploitable via the Documents Macro that is included since XWiki 3.5M1 and doesn't require script rights, this can be demonstrated with the syntax {{documents id="example" count="5" actions="false" columns="doc.title, before<script>alert(1)</script>after"/}}. Therefore, this can also be exploited by users without script right and in comments. With the interaction of a user with more rights, this could be used to execute arbitrary actions in the wiki, including privilege escalation, remote code execution, information disclosure, modifying or deleting content.

Patches

This has been patched in XWiki 14.9, 14.4.6, and 13.10.10.

Workarounds

It is possible to apply the patch to existing installations without upgrading. Only the files skins/flamingo/macros.vm and templates/macros.vm in the web application directory need to be replaced by a patched version.

For more information

If you have any questions or comments about this advisory:

Affected Packages

18 total 18 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.xwiki.platform:xwiki-platform-flamingo-skin-resources≥ 1.9-milestone-2&&< 13.10.1013.10.10org.xwiki.platform:xwiki-platform-flamingo-skin-resources:13.10.10
☕Mavenorg.xwiki.platform:xwiki-platform-flamingo-skin≥ 1.9-milestone-2&&< 13.10.1013.10.10org.xwiki.platform:xwiki-platform-flamingo-skin:13.10.10
☕Mavenorg.xwiki.platform:xwiki-platform-flamingo≥ 1.9-milestone-2&&< 13.10.1013.10.10org.xwiki.platform:xwiki-platform-flamingo:13.10.10
☕Mavenorg.xwiki.platform:xwiki-platform-web-templates≥ 1.9-milestone-2&&< 13.10.1013.10.10org.xwiki.platform:xwiki-platform-web-templates:13.10.10
☕Mavenorg.xwiki.platform:xwiki-platform-web≥ 1.9-milestone-2&&< 13.10.1013.10.10org.xwiki.platform:xwiki-platform-web:13.10.10
☕Mavenorg.xwiki.platform:xwiki-web-standard≥ 1.9-milestone-2&&< 13.10.1013.10.10org.xwiki.platform:xwiki-web-standard:13.10.10
Exploits & PoCs
2

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

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

  2. Fix

    Update org.xwiki.platform:xwiki-platform-flamingo-skin-resources to 13.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6vgh-9r3c-2cxp 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6vgh-9r3c-2cxp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6vgh-9r3c-2cxp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The [Livetable Macro](https://extensions.xwiki.org/xwiki/bin/view/Extension/Livetable%20Macro) wasn't properly sanitizing column names, thus allowing the insertion of raw HTML code including JavaScript. This vulnerability was also exploitable via the [Documents Macro](https://extensions.xwiki.org/xwiki/bin/view/Extension/Documents%20Macro) that is included since XWiki 3.5M1 and doesn't require script rights, this can be demonstrated with the syntax `{{documents id="example" count="5" actions="false" columns="doc.title, before<script>alert(1)</script>after"/}}`. Therefore, this can a
O3 Security · Impact-Aware SCA

Is GHSA-6vgh-9r3c-2cxp in your dependencies?

O3 Security finds GHSA-6vgh-9r3c-2cxp across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-6vgh-9r3c-2cxp: RCE (High 8.9) | O3 Security