CVE-2023-32315

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.

CVSS: 8.6Highscored by the publisher (CNA)
Exploited in the wild: Yes, in CISA KEV since 24 Aug 2023CISA deadline for US federal agencies: 14 Sept 2023public exploit code
EPSS: > 99.9%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 26 May 2023analysed here 12 Nov 2026

Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface: Server-side
Exploitable: At runtime
Attack vector: network
Weakness: CWE-22 Path Traversal
Can a WAF block it?: Yes. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Product	Affected versions	Vendor says fixed in
igniterealtime Openfire	>= 3.10.0 and < 4.6.8>= 4.7.0 and < 4.7.5Vendor says fixed in: not stated	Not stated by the vendor

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

igniterealtime:openfire

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Yes. The attack uses a path traversal in the web-based setup environment's HTTP requests to access restricted admin pages. Such traversal sequences can be detected by a WAF, but may overlap with some legitimate requests, making filtering only partly reliable. A custom WAF rule can filter path traversal sequences in URLs or parameters of the setup environment, but attackers can vary the request. No tracked WAF vendor has published a rule for this CVE yet.

What a custom rule would match: path traversal sequences in URLs or parameters of the setup environment

Also consider: patch · custom WAF rule · canonical path validation

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 24 Aug 2023.
CISA due date: 14 Sept 2023, the remediation deadline for US federal agencies
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploit code: Yes: 1 Metasploit module · 12 GitHub proofs of concept · 1 Nuclei template
CISA SSVC: exploitation active, automatable yes, technical impact totalAssessed by CISA 4 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

and 8 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

26 May 2023Published
14 Jun 2023First public exploit or proof of concept18 days later
24 Aug 2023Added to CISA KEV (exploited in the wild)71 days (about 2 months) later
14 Sept 2023CISA remediation due date (US federal agencies)21 days later
4 Feb 2025CISA SSVC assessment: exploitation active510 days (about 1 year) later
21 Oct 2025CVE record last updated259 days (about 9 months) later
12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

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

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	LowLimited modification possible.	Limited modification possible.
Availability	LowPartial degradation possible.	Partial degradation possible.

Common questions

Is CVE-2023-32315 being exploited?

Yes. CVE-2023-32315 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2023-32315?

CVE-2023-32315 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-32315?

Yes. A fix has been recorded for CVE-2023-32315. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2023-32315 affect?

CVE-2023-32315 affects igniterealtime:openfire. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

3 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Metasploit Framework: exploit and scanner modules
Nuclei templates: detection templates
PoC-in-GitHub: GitHub repositories that claim a proof of concept
OSV: advisory aliases and downstream package versions

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.