GHSA-mfjw-x4q4-69p9 is a critical-severity (CVSS 9.8) Server-Side Request Forgery (SSRF) vulnerability in org.igniterealtime.openfire:parent. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.igniterealtime.openfire:parent — see the affected versions and patch details below.
Ignite Realtime Openfire vulnerable to Server Side Request Forgery
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-mfjw-x4q4-69p9 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,166 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.igniterealtime.openfire:parentReal-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
A Server Side Request Forgery (SSRF) vulnerability in FaviconServlet.java in Ignite Realtime Openfire through 4.4.2 allows attackers to send arbitrary HTTP GET requests. The issue is fixed in version 4.5.0-beta.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.igniterealtime.openfire:parent | all versions | 4.5.0-betaorg.igniterealtime.openfire:parent:4.5.0-beta |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.igniterealtime.openfire:parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.igniterealtime.openfire:parent to 4.5.0-beta or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mfjw-x4q4-69p9 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-mfjw-x4q4-69p9 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mfjw-x4q4-69p9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-mfjw-x4q4-69p9
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-mfjw-x4q4-69p9 -u https://target- Template
- Ignite Realtime Openfire <=4.4.2 - Server-Side Request Forgery
- Severity
- critical
- Impact
- An attacker can exploit this vulnerability to send crafted requests to internal resources, leading to unauthorized access or information disclosure.
- Remediation
- Upgrade to the latest version of Ignite Realtime Openfire (>=4.4.3) to fix this vulnerability.
Template by ProjectDiscovery nuclei-templates (pdteam), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-mfjw-x4q4-69p9 in your dependencies?
O3 Security finds GHSA-mfjw-x4q4-69p9 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.