How severe is GHSA-w29m-fjp4-qhmq?

GHSA-w29m-fjp4-qhmq has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-w29m-fjp4-qhmq?

GHSA-w29m-fjp4-qhmq affects the following packages: org.opencastproject:base (Maven), org.opencastproject:base (Maven). Ecosystems affected: Maven.

How do I fix GHSA-w29m-fjp4-qhmq?

Update org.opencastproject:base to 7.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w29m-fjp4-qhmq is resolved across your whole dependency graph.

How do I detect GHSA-w29m-fjp4-qhmq in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencastproject:base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w29m-fjp4-qhmq if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-w29m-fjp4-qhmq actively exploited in the wild?

No public exploit code has been indexed for GHSA-w29m-fjp4-qhmq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-w29m-fjp4-qhmq?

GHSA-w29m-fjp4-qhmq has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 67th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-w29m-fjp4-qhmq?

GHSA-w29m-fjp4-qhmq is classified as CWE-99 (CWE-99), CWE-74 (CWE-74). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w29m-fjp4-qhmq published, and has it been updated?

GHSA-w29m-fjp4-qhmq was published on January 30, 2020 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

Unsafe Identifiers in OpencastGHSA-w29m-fjp4-qhmq

HIGHFix: opencast/opencast@bbb473f

GHSA-w29m-fjp4-qhmq is a high-severity (CVSS 7.7) CWE-99 vulnerability in org.opencastproject:base. A fix is available for org.opencastproject:base — see the affected versions and patch details below.

Also known asCVE-2020-5230

Published

Jan 30, 2020

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.opencastproject:base☕org.opencastproject:base

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Opencast allows almost arbitrary identifiers for media packages and elements to be used. This can be problematic for operation and security since such identifiers are sometimes used for file system operations which may lead to an attacker being able to escape working directories and write files to other locations.

In addition, Opencast's Id.toString(…) vs Id.compact(…) behavior, the latter trying to mitigate some of the file system problems, can cause errors due to identifier mismatch since an identifier may unintentionally change.

Patches

This issue is fixed in Opencast 7.6 and 8.1.

Workarounds

There is no workaround for this.

For more information

If you have any questions or comments about this advisory:

Open an issue in opencast/opencast
For security-relevant information, email us at [email protected]

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opencastproject:base`	all versions	7.6`org.opencastproject:base:7.6`
☕Maven	`org.opencastproject:base`	≥ 8.0&&< 8.1	8.1`org.opencastproject:base:8.1`

Affected Products

1 product · 2 configurations

Application

opencastapereo

< 7.6

1 version

8.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencastproject:base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opencastproject:base to 7.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w29m-fjp4-qhmq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Opencast allows almost arbitrary identifiers for media packages and elements to be used. This can be problematic for operation and security since such identifiers are sometimes used for file system operations which may lead to an attacker being able to escape working directories and write files to other locations. In addition, Opencast's Id.toString(…) vs Id.compact(…) behavior, the latter trying to mitigate some of the file system problems, can cause errors due to identifier mismatch since an identifier may unintentionally change. ### Patches This issue is fixed in Opencast 7.6