GHSA-8c52-x9w7-vc95 — xwiki-pro-macros-ui
MEDIUMGHSA-8c52-x9w7-vc95 is a medium-severity (CVSS 6.8) CWE-862 vulnerability in com.xwiki.pro:xwiki-pro-macros-ui. A fix is available for com.xwiki.pro:xwiki-pro-macros-ui — see the affected versions and patch details below.
XWiki view file macro: User can view content of office file without view rights on the attachment
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-8c52-x9w7-vc95.
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-8c52-x9w7-vc95 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 377,238 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
com.xwiki.pro:xwiki-pro-macros-uiReal-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
Summary
A user with no view rights on a page may see the content of an office attachment displayed with the view file macro.
Details
If on a public page is displayed an office attachment from a restricted page, a user with no view rights on the restricted page can view the attachment content, no matter the display type used.
PoC
- Install and activate the Pro Macros application
- Create a page and limit the view rights for a test user
- Add an attachment to the restricted page
- Create a new public page
- Add the view file macro and select the attachment from the restricted page using any display type
- Login as the test user with restricted view rights
- The user will see the content despite having no view rights
Workarounds
None
Impact
Private data can be leaked if a user knows the reference to an attachment and has edit rights on a page.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.xwiki.pro:xwiki-pro-macros-ui | all versions | 1.27.0com.xwiki.pro:xwiki-pro-macros-ui:1.27.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.xwiki.pro:xwiki-pro-macros-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.xwiki.pro:xwiki-pro-macros-ui to 1.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c52-x9w7-vc95 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8c52-x9w7-vc95 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8c52-x9w7-vc95. 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-8c52-x9w7-vc95 in your dependencies?
O3 Security finds GHSA-8c52-x9w7-vc95 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.