Vulnerability in PKP Open Journal Systems (CVE-2026-111609)
Summary
Vulnerability in PKP Open Journal Systems (CVE-2026-111609). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
PKP Open Journal Systems through 3.5.0-5 contains an insecure direct object reference vulnerability that allows journal or subscription managers to access other journals' subscriptions by supplying arbitrary subscription ids. Attackers can enumerate sequential ids through editSubscription to view subscriber details and use updateSubscription to reassign subscriptions to their own journal, revoking victims' access.
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-111609 has been found in PKP Open Journal Systems.
Risk of unauthorized operations or information disclosure. CVSS score: 3.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "PKP Open Journal Systems CVE-2026-111609" on the vendor's site.
CVE-2026-111609 (PKP Open Journal Systems) — CWE-639 / CVSS v3 3.8
Attack vector: remote (network-reachable) / no user interaction
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-639) exists in PKP Open Journal Systems.
Check the vendor advisory for the affected versions of PKP Open Journal Systems.
Severity: Low (CVSS 3.8/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで PKP Open Journal Systems を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。