Skip to content
Fencer Intel
critical 9.8

CVE-2019-18394 in the critical feed json

Ignite Realtime Openfire vulnerable to Server Side Request Forgery

published 7y ago modified 4mo ago also GHSA-mfjw-x4q4-69p9 , EUVD-2022-4551

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
32.3%
EPSS 32.3% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • maven org.igniterealtime.openfire:parent 4.5.0-beta

Is CVE-2019-18394 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

32.30% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Ignite Realtime Openfire <=4.4.2 - Server-Side Request Forgery nuclei detection template

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.igniterealtime.openfire:parent
<4.5.0-beta
4.5.0-beta

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.