How severe is GHSA-6pwg-gg6j-5crm?

No CVSS score has been assigned to GHSA-6pwg-gg6j-5crm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6pwg-gg6j-5crm?

GHSA-6pwg-gg6j-5crm affects the following packages: org.igniterealtime.openfire:xmppserver (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6pwg-gg6j-5crm?

Update org.igniterealtime.openfire:xmppserver to 4.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6pwg-gg6j-5crm is resolved across your whole dependency graph.

How do I detect GHSA-6pwg-gg6j-5crm in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.igniterealtime.openfire:xmppserver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6pwg-gg6j-5crm 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.

Is GHSA-6pwg-gg6j-5crm actively exploited in the wild?

No public exploit code has been indexed for GHSA-6pwg-gg6j-5crm 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-6pwg-gg6j-5crm?

GHSA-6pwg-gg6j-5crm has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th 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.

What type of vulnerability is GHSA-6pwg-gg6j-5crm?

GHSA-6pwg-gg6j-5crm is classified as CWE-250 (CWE-250). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6pwg-gg6j-5crm published, and has it been updated?

GHSA-6pwg-gg6j-5crm was published on March 26, 2024 and was last updated on December 7, 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

Not in CISA KEV

Ignite Realtime Openfire privilege escalation vulnerabilityGHSA-6pwg-gg6j-5crm

Fix: igniterealtime/Openfire@d66bddd

GHSA-6pwg-gg6j-5crm is a CWE-250 vulnerability in org.igniterealtime.openfire:xmppserver. A fix is available for org.igniterealtime.openfire:xmppserver — see the affected versions and patch details below.

Also known asCVE-2024-25421

Published

Mar 26, 2024

Updated

Dec 7, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6pwg-gg6j-5crm.

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.igniterealtime.openfire:xmppserver

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

An issue in Ignite Realtime Openfire v.4.8.0 and before allows a remote attacker to escalate privileges via the ROOM_CACHE component.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.igniterealtime.openfire:xmppserver`	all versions	4.8.1`org.igniterealtime.openfire:xmppserver:4.8.1`

Affected Products

1 product · 1 configurations

Application

openfireigniterealtime

≤ 4.9.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.igniterealtime.openfire:xmppserver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.igniterealtime.openfire:xmppserver to 4.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6pwg-gg6j-5crm 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.

Frequently Asked Questions

An issue in Ignite Realtime Openfire v.4.8.0 and before allows a remote attacker to escalate privileges via the ROOM_CACHE component.

O3 Security · Impact-Aware SCA

Is GHSA-6pwg-gg6j-5crm in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works