Unauthenticated Access Via OAI-PMH

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N

EPSS

• CVE-2020-5228: 0.98% estimated exploitation activity in the next 30 days; percentile 62.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Media publication via OAI-PMH allows unauthenticated public access to all media and metadata by default. OAI-PMH is part of the default workflow and is activated by default, requiring active user intervention of users to protect media. This leads to users unknowingly handing out public access to events without their knowledge. Patches The problem has been addressed in Opencast 7.6 and 8.1 where the OAI-PMH endpoint is configured to require users with ROLEADMIN by default. In addition to this, Opencast 9 removes the OAI-PMH publication from the default workflow, making the publication a conscious decision users have to make by updating their workflows. Workarounds In the organization security configuration (etc/security/mhdefaultorg.xml), change the roles required for accessing /oaipmh from ROLEANONYMOUS to ROLEADMIN. References - Public access configuration in the organization's security configuration For more information If you have any questions or comments about this…

Published by the source

30 Jan 2020, 21:22 UTC

Last modified by the source

9 Jan 2023, 05:01 UTC

Source last checked

26 Oct 2026, 15:52 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6f54-3qr9-pjgj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-5228

Advisory: Unauthenticated Access Via OAI-PMH
IDs: CVE-2020-5228, GHSA-6f54-3qr9-pjgj
Record: https://patchnext.com/advisories/cve-2020-5228 (revision 1, source checked 26 Oct 2026, 15:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.opencastproject:opencast-oaipmh-api 8.1, 7.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.opencastproject:opencast-oaipmh-api: affected < 7.6; >= 8.0, < 8.1; fixed in 8.1, 7.6

## Suggested inspection (read-only)
- Maven org.opencastproject:opencast-oaipmh-api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.opencastproject:opencast-oaipmh-api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6f54-3qr9-pjgj (GitHub-reviewed advisory GHSA-6f54-3qr9-pjgj lists affected ranges: Maven org.opencastproject:opencast-oaipmh-api >=0 =8.0 <8.1)

Commands are suggestions: review each one before running it.