CVE-2025-23367 — wildfly-server
MEDIUMCVE-2025-23367 is a medium-severity (CVSS 6.5) CWE-284 vulnerability in org.wildfly.core:wildfly-server. A fix is available for org.wildfly.core:wildfly-server — see the affected versions and patch details below.
Org.wildfly.core:wildfly-server: wildfly improper rbac permission
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-23367.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-23367 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.wildfly.core:wildfly-server☕org.wildfly.core:wildfly-serverReal-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
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.
Impact
Standalone server (Domain mode is not affected) with use access control enabled with RBAC provider can be suspended or resumed by unauthorized users. When a server is suspended, the server will stop receiving user requests. The resume handle does the opposite; it will cause a suspended server to start accepting user requests.
Patches
Fixed in WildFly Core 27.0.1.Final
Workarounds
No workaround available
References
See also: https://issues.redhat.com/browse/WFCORE-7153
Acknowledgements
The WildFly project would like to thank Claudia Bartolini (TIM S.p.A), Marco Ventura (TIM S.p.A), and Massimiliano Brolli (TIM S.p.A) for reporting this issue. https://www.gruppotim.it/it/footer/red-team.html
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wildfly.core:wildfly-server | all versions | 27.0.1.Finalorg.wildfly.core:wildfly-server:27.0.1.Final |
| ☕Maven | org.wildfly.core:wildfly-server | ≥ 28.0.0.Beta1&&< 28.0.0.Beta2 | 28.0.0.Beta2org.wildfly.core:wildfly-server:28.0.0.Beta2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.core:wildfly-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wildfly.core:wildfly-server to 27.0.1.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-23367 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-23367 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-23367. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat has evaluated this issue and the attacker must be authenticated as a user that belongs to the "Monitor" or "Auditor" management groups. It requires previous privileges to jeopardize an environment.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss Enterprise Application Platform | org.wildfly.core/wildfly-server:15.0.45.Final-redhat-00001 | RHSA-2025:3467 |
| Red Hat JBoss Enterprise Application Platform 7.4.22 | org.wildfly.core/wildfly-server:15.0.42.Final-redhat-00001 | RHSA-2025:4552 |
| Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8 | eap7-netty-0:4.1.119-1.Final_redhat_00004.1.el8eap | RHSA-2025:3465 |
| Red Hat JBoss Enterprise Application Platform 8 | wildfly-server | RHSA-2025:3992 |
| Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8 | eap8-apache-commons-io-0:2.16.1-1.redhat_00001.1.el8eap | RHSA-2025:3989 |
| Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 9 | eap8-apache-commons-io-0:2.16.1-1.redhat_00001.1.el9eap | RHSA-2025:3990 |
Frequently Asked Questions
Is CVE-2025-23367 in your dependencies?
O3 Security finds CVE-2025-23367 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.