{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61906 exists.","fix":"No fix has been published for CVE-2025-61906 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-61906 is a low-severity vulnerability in opencast, published on 8 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-61906 and fix it if it is affected.\n\nWhat it is: CVE-2025-61906 is a low-severity vulnerability in opencast, published on 8 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61906 exists.\n\nAffected product: opencast. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-61906/ (Markdown: https://insights.sbomify.com/CVE-2025-61906/index.md)","id":"CVE-2025-61906","markdown":"https://insights.sbomify.com/CVE-2025-61906/index.md","name":"CVE-2025-61906","record":{"aliases":["GHSA-x6vw-p693-jjhv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Opencast video platform","requires_auth":"low_privilege","summary":"Users with write access can accidentally publish internal media due to a UI logic flaw in the editor, exposing sensitive content.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"opencast","vendor":"apereo"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Opencast is a free, open-source platform to support the management of educational audio and video content. Prior to Opencast 17.8 and 18.2, in some situations, Opencast's editor may publish a video without notifying the user. This may lead to users accidentally publishing media not meant for publishing, and thus possibly exposing internal media. This risk of this actually impacting someone is very low, though. This can only be triggered by users with write access to an event. They also have to use the editor, which is usually an action taken if they want to publish media and not something users would use on internal media they do not want to publish. Finally, they have to first click on \"Save \u0026 Publish\" before then selecting the \"Save\" option. Nevertheless, while very unlikely, this can happen. This issue is fixed in Opencast 17.8 and 18.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Opencast's editor accidentally publishes videos/overwrites publications #1626","id":"CVE-2025-61906","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Icinga 2 API users could access restricted values in filter expressions","id":"CVE-2025-61907"},"packages":[],"prev":{"headline":"Not used","id":"CVE-2025-61895"},"products":["opencast"],"published":"2025-10-08","related":[{"cvss_score":9.9,"headline":"Files Accessible to External Parties in Opencast","id":"CVE-2021-43821","kev_date_added":null,"published":"2021-12-14"},{"cvss_score":8.7,"headline":"Authentication Bypass For Endpoints With Anonymous Access in OpenCast","id":"CVE-2020-5206","kev_date_added":null,"published":"2020-01-30"},{"cvss_score":8.1,"headline":"Opencast vulnerable to billion laughs attack (XML bomb)","id":"CVE-2021-32623","kev_date_added":null,"published":"2021-06-15"},{"cvss_score":7.7,"headline":"Opencast stores passwords using outdated MD5 hash algorithm","id":"CVE-2020-5229","kev_date_added":null,"published":"2020-01-30"},{"cvss_score":7.7,"headline":"Opencast uses unsafe identifiers","id":"CVE-2020-5230","kev_date_added":null,"published":"2020-01-30"},{"cvss_score":7.6,"headline":"Opencast allows unauthorized public access via OAI-PMH","id":"CVE-2020-5228","kev_date_added":null,"published":"2020-01-30"},{"cvss_score":7.5,"headline":"Opencast publishes global system account credentials","id":"CVE-2018-16153","kev_date_added":null,"published":"2023-12-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-08","vendors":["opencast"]},"summary":"Users with write access can accidentally publish internal media due to a UI logic flaw in the editor, exposing sensitive content.","url":"https://insights.sbomify.com/CVE-2025-61906/"}