Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2023-32315: Openfire administration console authentication bypass

Noroxi assessment

Priority: Now (action score 90/100)

  • CISA has confirmed exploitation in the wild (Aug 24, 2023). Remediation deadline for US federal agencies: Sep 14, 2023.
  • A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
  • Probability of exploitation in the next 30 days: 99.9% (FIRST EPSS); higher than 99.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: org.igniterealtime.openfire:xmppserver (Maven) 4.6.8, 4.7.5.

Patch today or shut off access. Upgrade to org.igniterealtime.openfire:xmppserver (Maven) 4.6.8, 4.7.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

Openfire is an XMPP server licensed under the Open Source Apache License. Openfire's administrative console, a web-based application, was found to be vulnerable to a path traversal attack via the setup environment. This permitted an unauthenticated user to use the unauthenticated Openfire Setup Environment in an already configured Openfire environment to access restricted pages in the Openfire Admin Console reserved for administrative users. This vulnerability affects all versions of Openfire that have been released since April 2015, starting with version 3.10.0. The problem has been patched in Openfire release 4.7.5 and 4.6.8, and further improvements will be included in the yet-to-be released first version on the 4.8 branch (which is expected to be version 4.8.0). Users are advised to upgrade. If an Openfire upgrade isn’t available for a specific release, or isn’t quickly actionable, users may see the linked github advisory (GHSA-gw42-f939-fhvm) for mitigation advice.

HighCVSS 7.5 · v3.1KEVWeaponized Fix available
Published
May 26, 2023
Updated
Jun 17, 2026
EPSS
99.9% · 99th percentile

Report tools

JSON

Action score

90

Now

Patch today or shut off access.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
30 / 30 · Listed
EPSS
30 / 30 · 99.9%

CISA SSVC decision

Exploitation
active
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · GitHub_M
8.6
1.1 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Aug 24, 2023. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Sep 14, 2023.

Get told when this record changes

  • In CISA KEV: exploitation in the wild confirmed
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-32315

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
igniterealtimeopenfire

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • igniterealtime openfire3.10.0 and later · before 4.6.8
  • igniterealtime openfire4.7.0 and later · before 4.7.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • igniterealtime Openfire

    • >= 3.10.0, < 4.6.8, >= 4.7.0, < 4.7.5affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.igniterealtime.openfire:xmppserverfrom 3.10.0 · before 4.6.84.6.8
Mavenorg.igniterealtime.openfire:xmppserverfrom 4.7.0 · before 4.7.54.7.5

Other highest-scoring records for the same primary product.

  • CVE-2008-6508Directory traversal vulnerability in the AuthCheck filter in the Admin Console in Openfire 3.6.0a and earlier allows remote attackers to byp
    55Plan
  • CVE-2019-18394A Server Side Request Forgery (SSRF) vulnerability in FaviconServlet.java in Ignite Realtime Openfire through 4.4.2 allows attackers to send
    49Plan
  • CVE-2015-6973Multiple cross-site request forgery (CSRF) vulnerabilities in Ignite Realtime Openfire 3.10.2 allow remote attackers to hijack the authentic
    46Plan

Published before and after this one in the same product

  • ← EarlierCVE-2020-35201Dec 12, 2020 · Ignite Realtime Openfire 4.6.0 has create-bookmark.jsp users Stored XSS.
    21Monitor
  • ← EarlierCVE-2020-35202Dec 12, 2020 · Ignite Realtime Openfire 4.6.0 has plugins/dbaccess/db-access.jsp sql Stored XSS.
    21Monitor
  • Later →CVE-2024-25420Mar 26, 2024 · An issue in Ignite Realtime Openfire before 4.8.1 allows a remote attacker to escalate privileges via the admin.authorizedJIDs system proper
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.igniterealtime.openfire:xmppserver4.6.8Package registry (OSV)
Maven:org.igniterealtime.openfire:xmppserver4.7.5Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×11

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Metasploit moduleexploit/multi/http/openfire_auth_bypass_rce_cve_2023_32315Openfire authentication bypass with RCE pluginexploit2023-05-26
Nuclei detection templateNuclei template CVE-2023-32315 —
Proof-of-concept repository on GitHubstars:02023-06-14
Proof-of-concept repository on GitHubstars:1432023-06-14
Proof-of-concept repository on GitHubstars:22023-06-15
Proof-of-concept repository on GitHubstars:612023-06-18
Proof-of-concept repository on GitHubstars:72023-07-02
Proof-of-concept repository on GitHubstars:52023-07-07
Proof-of-concept repository on GitHubstars:32023-08-31
Proof-of-concept repository on GitHubstars:02023-10-10
Proof-of-concept repository on GitHubstars:02025-01-30
Proof-of-concept repository on GitHubstars:12025-04-14

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Metasploit-1 d
  2. Published
  3. First PoC+18 d
  4. CISA KEV+89 d
  5. TodayOct 30, 2026+1253 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records