AI security incident: XWiki vulnerable to click-jacking through CSS injection in comments (GHSA-74rh-c5rh-8...
Impact It's possible using comments to inject CSS that would transform the full wiki in a link area leading to a malicious page. All versions of XWiki are impacted by this kind of attack. ### Patches The problem has been patched not by preventing injecting CSS in comments, which is currently a feature of XWiki, but by requiring confirmation from users when driving them to untrusted domains after clicking on a link, thus preventing any click-jacking attack. This security measure has been put in place in XWiki 17.9.0, 17.4.6, 16.10.13. ### Workarounds There's no out-of-the-box workaround, but it should be possible to partly reuse [the javascript code provided for the security measure](https://github.com/xwiki/xwiki-platform/blob/xwiki-platform-17.9.
Why This Is AI-Related
This advisory is part of the public incident archive, but the current source material uses limited explicit AI terminology, so the cited sources should be reviewed carefully when judging AI relevance and exposure.
- Explicit AI-specific signals are limited in the current source material, so use the cited advisory to validate scope during triage.
Affected Workflow
Review the AI product, dependency, and integration points mentioned in the source advisory before broadening remediation.
Likely Attack Path
The advisory indicates a security path that can affect AI applications, assistants, models, or connected automation workflows if the component is deployed.
Impact
The advisory has meaningful security implications for an AI-related product, dependency, or workflow and should be triaged against deployed usage. Severity HIGH. Classification confidence 53%. Source channel GHSA.
Detection And Triage Signals
- New security events tied to the affected component or advisory identifier
- Changes in AI workflow behavior, access logs, or plugin execution after the advisory window
- Evidence that the vulnerable version is active in environments that process sensitive data
Recommended Response
- Confirm whether affected products, models, or integrations are used in your environment.
- Apply vendor fixes or mitigations and restrict risky permissions until verified.
- Monitor logs for related indicators and document containment for audit evidence.
Compliance And Business Impact
Even when exploit details are still emerging, delayed triage can widen operational and compliance exposure around AI systems.
Sources
Want alerts like this in real time?
Get notified with incident context, likely impact, and response guidance.
Get Notified