How severe is GHSA-q52r-g8jf-wv3x?

GHSA-q52r-g8jf-wv3x has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-q52r-g8jf-wv3x?

GHSA-q52r-g8jf-wv3x affects the following packages: org.apache.openmeetings:openmeetings-parent (Maven). Ecosystems affected: Maven.

How do I fix GHSA-q52r-g8jf-wv3x?

Update org.apache.openmeetings:openmeetings-parent to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q52r-g8jf-wv3x is resolved across your whole dependency graph.

How do I detect GHSA-q52r-g8jf-wv3x in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.openmeetings:openmeetings-parent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q52r-g8jf-wv3x 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.

How does O3 Security protect against GHSA-q52r-g8jf-wv3x?

O3 pinpoints whether GHSA-q52r-g8jf-wv3x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q52r-g8jf-wv3x actively exploited in the wild?

No public exploit code has been indexed for GHSA-q52r-g8jf-wv3x 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-q52r-g8jf-wv3x?

GHSA-q52r-g8jf-wv3x has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 76th 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.

When was GHSA-q52r-g8jf-wv3x published, and has it been updated?

GHSA-q52r-g8jf-wv3x was published on May 13, 2022 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-q52r-g8jf-wv3x

HIGH

Apache OpenMeetings allows flash content to be loaded from untrusted domains

Also known asCVE-2017-7680

Published

May 13, 2022

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk76th percentile+0.55%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕org.apache.openmeetings:openmeetings-parent

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

Apache OpenMeetings 1.0.0 has an overly permissive crossdomain.xml file. This allows for flash content to be loaded from untrusted domains.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.openmeetings:openmeetings-parent`	≥ 1.0.0&&< 3.3.0	3.3.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.apache.openmeetings:openmeetings-parent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.openmeetings:openmeetings-parent to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q52r-g8jf-wv3x 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.
How O3 protects you
O3 pinpoints whether GHSA-q52r-g8jf-wv3x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q52r-g8jf-wv3x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Apache OpenMeetings 1.0.0 has an overly permissive `crossdomain.xml` file. This allows for flash content to be loaded from untrusted domains.

O3 Security · Impact-Aware SCA

Is GHSA-q52r-g8jf-wv3x in your dependencies?

O3 detects GHSA-q52r-g8jf-wv3x across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works