# WildFly improper RBAC permission Advisory record · `GHSA-qr6x-62gq-4ccp` - **Identifiers:** `GHSA-qr6x-62gq-4ccp` · `BIT-wildfly-2025-23367` · `CVE-2025-23367` - **State:** Confirmed - **Severity:** CVSS 6.5 Medium - **Critical:** No - **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) - **Published:** 31 Jan 2025 - **Updated:** 8 Dec 2025 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 31 Jan 2025, 17:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.wildfly.core:wildfly-server` (Maven): affected `<27.0.1.Final || >=28.0.0.Beta1, <28.0.0.Beta2`; fixed in `27.0.1.Final`, `28.0.0.Beta2` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > WildFly Core's wildfly-server (org.wildfly.core:wildfly-server) versions before 27.0.1.Final and versions from 28.0.0.Beta1 up to but not including 28.0.0.Beta2 are affected. A user without the required privileges, such as one holding only a Monitor or Auditor role, can suspend or resume a standalone server that uses the Role Based Access Control provider, because the suspend and resume handlers skip authorization checks. Upgrade to 27.0.1.Final or 28.0.0.Beta2. No workaround is available. Written 7 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from CNA (redhat) - **CISA KEV:** Not listed. - **EPSS:** 0.0077, the 56th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 30 Jan 2025, 14:30 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-23367) - 30 Jan 2025, 15:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-23367) - 31 Oct 2026, 15:09 UTC: First seen by agentprime - 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qr6x-62gq-4ccp) ## Sources - [GitHub Advisory Database: GHSA-qr6x-62gq-4ccp](https://github.com/advisories/GHSA-qr6x-62gq-4ccp) - [OSV: GHSA-qr6x-62gq-4ccp](https://osv.dev/vulnerability/GHSA-qr6x-62gq-4ccp) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .