How severe is CVE-2009-1595?

No CVSS score has been assigned to CVE-2009-1595 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2009-1595?

CVE-2009-1595 affects the following packages: org.igniterealtime.openfire:parent (Maven). Ecosystems affected: Maven.

How do I fix CVE-2009-1595?

Update org.igniterealtime.openfire:parent to 3.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-1595 is resolved across your whole dependency graph.

How do I detect CVE-2009-1595 in my Maven dependencies?

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.

How do I mitigate CVE-2009-1595 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2009-1595 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2009-1595, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2009-1595?

CVE-2009-1595 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th 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 CVE-2009-1595?

CVE-2009-1595 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2009-1595 published, and has it been updated?

CVE-2009-1595 was published on May 2, 2022 and was last updated on January 23, 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

CVE-2009-1595 — parent

Fix: igniterealtime/Openfire@97e1f08

CVE-2009-1595 is a Improper Authentication vulnerability in org.igniterealtime.openfire:parent. 4 public exploit or proof-of-concept references are indexed, 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 Allows Users to Change Passwords of Arbitrary Accounts

Published

May 2, 2022

Updated

Jan 23, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% 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:parent

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

The jabber:iq:auth implementation in IQAuthHandler.java in Ignite Realtime Openfire before 3.6.4 allows remote authenticated users to change the passwords of arbitrary accounts via a modified username element in a passwd_change action.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.igniterealtime.openfire:parent`	all versions	3.6.4`org.igniterealtime.openfire:parent:3.6.4`

Affected Products

1 product · 29 configurations

Application

openfireigniterealtime

≤ 3.6.3

28 versions

2.6.02.6.12.6.23.0.03.0.13.1.03.1.13.2.03.2.13.2.23.2.33.2.4

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-32967remotemultiple✓ Verified

Openfire 3.x - jabber:iq:auth 'passwd_change' Remote Password Change

by Daryl Herzmann · May 4, 2009

Exploit-DB Source

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:parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.igniterealtime.openfire:parent to 3.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-1595 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

The `jabber:iq:auth` implementation in `IQAuthHandler.java` in Ignite Realtime Openfire before 3.6.4 allows remote authenticated users to change the passwords of arbitrary accounts via a modified username element in a `passwd_change` action.