Internal media exposure via retained publish workflow
Published Oct 8, 2025 · Updated Oct 8, 2025
Information exposure in Opencast before 17.8 and 18.0 through 18.1 allows remote authenticated users to publish internal media. The editor's SaveButton kept selectedWorkflowId in later save-only requests, so returning from Save & Process Changes and choosing Save Changes launched the retained publish workflow. Exploitation requires event write access, editor use, and that exact sequence; the resulting publication can expose media intended to remain internal.
Summary
What happened
Information exposure in Opencast before 17.8 and 18.0 through 18.1 allows remote authenticated users to publish internal media. The editor's SaveButton kept selectedWorkflowId in later save-only requests, so returning from Save & Process Changes and choosing Save Changes launched the retained publish workflow. Exploitation requires event write access, editor use, and that exact sequence; the resulting publication can expose media intended to remain internal.
The record
- CVE
- CVE-2025-61906
- Published
- Oct 8, 2025
- Updated
- Oct 8, 2025
- Vendor
- Opencast
- Product
- Opencast
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 8, 2025CVE publishedPublication date reported by the CVE source.
- Oct 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 17.8
- Affected versionversion=>= 18.0, < 18.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Accidental publication workflow reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo