# CVE-2025-23367: Org.wildfly.core:wildfly-server: wildfly improper rbac permission

> Users with read-only roles can suspend or resume the WildFly server due to missing authorization checks in management handlers.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jan 2025
- **Updated:** 17 Sep 2026
- **Also known as:** BIT-wildfly-2025-23367, CLSA-2026-1780447845, GHSA-qr6x-62gq-4ccp

## What is CVE-2025-23367?

CVE-2025-23367 is a medium-severity missing authorization vulnerability in Redhat Jboss Enterprise Application Platform, published on 30 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the Wildfly Server Role Based Access Control (RBAC) provider. When authorization to control management operations is secured using the Role Based Access Control provider, a user without the required privileges can suspend or resume the server. A user with a Monitor or Auditor role is supposed to have only read access permissions and should not be able to suspend the server. 
The vulnerability is caused by the Suspend and Resume handlers not performing authorization checks to validate whether the current user has the required permissions to proceed with the action.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-23367?

5 open source packages ship an affected version, including org.wildfly.core:wildfly-server and wildfly. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.wildfly.core:wildfly-server` | Maven | All versions | 27.0.1.Final |
| `org.wildfly.core:wildfly-server` | Maven | All versions | 27.0.1.Final |
| `org.wildfly.core:wildfly-server` | Maven | From 28.0.0.Beta1 | 28.0.0.Beta2 |
| `org.wildfly.core:wildfly-server` | Maven | From 28.0.0.Beta1 | 28.0.0.Beta2 |
| `wildfly` | Bitnami | All versions | 27.0.1, 31.0.1 |

Products: Redhat Jboss Enterprise Application Platform, Redhat Wildfly.

## How do I fix CVE-2025-23367?

Upgrade org.wildfly.core:wildfly-server to a fixed version for your release line: 27.0.1.Final or 28.0.0.Beta2.

## Is CVE-2025-23367 being exploited?

There is no known exploitation of CVE-2025-23367 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2017-12149](https://insights.sbomify.com/CVE-2017-12149/): Red Hat JBoss Application Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2010-1428](https://insights.sbomify.com/CVE-2010-1428/): Red Hat JBoss Information Disclosure (medium 5.9, exploited in the wild)
- [CVE-2010-0738](https://insights.sbomify.com/CVE-2010-0738/): Red Hat JBoss Authentication Bypass (low 3.7, exploited in the wild)
- [CVE-2016-3690](https://insights.sbomify.com/CVE-2016-3690/): Deserialization in n/a (critical 9.8)
- [CVE-2017-7504](https://insights.sbomify.com/CVE-2017-7504/): Deserialization in JBoss (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23367 and fix it if it is affected.

What it is: CVE-2025-23367 is a medium-severity missing authorization vulnerability in Redhat Jboss Enterprise Application Platform, published on 30 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23367 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.wildfly.core:wildfly-server (Maven): affected all versions; fixed in 27.0.1.Final
- org.wildfly.core:wildfly-server (Maven): affected all versions; fixed in 27.0.1.Final
- org.wildfly.core:wildfly-server (Maven): affected from 28.0.0.Beta1; fixed in 28.0.0.Beta2
- org.wildfly.core:wildfly-server (Maven): affected from 28.0.0.Beta1; fixed in 28.0.0.Beta2
- wildfly (Bitnami): affected all versions; fixed in 27.0.1, 31.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-23367/ (Markdown: https://insights.sbomify.com/CVE-2025-23367/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23367
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23367
- OSV: https://osv.dev/vulnerability/CVE-2025-23367

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-23367/
Summaries are generated and may contain mistakes; the official description above is the record.