Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-55728 is a critical-severity Eval Injection (CWE-95) vulnerability in Xwiki Pro Macros. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique JavaScript (T1059.007); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
XWiki Remote Macros, a set of rendering macros intended for Confluence-to-XWiki migrations, contains an injection vulnerability in the panel macro. Starting with version 1.0 and prior to 1.26.5, the classes parameter is incorporated into XWiki syntax without escaping, enabling syntax injection that leads to remote code execution. The flaw is tracked under CWE-95 and CWE-94 and carries a CVSS 3.1 score of 10.0.
Any user able to edit a page can supply a malicious classes value and obtain arbitrary code execution on the server with no additional authentication or user interaction required. Successful exploitation grants full confidentiality, integrity, and availability impact across the affected XWiki instance.
The project security advisory and accompanying commit in version 1.26.5 address the issue by properly escaping the parameter; administrators are advised to upgrade immediately. The referenced GitHub advisory and XWiki Jira entry provide the patch details and upgrade guidance.
EPSS for the CVE rose from a low baseline to a peak of 0.2004 on 2026-01-13 before receding to the current value of 0.0400, indicating that exploitation interest increased after public disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-27451
Vulnerability Data
XWiki Remote Macros provides XWiki rendering macros that are useful when migrating content from Confluence. Starting in version 1.0 and prior to version 1.26.5, missing escaping of the classes parameter in the panel macro allows remote code execution for any…
more
user who can edit any page The classes parameter is used without escaping in XWiki syntax, thus allowing XWiki syntax injection which enables remote code execution. Version 1.26.5 contains a patch for the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.1V1.3.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and code analysis can discover eval-injection flaws but does not stop their introduction.
Input validation explicitly requires neutralizing untrusted data before it reaches dynamic evaluation constructs such as eval.
Least privilege limits the damage an injected code fragment can perform once executed.
Secure-development standards and tools can mandate safe coding patterns that avoid unsafe dynamic evaluation.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input neutralization and avoidance of unsafe dynamic evaluation.
PR.DS-10 protects runtime data confidentiality/integrity but has no bearing on neutralizing externally influenced input during code generation, so neither direction shows any preventive effect.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect eval injection vulnerabilities before deployment.
Secure development life cycle mandates input validation and safe coding practices that directly prevent eval injection.
Application security requirements include rules against dynamic code execution of untrusted input.
Secure architecture principles discourage unsafe dynamic evaluation constructs.
Secure coding explicitly requires neutralization of input before dynamic evaluation, directly mitigating eval injection.
Separation of environments limits the blast radius if eval injection occurs in non-production.