GHSA-x2xm-p6vq-482g is a medium-severity (CVSS 5) CWE-284 vulnerability in oro/calendar-bundle. A fix is available for oro/calendar-bundle — see the affected versions and patch details below.
OroCalendarBundle has incorrect system calendar events visibility
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-x2xm-p6vq-482g plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
oro/calendar-bundle🐘oro/calendar-bundle🐘oro/calendar-bundleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
OroPlatform is a package that assist system and user calendar management. Back-office users can access information from any system calendar event, bypassing ACL security restrictions due to insufficient security checks.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | oro/calendar-bundle | ≥ 4.2.0 | No fix |
| 🐘Packagist | oro/calendar-bundle | ≥ 5.0.0&&< 5.0.7 | 5.0.7composer require oro/calendar-bundle:^5.0.7 |
| 🐘Packagist | oro/calendar-bundle | ≥ 5.1.0&&< 5.1.1 | 5.1.1composer require oro/calendar-bundle:^5.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oro/calendar-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of oro/calendar-bundle has shipped for GHSA-x2xm-p6vq-482g yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-x2xm-p6vq-482g can be triaged on real exposure rather than presence alone.
Tailored to GHSA-x2xm-p6vq-482g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-x2xm-p6vq-482g in your dependencies?
O3 Security finds GHSA-x2xm-p6vq-482g across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.