← Back
CVE-2026-33137

Vulnerability in org.xwiki.platform:xwiki-platform-rest-server (CVE-2026-33137)

Summary

vulnerability in org.xwiki.platform:xwiki-platform-rest-server (CVE-2026-33137). Risk of unauthorized operations or information disclosure. Exploitable via `POST /wikis/{wikiName}`. Mitigation: upgrade to `18.1.0-rc-1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-33137** has been found in org.xwiki.platform:xwiki-platform-rest-server. Attackers can target a specific entry point like `POST /wikis/{wikiName}` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade org.xwiki.platform:xwiki-platform-rest-server to **18.1.0-rc-1** or later. If unsure, ask your IT team or search "org.xwiki.platform:xwiki-platform-rest-server CVE-2026-33137" on the vendor's site.
CVE-2026-33137 (org.xwiki.platform:xwiki-platform-rest-server) — CWE-862 / Attack surface: POST /wikis/{wikiName} Patched: `18.1.0-rc-1` — apply immediately Workaround: XWiki is not aware of any workarounds other than adding a rule into an HTTP proxy to prevent access POST request in the `/wikis/{wikiName}[/]` endpoint. Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-862) exists in org.xwiki.platform:xwiki-platform-rest-server. Attackers reach the vulnerable code path via `POST /wikis/{wikiName}` without authentication.
📍 Affected scope
org.xwiki.platform:xwiki-platform-rest-server — . Attack surface: POST /wikis/{wikiName}.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **18.1.0-rc-1**.
🛡️ Workaround
Workaround: XWiki is not aware of any workarounds other than adding a rule into an HTTP proxy to prevent access POST request in the `/wikis/{wikiName}[/]` endpoint.
🔍 Detection
Search webserver/proxy logs for unusual `POST /wikis/{wikiName}` requests with malformed payloads or SQL meta-characters. Run `grep -r 'org.xwiki.platform:xwiki-platform-rest-server' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'org.xwiki.platform:xwiki-platform-rest-server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.xwiki.platform:xwiki-platform-rest-server` を grep し、稼働しているサービス・バージョンを把握する。

  2. 3
    Hunt for indicators of compromise detect
    grep 'POST /wikis/{wikiName}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで `POST /wikis/{wikiName}` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 5
    Apply temporary workaround mitigate
    XWiki is not aware of any workarounds other than adding a rule into an HTTP proxy to prevent access POST request in the `/wikis/{wikiName}[/]` endpoint.

    パッチが適用されるまでの応急処置として、XWiki is not aware of any workarounds other than adding a rule into an HTTP proxy to prevent access POST request in the `/wikis/{wikiName}[/]` endpoint. を実施。回避策の副作用 (機能低下) を確認した上で。

  4. 6
    Apply patch patch
    Upgrade org.xwiki.platform:xwiki-platform-rest-server to 18.1.0-rc-1

    ステージング環境で 18.1.0-rc-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  5. 7
    Post-deployment verification verify
    Replay attack against POST /wikis/{wikiName} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.xwiki.platform:xwiki-platform-rest-server
[{"type":"ECOSYSTEM","events":[{"introduced":"18.0.0-rc-1"},{"fixed":"18.1.0-rc-1"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →