Vulnerability in drupal/wisski (CVE-2026-13239)
Summary
Vulnerability in drupal/wisski (CVE-2026-13239). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.2.0 or later.
Original description
The description as published by the source.
The module adds support for the mirador viewer in WissKI and enables annotations on images via the mirador viewer.
It does not sufficiently check the submitted parameters via a route and writes these to the session object without further checks, which can lead to Access Bypass.
This vulnerability is mitigated by the fact that it is specific to the wisski_mirador submodule.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-13239 has been found in drupal/wisski.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade drupal/wisski to 4.2.0 or later.
If unsure, ask your IT team or search "drupal/wisski CVE-2026-13239" on the vendor's site.
CVE-2026-13239 (drupal/wisski) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.2.0 — apply immediately
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.
A vulnerability (CWE-862) exists in drupal/wisski.
Check the vendor advisory for the affected versions of drupal/wisski.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 4.2.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'drupal/wisski' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'drupal/wisski' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
drupal/wisskiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade drupal/wisski to 4.2.0ステージング環境で 4.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web drupal.org
- web nvd.nist.gov
- web github.com