Security readout for executives and security teams
Plain-English summary
CVE-2023-37277 lets an attacker abuse a logged-in XWiki user’s browser to make unwanted REST API changes. If the targeted user has programming rights, the impact can reach remote code execution, putting site data, uptime, and integrity at risk.
Executive priority
Treat this as urgent for any active XWiki deployment, especially public or widely used internal wikis. The issue can escalate from a browser-based request forgery into full compromise when privileged wiki users are targeted.
Technical view
Affected XWiki Platform versions accept REST API POST requests with browser-form content types without requiring a CSRF token header. This enables CSRF. The vendor patched it in 14.10.8 and 15.2 by requiring a CSRF token header for susceptible request types.
Likely exposure
Organizations running XWiki Platform >=1.8 and <14.10.8, or >=15.0-rc-1 and <15.2, are in scope. Exposure is most serious where cookie-authenticated users with programming rights use the affected instance.
Exploitation context
The source bundle reports no CISA KEV listing and provides no evidence of active exploitation. Exploitation requires user interaction; the highest-impact scenario involves a victim with programming rights being induced to trigger unwanted REST API actions.
Researcher notes
The key condition is CSRF through REST API POST handling of form-compatible content types. Validate version exposure and privilege context; do not assume active exploitation from the provided sources. Patch behavior centers on CSRF token header enforcement.
Mitigation direction
- Upgrade XWiki Platform to 14.10.8, 15.2, or later vendor-supported releases.
- Review the GitHub advisory for any deployment-specific guidance.
- Verify SameSite cookie protections where compatible, especially for cookie-based authentication.
- Limit programming rights to users who genuinely require them.
- Monitor vendor advisories for any additional mitigations or backports.
Validation and detection
- Inventory XWiki Platform versions across production and non-production systems.
- Confirm affected instances are upgraded beyond the vulnerable version ranges.
- Check whether cookie-based authentication is used on affected deployments.
- Review accounts and groups with programming rights.
- Review logs for unusual REST API changes around sensitive pages or macros.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-37277 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.7CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-6xxr-648m-gch6CVE reference · x_refsource_CONFIRM
- https://github.com/xwiki/xwiki-platform/commit/4c175405faa0e62437df397811c7526dfc0fbae7CVE reference · x_refsource_MISC
- https://jira.xwiki.org/browse/XWIKI-20135CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.